error in scripts causes crash to desktop?

[Igneous01]

so ive noticed that when returning to one of my missions to work on, any sort of scripting errors that i would have (missing ; or brackets, etc) would cause the game to crash to desktop. Im not sure if its because of a new patch (if an update came out for oa) or an update on ace but now any syntax errors just cause me to CTD.

never used to happen before, and -showscripterrors always worked fine a week ago.

latest mod i installed was SLX mod, but after too many crashes with the mod itself i removed it from my target line.

so the only mods im running are all the ace mods and expansions, and cba

anyone got any ideas as to why this might be happening?

[VanhA-ICON]

not really no.. I use the parameter also but have experienced no crashes.
It displays the error and that's all. Of course the description.ext errors are still valid for a crash but that's different.

[Igneous01]

currently i have not done anything in the description.ext file, well technically i havnt created one yet (focusing on the main functions and actions that occur in the mission itself)

so its not related to that, but it certainly is annoying having to test the mission, crash, open up the rpt file, and correct any errors, and repeat the process.

i really want to find out what exactly happened since a week ago

---------- Post added at 08:05 ---------- Previous post was at 07:05 ----------

ok so now i can confirm its definitely causing crashes on any scripting errors i have.


i created another mission just for the purposes of this:

i added a trigger radio alpha

on act field i put "garbagenull = execVM "garbage.sqf"


in the garbage.sqf file i purposely put

hint "this is an error


with the quotation missing,

when i use radio alpha, the game CTDs

this is the snippet from the rpt file:


Error in expression <st.ProvingGrounds_PMC\garbage.sqf"
hint "this is an error>
Error position: <"this is an error>
Error Missing ""
=======================================================
-------------------------------------------------------
Exception code: C0000005 ACCESS_VIOLATION at 00AAA2A4
graphics: D3D9, Device: NVIDIA GeForce 9500 GT, Driver:nv4_disp.dll 6.14.11.9745
resolution: 1024x768x32
Addons:



so it looks like either something has been updated and is bugged, or possibly SLX mod has corrupted my game somehow

[Shuko]

Yep, have had the same since couple of patch back. Annoying.

[[FRL]Myke]

Can't confirm this on vanilla CO. Tried the exact repro steps as described but game didn't crashed (latest beta active).

[Igneous01]

maybe its an ace or cba related issue? if its not crashing on vanilla, it might be an issue with one of my mods (though i have not updated the mods for 2 weeks now, and it only recently started happening for me)

hmm ill have to test some more to figure out whats happening

UPDATE***

i have tested this now on vanilla, and it still happens. Im not positive as to which exact version im running, but as steam auto updates the game, i assume its the latest version

[[FRL]Myke]

Not sure about Steam but i think it "only" updates to the latest stable. I run it with latest beta.

:EDITH:

Tested now without beta also with and without CBA. In none of these cases i got a CTD.

[Igneous01]

im lost then :S


if it hasnt happened to you, im guessing the access violation im getting in the rpt files suggests somethings going on with my video card drivers/mb drivers

or possibly im getting out of ram errors.


but arma 2 was running perfectly until i ran SLX mod, script errors were showing (some bugs in the slx mod) but at random times i would end up crashing the game with it as well.

now that im not running it it seems that nothing has really changed.

also noticed that id get crashes with graphic card if i set it to default video memory (its 1gb of ram on the card) tho this is most likely unrelated.


but im at a loss as to what to do now.

[[FRL]Myke]

Sorry mate, can't help any further on this one. All i could do is to test it on my side. All it does is writing the script error to the rpt but it doesn't crash.

[Igneous01]

update again**

so i removed -showScripterrors from the target line of my launcher, and suddenly it stopped crashing on any script errors i got ^^


now to find out a way to make it work again with it on...

[[FRL]Myke]

update again**

so i removed -showScripterrors from the target line of my launcher, and suddenly it stopped crashing on any script errors i got ^^


now to find out a way to make it work again with it on...

Well, the solution is pretty simple: make no errors. :D

*ducks and run*

[Igneous01]

lol if only i were syntax inclined that would work ^^


guess ill try out one of the language programs that actually gives the errors before i run the script in game.


i hope that this will be resolved soon tho

[rundll.exe]

Sorry to dig up this old thread, But I have exactly the same problem: When running with -showScriptErrors the game crashes whenever a script error is present.

Did anyone actually find a cause for this?
It kind of disables me from any mission making now... Didnt have problems with it a few months ago tho.

[AZCoder]

What's the script error? I was taking several last night, with latest beta, no CTD.

[rundll.exe]

It doesnt really matter what error. It crashes on each.

I tested a lot, to rule things out, but now it gets weird: As soon as I rename the mission folder (im editing a mission with scripts inside the folder). Everything is fine. Renaming it back (Hike%20and%20Seek.Takistan) and it crashes again.
So the problem is gone by simply renaming it, but I still wonder what can cause the crash on such a simple change? I searched my hdd for the mission name and removed every reference (savegames mostly) but that doesnt change anything.


So can anyone try these simple repro steps? I doubt it will work for others but this is guaranteed crash for me:

1: start the game with the -ShowScriptErrors parameter
2: open a new mission on the editor (desert or takistan, doesnt matter)
3: place a unit
4: save the game with name: Hike and Seek (exactly like this)
5: Put an init.sqf in the mission folder with an error like "this is an error" on the first line.
6: preview the mission
7: Send crash dump to microsoft :o

[Clayman]

To what did you rename your mission? Just a wild guess, but maybe it's the spaces in the mission name. You could try to name your mission sth like Hike_and_Seek.Takistan and see if it still crashes.

[W0lle]

Tried exactly the repro steps from rundll, no crash to desktop here (1.57.77819).

[rundll.exe]

@<hidden>, anything else than "Hike and Seek" seems to work fine.

Thx for testing wolle, seems to be something broken at my system then? Still weird
anyway, nvm then ill just change the name and hope it doesnt happen again.

[Alwarren]

Digging up this old thread. I had the exact same problem, and the solution was, indeed, to use a simpler name. My mission name had spaces in it (albeit replaced by %20). I removed those, and now it does no longer crash even with the showScriptErrors command line option present.

Thanks Clayman for the wild guess :)