Results 151 to 160 of 460
Thread: A320 FMGS B52
-
07-05-2019, 05:57 AM #151
Re: A320 FMGS B52
I use p3d 4.5
P3D V5 HF1 - PC spec: Intel i5-6600K, 16 GB DDR4 2400, GPU Nvidia GTX1070ti, M2 SSD NVme, JH FMGS, GSX, ASP3D+ASCA+ENVSHADE
-
07-08-2019, 06:07 PM #152
Re: A320 FMGS B52
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
RegardsP3D V5 HF1 - PC spec: Intel i5-6600K, 16 GB DDR4 2400, GPU Nvidia GTX1070ti, M2 SSD NVme, JH FMGS, GSX, ASP3D+ASCA+ENVSHADE
-
07-09-2019, 06:12 AM #153
- Join Date
- Mar 2008
- Location
- France,Nice
- Posts
- 2,652
Re: A320 FMGS B52
For those with issues with b52.2.18 you can try this test build:
https://1drv.ms/u/s!AgqinWqhYcTFj4lYzDvdJb5YF8tWGQ
-
07-09-2019, 06:16 AM #154
Re: A320 FMGS B52
Hi JL, ok i'll try and report you
ThanksP3D V5 HF1 - PC spec: Intel i5-6600K, 16 GB DDR4 2400, GPU Nvidia GTX1070ti, M2 SSD NVme, JH FMGS, GSX, ASP3D+ASCA+ENVSHADE
-
07-10-2019, 04:52 AM #155
Re: A320 FMGS B52
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".
-
07-10-2019, 07:31 AM #156
- Join Date
- Mar 2008
- Location
- France,Nice
- Posts
- 2,652
-
07-10-2019, 07:31 AM #157
- Join Date
- Mar 2008
- Location
- France,Nice
- Posts
- 2,652
-
07-10-2019, 11:26 AM #158
Re: A320 FMGS B52
Did you insert an RNAV/RNP approach, or any non ILS approach in the MCDU?
-
07-10-2019, 11:38 AM #159
Re: A320 FMGS B52
Did you insert an RNAV/RNP approach, or any non ILS approach in the MCDU?
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.
-
07-10-2019, 05:50 PM #160
Re: A320 FMGS B52
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.
Pretty Girls from your city for night
Generic Analog Gauges