JeeHell FMGS forums

Hello No currently this is a hard limitation on the aerodynamics enhancement brought by the simpatcher module. Loading saved scenarios in P3D result in this problem. As for the FD ON after go around ,there could be some reasons such as flight phase not correct at the moment of the go around so it's ...

to be honest I doubt the file is corrupted, if you can see other airports then it is unlikely. Make sure you do not have issues like a space character added by mistake or else... Also post you fsscenery.cfg file.

Yes it is

Your flight plan is not sequenced. Actually it should not even display the VDEV et all in this case.

you may have had issues with navdata compilation, I would redo that process.

Yes it is there for me in latest Navigraph cycle 2409.

Only on a separate PC

There is no reason these stopped working, particularly if mobiflight works for someone else. I would start looking elsewhere. Do you have the FSUIPC module dll in c:\a320fmgs\hardware modules ?

Hello

No I did not change anything in regards to FSUIPC inputs. Can you be more specific on which inputs ?

That is surprising ? Make sure your antivirus is not blocking anything, and that you have of course deleted the old bin files and the new airac is there.
What does your navdblog says?

Don't reload the aircraft, this is a known problem nothing that can be done here.

With P3D V4, you need to download and install Hervé Sors navdata / ILS fix from here: https://www.aero.sors.fr/navaids3.html

this is usually an issue with c:\A320FMGS\Navdata\FSScenery.cfg which has bad paths.

If this is in manual flight then it is the normal pitch down of the flare law

I haven't had time to test yet, I can't recall any issues there so I need to test, thank you for giving me some time...

try to not change position with fs flight control until the simpatcher has loaded correctly (OK message in the P3D addons menu).

Your sim patch log indicates a problem.
Do you have particular addons?
Try to change the sleep time in simpatch.ini file to a higher value. (180000 is a minium, try 240000).
Avoid changing stuff from P3D menus as much as possible.

Hi Markus
best would be to ask them directly about compatiblity?

Try this DLL:
https://www.jeehell.org/JeeHell_IIT_v2.dll
(keep the old one safe, outside of hardware connect folder)

that already exists, check 78ED value 35

The rounding are probably always "round down" then. Which gives you this result. I don't recall exactly what was put there. And I will not change it because there is no issues in any case.

Geez, do you realize that the accuracy of the FOB and each tank is +/-10 kg, which means that depending on rounding what you see is therefore correct?
2134 is rounded down to 2130
2134+2134=4268 rounded up to 4270

SIOC (or more correctly open cockpit boards) is known to sometimes badly initialize switch state, that could be your issue (particularly if nothing happens without the switch declared).

fCU is for the FCU. The button on the sticks is AP TO. (Take over).

is it on all airports, even default one?
You should try to manually create the navdatabase (not with corte manager) by launching the FMGS Server with admin rights. And make sure your G:\prepar3D v5 folder is not protected (read only or else)