4.11: Some Missions Locking-Up

[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.

[Aviar]

Originally Posted by 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.

Just to clarify, I did not say this happens 'often' to me.

As I mentioned earlier, I pretty much detailed everything in my first post. I know it is a little long but if it is read closely, the info is in there.

As I stated, these seem to be a combination of 'big' maps and 'big' missions. The Solomons map(s) are just about the biggest maps in IL-2. So when you load even the blank map, your computer is already being taxed. If you combine that with a very busy (big) mission.....well you see that could eventually be an issue. (Again, I stated that I have 'smaller' missions on the Solomons map that work just fine in 4.11.)

Over the years, I have seen many posts that a certain individual could not load a particular map or mission....usually because of RAM issues. This is not unusual. Even the best and fastest computers have a physical limit.

***The strange part of my issue is that the same missions that are locking up in 4.11 are playing perfectly fine in 4.10.1....on the same computer.***

So, my common sense is telling me that my computer is fine and there may be an issue with 4.11. Does that make sense to you?

* Maybe all the new calculations for FM, AI, head tracking, moving plane parts online, etc. are stressing the IL-2 code? Too much info?

Aviar

[IceFire]

Definitely makes sense.

Yes the Solomons map does appear to be quite taxing. We tried to use it for a scenario on Battlefields1 and while the map ran fine for most players we had to pull it because some players weren't able to load past 90-92% and others would load but had missing textures on the ground or on planes. It's too bad because it's a beautiful map but some machines I guess are not quite up to the task.

I would agree with you that it is some sort of game related issue. In particular because the lockup does not affect the hardware. The game does lock up but you can alt-tab out and shut down the IL2 process without difficulty or loss of stability... and given that it happens on more than one system it's not likely to be a system specific problem either.

So big map and big missions...I'll have to have a look. See if I can recreate the same issues on other mission examples.

[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.