7570 AppCrash - a FIX!!!!!

[Heli Shed]

I created a mission without FC3 planes and it seems to work. After that I added 2x F-15C and boom - crash! Could it be this is the problem and FC3 creates the crashes?

 

Interesting possibility. I think at this point I'm going to wait for direction from the Dev's. If they would like us to continue this error hunting (not exactly my fav passtime, but guns, babes, breasts, beer and plenty of cake are), I'd like them to chime up here and request as such and give some guidance or steerage (should such a word exisit, which i fear it does not!).

 

It would also gives us all a much needed confidence boost.

 

Regards

 

'T'

[Isegrim]

Guys, the devs might have found the cause of this problem, lets hope they can get a fix out fast.

 

I really hope there will not come up new mayor Bugs than.:cry:

 

I really really dont want that.:cry:

:cry:

:cry:

ISE:cry:

[Scorpi]

Okay then let's hope for a fast update.

[ENO]

Yeah... from the other thread...

 

I'm getting that 7570 crash as well. Going through a reinstall now. My server is on the DMZ as well and I'm attached by LAN...

 

VERY frustrating to get no input- but hopefully the end is in site.

 

5 others are on the server right now with no problems... so I know it's not the issue.

 

Tried upping all the settings and ended up crashing my system so hard I can't even get the program to start up again. Make sure if others end up in the same predicament once you uninstall (if it comes to that) that you don't forget to erase all your file folders and run something like ccleaner to clean out your reg to remove all traces. Unfortunately during my reinstall I'd left trace and as a result whatever setting I had that fudged my initial install was still there- and I was unable to even load dcs.exe.

 

Thanks for your work on this Tyger... Bast was in as well talking with me about this and the way he explained it added some depth to what you were saying here. I wasn't quite capturing the whole concept on here (I'm daft that way)... but he cleared it up. Concept seems very sound- hopefully we can get this thing figured out on our end!

CRASHES.ZIP

Edited November 29, 2012 by ENO

[DoctorStrop]

I was hosting a map yesterday evening. I have 7570 build. I tried my custom map, and only one friend could connect, but it took him about 10 attempts, my other friend kept getting booted back to the lobby.

 

Then I loaded a slightly edited stock map (with a couple of F15's and a MIG29 I had previously added for my mate with FC3) which worked fine, and all could connect.

 

This was without rebooting, re-installing, or even restarting the MP DCS application.

 

I have not examined the elements of the stock map, but the custom map I put together has some triggers to activate certain SAMs. I can only assume it is must be being caused by a particular unit type being placed on the map, or by a trigger I have added. I had added dynamic weather to the custom map, but removed this when I started noticing problems. I do not enforce anything in the custom map.

 

Hope this info helps someone.

 

Cheers

 

Andy

[Heli Shed]

Guys you are all chasing errors now.

 

the error is preloading and pre caching of graphics. stop trying to tear your missions apart looking for it, its all specualtion that leads to frustration a hammer and.................................

 

you get the point.

 

We wait for ED, right now, it's broke.

 

If neccessary add 'update 1.2.2.7286' at the end of the command line to revert.

 

I will be making everyone revert on Sunday to attend the workshop if it is not fixed by then.

 

Regards

 

'T'

 

'T'

[taps]

In my opinion, trying to find a workaround for a bug (or possibly and likely dozens of different bugs) w/o access to the source code and w/o being knowledgeable about this big heap of source code that DCSW probably is, is a futile endeavor. The chance of you actually finding a solution is as big as finding a needle in a haystack because of the thousands of different possibilities you have to cover.

 

As much as I know about software development, you can realistically only sit and wait for ED to fix the problem. Or try to be hired by them :smilewink:

[Heli Shed]

In my opinion, trying to find a workaround for a bug (or possibly and likely dozens of different bugs) w/o access to the source code and w/o being knowledgeable about this big heap of source code that DCSW probably is, is a futile endeavor. The chance of you actually finding a solution is as big as finding a needle in a haystack because of the thousands of different possibilities you have to cover.

 

As much as I know about software development, you can realistically only sit and wait for ED to fix the problem. Or try to be hired by them :smilewink:

 

Or..........................................................

 

Rely on experience with the internal scripting of DCS Modules, the sim's behaviour when it is 'normal', intimate knowledge of Mission Design, hell - the whole product and of course former knowledge of internal business as a tester, all topped off with the drive and desire for the good and benefit of the community as a whole, to find a workaround that lets people enjoy the sim as a passsionate hobby rather than a chore.

[taps]

For example if some programmer inadvertently writes to an array element that has not been correctly allocated thereby writing to a piece of memory where the runtime decided to place a variable x thereby giving it a wrong value. Now a million LOCs and hours of game time later x is suddenly used and expected to be in a certain value range but it is not so the game crashes. How can you know w/o access to the source, what the actual problem is? You cannot.

 

That's just my opinion, I don't want to imply that there are no people who know these things better than me.

[BrontoloIT]

Meanwhile that we are here waiting to fly and speculating on a workaround...

 

We know ED is aware of the bug but can we receive some update/feedback on a solution?

I know I can't pretend an ETA but at least a confirmation that ED has found (not "might") the bug's origin.

 

Please keep us updated.

[Scorpi]

http://forums.eagle.ru/showpost.php?p=1617490&postcount=465

[Speed]

Tyger,

we were able to make Quax's mission load and not crash for clients by deleting all the service providers (AWACs, Tankers, etc).

 

Actually, I suspect the problem could be with tankers or things that are broadcasting TACAN.

 

So, in summary:

If you're having a mission that clients cannot join after mission start, first delete the tankers/AWACs/JTACs/etc. If that allows clients to join your mission after mission start, then go back to the mission version before you deleted the units. Try fiddling with tanker radio frequency, callsigns, and TACAN channel and channel types. See if that fixes the problem.

[Heli Shed]

Tyger,

we were able to make Quax's mission load and not crash for clients by deleting all the service providers (AWACs, Tankers, etc).

 

Actually, I suspect the problem could be with tankers or things that are broadcasting TACAN.

 

So, in summary:

If you're having a mission that clients cannot join after mission start, first delete the tankers/AWACs/JTACs/etc. If that allows clients to join your mission after mission start, then go back to the mission version before you deleted the units. Try fiddling with tanker radio frequency, callsigns, and TACAN channel and channel types. See if that fixes the problem.

 

Thanks, but im still convinced this is a pre-load error. The appcrash lends me to believe that.

 

I will however, delete the tanker (just saving it as a difernt mission version number) and JTAC, which incidentally, is on both Phase 1 and 2 of Op Dynamo.

 

but.............................................the whole thing is SERIOUSLY broken if this is indeed the case.

 

just my tuppence, for those that want it.

 

Thanks Speed.

 

'T'

[Heli Shed]

http://forums.eagle.ru/showpost.php?p=1617490&postcount=465

 

???? whats this got to do with it Scorpi?

 

I think the problem you have and everyone else has is completely different. You are using a third party mod ontop of a complex mission that is complex in itself - you will be chasing the error for months.

 

I'm talking a bout a bog standard mission, with ground targets, nothing fancy - slots.

 

Vanilla. more vanilla than bloody vanilla! ;-)

 

people get app crash - go figure.

[Scorpi]

Pardon. I did mention the tanker, because it seemed not relevant to me. All of my missions work without tankers. Thanks Speed!

Edited November 29, 2012 by Scorpi

[Scorpi]

In all my test missions tankers set to "late activation" caused crashes only when they get activated. This is my experience!

[Scorpi]

Coincidence?

Edited November 29, 2012 by Scorpi

[Heli Shed]

yep coincidence.

 

Having tested with tankers, without tankers, late activation (called) late activation timed, likewise with JTAC's and other AI aircraft, makes no difference.

 

like i said. this is a graphics preload and cache problem.

 

 

we wait.

 

In the meantime, right click the DCS World shortcut on the desktop, in the target box and after the " give a sapce and type update 1.2.2.7286

 

save and execute.

 

now go fly and enjoy on LYNX, STP servers and a fair few others out there whilst we wait for ED 'Dev's' to answer here, issue a hotfix or combine in the next patch.

 

as ever, we wait patiently. sortof. ;-)

[Speed]

???? whats this got to do with it Scorpi?

 

I think the problem you have and everyone else has is completely different. You are using a third party mod ontop of a complex mission that is complex in itself - you will be chasing the error for months.

 

I'm talking a bout a bog standard mission, with ground targets, nothing fancy - slots.

 

Vanilla. more vanilla than bloody vanilla! ;-)

 

people get app crash - go figure.

 

Actually, it's quite possible that all this different things are just different symptoms of the very same bug.

[Scorpi]

No crash in multiplayer. Please test! Tanker(late activation)

New Mission.miz

[Mustang]

In the meantime, right click the DCS World shortcut on the desktop, in the target box and after the " give a sapce and type update 1.2.2.7286

 

save and execute.

 

now go fly and enjoy on LYNX, STP servers and a fair few others out there whilst we wait for ED 'Dev's' to answer here, issue a hotfix or combine in the next patch.

 

as ever, we wait patiently. sortof. ;-)

 

Don't forget the 104th, we are successfully hosting 1.2.2.7570 so if you wish to fly with us you'll need to revert back up to this version (rolling back and forward on versions is harmless so its all good)

 

P.S on the bugfixing side of things, as i mentioned in an earlier post this problem has been isolated and ED is working hard to get it to you all in a future update.

Edited November 29, 2012 by Mustang

[chromium]

@Mustang: I love your avatar :D

[Heli Shed]

Actually, it's quite possible that all this different things are just different symptoms of the very same bug.

 

Aye agreed.

 

Whatever it is, Dev's need to fix, acknowledge or advise appropriately.

 

until then 7286 and

idle_timeout = 0

game_timeout = 0

 

as global parameters in Network.cfg are the way to go.:music_whistling:

[Supersheep]

Are these parameters put at the bottom of the file or added at a specifilc place?

 

 

Super-

[Heli Shed]

Are these parameters put at the bottom of the file or added at a specifilc place?

 

 

Super-

 

on their own lines after the last }

 

ie - Globally

 

This will assist on the CTD caused by client disconnects - they will simply never Client Timeout.:lol:

 

If you edit the file again after playing, please note that these lines may have been placed elsewhere by the sim in the .cfg file but they will still be global commands - ie, not encased - {}

Edited November 29, 2012 by Tyger