JeeHell FMGS forums

Hi I just checked. There was a runway numbering change in LIML a few months ago, the main runway went from 18/36 to 17/35. Unfortunately, there is an old decommissioned runway in LIML which is 17/35 also in P3D. The navdata compilation is thus mistakenly using that one, which is too small to appear ...

Most of the selectors should be clicked on the labels of the functions you want (ON/OFF/AUTO) and not necessarily on the switch itself. YOu can also use on some selectors(rotary ones) left/right clicks. Hardware: make sure you did NOT install support for hardware you do NOT use, it could interfere. ...

prosoft wrote: ↑Thu Jan 25, 2024 4:58 pm

gillesaqsim wrote: ↑Wed Jan 24, 2024 10:28 pm Verify if simpatcher exist on add-on P3D menu
Regards

yes, Simpatcher B57.0 is present on P3D menu

Massimo

It should be b60 not b57. You should reinstall and make sure to select the correct options.

Nope, the nose down moment will be towards ref pitch -2°. The flare law is a actually Nz law, the NZ inputs are the pitch error (so ref target is pitch at 50ft -2°) with some gain, plus stick deflection with some gain as well, and also pitch rate with some gain. And No, you would not slam with nose ...

The flare law does NOT lower to -3°, it lowers BY 2 degrees over 8s. That means that to keep a steady pitch you need to counter the nose down moment by using some aft pitch, to simulate a conventional flare feedback. The flare law is modeled, it is not necessarily easy to "feel" as it is s...

The description was a bit inaccurate, sorry. It's not about the glideslope display in the PFD, but about the flight path to the runway. the glideslope does not lead to the correct touchdown point, the aircraft either lands in front of the runway, or far behind the actual touchdown point, following ...

Which version of FDS support did you install with my software?

Please everyone take care about opening links from a user with 1 post only (sorry Scorpi1987 if this is genuine, but people need to be careful).
UPDATE: this is a legit link after all.

What do you mean by not correct?

did you rebuild your navdata bins after installing your new addon scenery?

UNder P3D V4, V5 and V6 you should have an addon xml file in your folder C:\Users\Your_User\Documents\Prepar3D vX Add-ons folder (adapt You_User and P3D vX folders of course) That file should tell P3D where to look for the simpatcher location. Some addons interfere with the proper functionning of Si...

this option is for some hardware trim wheels which are too slow to react, but in the case of skalarki it should not be used, I havent tested that in depth with all hardware obviously.

That will be fixed in next update.

I checked with the software OVHD panel and it works correctly. That probably means there is a problem on the skalarki side.
Check the assignments are correct in the profiler and that the correct assignment lights up the correct hardware LED...

The bell sound is a big it dates from a time when I did not have the HORN sound. That will be corrected.
Do you have dual sounds for the other sounds?

MAybe a different version in skalarki profiler?

I will try to check that button in the next days.

can you share how you declared the landing gear lever joystick buttons precisely?

What hardware?
Did you update all PCs? And with the same options so as to have all files in the correct version?

Are you sure you selected the correct options on the correct PCs?
A possible workaround is to install the FMGS server on P3D PC to get the files then reinstall without FMGS server option.

Did you select P3D master PC with the correct p3d version at installation?

It could help

Go in your C:\Users\Your_User\Documents\Prepar3D vx Add-ons\A320FMGS and check the content of add-on.xml.
Also make sure you did not disable jeehell FMGS addon in P3D (P3D menu bar -> options- addons -> jeehell FMGS -> check it is checked)

What version of P3D do you use?

pe_martin, do you have any issues like hearing the sounds twice?