MSFS Products

Worked for me as well. Actually, there is only one line of code that messes up the compass. Fix it and the compass works. ``` <Code>(L:UPPER_compass, number) 10 *</Code> to be replaced with <Code>(L:UPPER_compass, number)</Code> The only difference that I can see is the [ **10*** ]. If that were to be deleted, you should be good. I do suggest that you back up the original file though, just in case.

Aah, got it. For anyone else looking for this answer, just download and run the installer for the new version, it will update the existing plane. No need to uninstall. G.

@copper That works at some airports but not at others. I think it only works if there's refuelling trigger set for the fuelling station.

It's on sale from JF now as it happens. https://www.justflight.com/product/aerosoft-aircraft-crj-550-700

@Perrin Let us know if this remains a problem, I have heard one other user who had the same issue. I don't think it's the aircraft itself that's causing it as MSFS has been a bit odd since the last major update, but if you find a solution it would be good to let us know

@copper Thanks for the reply. Very informative!

You are best off asking this question on the dedicted AH2 support forum: ah2.justflight.com

@DC1973 Hi again and thanks again for the quick response. Unfortunately the coordinates displayed on the F-15E aren't even close to actual coordinates. The readout on the ground at KNQX at start up was 0.4289 and -1.4260. I converted those to degrees and minutes, which are N0 25' 44.04" W1 25' 33.60". The coordinates for Key West Naval Air Station per Jeppeson are N19 54.4 and W 075 12.4 I've been flying FSX for years and the coordinates for any aircraft I flew were spot on real world coordinates. It appears that the MSFS coordinates are off by a lot--or else I am! EDIT: Sorry, I had the F-15E position readout at Key West correct and the conversion to N 0 25' 4404" W 1 25' 33.60" correct but I erroneously showed the Guantanamo NAS coordinates instead of the Key West NAS correct coordinates of N24 34.5 W081 41.2 Upon arrival at MUGM the F-15E position readout was 0.3475, -1 3127, which converts to N 0 20' 50.99" W1 18' 45.72. Per Jeppesen the correct coordinates for Gitmo NAS are N19 54.4' W075 12.4'. Sorry for the confusion.

@anthony96 It's in the works for this summer, but I'm awaiting proper supersonic support from MSFS as it's important for the autopilot to work at those airspeeds ( it doesn't very well at the moment beyond supersonic ).

@Stwutter The bind you are looking for is "Spoiler". Best set up with an axis instead of a buttons, so "Spoiler Axis" is best. You have more control that way.

Got it. Thank you

@Derek Ok thanks

@Smykel Ensure you set the Flight Model option to 'MODERN' in the MSFS Options (OPTIONS > GENERAL > FLIGHT MODEL). That will sort this issue for you.

Thanks much for the quick feedback. I've since discovered your thread on the MSFS forums as well. Thanks for having the open dialog with the player community. I did purposely wait until 1.0.1 prior to purchasing and these efforts have turned the tide on this aircraft. Take pride in knowing the sonic boom scares me every time.

@DC1973 @DC1973 said in F-15 persistence.cfg file?: @Hotzoner Hi, there doesn't seem to be a way at present. What you could do is create several different flightmodel.cfg files and enter the required weights into each, depending on what load-out you want, and then just swap the files for whichever one you need each time you fly. That's about the only way I can think of at the moment, hope this helps Understood, I will give that a try. Thanks for the suggestion