[OPEN]C++ Crash 1.2.6

[Mainstay]

Nothing but trouble atm with DCS :(

 

Had a perfect stable and never failing 1.2.5 and previous versions but since 1.2.6 i just cant seem to enjoy a stable sim.

 

I have the latest install of C++ 32/64 bit no problems before.

 

 

 

What happened :

 

Started DCS and clicked on multiplayer. Multiplayer window opened selected a mission and as soon as i selected a slot and clicked fly it crashed.

 

You can find my DXDIAG here

http://forums.eagle.ru/showthread.php?t=113447

[NineLine]

I have the latest install of C++ 32/64 bit no problems before.

 

So just to confirm, you have run the 2010 C++ installer to make sure its ok?

 

http://www.microsoft.com/en-us/download/details.aspx?id=14632

[Mainstay]

So just to confirm, you have run the 2010 C++ installer to make sure its ok?

 

http://www.microsoft.com/en-us/download/details.aspx?id=14632

 

Yes and i just did again to show its not that :(

 

[NineLine]

Is this crash random or does it happen everytime?

 

I dont know if this will help, but can you try running the 2012 C++ installer?

[Mainstay]

Crash is random Sithspawn. Ill try runtime 2012

[NineLine]

Crash is random Sithspawn. Ill try runtime 2012

 

Ok, I dont know that it will help, but I am at a loss at this point, you like others have system specs that would make mine feel shame and I have no issues at all... just missing something...

[Mainstay]

Never hurts to try i guess. Hope the pixelwizards at ED can figure out whats going wrong untill then i guess ill have to deal with the crashes. Thanks for helping

[NineLine]

Never hurts to try i guess. Hope the pixelwizards at ED can figure out whats going wrong untill then i guess ill have to deal with the crashes. Thanks for helping

 

 

Usually timeline wise we see a patch soon, so lets hope they have some stuff figured out, they are aware of the issues. These ones are tough though because they are, seemingly, random.

[MegOhm_SD]

I had a similar problem but crashes after 30 minutes. C++ Runtime error.

 

Did a clean install of DCSW and all Modules from scratch, ran the C++ installer and later repair and so far no further crashes

 

This was the 1st time I have ever had any problems like this with DCS.

[RotoFly]

I have the same problem

 

 

just for info

 

install a new your game

 

and Do not install ( C++ 2010 and 2008 Dx ) from your game

 

problem solved for my

Edited September 20, 2013 by S125

[Alireza.kh]

as long as i dont use atc (\ then F5 menu) no c++ happens,maybe there is something related to this.

[NineLine]

as long as i dont use atc (\ then F5 menu) no c++ happens,maybe there is something related to this.

 

 

Yes there are known issues with the radio.

 

http://forums.eagle.ru/showthread.php?t=113874

[Lilkiki]

Dear Pilots,

 

It seems that the crash of the C++ Runtimes has vanished after a fresh installation of Direct X et C++ Runtimes Libraries 2012 (x64). I advise you to download these files from Microsoft's website.

 

We (some members of my virtual DCS team & I) 've made some test two hours ago with ATC comm etc ..., no more crash :)

 

If this could help

[NineLine]

Dear Pilots,

 

It seems that the crash of the C++ Runtimes has vanished after a fresh installation of Direct X et C++ Runtimes Libraries 2012 (x64). I advise you to download these files from Microsoft's website.

 

We (some members of my virtual DCS team & I) 've made some test two hours ago with ATC comm etc ..., no more crash :)

 

If this could help

 

 

That's excellent info, keep us posted!

[Mattressi]

I'm constantly getting this crash too. I tried updating my C++ Runtimes to 2010 SP1, which didn't help, then C++ 2012 Runtimes, which still didn't help. I've got the latest graphics card drivers. I've got DCS:W running as administrator. I'm using Windows 7, 64 bit and I've got 8 Gb of RAM.

 

I seem to get this in all missions, with seemingly no reason. I've tried never using the radio (taking off without permission, too) and I've tried just flying straight without doing anything else (setting up and using weapons, for example). The crash is always a C++ Runtime crash (same screen as in the OP). It usually happens 10 to 20 minutes into the mission, but it doesn't seem to have a specific time where it will crash. I think the longest I've gone without it happening is 40 minutes.

 

The main things I'm doing are flying the Su-25 (not 25T) in instant mission and flying the very first mission of the campaign, over and over and over; because it always crashes. Every time I read something on here and try the mission again, thinking "surely this will be the fix". And every time, it crashes :(

 

I can't work out what's causing this. My specs seem fine (GTX 560, i5 2500k, 8 Gb RAM) and I don't experience crashes with most other games (only buggy betas, usually).

 

Is there any confirmation that 1.2.6 caused these problems? I spent most of 1.2.5 just messing around in freeflight, so I didn't fly long enough to know whether it was crashing like this or not. Is there anything else I can do to try to fix this? I literally cannot progress through the campaigns, because I can't finish a single mission due to this crash.

 

Edit: I just had a thought - in missions, I usually use time acceleration (I'm not such a hardcore realism fanatic that I enjoy flying level for 120 km in a slow-moving Su-25. Especially when it's in a mission which I've played probably 20 times). One time the game crashed when I turn it back down to real-time, but that could have just been a coincidence. But perhaps using time acceleration is bad, in the same way using ATC is? I might try playing through without it when I get some time; but I don't exactly look forward to spending 1 hour on the same mission (for the 20-something time...) without time acceleration, lol.

Edited September 22, 2013 by Mattressi

[Alireza.kh]

mattressi , there are no way to complete fix the c++ error until now, we should wait until next update.

[Mattressi]

mattressi , there are no way to complete fix the c++ error until now, we should wait until next update.

 

Yeah, I'm starting to see that. I've read a lot of posts from people saying that going back to 1.2.5 fixed everything for them. I don't really want to roll back to 1.2.5, so I guess my main option right now is to wait for 1.2.7 and hope it fixes everything.

[NineLine]

Yeah, I'm starting to see that. I've read a lot of posts from people saying that going back to 1.2.5 fixed everything for them. I don't really want to roll back to 1.2.5, so I guess my main option right now is to wait for 1.2.7 and hope it fixes everything.

 

Just a few posts up someone talked about fixing theirs....

[Mattressi]

Just a few posts up someone talked about fixing theirs....

 

As I said in my previous post, though; I tried that fix (updating my C++ Runtimes to 2012) and it didn't do anything at all for me. I'm open to suggestions, but I'm erring on the side of it being an issue with DCS, rather than my end. Maybe when I can be bothered, I'll try rolling back to 1.2.5 and see if that fixes it, but I think that will mean I won't be able to use my Mi-8?

 

I'm still looking around for other ideas to fix it, but I'm not seeing too many. I read on here that joining a multiplayer game (something I've never done, yet) fixes it for some people, so I might give that a go soon. If I find a fix, I'll let you know in this thread :)

[Mattressi]

As I said in my previous post, though; I tried that fix (updating my C++ Runtimes to 2012) and it didn't do anything at all for me. I'm open to suggestions, but I'm erring on the side of it being an issue with DCS, rather than my end. Maybe when I can be bothered, I'll try rolling back to 1.2.5 and see if that fixes it, but I think that will mean I won't be able to use my Mi-8?

 

I'm still looking around for other ideas to fix it, but I'm not seeing too many. I read on here that joining a multiplayer game (something I've never done, yet) fixes it for some people, so I might give that a go soon. If I find a fix, I'll let you know in this thread :)

 

Ok, I tried joining a multiplayer game and then playing singleplayer. I'm going to *tentatively* say that it worked. I finally managed to finish the first mission of the Su-25 campaign, since DCS finally did not crash. I'm not going to get excited yet; I'll keep flying and see if nothing happens for another few missions, before I'm ready to declare it fixed. However, it does seem to be better now. Also, I've still been using time acceleration, so it seems that it might not have been a problem.

 

I have no idea why this fix would work though. Is there any reasoning or have I just got quite lucky (it was crashing every single time in around 20 consecutive missions and now did not crash)?

[Mattressi]

Ok, I tried joining a multiplayer game and then playing singleplayer. I'm going to *tentatively* say that it worked. I finally managed to finish the first mission of the Su-25 campaign, since DCS finally did not crash. I'm not going to get excited yet; I'll keep flying and see if nothing happens for another few missions, before I'm ready to declare it fixed. However, it does seem to be better now. Also, I've still been using time acceleration, so it seems that it might not have been a problem.

 

I have no idea why this fix would work though. Is there any reasoning or have I just got quite lucky (it was crashing every single time in around 20 consecutive missions and now did not crash)?

 

Nope, I just got a crash (same runtime error as before). Guess it was just luck that it didn't happen for the first mission. Now I'm back to trying to work out other fixes.

 

Edit: Here's the last bit of my DCS log:

 

00023.821 INFO EDTERRAINGRAPHICS3: force loading finished!

00023.821 INFO EDTERRAINGRAPHICS3: Force loading pipeline 'map'. Radius 30000.000000. Pos=-164408.765625,32.686844,461922.218750!

00023.912 INFO EDTERRAINGRAPHICS3: force loading finished!

00028.941 INFO DXRENDERER: Creating Resource "Unicode" of type 5

00037.700 ERROR Trigger: can't execute trigger, err:"[string "?"]:1: bad argument #1 to 'loadstring' (string expected, got function)"

00076.532 WARNING LOG: 3 duplicate message(s) skipped.

00076.532 ERROR SOUND: source_is_playing(-1): invalid source

00127.334 WARNING LOG: 3 duplicate message(s) skipped.

00127.334 INFO TERRAIN: lObjectFire::lObjectFire for building id=268618631

00140.284 ERROR SOUND: source_is_playing(-1): invalid source

00144.517 INFO TERRAIN: lObjectFire::lObjectFire for building id=268618606

00152.775 ERROR SOUND: source_is_playing(-1): invalid source

00250.733 WARNING LOG: 5 duplicate message(s) skipped.

00250.733 INFO TERRAIN: lObjectFire::lObjectFire for building id=268618604

00253.492 ERROR SOUND: source_is_playing(-1): invalid source

00258.565 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50 piloteject.bmp

00259.303 INFO TERRAIN: lObjectFire::lObjectFire for building id=268581460

00261.296 INFO TERRAIN: lObjectFire::lObjectFire for building id=268618612

00288.293 INFO TERRAIN: lObjectFire::lObjectFire for building id=268581460

00288.928 WARNING LOG: 3 duplicate message(s) skipped.

00288.928 ERROR SOUND: source_is_playing(-1): invalid source

00324.326 WARNING LOG: 2 duplicate message(s) skipped.

00324.326 INFO TERRAIN: lObjectFire::lObjectFire for building id=268618612

00334.285 INFO TERRAIN: lObjectFire::lObjectFire for building id=268618604

00334.407 INFO TERRAIN: lObjectFire::lObjectFire for building id=268618624

00334.901 ERROR SOUND: source_is_playing(-1): invalid source

00351.544 WARNING LOG: 13 duplicate message(s) skipped.

00351.544 INFO TERRAIN: lObjectFire::lObjectFire for building id=268618610

00352.203 ERROR SOUND: source_is_playing(-1): invalid source

00362.133 WARNING LOG: 10 duplicate message(s) skipped.

00362.133 INFO TERRAIN: lObjectFire::lObjectFire for building id=268618609

00362.786 ERROR SOUND: source_is_playing(-1): invalid source

00377.108 WARNING LOG: 12 duplicate message(s) skipped.

00377.108 INFO TERRAIN: lObjectFire::lObjectFire for building id=268618604

00413.191 WARNING LOG: 2 duplicate message(s) skipped.

00413.191 ERROR SOUND: source_is_playing(-1): invalid source

Edited September 23, 2013 by Mattressi

[NineLine]

Were you using time acceleration at the point of the crash again?

[Mattressi]

Were you using time acceleration at the point of the crash again?

 

Yep. Do you think that's what it could be? I'd been using it (and at a higher acceleration) for probably 2 minutes, then reduced it and after a minute it crashed. I guess I should try playing without it; but the 100+ km long stretches in the Su-25 campaign can be very dull at normal speed, lol.

[NineLine]

Yep. Do you think that's what it could be? I'd been using it (and at a higher acceleration) for probably 2 minutes, then reduced it and after a minute it crashed. I guess I should try playing without it; but the 100+ km long stretches in the Su-25 campaign can be very dull at normal speed, lol.

 

 

Please try without and let me know if you still crash, tonight when I get home I can try and reproduce, steps to reproduce are the only way we can get these bugs fixed up. lease let me know. If it crashes at regular speed, please note any triggers, actions, etc that might have occurred at the same time.

[Mattressi]

Please try without and let me know if you still crash, tonight when I get home I can try and reproduce, steps to reproduce are the only way we can get these bugs fixed up. lease let me know. If it crashes at regular speed, please note any triggers, actions, etc that might have occurred at the same time.

 

Sure thing. I don't have time to test it more now, but tomorrow I should be able to. Thanks for your help :)

 

Edit: I just had a thought - I might have used too high of a time acceleration. I pressed the key combo to increase it a little too much and got to the point where I had ~3 to 5 FPS. I then turn it down and flew like that for 2 minutes, and then turned it down some more. So maybe there's some kind of maximum time acceleration which is stable? I was using it in the missions before when I didn't get crashes, but I might have just not been turning it up so high.

Edited September 23, 2013 by Mattressi