Post SU13 PMDG weirdness

[Bobsk8 12,835]

1 hour ago, Fiorentoni said:

You should disable crash detection in MSFS. It's fundamentally broken, especially with custom aircraft. Apart from that I guess one would simply know when he has crashed a 737, so one wouldn't need a screen to tell him that.

Crash detection has been broken for decades in MSFS. First thing I do is turn it off. 

[somiller 694]

The worst I've noticed about SU13 is when I'm at an airport with heavy traffic (PSXTraffic + RT + AIG & FSLTL models only) sounds start to break up and drop out...just like it used to be when P3D was about to crash, and it seems like MSFS is about to crash or BSD. Before SU13 I only encountered this once and never experienced it again. When this happens textures also seem to quit loading and all the ground, taxiway and runway textures turn to mud.

[halobiont 5]

I had this happen a couple of times.  Both times I turned off the FSLTL injector and it didn't happen again.  Most recently I decided to try again.  Downloaded the most recent stable version and everything was fine until short final when once again I had traffic warnings.  I used the in game FSLTL panel to remove nearby traffic and the freeze as you describe.  I did not conduct thorough testing to confirm it was the FSLTL injector but with it off I haven't had this happen again.

[somiller 694]

10 minutes ago, halobiont said:

I had this happen a couple of times.  Both times I turned off the FSLTL injector and it didn't happen again.  Most recently I decided to try again.  Downloaded the most recent stable version and everything was fine until short final when once again I had traffic warnings.  I used the in game FSLTL panel to remove nearby traffic and the freeze as you describe.  I did not conduct thorough testing to confirm it was the FSLTL injector but with it off I haven't had this happen again.

That's great, so now SU13 has improved MSFS so I can't run traffic. This is not going the right direction.

[G-YMML1 584]

On 10/2/2023 at 7:44 AM, nrunning24 said:

What are you using for AI? This has happened to myself and a few other simmers who use PSXT and RealTraffic and get a RA or TA on approach.  Solution is to set TCAS to TA only vs TA/RA haven't had it happen since.  Seems PMDG is somewhat aware of the issue but at this point its more of a ghost in the machine as there doesn't seem to be a solution outside changing TCAS modes until they figure it out.

This

[Drumcode 1,907]

On 10/2/2023 at 5:44 AM, nrunning24 said:

What are you using for AI? This has happened to myself and a few other simmers who use PSXT and RealTraffic and get a RA or TA on approach.  Solution is to set TCAS to TA only vs TA/RA haven't had it happen since.  Seems PMDG is somewhat aware of the issue but at this point its more of a ghost in the machine as there doesn't seem to be a solution outside changing TCAS modes until they figure it out.

FSLTL + AIG Models. FSLTL had an update yesterday after which I took the same flight to IAH and had no issue. Not saying the injector was at fault, but it's possible. 

[G-YMML1 584]

4 minutes ago, Drumcode said:

FSLTL + AIG Models. FSLTL had an update yesterday after which I took the same flight to IAH and had no issue. Not saying the injector was at fault, but it's possible. 

I have had the behavior that you described before SU13 as well. Switching off TA/RA on approach cured the issue. PMDG is aware of the problem.

[Alvega 2,125]

16 hours ago, David Mills said:

If you're using more than one monitor, some controllers won't respond if the last-clicked monitor isn't your main instrumentation monitor. For example, I run a separate monitor just for Little Nav Map. Whenever I click on the Little Nav Map monitor, my controller no longer works at all. No controller input is recognized. It's just as if I'd unplugged the thing. I must click the main monitor again to restore function to my controller.

That's strange, I also use a second monitor for LNM and even when I'm clicking on it all my controls work fine.

[Bobsk8 12,835]

Just now on approach to EGLL, entire cockpit froze up, FMC, AP, everything. This happened when TCAS warning started. I am stuck circling right before the gliderslope. 

[Bobsk8 12,835]

On 10/2/2023 at 1:04 AM, Drumcode said:

I gotta say, I never had any issues with the 738 ever since it was released. Tonight on final to FSDT’s KIAH AT ABOUT 2,000ft I lost control of the entire cockpit, literally everything stopped working, either using the Honeycomb Bravo or trying to click things on the screen. The only thing that worked was the axis on the Alpha and throttle on the bravo, landed but I couldn’t do anything beyond that. Hopefully it was a one off, I’ll keep monitoring.

Is anyone seeing any weirdness post SU13?

Same thing happened  to me just now, just as you described. Nothing worked, I finally had to exit MSFS.

 

[Bobsk8 12,835]

On 10/2/2023 at 7:44 AM, nrunning24 said:

What are you using for AI? This has happened to myself and a few other simmers who use PSXT and RealTraffic and get a RA or TA on approach.  Solution is to set TCAS to TA only vs TA/RA haven't had it happen since.  Seems PMDG is somewhat aware of the issue but at this point its more of a ghost in the machine as there doesn't seem to be a solution outside changing TCAS modes until they figure it out.

This freezing of everything I experienced just now when I got a TCAS RA warning. Going to use TA only from now on. 

[Drumcode 1,907]

2 hours ago, Bobsk8 said:

This freezing of everything I experienced just now when I got a TCAS RA warning. Going to use TA only from now on. 

This must be an issue introduced in SU13 and PMDG's 737, as I never experienced this pre SU13. I guess another option here is to reset the FSLTL traffic on final to avoid the warnings and now that I think of it, I had the TCAS warnings on final too! Dang, thanks Bobster for confirming the issue.

Edited October 3, 2023 by Drumcode

[pmplayer 9,589]

On 10/3/2023 at 2:12 AM, David Mills said:

If you're using more than one monitor, some controllers won't respond if the last-clicked monitor isn't your main instrumentation monitor. For example, I run a separate monitor just for Little Nav Map. Whenever I click on the Little Nav Map monitor, my controller no longer works at all. No controller input is recognized. It's just as if I'd unplugged the thing. I must click the main monitor again to restore function to my controller.

This is normal like this, happens to me all the time and i am working with three Monitors .

You have to allways click on your used on to use the mouse ect., ect.

cheers 😉

[Alvega 2,125]

1 hour ago, pmplayer said:

This is normal like this, happens to me all the time and i am working with three Monitors .

You have to allways click on your used on to use the mouse ect., ect.

cheers 😉

When David says controllers I assume he is talking about joystick, throttle, yoke, etc. I can use those even if I am clicking on the second monitor, so I don't think it's normal. Of course to use the mouse you need to click on the monitor you want to use it.

[pmplayer 9,589]

29 minutes ago, Alvega said:

When David says controllers I assume he is talking about joystick, throttle, yoke, etc. I can use those even if I am clicking on the second monitor, so I don't think it's normal. Of course to use the mouse you need to click on the monitor you want to use it.

Yes sorry, for example XBox controller works without clicking first on the used monitor..

cheers 😉