codelegend.com

That's correct, 242 is what you have at SP1A, which IF10 works with also, otherwise it wouldn't work with that. I'm afraid you continue to jump to conclusions with no forethought, there's always more to it than you at first might think.

...yes I did mean a "blank" dll.xml, dll's can seriously muck up FSX.

Ideal Flight 10 looking pretty and neat in your SysInternals window there mate! To complete a full-on windows exe is a vast undertaking.

Steve Waite wrote:That's correct, 242 is what you have at SP1A, which IF10 works with also, otherwise it wouldn't work with that. I'm afraid you continue to jump to conclusions with no forethought, there's always more to it than you at first might think.

Then how does IF10 decide when to use 259 instead of 242? It is still using 242 even when SP2 is installed.

...when only 242 is available, 60905 has legacy weather and gravity, so is ignored.

OK. So when 259 is available, should IF10 not be loading 259 instead of 242?

nope. IF can even use 60905 if that's all there is but no weather and zero points

Funny. Then why does IF10 give an error when only RTM is installed? It should still be able invoke FSX right? IF10 invokes FSX only when SP1 (minimum) is installed. IF10 does not work on my machine without SP1.

...hehe, yep SP1A. Do you honestly think you'll find some kind of catastrophic error in IF10 that targets only one machine?

No. I am trying to understand how IF10 is set to reference 242 on my machine even when 259 is available. If IF10 was built to work with RTM, it should reference the RTM version of the dll (no matter which other dlls were present)

The other method is if you have linked IF10 to all three versions of the dll. If you are loading the dll dynamically at runtime, then IF10 should load RTM, 242, or 259 depending on which is present. But IF10 seems to link to the 242 version always. But this comes in the realm of 'non standard' coding which you have agreed you are not employing for IF10.