A320 FMGS B35

[jeehell]

Try again updating, with the online tool or the full package:
http://www.jeehell.org/A320FMGS_B35.3.exe

JL

[jeehell]

By the way, it's better to have OVHD on the server computer. Most issues come from there I think.

JL

[tcane]

By the way, it's better to have OVHD on the server computer. Most issues come from there I think.

JL

I can now update all Network PC`s. Thanks.
Actually i made an testflight and it looks like everything is running again. Thanks for this!
Unfortunately I can not run the overhead on the server, because when i fly I, click on the same screen were my fsx is running.
so at this moment, my ovhd (also Ivap, teamspeak etc.) is running on my laptop there is directly on my sidestick area, and it´s easy to controll.

Regards
Florian

[stefangr]

Hi JL,

thanks for the update. Works like a charm now, so overhead is back again

I hope I can make a test flight tonight.

By the way, it's better to have OVHD on the server computer. Most issues come from there I think.
JL

Also for me this is unfortunately not an option. It needs to run on a separate PC because the overhead hardware is not complete yet and quite a few buttons need to be pressed with the mouse.

Thanks
Stefan

[stefangr]

Hi JL,

perparing my first test flight now, I am again having the problem that NDs freeze as soon as departure runway is entered in MCDU. This was reported in tracking tool as ID#945 and a complete new install obviously solved it at that time.

Will this again be necessary? I thought I could just use the updater. Anything to do with the NAVDB.DLL as it was the last time?

Thanks
Stefan

[jeehell]

I need to know the exact route you entered.

[buentead]

Thanks, JL, also from my side! Everything works correct on my installation and my two flights went well.

Great job! Thanks
Adrian

[stefangr]

I need to know the exact route you entered.

Hi JL,

I entered the route EDDW/EDDW for my test flight. As soon as I selected departure runway 27, both NDs froze. I tried it 3 times (with PC reboot in between), always the same.

I then re-installed FMGS completeley again, and now the failure is gone. I think the auto updater might have missed a file?

I have seen that a joystick.dll was also updated. Will that fix that we had inop axes (especially throttle axes) during flight?

Thanks for your help + the new version, my test flight was going smooth tonight.

Stefan

[filippoporcari]

just for info: with the new update (35.3) may we keep the joy config file from 35.1?
regards
fil

[jeehell]

@Stefan: I'll try to check why the auto update did not work correctly, it's strange.
As for the joysticks, I do not know. I do not have that issue so it's hard to know if it may or may not solve it. IT should at least solve an error in FMGS Config where crash windows appeared if you did not have an USB joystick plugged in.

@Filippo: yes.

JL