JeeHell FMGS forums

Hi,
you can update to B60 immediately.
Personally, I back up the old installation first.
After the update, you should check the Starter.bat if you have made any entries there.
The aircraft is now in the folder A320 not A320-200. You have to transfer your liveries manually, if you use any.

I have found an older FCOM. And here, too, it is written quite precisely in 2010.

...reducing it to 2 Degrees NOSE DOWN....!
My initial statement is correct.

Jean Luc,
the screenshot above is from the FCOM from a real A320 pilot. Your assumption is not correct. As already written, in more recent FCOMs since 2018, the lowering of the nose to -2 degrees in 8 seconds is explicitly described.
I think a real A320 pilot knows what he is talking about.

Hi, the target pitch is after 8s -2° ... so if you have at 50ft a pitch of 4°, the nose down will be 6° within 8s. If you have a Pitch of 6° at 50ft, the nose down will be 8° within 8s. And yes - if the Pilot not flare, the NWL will touch first :-) P.S. The File-Upload in the forum doesnt work ... ...

Hello Jean Luc, I have to disagree with you. I was actually wrong about -3 degrees, as it is -2 degrees. But the basic description I gave is correct. And no, the Airbus does not change the pitch by 2 degrees, but to -2 degrees. Take a look at the picture, the text comes from the FCOM. https://a320-s...

No, Peter's problem has nothing to do with the faulty flare mode. What I mean is described in the FCOM -> Aircraft Systems -> Flight Control System -> Normal Law -> FLARE MODE. I already wrote about this in December 2022. In the meantime, I have not seen this problem, which I have already described ...

Hello Jean Luc, I reported some time ago that the flare mode is not working properly. I have now carried out several test flights and landings and noticed the same behavior each time. According to the FCOM, the A320 saves its settings at an altitude of 50 feet, then the nose is lowered to -3 degrees...

I can confirm the behavior described by Bernd.

You will need to copy all the *.bin files to the navdata folder in all client computers where you have setup PFD/ND (EIS.exe) screens. Or you use my Tool UPDNAV. With UPDNAV, the entire process of distributing navigation data across the network becomes much easier The tool has been available on my ...

A newer version with bugfix and additional functions is available for download.

Hi all, Anyone who carries out training in Jeehell for landing will certainly also use the function for recording in P3D. So that you don't always have to start the recording manually, I have written a small tool that automatically records the landing in P3D. Download and information on my website a...

So, problem solved, after I deleted all the saved flights and saved a new scenario, the trim wheel is also set to 0 when I touch down.

Hi JL,

Today I switched to the B60.
A small problem, the Hardware Connect window is no longer minimized.

Hi Michael,

you use a Skalarki TQ? After touchdown my TQ doesn't reset to 0.

Hello everyone, for everyone who bought my Airport Hamburg Finkenwerder (EDHI) from Aerosoft. I have created an update for Prepar3d v5.4 including dynamic lights and new night textures. Furthermore, the AFCAD was changed to the new frequencies. I can't say whether the update also works in v6 because...

Okay, thanks.

I can confirm Michael's problem, it's the same for me. I would also be interested in a solution.

I describe this problem with the Overhead on my website: https://a320-simulator.de/homecockpit/s ... ht-switch/
And the Jeehell server must be loaded before the profiler is started.

Jean Luc,

any answer?

Hi Jean Luc,

after I discussed the problem with Marcin, it is relatively certain that since B59 the trim wheel is no longer set to 0 when touching down.
I have no idea if this is only the case with the skalarki TQ.

@Jean Luc,

in a fresh Setup of Jeehell FMGS the rudderFilter.txt is not created!

I'm using P3D v5.4 and have no problems since the work from JL for this problem.
Create a rudderFilter.txt in your FMGS Server folder.

Okay, I don't know if it is only needed with a separate FMGS server. This is for Jean Luc to answer.
Otherwise just create an empty text file and name it rudderFilter.txt

That's right, I can confirm, there is an HTML error output.

There are some more errors on the ND. No TOC or DECEL Point are shown. And the ND Range are not calculated correct.
Waypoints shows to late at higher EFIS Setting e.g. 20. I think with version 57.x this errors were not present.