JeeHell FMGS forums

Version B61.3.7 introduced a nice little change: -MCDU GUI: config now with a readable config file, may need to reconfigure it at first run. Fixed potential openGL issue with it. I finally had a chance to test it today as I always had a very hard time precisely positioning the MCDU window on the cap...

On my Skalarki setup the red arrow does indeed illuminate at low altitude if the landing gear is not extended.

As pointed out in the previous message the problem is compounded by the fact that the FMGC doesn't seem to import any constraint (altitude or speed) associated with the initial waypoint in a STAR (despite the fact that such constraint, if it exists, is properly included in the Navigraph data).

Out of curiosity, do you know if it matters if the flight plan is imported before or after the IRS are fully aligned?

That is the expected behavior. When you click Compute (after updating the weather first) you will get the takeoff performance numbers for both TOGA and FLEX. TOGA is the first line, with the current OAT. FLEX options are listed below that for a few FLEX temperatures. If you click Results you will se...

The blue arrow is a "level off" indication based on the selected altitude (FL200) which you can see at the bottom of the altitude tape. I believe that part is all normal. It's the location of the magenta (D) symbol that is incorrect, being way too early in the descent.

I have observed on some flights that the magenta (D) Decelerate Point is displayed much too early in the descent. See the example below where it is a little more than 10 NM ahead of the aircraft despite being still above FL280 and roughly 120 NM from the runway. This is with version B60.0.6 https://...

I hope it's okay for me to bring back this topic. Would it be possible, as a simpler step in the direction of the suggestions above, to have an option by which the cabin temperature would be set to the OAT? Default behavior would be unchanged (starts at 24C) but with the option ON the 3 zones would ...

I have noticed in several locations that when using the terrain display on the ND the minimum elevation is quite often "-13" (minus 13), which I believe would indicate -1,300 ft. Here is an example: https://www.flightpathsimulation.club/wp-content/uploads/jeehell-issues/Terrain%20-%20Min%2...

Here is an example of this issue. Notice the "005 37.10E", which I believe should read "005 38.0E".

I can confirm the behavior described by Bernd. I have seen this behavior as well. Basically the flight path is not displaying part of the SID past a certain fix. It happened for example on the VEBI1Y SID out of runway 28 at LSZH (no path after ZH544, until you fly past that waypoint). And to avoid ...

Unfortunately I have to report that I have observed the Overhead disconnected issue 3 times in the last 2 weeks. I have been using B60 for maybe 5-6 weeks now but I don't know if it related to the upgrade or not. It seems that the issue was less frequent (maybe even absent?) with B59 (but present on...

One is never too careful indeed but this seems all legit.
Thanks Scorpi1987 for sharing this and for your efforts. I know numerous people are patiently waiting for JeeHell FMGS to work in MSFS2020.

Very interesting. Is Sven mod publicly available?
Thanks in advance for any additional information you could provide.

Thanks for checking. It looks like it might have been a one time fluke. Everything seems back to normal now (I think I did press the Emergency Gen Test as part of my debugging and that might have fixed it).

I'm not sure if I remember correctly but I believe I had to delete the shader cache when tinkering with the lights for any change to take effect. Might be worth a try.

I'm using a Skalarki overhead panel.
All 3 PCs have been updated to the latest version as per the usual procedure.
The overhead is connected to the main PC running the sim and the FMGS server.

Another thing I observed after installing B60.0.6 is that the ETP point on the ND is sometimes incorrectly displayed:
- The text "(ETP)" is displayed at the correct location along the flight route, but
- The green ETP circle appears around the waypoint preceding the correct ETP location

I just updated to B60.0.6 today and noticed that if you press (turn ON) the LDG FLAP 3 push button on the overhead the red FAULT light on the RAT & EMER GEN comes on.
Could someone confirm this?
Thanks,

Thanks for the update!

Great suggestion. This would be a nice addition!

I have observed the same issue. It was working in previous versions.

WorldFlight 2023 is now in full swing and the VATSIM community is getting used to the JeeHell (JHL) callsign!

Check it out when you have a minute:
https://www.flightpathsimulation.club/w ... 2023-live/

Very nice. It looks like the file even has the old approach into Queenstown (NZQN), famous for this video:

I have done a short test flight with the latest update(and the new "trimwheel feedback" option set to 'no', which was the default) and haven't experienced the auto-pilot disconnect issue. However one thing I noticed is that the trimwheel on my Skalarki hardware does not return to 0.0 anymo...