December 15, 201510 yr For some reason, FS2Crew suddenly only uses the standard U.S. 18000 ft/FL180 as the transition altitude/transition level, regardless of my input in the FMC. Also for the minimums it started to use a default value, instead of what I fill in on the approach brief page of the settings window. What could cause this and how can I solve this problem? EDIT: The above was for yesterday's flight. On today's flight I found out that FS2Crew used 7000 ft instead of 2000 ft for the FAF, FL100 instead of FL030 for the transition level and > 500 ft instead of 187 ft for the minimums. I am 100% positive I filled everything in correctly in both the FMC and the FS2Crew settings. It never did this before. Very strange... Edited December 15, 201510 yr by ApacheHunter With kind regards, Kevin Schepers
December 16, 201510 yr Commercial Member The problem is that your FS units of measurement for altitude are set to Meters. You must have somehow reset your FS setting. They need to be set to "Feet". B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
December 16, 201510 yr Author That's right, I recently changed that setting. I didn't know it would affect FS2Crew. I'm setting the units of measurement back to feet. Thanks for your help!! With kind regards, Kevin Schepers
December 16, 201510 yr Setting FSX to metric altitude breaks all sorts of addons, definitely leave it at as feet! ckyliu, proud supporter of ViaIntercity.com. i5 12400F, 32GB, RTX4070, more in "About me" on my profile.
Create an account or sign in to comment