ISSUE DESCRIPTION
Description of the issue:
I had a flight over the alps in career. EFB was set to FL39.99 on default (why that odd number? and is there anywhere in the world where 4000ft would already be above TA? 
), which is obviously too low to go over the mountains, but i left it as is. ATC gave me IFR clearance with an initial altitude of 9000ft (I was starting just outside the mountains). While on my way to the first waypoint, ATC requested me to climb to 11000ft as I was nearing the mountains. After reaching cruising altitude, I judged by synthetic vision that 11000ft was still too low (I was well within the cloud layer, so better be safe than sorry), so I requested an altitude change by 2000ft. Now the 1 million credits question: Which new altitude did my pilot request?
A) 9000ft (because I mixed up climb and descent)
B) 11000ft (because why not, it’s cozy here not knowing if there is a mountain top in your path)
C) 13000ft (because that’s what math would get)
So my pilot obviously decided that the right answer was B. After a WTF moment and another request for additional 2000ft (which then got me my desired 13000ft), I think I understand why a wrong altitude was requested: very likely the 2000ft where added to my initial clearance of 9000ft instead of the later cleared 11000ft. As I don’t know what my flight plan really contained as cruising altitude, I can only guess that that where the initial 9000ft. ATC later required me to climb even further for terrain clearance, but that was not taken into account for the altitude change request. So there are two problems that should be solved:
- Always use your actual cleared altitude for calculating change requests.
- Don’t give the altitude difference as options, but show the new altitude in the ATC dialog.
As I later found out by putting the flight plan into Little Navmap, my intuition was right: There is one mountain top going over 10000ft (estimation is 10500ft) in my flight path, so 11000ft would have gotten me dangerously low and Little Navmap gave me 12000 MSA. Why ATC deemed that altitude high enough for terrain clearance would have to be a topic for another bug report…
And that I later had to abort my flight because the promised VMC at destination where nowhere to be seen (1000ft AGL (using only synthetic vision to descend into a valley) I was still within the cloud layer) is just career being career 
If applicable, which aircraft is experiencing this issue:
Vision Jet G2
[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Yes
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
On that one flight, but I can remember similar things happening before
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
- Make an IFR flight plan from LSMD with RWY29S departure via GODRA and ESOKO to LFLJ at FL39.99
- Receive ATC clearance for 9000ft
- Receive new altitude of 11000ft
- Request change to higher altitude by 2000ft (or maybe every other value, I don’t think it will matter)
YOUR SETTINGS
If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
What peripherals are you using, if relevant:
[PC Only] Are you using Developer Mode or have you made any changes to it?
No
[PC, MSFS 2020 Only] Are you using DX11 or DX12?
[PC Only] What GPU (Graphics Card) do you use?
[PC Only] What other relevant PC specs can you share?
MEDIA
Please add a screenshot or video of the issue occurring.
[END OF FIRST USER REPORT]
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
•
Provide extra information to complete the original description of the issue:
•
If relevant, provide additional screenshots/video:
•
I reserve my own votes for the bugs that really hinder gameplay (until they are solved) and not on the small stuff…