Jump to content

Recommended Posts

Posted (edited)

Had a couple crashes recently- granted on an older mission that was reopened and resaved under a new name.

 

It happened twice on the same mission- All pertinent files are included.

 

Maybe there is a tidbit in here that someone could comment on?

 

Thanks guys.

 

Edit: Tossed in the last tacview file... just in case. The one before it was quite a bit bigger so I'll post it if needed through my gdrive link.

crash 03.03.13.zip

Tacview-20130303-205824.txt.zip

Edited by ENO

"ENO"

Type in anger and you will make the greatest post you will ever regret.

 

"Sweetest's" Military Aviation Art

Posted (edited)

This error is occurring constantly on my server and I'm getting more crashes now than with 1.2.2.

 

Seems to happen when AI resources are engaging targets but short of that I can't seem to nail down exactly what is happening.

 

I've checked out the tacview files associated with these crashes and in one the crash happened while AI Zsu23-4 was shooting at what I believe was a CA controlled JTAC unit on a weapons hold (JTAC is supposed to have a hold order and couldn't have moved without direction).

 

The other one happened a split second before an SA-19 hit a SU-25 controlled by a player.

 

I can provide the tacview files for both those crashes if desired... I'm not sure if they're linked.

 

Anyway, here are some crash logs and supporting documentation as requested.

 

Having some trouble uploading- going to try again

crash 03.06.13.zip

Crash 03.09.13.zip

Edited by ENO

"ENO"

Type in anger and you will make the greatest post you will ever regret.

 

"Sweetest's" Military Aviation Art

Posted (edited)

And another.

 

I have asked the guys who were playing at the time to send me their logs as well so you can see the server and client side logs. I have to add mine to the mix and I will once I get logged into that comp again.

 

One of my members made a point to mention that mine and the 76th are the only ones that seem to run 24 hours that continue to crash on a relatively steady basis- and he (blooze) also pointed out that we're both on the west coast.

 

Is this just a coincidence or is there some common handoff point that is collapsing somewhere in the middle?

 

Thanks...

 

 

 

 

EDIT: c0ff has contacted me by my email request and did say he pointed it at the right people. I'm going to keep supplying logs here in hopes that it'll help.

 

I'm having some trouble with the attachment manager... but I have a couple extra files to add to this crash file. Will do it once that file manager stops taking a dump

 

Edit again:

 

I've updated the crash.zip file to include a couple of the crash logs from Gordo. The only one missing is from my client machine- but judging by what c0ff was saying those files already included just point to normal dcs bugs and "no magic."

 

So we're on the right track.

crash.zip

Edited by ENO

"ENO"

Type in anger and you will make the greatest post you will ever regret.

 

"Sweetest's" Military Aviation Art

Posted (edited)

New crash- server was fine but it kicked everyone in the room. Logs attached in ZIP include the client and server side logs (just my client... not the others).

 

I clipped the server log at the moment it kicked us all- and also included the slmod event log (though I don't think slmod had anything to do with it, let that be clear.)

 

 

EDIT: Server did crash shortly thereafter... no crash notification at all- it just ceased to exist.

 

I grabbed the "old" log because I forgot about it until after I started the server again.

 

Original client crash files all included plus the server side log for that crash... and the "old" log is for the server side crash plus the crash log.

Crash 03.25.13.zip

Edited by ENO

"ENO"

Type in anger and you will make the greatest post you will ever regret.

 

"Sweetest's" Military Aviation Art

Posted

Further crash logs. These two look to be the same- Unfortunately once again I got a mission restarted too quickly to get the log- and I think a part of the issue was that I had a version of the .old log open in ++ when it crashed. It tried to write to it and I must have screwed something up.

 

Anyway, sorry I don't have more.

crash 03.28.13.zip

"ENO"

Type in anger and you will make the greatest post you will ever regret.

 

"Sweetest's" Military Aviation Art

Posted

Client side crash this time... server stayed up. Main Zip is server side file along with some slmod information (again, don't think slmod contributed, just extra info). Client side crash file and log is in a separate folder within.

 

Thanks guys.

04.05.13.zip

"ENO"

Type in anger and you will make the greatest post you will ever regret.

 

"Sweetest's" Military Aviation Art

  • 2 weeks later...
  • Recently Browsing   0 members

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