Screen freeze in both 32 & 501 squadron campaigns

[RupertVonHentzau]

Originally Posted by bolox

...
The freezing- is it always the same mission/place in mission?
If it is let me know which mission(s) it is and I'll have another look to see if anything has changed in 1.08 (or are you running these on 1.05?)

PC certainly has a bit to do with these campaigns- they both like 100+ AC for some missions

Personally if this happens to me I refly the mission (maybe going to normal speed earlier- if you must use time acceleration )

Just downloaded and installed "32_Squadron". Flying the first mission I experienced a runtime error/black screen as soon as enemy planes were reported (not even in sight). No time acceleration - so even more frustrating to be kicked out of a mission that took so long up to here.

Please check my specs in the post above: it is a notebook, but never fails to play default missions and campaigns with high settings.

Should I simply forget about the more challenging hand-made campaigns?

[bolox]

just tested this(32sqn campaign 1st mission) on my rig- and also got a runtime error at a similar point

Taking a look at system events (control panel>system and security>admin tools>view event logs) there seem to be 2 events- a .net runtime event ID 1026
leading to an application error in launcher.exe ID 1000 with core.dll being the faulting module


Now I'm certain that this ran fine on 1.05
There was something on reverting dot net runtimes as a fix with beta patches but I can't find it atm (I had done this )

The 'good' thing about this is it looks like a reproducible fault so in theory it should be easier to fix.

Time to send crash dumps to Ilya again
ishevchenko@1cpublishing.eu

As to continuing with user made campaigns- well atm I'm testing a new 109 campaign and am not experiencing any crashes on that- I am wondering if this is Hurricane related???

For the record my rig is i7 920@4.0, 580 gpu (1.5gb), 6 fb ram win7 64bit running 1.08beta

[RupertVonHentzau]

Originally Posted by bolox

...
There was something on reverting dot net runtimes as a fix with beta patches but I can't find it atm (I had done this )

The 'good' thing about this is it looks like a reproducible fault so in theory it should be easier to fix. ...

Thank you very much, bolox.

I am kind of relieved to hear this is something that can be fixed. If you find a solution I very much appreciate the hint what to do.