Well, it worked.

For a while...

Deleted the 1C folder (with all the settings and saved games [not that were any for obvious reasons]) and the game started fine. Not actually flying, because I couldn't be bothered to put my TrackIR hat on, and plug in the pedals and joystick; just the menu screen.

Changed some graphics and audio settings, exited and then started again.

All fine.

Then changed lots of control options, saved the file (in that folder, of course), and exited the game.

On re-starting the game, launcher crash during Ubi splash screen.

I think I'll just put this game away for a few months until the myriad problems it seems to have are sorted out, or at least until the deal breakers like this are.

Back to RoF and holding breath for CM:BN.

R

Deadstick you are a champion. All these other fools that just want to bag out the ones having trouble and you stepped up to the mark with excellent advise. As you as I did what you suggested it worked. Thank you heaps mate.
Now I only have to work out how to activate my pedals and get the joystick part of my x52 to work and I'm off. Thanks again mate.

It was good advice, especially since there was nothing coming from official channels, and since it is clearly a problem many users are experiencing.

Unfortunately it didn't work for lots of other people.

Time for 1C/Steam to step up to the plate, I think.

R

I'm one of the unfortunates who is still having problems despite trying ALL of the above. This think does not appear to like my system at all.

Well I am happy to report that, after following the redist advice and switching off the AVG resident shield I have stuttered aloft!

The machine as it stands is way below minimum spec (core 2 Duo 8500, 4GB DDR2 and 9600GTE 512MB) and CloD ran (badly).

My table is stacked with an i5 760, GTX 550 and associated mobo and RAM which I will try to install shortly :)

Happy man, but it was a fight LOL

Me too - tried everything.

Worst thing for me is that we're not hearing anything official.

I know virtually everyone seems to be having deal-breaking performance issues, but there are still some of us, who can't even start the game (at least not consistently).

I really wish I hadn't pre-ordered and had waited until all this storm had blown over with the requisite patch(es), but I wanted to support 1C. Some teething troubles are inevitable, but this release seems thoroughly porked at present.

R

where is the support here !!!!

Are we going to get a reply from 1C ?

the following is my crash data


Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: launcher.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: 4d6e3d08
Problem Signature 04: core
Problem Signature 05: 1.0.0.0
Problem Signature 06: 4d92ff5c
Problem Signature 07: e26
Problem Signature 08: 0
Problem Signature 09: System.AccessViolationException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 3081
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789


WHERE IS THE SUPPORT !

Stupid question, but where do you get that information from?

From Windows Event Viewer I got the following:

Faulting application name: Launcher.exe_Launcher, version: 1.0.0.0, time stamp: 0x4d6e3d08
Faulting module name: nvd3dum.dll, version: 8.17.12.6724, time stamp: 0x4d64b610
Exception code: 0xc0000005
Fault offset: 0x005a78bc
Faulting process id: 0x1594
Faulting application start time: 0x01cbf06e3a71bf48
Faulting application path: d:\program files (x86)\steam\steamapps\common\il-2 sturmovik cliffs of dover\Launcher.exe
Faulting module path: C:\Windows\system32\nvd3dum.dll
Report Id: 85e64adc-5c61-11e0-b0e8-00242153ac33

Looks like nvd3dum is the problem, and I'm guessing it's an NVidia file.

Will seek advice...

The information is from the Lanucher dialog window under the dropdown - "View problem details".
I think its default windows, maybe .NET ?