Leaderboard

I did found the issue! My PC Time was still on "wintertime" in germany....1 hour behind. I did update the time a few minutes ago and tried again...issue solved. But maybe important for other users.

Hello all ! Missing your night ligths at HTKJ Kilimanjaro ? The solution is SO easy. Nothing to do with a "P3D glitch" or whatsoever. For whatever reason, the installer installs simobjects required by SODE to inject the lights at night in the wrong folder, actually in your sim root under ../Simobjects/Misc/HTKJ. SODE, since version 1.3 (December 2015 !), uses its own simobjects folder under PorgramData/12bpilot/SODE/SimObjects. Just move the HTKJ folder in that folder. Last modification : you have to amend the HTKJ_L.xml file in ProgramData/12bpi

A known issue when trying to save via the 'aircraft list'

Hi Stephen, thanks for the screenshot! It does indeed look like the updated configuration tool files are placed incorrectly, try merging the content of the "Configuration Tool" folder inside the SimObjects folder with the original that's in the sub folder of the Cologne root folder. The update only included changes in the configuration tool, so no other changes should be needed. I'll try and get some info from those that know more of the inner workings of the updater why this is happening.

Jo is the update via Aerosoft Updater 1.0.7.5 placing the Configuration Tool in the correct location as the original is a sub folder of Cologne root whereas the new update is created under simobjects and is missing images:

And there is also a strange thing I found out. After many CRJ reinstalls I noticed that yoke is in the full left (or right) position with no systems working if I have the 2.0.0.0 version (the problem that happens if you have an old P3D version but I have the latest one) . If I update the CRJ to 2.0.0.3, it is working (with FPS problem). It is strange that version 2.0.0.0 doesn't work at all. Am I missing something, some runtime libraries etc. and that causes the low FPS problem in 2.0.0.3?

This is really strange. Have you tried setting NVidia threaded optimization (in the driver control panel) to on? This sometimes solves strange issues and this one is really weird.