For LEBB-EGLL, route
MAPAX N867 NENEM YURZI ERIGA REVTU UP88 VASUX
with constraint
20000/YURZI/35000/REVTU/34000
produces
N0454F190 MAPAX N867 NENEM/N0454F200 DCT YURZI DCT ERIGA/N0454F350 DCT REVTU/N0454F330 UP88 VASUX
instead of
N0454F190 MAPAX N867 NENEM/N0454F200 DCT YURZI/N0454F350 DCT ERIGA DCT REVTU/N0454F330 UP88 VASUX
which makes the route fail IFPS
This is actually LEBB → EGKK and not EGLL 
This bug only affects the “Performance and tools” section; the restrictions work correctly when actually generating a flight plan/briefing package.
A bit annoying nevertheless.
Also, the restriction preventing climb before YURZI (LF3512: LFRRNIU/LFRRGIU/LFRRAIU not available for traffic arriving VIA LFRRNSF/LFRRGS/LFRRAS AND-THEN VIA LFRRNIU/LFRRGIU/LFRRAIU) does not require you to stay as low as FL200, I can get it to validate all the way up to FL340 starting from NENEM (must remain at FL200 until NENEM because of LELF1018):
Seems to hold true for most aircraft types I have tried.
So you could use:
20000/NENEM/34000/YURZI/35000/REVTU/34000
Regards,
Tim
Hi, France uses a north/south semi-circular rule so the max altitude would rather be 20000/NENEM/34000
The FL340 limitation is due to 2 RAD rules:
- EGLF1045 that reflect the IRL LoA LFRR<>EGTT (FL340@REVTU)
- LF3512 a summer flight capping that forbid south UK arrival to enter upper Brest sector (NIU, GIU and AIU, which bottom is FL355, but since you are a northbound traffic FL340 is the maximum usable level
But if you fly on a network, you can always ask ATC if you can climb to a higher level
Hope that answer you questions
Yep, that is arguably more correct. For the sake of simplicity, I personally prefer to enter the maximum altitudes that allow the route to pass online validation and let Simbrief handle the choice of odd or even.
So even when entering 20000/NENEM/34000/YURZI/35000/REVTU/34000 as the restriction, the Simbrief generated plan will actually have something like F200 SID MAPAX N867 NENEM/F340 YURZI ERIGA REVTU UP88 VASUX STAR anyway.
Regards,
Tim