as of now it is my understanding that I can only force Simbrief to an altitde for the whole flight or automatically.
Given the Y/Z flight plan options planning with optimal level is unlikely as I might puck up (or am forced to) much later than optimal or cancel much sooner, both requiring a lower level and higher fuel burn.
PFPX had these options and especially the lower window, where you could set speeds, altitured, step climbs or delay holding time in minutes for enroute STAY options was really cool!
It does not have to be like this but it would be cool to have greater control about altitude and the option for enroute STAY (including them correctly in the flight plan would be even cooler 
)
It’s possible that similar options will be added down the road, though not in the near future.
However for now, you can already force altitude changes mid-route by entering them directly into your route string. For example:
JFK J1 ALB/F330 DCT SYR
This will force an altitude change to FL330 after ALB. Speeds or holding time cannot be added at the moment though.
Best regards,
if that works that’s would solve the issue (except maybe for stay but that’s a niche problem). However, it does not work for me 
A321 LOWW EDDS with the following inputted route
LUGE1C LUGEM/N0426F240 DCT KIRDI DCT EBEDA/N0426F300 L173 MAH/N0426F240 L173 DODIL T127 TEKSI TEKS1W
and I got this
LOWW/29 N0465F340 LUGE1C LUGEM DCT KIRDI/N0452F300 DCT EBEDA L173 MAH/N0426F240 L173 DODIL T127 TEKSI TEKS1W EDDS/25
and with less restrictions
If you want to force FL240 as the initial altitude, that needs to be set using the “Altitude” option. Then subsequent altitude changes can be set in the route.
By setting the following route (without the “Altitude” option set):
LUGE1C LUGEM/N0426F240 DCT KIRDI DCT EBEDA/N0426F300 L173 MAH/N0426F240 L173 DODIL T127 TEKSI TEKS1W
You are basically telling SimBrief to use default altitudes until LUGEM, then FL240 afterwards. But since the default initial altitude for this route is around FL340, the LUGEM step you entered occurs during the climb phase and is ignored.
The correct way to set this altitude profile would be to either enter “24000” in the “Altitude” option, then enter subsequent steps in the route. Or, you can enter an initial altitude in ICAO format at the beginning of the route, like so:
N0426F240 LUGE1C LUGEM DCT KIRDI DCT EBEDA/N0426F300 L173 MAH/N0426F240 L173 DODIL T127 TEKSI TEKS1W
Using the “Altitude” option for the initial altitude is preferred though, it’s a bit better supported by the system.
Best regards,
ok thank you, that is good to know! Knoowing this I can trust it again
