Do you mean put a copy of the GTNS2 in the rxpGNS gauge file?  I'm not a home so can't check but from memory the rxpGNS is a folder not a .cab........?

aw

The gauge files installs in the gauges folder like this: "FS9\Gauges\rxpGNS2.gau"

If you copy and rename the copy to rxpGNS.gau, legacy aircraft panel.cfg files referring to gauge##=rxpGNS! will pick the GNS V2 renamed gauge file instead.

Thanks to V2 also enhancing the default SDK with "aliased" gauge names, it will also work transparently: rxpGNS!GNS530 will be picked up as GNS_530_1 automatically internally.

Edited September 7, 20214 yr by RXP

Hi RXP,

Further to the above, I have tried out all the options discussed to the best of my ability and can confirm that I am no further forward.

1/.  Manually configuring the .cfg files gives me nothing at all!  No sign of a gauge, no black blank window - nothing!  I have attempted to install in both separate windows and directly into an existing view (main panel for example.) 

2/.  I have tried using a variety of gauge names, both legacy and new ones with the same result - nothing!

3/.  As to enabling the "Use Legacy Vars" GNS v2 setting, this I cannot do because there is no .ini file in any of the aircraft folders.  I understood that this file is created when the configurator is run, which as you know does not occur.

I am especially confused about 1/. because I am quite confident of my skills in this area and would have expected to see a gauge show up.  Or something at any rate!  

Where do we go from here? !!

Andy

Please see post above but I forgot to add that I tried the copy-and-rename option too.  What I did was rename the copy of rxpGNS2.gau as rxpGNS.gau in FS9/Gauges.  The other relevant rxp .gau file I have in that location is RealityXP_FL530XP.gau.

It might be worth noting that the rxpfsxml.exe - FltSim Config File Helper - does not run either from it's default location.

Please note: I have several days ahead of me to attend to problem before being absent from flight simming and my computers for a month.  Therefore if we are unable to resolve this shortly, I will go quiet.  This does NOT mean that my desire to find a solution has gone away!!

Regards,

ANDY

Please see above 2 threads.

Version 2 GNS530 requires FS9.1.  That is clear in the description.  I regret to say that due to an oversight on my part, I am trying to install in FS9.0!  This is nobodies fault but mine; I take responsibility for missing this.  I have several copies of FS9 in operation (the others ARE FS9.1) and I must have inadvertently checked the wrong one.  Oh dear...   

There is no way that I can upgrade the copy I want to use to FS9.1 as the upgrade installer really requires a clean copy of the original.  It just fails if much has been modified from stock - as mine has.  (It is way too much trouble.)  So, is there anyway around this?  What exactly does the v2 gauge need from the update?  Surely it does not require the whole thing...?  Is there a way to manually update whatever elements are required, as a work-around?  

I realised this might be the problem when I installed GNS v2 on another machine with windows 10, with a copy of FS9.0.  Just to see.  I got further here as the configurator runs and loads the gauges into the panel.cfg file.  But I still see no gauges, even when using the "replace stock FS9 GPS gauge" option.  The window with the GNS v2 in it just does not load.....

So, while accepting a huge dose of humble pie that I must consume, are there any solutions?    

Edited September 11, 20214 yr by andywilby

There isn't much else to do that updating FS9.0 to FS9.1 unfortunately. This is a very old FS version on a very old OS which we support for the time being but no for long either. IIRC (it's old now) 9.1 did correct a lot of bugs which are important just so that the gauge, as a gauge, can run like expected. This is also the most updated version of FS9. NB: we have similar requirements with FSX where our products are only compatible with the latest version: SP2/Acc Pack.

I'd suggest you manage to install FS9.0 and update to FS9.1 by itself, and eventually you copy back the files into your running FS9 installation (make a backup first just in case!) Otherwise, it is well known a lot of users are running the 9.1 version with a "modified" .exe file because the check system is not working on our modern computers and CD drives.

RXP,

Thanks as always for your help and advice.  Just to confirm then: Without somehow updating to FS9.1 it will be impossible for me to run your version 2 gauges.  Is that correct?  I have tried in the past to run the upgrade but it just fails, largely I think because of all the add-ons and so on that may have modified the stock files.  It is these very add-ons that make FS9 still so very satisfying and worthwhile.  Like many dedicated FS9 users, I have much invested in the sim and to get the same level of detail, smoothness and depth in say FSX would take an inordinate amount of investment of time and money.  I cannot face doing so just to get back to something I feel I've already got!  I shall ask around on other forums for some advice on "manually" upgrading - somehow - to FS9.1.  How on earth would I identify which files are the upgrade to be copied across, if I was to follow your suggestion?

In the meantime, could you elaborate on what you mean by this statement: 

Otherwise, it is well known a lot of users are running the 9.1 version with a "modified" .exe file because the check system is not working on our modern computers and CD drives.

I have no understanding!

We began this thread with a fairly clear understanding that it might well be a struggle to get your version 2 gauges to run on my software and hardware.  That has proved to regrettably be the case and I think a request for a refund from F1 is probably the only outcome from here on in.

Well, at least we tried!

AW

 

Edited September 13, 20214 yr by RXP

4 hours ago, andywilby said:

I shall ask around on other forums for some advice on "manually" upgrading - somehow - to FS9.1.  How on earth would I identify which files are the upgrade to be copied across, if I was to follow your suggestion

Well it is rather simple in fact: backup your FS9.0 installation (everything should be in the FS9 folder) then install a new FS9.0, update it to FS9.1. From there you just need to compare the files between your FS9.0 backup and FS9.1 new install using a diffing tool like this one: http://kdiff3.sourceforge.net/

 

4 hours ago, andywilby said:

In the meantime, could you elaborate on what you mean by this statement: 

https://answers.microsoft.com/en-us/windows/forum/all/fs9-2004-compatability-with-windows-10/72da8076-26ac-4cd0-ab5c-7c9b8782dc05?msgid=4fee4f38-8a33-4b1e-883f-6d74927bdfaa

 

Disclaimer: the information published in the URL above is for education purpose only.

 

RXP,

I can see that your suggestion of using a "diffing tool" might work.  While it might be more work than simply running an installer, I would feel confident doing it.  Below is a list of all the files modified by the FS9.1 update.  Do you by any chance know which ones are needed for your gauges to run?  For example, does your version 2 REALLY need a new atc.dll in order to work...?  (The A610 bit in the file name can be ignored as it is added by the update process.)

ablscpt.A610.dll
acontain.A610.dll
ai_playr.A610.dll
atc.A610.dll
controls.A610.dll
demo.A610.dll
display.A610.cfg
dynamic.A610.dll
facilities.A610.dll
fe.A610.dll
flight.A610.dll
fs9.A610.exe
fsui.A610.dll
g2d.A610.dll
g3d.A610.dll
Generic.A610.bgl
global.A610.dll
gps.A610.dll
gps_export.A610.dll
instructor.A610.dll
main.A610.dll
mpchat.A610.dll
multiplayer.A610.dll
panels.A610.dll
reality.A610.dll
sim1.A610.dll
simscheduler.A610.dll
sound.A610.dll
symmap.A610.dll
terrain.A610.dll
traffic.A610.dll
unpatch.bak
util.A610.dll
visualfx.A610.dll
weather.A610.dll
window.A610.dll

I assume that a diffing tool would give exactly the same list, right?

AW

Edited September 13, 20214 yr by RXP

All these are the core simulator files and you can't change one without changing all of them, because they are inter-dependant. In any case, unless you are running a specific FS9 add-on only compatible with 9.0, and not 9.1, there shouldn't be anything much too loose in updating. To play on the safe side, just backup your entire FS9 prior updating the files, then once updated test to see whether everything is working. Otherwise I understand you're also using an OS+SIM which is too old for the product requirements and like you said at least we tried.

Edited September 13, 20214 yr by RXP