Same for me and one more detail. FSX crash after few minutes when start A320 FMGS B52.2!? B52.0 works fine.
Printable View
Same for me and one more detail. FSX crash after few minutes when start A320 FMGS B52.2!? B52.0 works fine.
Forgot to say that I´ve noticed these FSX crashes as well. Thanks for reporting these issues. So I know that I'm not the only one.
Regards
René
Hello JL,
Same for me, with Skalarki TQ Engin start is not possible.
Everything Works find with the old Version.
Regards Micha
Just confirming that B50.2 works fine on my PCs
Hi JL, All,
I'm afraid EGPWS and WX have disappeared for me.
Data was copied to new EGPWS data directory on the PFD/ND display machine
Above PC is set as running EGPWS (Not running FGMS)
Directories are set, both EGPWS and EGPWS data, and exported
On the client machines EGPWS is set as not running, EGPWS output directory is mapped correctly to exported directory from master EGPWS, EGPWS Data directory option in config is grayed out.
WX config has not changed.
But nothing is being displayed for either.
Additionally -- I've just found what's probably the problem. The config on the EGPWS server is not saving. I click EGPWS server, click done, and when I re-open the config it has lost that setting. This happens running configure as both a user and as administrator.
Work around the non saving configuration was to reinstall, now EPGWS is running on the PFD/ND machine only but still no Terrain data. No weather to test on at the moment, but Edinburgh looks a bit dodgy right now, so just going EGLL EGPH to try it out.
Hi JL, yesterday i tried to have firt full flight with the new version.
I was not able to move because the engine had no power despite the levers being in TOGA.
See image
Did you rebuild the navdata? did you recalibrate your axis?
Yes , i did
FSx or p3d?
Sorry, p3d 4.5 .
check you haven't inadvertently installed an unused hardware module. Last update brought "symulatory/poldragonet support", by default it was probably selected for installation. If so delete the DLL in c:\A320FMGS\hardware modules (on any computer where it may be installed).
i'll chek soon. thanks
JL, i checked the hardware modules directory :
Main PC (FGMS Server + OVH Panel + all hardware) :
CockpitSonic.ini
EHIDModule.dll
FSUIPCModule.dll
SkalarkiIO.dll
On Slave PC (ND/PFD/ED/SD) i don't have any Hardware Modules dir (is it normal?)
I use a Saitek Throttle for the TQ at moment.
Hi JL, the hardware seems ok.
I checked it by fgms configuration and i recalibrated it.
FGMS recognizes the TQ are moving, but the power remains at 0.
In any case , i try to reinstall the old version B50 so i can try if the problem is the B52 or not.
Thanks for your support
You only use the saitek TQ as hardware? What about the Skalarki and cockpitsonic modules installed??
Hi JL, i have still the issue that the estimated time computations of the MCDU in the FP are incorrect. I took another leg from LFMN to EDDH, take off was at 10:30 UTC and the MCDU gave me an ETA at EDDH of 23:50 once when i was airborned. While flying the MCDU constantly computed the ETA at EDDH down and just when i was on final the ETA matched the actual UTC. Same for the ETA´s of each waypoint in the FP.
Do you have any idea what could be wrong?
I´am using P3d 4.5, and the FMGS is running on a dedicated Server.
One more Question: In the real Airbus you can put an estimated take-off time in the MCDU FP at the Departure-Airport. You doing this by select the Departure ICAO in the FP via the LSK and then you can put in the ETD. Is this Funktion implemented? I tried it but i get the message "not allowed" in the scratchpad. Just ask.
Actually my hardware set is :
- 1 Skalarki MCDU (CPT)
- 1 CockpitSonic FCU
- 1 CockpitSonic Radio Panel
- 1 CockpitSonic ECAM Switch Panel
- 2 Saitek Throttle (1 for the TQ , 1 for Spoilers and Flaps)
- 1 Saitek Pedals
- 1 LeoBodnar USB Key with Engine Panel and Gear Lever (From Skalarki)
- 1 Logitech Attack 3 for the Stick and Rudder
Ovh is only software at moment.
Regards
I don't understand, sorry... if i don't have the hw connected, how can i try the engine power ?
when i pushed F4 key , the engine had power as well
you dont need the ecam panel, or the cokcpitsonic modules you have to test the engine start. Just keep the joystick hardwar eyou use (saitek + bodnar) and do not run hardwareconnect (remove it from the starter.ini file, or simply rename hardware modules folder to something else temporarily).
Ok i'll try asap
thanks
Hello Jeehell,
Have you any idea for the Engine start problem with Skalarki TQ in the new Version B52?
I am flying with FSX.
Regards
Micha
Hi Jerhell,
same here, problem not solved yet. It looks like first engine doesn’t get any APU bleed air. Had to go back to 52.0.
Regards
René
Are you all with troubles still using FSX??
All, I don't know but at least for Micha and myself it's yes.
I use p3d 4.5
Hi JeeHell i tried to run without hardware module and i had same problems.
I reinstalled the B52.0 and all is ok, so i think the problem was the B52.2.18
Regards
For those with issues with b52.2.18 you can try this test build:
https://1drv.ms/u/s!AgqinWqhYcTFj4lYzDvdJb5YF8tWGQ
Hi JL, ok i'll try and report you
Thanks
Hi JL, first of all, merci beaucoup for your great support and your ongoing Mission to constantly evolve your FMGS that we all love so much. I´ve made a Little testflight yesterday from EDDH to EDDF and it seems that the time calculations in the MCDU FPlan do make more sense now. After takeoff when the estimations swich to UTC, at 21:45 the ETA at EDDF was calculated as 22:50 UTC what seems correct. The actual Arrival was at 22:44 UTC because of enroute Wind from the back.
The calculation for the waypoints match aswell and even the TOC and TOD was exact at the right UTC.
But the ND still Shows two TOD arrows on the Fplan path. the first one is correct at the correct Position of the leg and time but there´s a second one shown and it seems this one is Always around the FAF at the Destination.
It would be great if you could implement one day the function to set an estimated take off utc-time for the Departure Airport in FPlan like in the real Airbus. May be you put this onto the "todo-list".
As usual have no approach information set in the FPlan like runway or STAR. Usually i set those in flight because of not knowing to which RW the ATC will guide me at least. I will have a look on it if it makes any difference if i set the arrival information into the FPlan.Quote:
Did you insert an RNAV/RNP approach, or any non ILS approach in the MCDU?
Did you insert an RNAV/RNP approach, or any non ILS approach in the MCDU?
After reading my own post i think i have to make it more clear, sorry. For some reason the reply with quote and edit the post function is not working anymore in this forum.Quote:
As usual have no approach information set in the FPlan like runway or STAR. Usually i set those in flight because of not knowing to which RW the ATC will guide me at least. I will have a look on it if it makes any difference if i set the arrival information into the FPlan.
I meant that i usually put no arrival settings into the FPlan until i´am airborned and already follow my leg. Once i got actual weather and active runway for destination airport i put the arrival information into the FPlan. I think, but i´am not sure at the moment, that even with the specified arrival waypoints set for the specific runway, the second TOD arrow still apear around the FAF. But i will check this again and let you know.
Hi JL, well you made an educated guess. The second TOD arrow disapeared once i�ve put in the arrival informations. I have attached two pics which make it clear.