• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FS2004 SOLVED! - FS was unable to load...

R

Ravamar

Messages
100
Country
italy
I have released a first Beta of a newer version CIVA INS gauges...BUT...one of the beta testers, who is still using FS2004, reported me that the 32bit gauges no longer works.
The exact dialog box message is: "Flight Simulator was unable to load some aircraft or software. You can continue using Flight simulator but the aircraft or software will be disabled."
Then it references INS.GAU which is one of the gauges in the CIVA package.

So latest 32bit gauges I built are no longer compatible with FS9 while they are expected to be so :yikes:
Latest version was compatible, and this has to be so too (FS9 compatibility is very important for Ready For Pushback Classic 747 users).

My question is: What can cause such message?
I thought about GAUGE_HEADER_FSx00 but I checked and the 32bit build uses GAUGE_HEADER_FS800 which is supported by FS9 so something else should be causing this :banghead:

Any experience?

Thank you!
Marco
 
Which version of gauges.h are you using?
If you want the gauges to work in FS9, I would be using the gauges.h file from the FS9 SDK.
 
I checked that too and discovered (I did not remember it LOL) 32bit gauges actually use fs2002 gauges.h! And I haven't touched it.
And, I forgot to specify, latest 32bit version works perfectly under FSX or P3D V1/2/3.
So it looks like the 32bit "dll" is ok, I "just" lost FS2004 compatibility and that should (or, at least I think) be related to gauge's FS interface itself (the "GAUGESIMPORT" based one) being more recent than FS2004 and consequently not handled.

All the changes the new version includes are minor except of course for the P3DV4 compatibility which requires several modifications to the gauge interface but they're all under #ifdefs. I believe if I am missed any #ifdefs then I would have lost also FSX compatibility or get some warnings or errors from the compiler.
Latest version also uses a new TOKEN variable (FORWARD_GROUND_VELOCITY) which was available in FS2002 (yes 2002, I checked) plus I would expect a compilation error if undefined.

I'll re-check everything once again, but I feel I'm missing something...
Thank you!
 
I discovered something new.
I tried the 32bit CIVA gauge under P3DV3, where I have enabled the "production" of contenterrorlog.txt file.
Inside it I found this kind of error:
"error=C-style gauge failed to load: D:\Prepar3Dv3\Gauges\../civa/INS.dll, Gauge: Config. Verify the correct version of SimConnect is installed."
This error is repeated for ALL gauges included in INS.GAU.
The problem is...the gauge isn't supposed to use SimConnect, nor am I linking any library related to simconnect.
Does anybody have any idea on what can cause this problem?
Thank you in advance!
 
Last edited:
I luckily and finally found the problem.
In Beta 2 I modified CIVA code dealing with DirectInput because under 64bit the minimum allowed version is 8.00 while in the 32bit environment I am using 7.00.
But I made a mistake and defined DIRECTINPUT_VERSION as 0x800 not only for P3DV4 compilation but also for 32bit compilation mode (FS2002, 2004 and FSX/SE).
I solved the problem by putting #ifdefs so that 0x700 is used for 32bit and 0x800 for 64bit.
So SimConnect reference in P3DV3 contenterrorlog.txt had nothing to do with the actual problem, but I still cannot explain why a "badly" defined DirectInput version ends up causing such kind of error message....
 
I think the answer may be simpler than it appears. Once the error is thrown, there is nothing to immediately trap the DirectInput error. The first error trap that can deal with the problem happens to be the one to do with SimConnect, so that is what you see.
 
Thanks for the explanation Dai, but I still don't get it.
I don't know how FS/P3D would detect a gauge isn't "good". Then, once established the gauge cannot be loaded...FS2004/FSX display a generic error "can't load bla bla" (which is fine), while P3D, on the contrary, gives a much more detailed message in contenterrorlog.txt. Maybe that is a "generic" message as well because SimConnect is USUALLY the reason?
 
You must log in or register to reply here.
Back
Top