Ok The Falcon 50 V1.9B is available at our store to download. Please test again with this version. I just made a film of me using this version and landing at KPTA. 

 

Edited January 22, 20206 yr by Flysimware

14 hours ago, Gazzareth said:

 

Ran XMLTools installer (as admin)

This new installer installs XML Tools and the XML.DLL entry for all sims. So if you read the new info that comes with the zip file there is nothing to do but change GPS units which the exe is now in all programs from the start menu.

22 minutes ago, Flysimware said:

This new installer installs XML Tools and the XML.DLL entry for all sims. So if you read the new info that comes with the zip file there is nothing to do but change GPS units which the exe is now in all programs from the start menu.

I'm not even changing the GPS units at the moment, because this issue is happening with your GNS530 as well.

Will test shortly.

 

G

8 minutes ago, Gazzareth said:

I'm not even changing the GPS units at the moment, because this issue is happening with your GNS530 as well.

Will test shortly.

 

G

I see now how the problem has nothing to do with GPS units. I was just letting you know the new installer now does some more magic for the XML Tools installation..

I have another pilot going to do some testing tonight to see if he can solve the mystery. So far only 3 users. By the way did you add any updates for airport info for your P3D? Could be that some ILS approaches have no glideslope now. 

Another test you can do is install a fresh copy of P3D V4.5 and report back what happens. I have found this has solved the other issues more times than i can count.

Edited January 22, 20206 yr by Flysimware

2 hours ago, Flysimware said:

Another test you can do is install a fresh copy of P3D V4.5 and report back what happens. I have found this has solved the other issues more times than i can count.

P3D 4.5 was only installed last week, so is as fresh as anything ..... No airport scenery installed anywhere, plus as I pointed out your Lear AND the Falcon 1.8c follow the Glideslope at EGPH perfectly..

 

G

Edited January 22, 20206 yr by Gazzareth
Clarity

7 minutes ago, Gazzareth said:

P3D 4.5 was only installed last week, so is as fresh as anything ..... No scenery installed anywhere, plus as I pointed out your Lear AND the Falcon 1.8c follow the Glideslope at EGPH perfectly..

 

G

Could be that we added dynamic lighting so now your system can't handle the new update. Maybe lower settings like effects and lighting. 

But for sure test V1.9B as i just uploaded this earlier tonight.

 

Edited January 22, 20206 yr by Flysimware

1 hour ago, Flysimware said:

Could be that we added dynamic lighting so now your system can't handle the new update. Maybe lower settings like effects and lighting. 

But for sure test V1.9B as i just uploaded this earlier tonight.

 

Just tested with your GPS installed, although set to NAV mode and it actually just flew straight through the Localiser, switched to it, but ignored it just like it was doing with the glideslope..... that's a first! Oh and this is on p3d3, so I don't believe dynamic lighting is a thing ?? (I know the OP was for p3d4.5 - but since I found the error on both I've reinstalled 1.8c on P3D4.5 so I can use it)...

 

So whatever you changed, do the opposite !

G

Edited January 22, 20206 yr by Gazzareth

2 hours ago, Gazzareth said:

although set to NAV mode and it actually just flew straight through the Localiser

I noticed on your test video you didn't select approach mode  to intersect the ILs and glide slope.

bob

 

4 minutes ago, onebob said:

I noticed on your test video you didn't select approach mode  to intersect the ILs and glide slope.

bob

 

From my understanding (and literally what I have always done) the correct way to do it is to select NAV until LOC is captured, then select APPR after that. Either way it still flew straight through the localiser, which it shouldn't have done - and didn't do as recent as 1.9a...

 

G 

If you fly a  flight plan with the GTN in GPS mode the gtn swaps to vloc  and then you select approach mode, for this to happen you need to have the ILS tuned in two miles before the FAF for this to happen.

bob

31 minutes ago, onebob said:

If you fly a  flight plan with the GTN in GPS mode the gtn swaps to vloc  and then you select approach mode, for this to happen you need to have the ILS tuned in two miles before the FAF for this to happen.

bob

Normally at that point I'd be in GPS mode as you will notice I wasn't receiving the localiser initially - however, as I was testing the NAV mode rather than GPS I had it in VLOC from the start. I was aware it auto switches, although didn't realise about having it tuned 2 miles before the FAF  that's useful to know.

 

G

Hi Everyone!

Please take note of the following issues after latest updates.

1.- The Cockpit Flashing Issue Fix has not been included in recent updates. Every time that there is an update we, 32 bit users, have to run the fix

2.- The DME in the VC when tuned N1, displays distance to next waypoint instead of distance to tuned VOR/ILS

Thanks,

Best Regards,

Roberto

2 hours ago, Ralvarez232 said:

2.- The DME in the VC when tuned N1, displays distance to next waypoint instead of distance to tuned VOR/ILS

Thanks,

Best Regards,

Roberto

Roberto,

That will be true if you are in GPS mode because in GPS mode P3D and FSX substitutes the GPS signal for the tuned NAV1 signal (that is, the NAV1 signal is replaced with the GPS signal). However, when in GPS mode you still can tune the DME gauge to NAV2 to pick up the signal NAV2 is tuned to.

I suppose an alternative would be to have the DME gauge show nothing for NAV1 when in GPS mode.

Al

Edited January 22, 20206 yr by ark

12 hours ago, Gazzareth said:

From my understanding (and literally what I have always done) the correct way to do it is to select NAV until LOC is captured, then select APPR after that. Either way it still flew straight through the localiser, which it shouldn't have done - and didn't do as recent as 1.9a...

 

G 

I didn't bother mentioning in my posts, but even though the 1.9A Falcon tracked the LOC, it rarely did it accurately, and it was not uncommon to be either side of the LOC track by 1/4 dot or so. It just seems as though the AP is VERY "lazy" in it's effort to track anything. I get weird tracks to GPS course, where during a turn the AP will fly right through the course and then have to make a large correction to turn back on course. I don't know what's up, but I believe this is all AP function related, and that there is some bug in the AP logic that only affects some of us.

Somewhere further up-thread the question was asked whether we have addons other than aircraft or scenery installed. Answer: Of course...who doesn't, and none of them cause any other aircraft I own to not fly an ILS approach - A2A, Carenado (I know, who cares about Carenado aircraft), Alabeo, Milviz, etc. etc., they all have the GTN installed, and all fly an ILS just fine.

At this point I think it's back to v1.8 for me until this is sorted out.

Kind Regards,

Wow, what's up with DL's on the FSW website...I'm trying to DL 1.9B and getting 225 KB (kilobytes)\sec DL speed on my 100 Mb connection?