A320 FMGS B38

[romeow]

Thanks for your help, Florian!

I'll try and see!

Kind regards
René

[OmniAtlas]

Hello JL,

As others have also reported, when turning on EGPWS there is now an access violation.

Thank you,

Ben

[tcane]

Hi JL,

sorry, big mistake frome me.
There are no ELAC 2 issue. Without the displayed connected not connected issue and P3D crash, all works fine! (For me GPWS works without a problem...)
Have made a complete new SIOC_Creator assignment and the FD and ELAC2 Korry have the same Input Number but a different IDX. And i assignment on the same IDX like the FD Button.
Sorry for making trouble with this here.

King regards
Florian

[tomahawk66]

Hi JL,

As I have mentioned in posts elsewhere in this forum, I am working on a 2-D panel interface to the JH A320 using XML gauges and FSUIPC-LUA scripting. Thank you for attending to related issues concerning certain FSUIPC offsets, which I have acknowledged in the relevant threads.

A few more issues are noted here:

(1) Capt- and FO-MCDU's LSK and RSK keys do not work when activation is attempted through FSUIPC offset 78EC (values 38-43 and 44-49, values 221-226 and 227-232) . However these keys work normally on the native graphical MCDU's. So I suspect that this is a problem with the FSUIPC offset. This problem existed even with update B37 and continued till B38.

(2) With update B38.1, both MCDU's get stuck on 'loading nav data' and are wholly inoperative thereafter. No keys work, even on the the native graphical MCDU's. Reverting to version B38 restores functionality of the keys and allows loading of nav data, but the problem noted above with the offsets for line select keys returns.

(3) The 'always on top' feature for the graphical display units does not work reliably, and this was an issue even with version B37. I wonder if this is a general problem faced by everyone, or whether this is related to my own multi-monitor configuration. (I operate 6 monitors off my server desktop using 2 dual-head graphics cards as well as 2 Matrox DH2Go units. My system has worked stably and efficiently with all other FSX add-ons, including the PMDG B737 NGX and the FSLabs Concorde)

(4) I am having problems with APU start and Engine Start. They often get stuck/hang mid-way. I am wondering whether this is due to my trying to operate all the units on the server, rather than distributing them over a network, which is of course how your software is intended to be run.

Thank you for your attention.

Regards,

Chakko.

[OmniAtlas]

Hi all,

I will not add xplane support because of no available A320 flight model that can be used, and the time required to add full support.

Some EGPWS issues may come from graphics cards/drivers.

JL

Hi JL -- if you reconsider, please take a look at the QPAC A320, their 1.0 version is available for free. http://forums.x-plane.org/index.php?showforum=110

Thank you,

Ben

[tcane]

Hi Jl,
today i flown a 3,5 hour long online leg. Between 2,5 and 3 hours after departure i got a "Wide FMGS Out of memory" message. It still works continue but with some lags and crashing frame rates in P3D.

Regards Florian

[immaging]

Hi JL and All,

I downloaded the new version of Fmgs 38.1, but i Have a problem.
The server pc working ok ( p3d-pfd-nd-mcdu-Ohv- Cpt side).
But the client pc( pfd-nd-mcdu-ewd-se Foside) after 10-20 second, freeze and dont work anymore.
the message on the fmgs module is this:

WideFMGS Client log.
Port 8005: connected
Port 8004: connected
Port 8003: connected
MsgListMutex timed out
MsgListMutex timed out
MsgListMutexMain2 timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutexMain2 timed out
MsgListMutex timed out
MsgListMutexMain2 timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutexMain2 timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutexMain2 timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutexMain2 timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
TfmapsThread timeout
Port 8003: connected
MsgListMutexMain2 timed out
MsgListMutexMain2 timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
MsgListMutex timed out
Port 8003: Disconnected
TfmapsThread timeout
MsgListMutexMain2 timed out
Port 8003: connected
MsgListMutex timed out
Port 8003: Disconnected
TfmapsThread timeout
Port 8003: connected
MsgListMutex timed out....

Help for Idea??

many TKS

Daniele

[anzabon]

(1) Capt- and FO-MCDU's LSK and RSK keys do not work when activation is attempted through FSUIPC offset 78EC (values 38-43 and 44-49, values 221-226 and 227-232) . However these keys work normally on the native graphical MCDU's. So I suspect that this is a problem with the FSUIPC offset. This problem existed even with update B37 and continued till B38.

(4) I am having problems with APU start and Engine Start. They often get stuck/hang mid-way. I am wondering whether this is due to my trying to operate all the units on the server, rather than distributing them over a network, which is of course how your software is intended to be run.

Chakko.

Hi Chakko, I also run the CPT and F/O MCDU LSK and RSK keys via the FSUIPC offsets and still don't have any problems with them in B37 and B38. The APU and both engines also start without any problems. Maybe some difficulties in your hardware configuration, for example the network or computers...

Regards, Bon

[tomahawk66]

Hello Bon,
Many thanks for this valuable information......I'm going to now have to test whether these problems I am experiencing have something to do with attempting to run both Captain and F/O sides on the same PC.....not just both MCDU's but all the other DU's as well.
Regards,
Chakko.

[jess-b]

Got my first flight with the latest beta tonight. All went well until after landing. Just cleared the runway and I suffered what I assume was a disconnect. I lost my engines and all power for no reason. I got the apu running soon after, but couldn't get the engines running again.

Will test again tomorrow to see if the problem reoccurs.

Jess B