4.11: Some Missions Locking-Up

[MicroWave]

Originally Posted by Aviar

Are you sure NOTHING was done regarding this issue? After applying the 4.11.1 patch, I can now play my 'bad' missions in coop mode without any lockups.

The only problem I still have is loading these big maps into the FMB. For instance, the Solomon maps refuse to load most of the time. Once in a while they will load but I haven't figured out the 'trick' (if there is one) to getting them to load every time.

However, I'm happy that now my Solomon map missions are actually playable without locking up.

Aviar

You've been very helpful in providing missions to test, so we did manage to fix some stuff. But for example 'Stress test mission' still causes lock up after some time.
I'm not sure what's going on with DCG missions lockups that I see reported.
I guess I'm off to play some DCG campaigns.

[yeikov]

In case it helps, I've attached the mission that caused my lock ups in 4.11.1 (generated by DCG 3.47 beta6).
I've run it 3 times now, 2 times it locked up after ~30 min flying, the other time I tried the workaround explained by Jameson here and it did not.

Thanks for the support, and for the great work you're doing!

[Aviar]

Originally Posted by yeikov

In case it helps, I've attached the mission that caused my lock ups in 4.11.1 (generated by DCG 3.47 beta6).
I've run it 3 times now, 2 times it locked up after ~30 min flying, the other time I tried the workaround explained by Jameson here and it did not.

Thanks for the support, and for the great work you're doing!

That 'workaround' may or may not work for offline play but obviously could not be used with an online mission or a mission played offline in Coop mode.

On another note and just out of curiosity, what does this part of the 'workaround' mean? ---->

"The only thing I've found that works is to pause when it starts to lock up..."

In particular, what does "...when it starts to lock up..." mean? When I was experiencing lockups (in 4.11), the mission would simply lock up out of the blue. There was no 'start' or warning. So, once the mission was locked up, are you saying that following this 'workaround' would unlock the mission?

*Could it be that the person who wrote the 'workaround' instructions MEANT to say '...The only thing I've found that works is to pause BEFORE the mission usually locks up..."....?

Aviar

[yeikov]

Hi Aviar,

Yes, you're right, it's just a temporary (I hope ) "fix" just for offline missions.
I also did not understand the part "when it starts to lock up", for me it happens suddenly too. So the time I tried I just did it at the start of the mission, and as I said I had no lock up.
Maybe just luck, 3 tries are not a very thorough testing... But for my part, I'll include that in my engine start and warm up procedures from now on

Y.

[jameson]

Aviar, problem is like when in some missions planes spawn and there is a slight lock up, but it reoccurs at ever decreasing time periods until "applications tried to read memory at xxxxxxxx, memory could not be read" message appears. Thus I pause the game to stop it fully locking up. I have not had the problem onine but then it's been a while since I been online, I did not think this affected online play, but will stand corrected if this is the case. Regards.

[Aviar]

Originally Posted by jameson

Aviar, problem is like when in some missions planes spawn and there is a slight lock up, but it reoccurs at ever decreasing time periods until "applications tried to read memory at xxxxxxxx, memory could not be read" message appears. Thus I pause the game to stop it fully locking up. I have not had the problem onine but then it's been a while since I been online, I did not think this affected online play, but will stand corrected if this is the case. Regards.

It looks like you are having a different issue than I was having. I never had anything like "...ever decreasing time periods..." or any kind of error messages once my game locked up.

Also, my lockups were occurring online as well as offline, as I host a lot of coop missions.

Aviar

[fabianfred]

Since I recently restarted playing Il2 after a couple of years rest I had to start from scratch. I have two installs. One is 4.11.1 with HSFX 6 and the other is 4.10 with SAS DBW.
I have several of my old favourite missions...all of which are large and what you would call stressfull. They either will not run or get the lock-ups after about 8 minutes into the mission.
This happens on both installs.
I am now using Win7 but previously when they ran OK I was on WinXP and that was with 4.09 and 4.10 and HSFX 5.