thanks for the help.
The VOR1 OBS is not working also with the GPS100 and restarted the sim multiple times.
As for the 530, I updated to the latest version this morning.
Still could not make it work. I’ll try to revert to the previous version from backup.
There is a hidden clickspot below the autopilot coupler knob to switch from GPS to VLOC (click on the label saying “NAV1 - OFF - NAV2” vertically). Try that one. Or switch to GNS530 and click on the CDI button.
I have no issues with the GNS530 to turn on, have also the mod installed. Sometimes it doesn’t work but that is always solved with a restart (ESC → Restart). I doubt that a reinstall will help. Maybe try without the GNS530 mod, not sure where you downloaded it today, the most recent version is 1.0.29.
Do you have state saving enabled in the EFB? If so, try turning it off. Also turn off “Maintenance → Enabled” in the EFB.
Further try setting the aircraft to State “Ready for Takeoff” to see if that makes the GNS to turn on.
530 doesn’t work.
With or without mod.
That’s wrong if you state it like that. See my screenshots above, it worked fine for me.
Here’s from cold&dark, just turning BAT+ALT on and GNS530 is booting.
I have the mod installed.
They fixed the issues in VR with the doubled mouse and the inability to zoom the view in VR. They both work now. Planes I bought from a certain other company back when they were the only option still haven’t fixed this. It looks fantastic in VR IMHO!
What fixed the trick was that, the GNS430 came on turning the “automatic squelch ON” knob and I was able to switch from GPS → VLOC and that fixed the VOR1 OBS now working with NAV1 radio.
The GNS530 doesn’t come on turning the same knob and stays off, dead and gone 
(not a big deal as I prefer the GPS100 with the PA28)
The GNS mod is updated to 1.0.29 and works perfectly with other airplanes (mooney, seminole, etc) so, if there is any problem it seems to be on the PA28R side which was working fine until this morning before the update.
The whiskey compass remains broken though.
thanks for your help, somehow I managed to get it fixed.
ps: does the GPS100 support coupling with the autopilot? I can’t remember.
Ok, if I choose, 530 then start the plane and save the state… I restart the flight, and 530 is on.
If I change to 430 during the flight, 530 die forever.
I’ll wait for a patch (JF forum)
Ah, I got the issue as well now: The GNS530 is working if you boot it with it already enabled. If you cycle through the GNS versions in the EFB, the GNS530 is off and stays off while the GNS430 is on.
You don’t need to have state saving on, it will remember your GNS choice anyhow. So as long as you don’t switch it in the EFB you can use it on future flights without issues.
looking forward to buying this once it is in the marketplace.
Not necessary. The new installer automatically uninstalls the previous version in one go. 
EDIT: maybe you gotta uninstall after all, to be sure. Look at Coppersens’ entry below.
I thought so, too, but JF Staff said they recommend an uninstall first:
I did no uninstall since I rely on having a properly implemented installer which, if needed, uninstalls the previous version. Would be bad if it didn’t.
Thanks, good to know. If issues arise will uninstall and reinstall.
I have a question about repaints for the Arrow III. Is it possible to make standalone repaints that you can just drop in the Community folder and that just work, as is the case with other aircraft?
I’m asking, because I’m pretty sure that I have set up my repaint folder correctly, with a layout.json file that only includes the changed files of my repaint (and without a comma at the last brace), a manifest.json file and an abridged version of the aircraft.cfg that only contains this:
[VERSION]
major = 1
minor = 0
[VARIATION]
base_container = "…\JF_PA28_Arrow"
and then the aircraft information in it’s own [FLTSIM.0] section.
But every time I drop that repaint folder into the Community folder the Piper Arrow doesn’t show up in the aircraft selection screen at all. So far the only way to make the repaint work properly seems to be integrating it into the actual Just Flight aircraft folder, ammending the aircraft.cfg with a [FLTSIM.12] entry and making new entries for the repaint files in the layout.json file. That way it works fine, as you can see here:
)
Any tips/pointers what could be the issue? That would be much appreciated. I just need to know if it’s something special about the Just Flight Piper Arrow that prevents it from working or if there is something general I might be doing wrong.
p.s.: stencils off in the repaint PSD right? Otherwise I see double with the new decals.
Check out this download:
It contains a ready folder structure to start with. Also you can download other repaints and take them as an example for your repaint.
Thanks, I will check that out!
Anybody else lose the whiskey compass (frozen) with the new update? Weird…
According to a post from JF Staff in their forums, it never worked. I guess they are aware of it, but better open a ticket.
I thought it was working… maybe I’m going nuts… lol…I did a fresh uninstall and reinstall and it’s still frozen. Also the GNS 530 was dead on boot up. Went to developer mode as a work around… switched aircraft to a 172 classic for a moment and then switched back to the Arrow and the 530 was magically working again. Weird again! What a great little plane, cheers all.
They did clean the windows quite a bit, didn’t they? Looks like I can keep the dirty cockpit textures now. Thanks! 
