Jump to content

Server crash and Runtime error, Plz read before posting.


Cougar

Recommended Posts

Hello to all,

 

Recently we have seen an increase of post about multiplayer crashes or c++ runtime errors and we might have found the step to reproduce what you all are experiencing at the moment.

 

c++ Runtime error

 

Singleplayer or Playing while being the host of a multiplayer server, while finishing spawning in the cockpit and the mission is heavy:

 

You might get this error if you are working on communication for example with the ATC. If you are pushing F1 inbound for an airfield but you realized you made a mistake and change quickly to another airfield "F1 inbound" without the first airfield responding to you the runtime error will happen.

 

So my advise is to wait to get a response from the party your trying to reach before pressing another communication options to avoid this problem.

 

Multiplayer server crash

 

The problem is basicaly the same as the above but with a little twist and the problem is clients side only. Let's say you work the communication and do the same mistake as mentionned above the communication will stop working without the runtime error (You'll be able to send request but you won't get any response). Lets say you've landed at your airfield and want to spawn in another aircraft, you hit ESC to bring the plane selection lobby and try to double click the aircraft slot you want. It will make the server crash instantly or shortly after.

 

Again my advise is to wait to get a response from the party your trying to reach before pressing another communication options to avoid this problem.

 

 

I just would like to ask you to restreint yourself from posting more Runtime error or server crash thread if you think the above could have happened to you or your server until the problem is solved.

 

Thank You

 

Cougar

  • Like 1

sigpic4165_1.gif

attachment.php?attachmentid=36435&d=1266786388

Link to comment
Share on other sites

Nice to see that were closing in on the problem :thumbup:.

 

I just had another crash in the SU-25A on the ESL server that seems related to communication. Because of this post I didnt use the communication menu at all for take off. After taking out some targerts I was returing to Kobuleti, the following happened:

 

1. Opened communications menu.

2. F5 for ATC.

3. F12 to close the panel again (didnt send anything!).

4. F10 for the map, since I wasnt sure it is Kobuleti im approaching.

5. Opened communications menu again.

6. F5 for ATC

7. F1 for Inbound, sent the request and also got the answer from ATC with directions.

8. Couple of seconds later, windows error message sound, image freezes and I have a normal mouse arrow.

 

Unfortunately I somehow closed the error message that popped up in the background while minimizing DCS, so I dont know if it was a runtime error.

Link to comment
Share on other sites

Nice find, though, does using the rearm menu also count as an radio function?

 

Cause i never use ingame ATC or anything like that but get the same crashes.

(multiplayer)

 

Yes it is as when you use the menu and click ok....the ground crew respond to you. If you request again without them stating that rearming or refueling is complete you will have hints that it might crash if you dont get anymore response and try to double click another aircraft for example.

 

At the end we are talking about the same problem, just different way to get to the finish line. :)

 

 

Cougar

sigpic4165_1.gif

attachment.php?attachmentid=36435&d=1266786388

Link to comment
Share on other sites

Not sure if it helps but it might be worth to let you know:

2 installations 1.2.6 (non Steam) so far - both tend to crash. Both were cured by installing the Mi-8 module. On one installation the Mi-8 is in use and activated on the second PC it is just there and not activated (other account).The Steam installations on the same PCs didn´t crash.

Another fresh install didn´t solve the problems either (both PCs/different downloads).

Edit 16.09.2013: on second PC the DCS World started to crash again .... so it might has been just a coincidence that the installation of the Mi-8 module brought back the stability to PC number one


Edited by BrunoDerRabe
Link to comment
Share on other sites

nice find. My server crashed today with run.dll error when I was pushing radio buttons... I can't remember if I gave commands and didn't wait but it could be... I'll be careful tomorrow

[sIGPIC][/sIGPIC]

I5 4670k, 32GB, GTX 1070, Thrustmaster TFRP, G940 Throttle extremely modded with Bodnar 0836X and Bu0836A,

Warthog Joystick with F-18 grip, Oculus Rift S - Almost all is made from gifts from friends, the most expensive parts at least

Link to comment
Share on other sites

Here is my Crashlog. All my Server crashes has the same crashlog file...

 

# -------------- 20130915-132708 --------------

 

# E06D7363 at FD9D940D 00:00000000

00000000 00000000 0000:00000000

FD9D940D 001DEB70 0000:00000000 RaiseException()+3D

732A142D 001DEBE0 0001:0006042D C:\Windows\system32\MSVCR100.dll _CxxThrowException()+81

 

7336F986 001DEC30 0001:0000E986 C:\Windows\system32\MSVCP100.dll ?_Xout_of_range@std@@YAXPEBD@Z()+36

 

E77B5486 001DEC70 0000:00000000 ??4wRadioTransmitter@@QEAAAEAV0@AEBV0@@Z()+136

 

E77B7A94 001DECE0 0000:00000000 ?receiveMessage@wCommunicator@@UEAA_NAEBV?$Ptr@VwMessage@@@Mem@@W4RadioMessageEvent@@@Z()+234

 

E77F21A2 001DED30 0000:00000000

?sendMessage@wCommNet@@QEAAXAEBV?$Ptr@VwMessage@@@Mem@@IW4RadioMessageEvent@@@Z()+82

 

E77B168F 001DED60 0000:00000000 ?sendMessage@wCommunicator@@MEAAXAEBV?$Ptr@VwMessage@@@Mem@@W4RadioMessageEvent@@@Z()+1F

 

E77B3E3C 001DEDA0 0000:00000000 ?finishTransmition@wCommunicator@@UEAAX_N@Z()+5C

3F94290E 001DEDD0 0000:00000000

3F999A01 001DEEA0 0000:00000000

E933EA9D 001DEEE0 0000:00000000 ??1Reader@Mail@@UEAA@XZ()+27D

E70795DE 001DEF50 0000:00000000

E70796B1 001DEFA0 0000:00000000

E707C088 001DF140 0000:00000000

E7089F57 001DF1A0 0000:00000000

E709F403 001DF1D0 0000:00000000

E70B3A73 001DF200 0000:00000000

3FA2AA45 001DF260 0000:00000000

3FA40A14 001DF290 0000:00000000

3FA408EB 001DF2C0 0000:00000000

3FAD4B38 001DF330 0000:00000000

3FAD6139 001DF930 0000:00000000

3FAD8DAB 001DF9E0 0000:00000000

76F4652D 001DFA10 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D

773EC541 001DFA60 0001:0002B541 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

Link to comment
Share on other sites

  • 11 months later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...