March 2, 20215 yr Recently purchased the 530 over the weekend for FSX, I've been using both the 430 for several years with no issues, and the 650 since it came out. I did know that Norton will initially block or quarantine a number of files associated with these legacy Garmin units, but I attempted to install with everything turned off, and also made exceptions in the anti-virus associated with folders the files are located. Still no luck getting it to work, though the other units still continue to work after several attempts to reinstall the software. But the 530 does show up within the Configuration tool, along with the 430 as usual. I'm wondering if certain critical 530 files are still missing or if Norton is still blocking/restricting them. I would appreciate any assistance.
March 2, 20215 yr Did you reinstall from the Flight1 wrapper? This sounds like it might be a licensing issue. David Porrett
March 2, 20215 yr Author Yep, multiple times. I suspect it does have to do with licensing as that's the common cause for this problem, but I'm not sure how else to get around it other than what I've done. Edited March 2, 20215 yr by AZMRA
March 3, 20215 yr 9 hours ago, AZMRA said: Recently purchased the 530 over the weekend for FSX, Which GNS did you purchase exactly? We're only selling and supporting the GNS V2, the GNS legacy e-commerce installer is left available for existing customers wanting to reinstall only?!
March 3, 20215 yr Author 8 hours ago, RXP said: Which GNS did you purchase exactly? We're only selling and supporting the GNS V2, the GNS legacy e-commerce installer is left available for existing customers wanting to reinstall only?! The 530. I have no idea which version, though I'm assuming V.2 given what you just said. I just purchased it on Saturday.
March 3, 20215 yr If you get a pink gauge it means you've loaded the legacy version (check your panel.cfg) and in addition it was not authenticated on your system (check reinstalling with e-commerce installer). You should know which one you've purchased looking at the product name on your receipt...
March 3, 20215 yr Author 23 minutes ago, RXP said: If you get a pink gauge it means you've loaded the legacy version (check your panel.cfg) and in addition it was not authenticated on your system (check reinstalling with e-commerce installer). You should know which one you've purchased looking at the product name on your receipt... This is the product name on the receipt: "RealityXP Garmin GNS 530 (FltSim)" Is there a way to upgrade to the V2 without having to repurchase? Or is there a way to authenticate the version I did purchase?
March 3, 20215 yr Author Now I'm thinking it is the v.2 gauge I purchased because I found the manual associated with v.2 and it describes the installation as a process similar to my GTN 650 I purchased previously. However, under "Addons" within FSX, only the GTN setup menu is there, not anything associated with a GNS gauge. That seems to me like even though I've installed it several times it never installed into FSX itself in the way that the GTN 650 has. The pinked-out image I see is after using the legacy configuration tool that I use for the 430 I purchased several years ago. So maybe what I really need is assistance in installing the v.2 into FSX.
March 3, 20215 yr Great! So you did purchase GNS 530 V2 (FltSim version). Therefore you get a pink GNS gauge because the panel.cfg is not referencing the GNS V2 gauge file, but the older legacy GNS gauge file. Please make sure to review the panel.cfg for this. You'll find gauge file name information (and much more) in the RXP GNS User's Manual. Edited March 3, 20215 yr by RXP
March 3, 20215 yr Just now, AZMRA said: However, under "Addons" within FSX, only the GTN setup menu is there, not anything associated with a GNS gauge. Please review the RXP GNS User's Manual Troubleshooting section for solutions.
March 3, 20215 yr Author 23 minutes ago, RXP said: Please review the RXP GNS User's Manual Troubleshooting section for solutions. THANK YOU! Adding that menu code to the .dll file did it, and it reminded me that I had to do the same thing for the GTN 650 to work when I first purchased that one, too. Again, appreciate your assistance!
Archived
This topic is now archived and is closed to further replies.