When I create a flight plan everything in the Flight Plan Elevation Profile is at cruise altitude (including departure and destination runways.

Obviously these flight plans don't work well in X-Plane

Use it all the time. Never had an issue, but youve given very little info.

I generally disregard the flight plan's elevation profile as I find it not really helpful.

@john9002 you gave zero information about the issue and I already answered your email. Obviously at least a screenshot or the flight plan is needed to diagnose any issue.

But first have a look at the flight plan table. Below the table is a red error message that gives you hints why the profile calculation failed. Hover the mouse over the message or click it to see details.

You can use the flight plans in X-Plane even with a failed profile calculation, BTW.

Alex

Tell me what informatin would help.

The problem is that the when I use the flight plan in X-plane (Toliss A320), the FMA shows 'TOC Reached' all the time, even directly after takeoff. The NAV ignores the flight profileand climbs directly to the cruising altitude. All waypoints are circled in orange (unattainable).

I have some screenshots of the proble, but don't see a way to upload them here.

I have some screenshots of the proble, but don't see a way to upload them here.

You need to use an image hosting service where they are visible to all including the UK. See below.

OK, I think I've solved it. If, in a sort hop for example, you set a cruise altitude higher than can be attained, LittleNavMap sets all items in the Flight Plan Elevation Profile to the cruise altitude. This includes departure and arrival airports (LGKK and EGBB at 25,000 ft!) and all intermediate waypoints nav aids etc at the cruise altitude.
This seems odd behaviour.

Looks like you have not inserted the flight plan. You need to click on the right bot key

OK, I think I've solved it. If, in a sort hop for example, you set a cruise altitude higher than can be attained, LittleNavMap sets all items in the Flight Plan Elevation Profile to the cruise altitude. This includes departure and arrival airports (LGKK and EGBB at 25,000 ft!) and all intermediate waypoints nav aids etc at the cruise altitude.
This seems odd behaviour.

What do you expect if you put in wrong values like a too high cruise altitude? The profile simply cannot be calculated and shows a red error message below the flight plan table (see screenshot above). Nothing odd at all.🤷‍♂️

Alex