I'm assuming that the only way at this point to use things like fsmap, rex latitude, etc via remote laptop is to use p3d v2 in legacy mode with the Estonia Migration tool..

 

So in my testing i've also noticed that the fps average is about 13 fps less (using my benchmark that i've done for p3d) in legacy mode than it is in standard mode..

I checked in P3D settings and tried to make sure all settings were the same there..

 

What i'm thinking is that the "fake" fsx.cfg that seems to appear with these contents each time needs to have some of the tweaks i did for the p3d one, in it.. but i'm not sure if this is accurate?:

[Display]

SKINNED_ANIMATIONS=1

[MAIN]

FIBER_FRAME_TIME_FRACTION=0.33

[TERRAIN]

LOD_RADIUS=4.500000

TEXTURE_RESOLUTION=25

MESH_RESOLUTION=22

[GRAPHICS]

TEXTURE_QUALITY=3

IMAGE_QUALITY=0

TEXTURE_MAX_LOAD=1024

 

The above is what i see in the fsx.cfg that replaces my old one once the enable virtual fsx is turned on..

 

Any thoughts here...

 

Thanks

that is strange....any tweaks you apply to the p3d.cfg should automatically appear in the fsx.cfg with the migrator tool. you should never modify anything in the fsx.cfg file, always in the p3d.cfg file.

that is strange....any tweaks you apply to the p3d.cfg should automatically appear in the fsx.cfg with the migrator tool. you should never modify anything in the fsx.cfg file, always in the p3d.cfg file.

 

Yeah i'm not sure why there is this dummy fsx.cfg in the appdata\microsoft\fsx folder.. there are 3 files in there..  fsx.cfg the exe.xml and dll.xml (but junction files or symbolic links obviously with estonia)..

 

What was causing the difference in frames per second was at first.. different settings in p3d when it launched in "compatibility mode" which is just the fsx.exe file that estonia creates.. coupled with the fact that inspector then uses my settings from fsx for the fsx profile i had..

 

So unfortunately, i modified the fsx profile in NI and made it the same as for the prepar3d one.. then now the numbers are about the same whether launching compatibility mode or normal.. 

 

Since ill mostly run simconnect over a laptop i've made the compatibility mode the default for now...  (although some things like latitude dont seem to need it)