I use p3d 4.5
Printable View
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.