MSFS Products

Have you tried contacting JF through the support function?

https://community.justflight.com/topic/1797/product-support

@nasaspaceboy yes, we are...

Reinstalled the Arrow and now it works! My first Add-on in msfs 2020 and Glad to get it running.
Thanks guys for the help.

@Rich Thanks Rich, I've raised a ticket.

The default cockpit lighting has always been dimmable, that's not what the mod is about.
It introduces a new luminosity mask that overrides the default.
No reason this mod wouldn't work after an update. If there is an incompatibility, the mod creator would just need to update the mod.
JustFlight will for sure not simply incorporate other's work.

I myself created the "lights mod" that changes the external lights and also will keep it updated to have it compatible with the most recent version of the addon.
You might want to have a look at it:
https://flightsim.to/file/10201/piper-pa28r-arrow-iii-justflight-lights-mod

EDIT: I just tested the panel lights mod, unfortunately it breaks my exterior lights mod. So currently it's either the one or the other to be used :(

hello and thanks to all for this info Actually I changed the GPS and put the 430 ( because the 530 does not work at all!!..) and I switched to NAV , then I came back on the GPS 100 and it worked I do not find it quite normal but for the moment I would be satisfied Thanks again

did this too. With the old version the Gps worked well.

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.