4.11: Some Missions Locking-Up

[Aviar]

Originally Posted by HundertneunGustav

RAM check for hardware failure? OS environment? GC temps? stuff like that, hardware oriented?

Thank you for replying. However, did you read my entire post?

I did state that I have run (and re-tested) the 'bad' missions in 4.10.1 and UP3 RC4 without any lock-ups at all. I'm only getting lock-ups in 4.11.


*As an update, I have found another 'big' mission (Slovakia map) that locked up on me. Again, this mission has never locked-up in 4.10.1. So I'm kind of stumped, as the problem seems to be connected to 4.11....not my computer. Has anyone had the chance to see if there might be some sort of memory leak in 4.11?

Aviar

[MicroWave]

I can get the lock-up in 4.11 with the mission you posted.
We'll see what can be done about that.

[Aviar]

Originally Posted by MicroWave

I can get the lock-up in 4.11 with the mission you posted.
We'll see what can be done about that.

Ok, that's interesting. What would be more interesting is if you could try what I did and run the same mission in 4.10.1. On my computer, all of the 'bad' missions ran perfectly fine in 4.10.1.

Aviar

[KG26_Alpha]

Originally Posted by MicroWave

I can get the lock-up in 4.11 with the mission you posted.
We'll see what can be done about that.

What point did the mission lock up.

I have run that mission over 10 times now and it never locks up ?

Only a lag pause as mentioned in my above post.

[Aviar]

Still, there seems to be something strange in my 4.11. As I play more IL-2, I am finding more missions that are locking up. Just today I hosted a coop that locked up about 5 minutes into the mission.

Even right from the start I could see something was wrong. I was getting a slight freeze about every 10 seconds. This is unusual and never happened in 4.10. As I mentioned, it eventially just locked up. Now, this is a mission I have hosted dozens of times over the years with no problems at all.

I immediately fired up 4.10.1 and played the same mission. It was as smooth as ever and did not lock up at all. I completed the mission without any issues.

I don't know what it is, but there is some sort of paging or memory issue with my 4.11 install. Another thing that is happening is with the screenshot feature. In 4.11, sometimes when I press the key for a screenshot, the game will lock up. Again, this does not happen in 4.10.

Aviar

[IceFire]

That's really weird Aviar... before and after release I went through all kinds of missions testing them out with a variety of different sequences, scenes, and other scenarios and never did I have that happen.

Does this only happen when it's being hosted as a coop or does it happen if run through the FMB or a single mission as well? I skimmed through all of the posts and I didn't see that mentioned. My apologies if you did mention it. I'm going to test the mission in a few!

[Aviar]

Originally Posted by IceFire

That's really weird Aviar... before and after release I went through all kinds of missions testing them out with a variety of different sequences, scenes, and other scenarios and never did I have that happen.

Does this only happen when it's being hosted as a coop or does it happen if run through the FMB or a single mission as well? I skimmed through all of the posts and I didn't see that mentioned. My apologies if you did mention it. I'm going to test the mission in a few!

Thanks for being concerned. I know my first post was a little long, but the answer to your question at the bottom of that post.

In short, it happens basically all the time. Online coops, offline coop testing and then simply running the mission straight from the FMB. The latter is the quickest way to test it. Just accelerate it to 2x or 4x and let it run. Changing views and scrolling through the different flights sometimes seems to accelerate the lock-up time. This is why it seems like some sort of paging or memory issue. Many times it will lock up as I am moving my mouse or zooming the view in/out.

I want to thank you for giving of your personal time in the testing of the beta. I know it's not easy. However, I played the heck out of 4.11 for weeks before I found the first lock-up. It was simply because I had not played one of these 'bigger' missions in my folder. It's just like a bug that gets by all the testers and gets released in the final. It happens....we all know that.

But even now I'm still not comfortable calling it a 'bug'. Maybe there is something unique to my computer and eventually I can resolve the issue.

Aviar

[IceFire]

Tested it and confirmed. Locked my system too. You say this happens often to you... any commonality between the missions that this occurs in? Same map? Same type of complexity? You do have a lot of aircraft and quite a few vehicle waypoints... more than I tend to use on an average basis. Just thinking out loud.

[KU_Rigamortis]

I get the same IL-2 failure to respond with the Solomon's map. Running a rather large (126kb) dogfight mission and testing in FMB using 2x, 4x, and 8x acceleration to verify sequencing of AI.

I can exit out of FMB and back to the main IL-2 screen, but when I then click any other screen button, I get a second mouse pointer and a blue spinning circle. IL-2 never responds beyond this point and I have to CTRL-ALT-DEL to exit.