Page MenuHomeFeedback Tracker

Random CTD on mission load
Closed, ResolvedPublic

Description

Arma will crash to desktop on mission load [technically, load on preview] -occasionally- with a well tested map and mod package. I'm certain it is not the mod that is causing the CTD, as I said, it's pretty well tested. Even if it were, there should be a usable error message produced if this is going to happen. {F25466}

Details

Legacy ID
944381548
Severity
None
Resolution
Fixed
Reproducibility
Random
Category
Game Crash
Steps To Reproduce

Not sure. I have included the mdmp, rpt and the only script to fire from the mod before the time of crash.

Additional Information

Again, I'm running modded. I can't test this without the mod files. I'm mostly reporting this to pass along the mdmp file for someone to look at.

Event Timeline

Tiskahar edited Additional Information. (Show Details)
Tiskahar set Category to Game Crash.
Tiskahar set Reproducibility to Random.
Tiskahar set Severity to None.
Tiskahar set Resolution to Fixed.
Tiskahar set Legacy ID to 944381548.May 7 2016, 8:10 PM
Tiskahar edited a custom field.
Tiskahar added a subscriber: Tiskahar.

I've been dealing with this now for a couple hours. It is occurring every other time I load the mission.

Further information: Saving the file while it is open in the editor precludes every crash.

Bohemia added a subscriber: Bohemia.May 7 2016, 8:10 PM

Well you have writed you have tested it - OK, but i see that in rpt files are some errors about unsupported uniforms

Yes, there is that error, which we are working on. However, I am able to run the mission without issue with that error popping. I've also gotten the crash running this with normal, vanilla units that do not produce the unsupported uniform error. The crash only occurs when I hit the save button and then preview. In my mind, the crash is related to saving the map file, possibly with my extra class (cfgScenario), or with cfgFunctions. I should note, this has started occurring only with the last stable branch update.

Thank you for looking into it!

This issue appears to be resolved as of ver. 1.38.128937
Please mark the ticket as such.