Flying the same route at the same time but with Ai enabled. Lockup occurred at one of the usual places. Advice from AIG is to remove half the BGL files and see if the problem is resolved. If it isn't then the problem lies in one of the remaining files.

Continue the binary chop until the erroneous aircraft is found and then tell AIG. But running Ai Companion I can reduce the possible suspects as it's a quiet part of the world with only a few Ai. Maybe one of these.

Closing in on a frustrating problem.

16 hours ago, Ray Proudfoot said:

@spilok, Is your monitor capable of 30Hz without forcing it with NCP? I suspect not. But mine is and it delivers a quality image with no jerkiness or stutters.

There's no point turning off VSync to get the highest possible fps. The sim becomes juttery as the CPU is working flat out.

The number of Ai at Heathrow means I actually have to limit the number to 160 to maintain 30fps. If I didn't the Ai would be over 220 and the frame rate would drop as the CPU would be incapable of delivering 30.

With no Ai I probably could get 60fps but where's the fun in being the only aircraft in the airport? 😁

You're right.  I have to force it.  The movement in the sim was sluggish and even the mouse movement was jerky.  So, my LG monitor won't do it on its own. I guess I'm just trying to eliminate possible issues in an effort to help you. I'm sure you'll eventually find your culprit.

Stan

19 minutes ago, spilok said:

You're right.  I have to force it.  The movement in the sim was sluggish and even the mouse movement was jerky.  So, my LG monitor won't do it on its own. I guess I'm just trying to eliminate possible issues in an effort to help you. I'm sure you'll eventually find your culprit.

Stan

Stan, next time you're shopping for a monitor choose one with either variable refresh rate or 30Hz. Gaming monitors with 144Hz etc. aren't really suitable for flight sim.

It looks like a bad AIG Ai file is responsible for the lockups. Process of elimination to identify the one(s) responsible. A relief really since it's nothing to do with the computer hardware. That is a relief.

3 hours ago, Ray Proudfoot said:

Stan, next time you're shopping for a monitor choose one with either variable refresh rate or 30Hz. Gaming monitors with 144Hz etc. aren't really suitable for flight sim.

It looks like a bad AIG Ai file is responsible for the lockups. Process of elimination to identify the one(s) responsible. A relief really since it's nothing to do with the computer hardware. That is a relief.

I absolutely do love my LG 4K IPS 32" monitor, though.  It is a 60hz monitor, and I am definitely aware of Gaming monitors with the high Hz levels.  I did try a few out when I was shopping and returned every one because the quality of the image didn't measure up. I also use 4096 x 4096 in the sim, and the image is just great. 

That is great relief that you found the culprit.  I never used AIG, as you know (we did a comparison once - you and I) and I am still using UT LIVE; Although it's not as prolific in aircraft everywhere, it suits my purpose of having sufficient aircraft and vehicles at all airports and in the air.

Stan

Edited December 27, 20232 yr by spilok

I've been thinking about this lockup problem overnight. This is happening regularly with my new PC. For a time I thought it was caused by an overheating problem but after using HWINFO to log things that is not the problem. Then an Nvidia driver update seemed to fix it but that wasn’t the cure either.

When I first set up this new PC in mid-October I wasn't getting this problem of lockups despite all my AIG flight plans being active. Then something changed and the lockups started.

Thinking back the only change I made was installing 5.4. Previously I had been running v5.3 HF2 both on this computer and for many months on my old one.

I never got these lockups on the old computer.

Now despite the last update to v5 being just a point update I believe something significant was changed in how it treats flight plans of Ai aircraft. So much so that it causes these lockups. I can't think of any other explanation.

I'm giving serious consideration to reverting to 5.3HF2. Before I do that I'd be interested in your thoughts.

I've been a long time fan of AIG but as things stand it's becoming frustrating to use it with 5.4.

Ray what was the reason for you moving to v5.4?

 

Just another data point -  I have the latest version of AIG loaded (the one with the new UI)  with various flightplans of airlines installed (around 80 right now) and I don't experience any lockups. I am using v5.3 HF2.

 

 

27 minutes ago, 787flyer said:

Ray what was the reason for you moving to v5.4?

Just another data point -  I have the latest version of AIG loaded (the one with the new UI)  with various flightplans of airlines installed (around 80 right now) and I don't experience any lockups. I am using v5.3 HF2.

Mark, there were problems with flashing clouds using ASP3D / ASCA that Damian said would be “better” with 5.4.

If you have just 80 then that’s pretty modest. I have a couple of hundred. The Verify option doesn’t check for bad data, just missing data. It’s not really helpful in identifying where the problem lies.

But critically you’re using the version I was running for a long time without ANY issues. I think the problem lies with changes in 5.4. Thanks for confirming no issues with 5.3HF2. 👍

I recently moved to 5.4 attempting to fix an issue where the FSLabs crashes P3D on exit according to Windows Error Reporting, something which I cannot determine the cause of and have reported to FSLabs. Since updating the client, I started getting terrain.dll crashes during flights, so have restored the pc back to 5.3 HF2. I'm taking the approach that "if it works don't fix it". As far as I recall, the changes to 5.4 were fairly minor and not of much interest to me - a lot of GPS stuff for default aircraft.

Edited December 28, 20232 yr by simfan1983

19 minutes ago, simfan1983 said:

As far as I recall, the changes to 5.4 were fairly minor and not of much interest to me - a lot of GPS stuff for default aircraft.

Hmmm, interesting. I wonder if that has affected Ai aircraft.

I had a terrain.dll CTD recently but I was slewing fast and low around Sydney so put it down to that. Normal flying hasn't resulted in any.

Almost completed the 30Gb download of 5.3HF2. I knew I should have kept it! 😁

1 minute ago, Ray Proudfoot said:

Almost completed the 30Gb download of 5.3HF2. I knew I should have kept it! 😁

I only upgraded / downgraded the client - am always nervous about doing the Full Monty!

4 minutes ago, simfan1983 said:

I only upgraded / downgraded the client - am always nervous about doing the Full Monty!

Pretty easy really. Uninstall Scenery, then Content and finally Client. Then install in the reverse order - Client, Content and Scenery.

You could probably also uninstall the final P3D entry in CP / Add/Remove without issues. Just remember to retain the licence of course.

2 hours ago, Ray Proudfoot said:

But critically you’re using the version I was running for a long time without ANY issues. I think the problem lies with changes in 5.4. Thanks for confirming no issues with 5.3HF2. 👍

Ray, you seem to make a lot of conclusions based on very little data. I'm glad you've tracked down the issue. My .02 is before you start making significant changes to your sim setup and changing more variables, enjoy what you have. If you get more lockups, then consider a change.

And if you do go back to 5.3HF2, I'd restore the offending AIG package and see if you can get a lockup. I suspect you will.

Cheers

20 hours ago, Ray Proudfoot said:

Gaming monitors with 144Hz etc. aren't really suitable for flight sim.

I think this statement, on its own, is a little inaccurate. There's nothing inherently wrong with a high refresh rate monitor, nor is it incompatible with a flight simulator. I have a 165Hz monitor, and it works great - except that in flight sim you're not going to get those high refresh rates and you're paying for something you may not use.

Variable Refresh Rate, as you point out, is the key. I have my frames capped at 59fps via the drivers and that's easily in my monitor's GSync range. As more modern sims like P3Dv6 and MSFS include DLSS and eventually Frame Generation, it won't be unreasonable to have smooth 60 or even 120Hz video in our sims.

No reason not to get a monitor that supports it.

Cheers

1 hour ago, Ray Proudfoot said:

Hmmm, interesting. I wonder if that has affected Ai aircraft.

I had a terrain.dll CTD recently but I was slewing fast and low around Sydney so put it down to that. Normal flying hasn't resulted in any.

Almost completed the 30Gb download of 5.3HF2. I knew I should have kept it! 😁

I know my system cannot compare to yours ! but I have been running V5.4.9.28482 with AS/ASCA and AI (FSUIPC limit 50/150) since it came out and nothing untoward has happened regularly. Of course, I have had the odd blip, but all in all it has behaved admirably. 

I just hope for whatever is left of your sanity, that this downshift will help.

Keep us posted, we follow with bated breath.

One of the issue with these kind of problems is the lack of useful error reporting. I spend a considerable portion of my time keeping P3D running - not helped by other software updates introducing new issues. I'm still not ready to move to MSFS though.....