Freeze (crash) on existing Mission Editor (not always)

[Worrazen]

Hello

 

Exiting editor produces a black screen sometimes.

 

Appears it happens on certain occasions depending on what it's being done inside the editor.

 

It happened like 5-6 times now ... almost a 40% probability.

 

There is no crash report or dumps, only logfile has something about a "group" being null value.

 

EDIT: Shouldn't the forum allow .log file attachements?

 

EDIT2: this line was created after I forcefully killed the process 2018-02-28 20:00:52.327 INFO EDCORE: (dDispatcher)enterToState_:5 <--- this does not happen at the moment of freeze.

dcs25ob_freeze_exit_MissionEditor_28Feb2018.log.txt

Edited March 1, 2018 by Worrazen

[BIGNEWY]

Hi

 

thanks for the log, do you have any unofficial mods installed?

 

2018-02-28 19:58:51.708 ERROR Lua::Config: Call error onShowMainInterface:[string "./MissionEditor/modules/me_aircraft.lua"]:2083: attempt to index field 'group' (a nil value)

stack traceback:

[C]: ?

[string "./MissionEditor/modules/me_aircraft.lua"]:2083: in function 'onSpinUnitOf'

[string "./MissionEditor/modules/me_aircraft.lua"]:1716: in function 'verifySingleInFlight'

[string "./MissionEditor/modules/me_aircraft.lua"]:738: in function 'changeType'

[string "./MissionEditor/modules/me_aircraft.lua"]:1189: in function 'setType'

[string "./MissionEditor/modules/me_aircraft.lua"]:1084: in function 'changeCountry'

[string "./MissionEditor/modules/me_aircraft.lua"]:1568: in function 'fillCountries'

[string "./MissionEditor/modules/me_aircraft.lua"]:1522: in function 'updateCountries'

[string "./MissionEditor/modules/me_mission.lua"]:1496: in function 'load'

[string "./MissionEditor/MissionEditor.lua"]:552: in function 'prepareMissionPath'

[string "./MissionEditor/MissionEditor.lua"]:675: in function <[string "./MissionEditor/MissionEditor.lua"]:668>.

2018-02-28 20:00:52.327 INFO EDCORE: (dDispatcher)enterToState_:5

 

I would try deleting your missionEditor folder in dcs root and then do a repair, see if it helps

[Worrazen]

Right now only some cockpit mods which I put into the DCS Saved Games folder and I've done no other mods myself yet. I also refreshed my memory with custom liveries and the only thing I did was adding a few livery lua files in the appropriate places.

[Gannet]

Hi, I had programme freeze whilst creating simple mission with Huey out of Beslan. Editor froze when clicking between waypoint and loadout tabs. c. 1 minute and then ok.

[Worrazen]

Hi, I had programme freeze whilst creating simple mission with Huey out of Beslan. Editor froze when clicking between waypoint and loadout tabs. c. 1 minute and then ok.

 

That's normal asset loading. Well, it's because it's not preloaded when starting the editor. This is a efficiency measure so it doesn't run out of memory on various systems but also a tradeoff bettween wait times in the beginning, you would need to wait for many things you might never need.

 

If it's not that it's taking some time for the code to finish populating the elements, the code that does that may be a higher level gui script which doesn't run as fast as a C++ core engine would so that's why it takes time, this is pretty normal across the industry, GUI and database things usually don't run with blazing speeds.

 

That said, that script might still be able to be further optimized.

 

Eventually we should be able to choose between efficency vs convenience even in the asset loading department, not many games, if any, do expose such options to the user, DCS would set the bar and proudly support the PC platform if this materializes, special goodies for special customers.

 

So people with 64GB or 128GB RAM and a NVMe SSD could just preload everything in beginning and forget about it.

But in terms of textures, GPUs would need to have like 32GB or more VRAM too, to preload the whole map inside and all the liveries hehe.:prop:

 

Maybe on the pro-simulators for the actual training facilities may already have something like this, the TBS or what, the reluctancy I see is the people who aren't up to par trying to use it and newcomers getting confused, but that could be solved by just putting the option deep into the options, there could even be some kind of a minigame to unlock it, hidden special mission, now that would be a really cool easer egg for a while.

 

It is not that far fetched because with the HBM memory ... things can really start to get rolling in the amounts of VRAM they will be able to put on a GPU and even make it down to the high-end ranges ... in a few years.

Edited March 1, 2018 by Worrazen

[ivo]

Hello

 

Exiting editor produces a black screen sometimes.

 

Appears it happens on certain occasions depending on what it's being done inside the editor.

 

It happened like 5-6 tcase now ... almost a 40% probability.

 

There is no crash report or dumps, only logfile has something about a "group" being null value.

 

EDIT: Shouldn't the forum allow .log file attachements?

 

EDIT2: this line was created after I forcefully killed the process 2018-02-28 20:00:52.327 INFO EDCORE: (dDispatcher)enterToState_:5 <--- this does not happen at the moment of freeze.

 

hi, in my case when I out the refueling plane any models...

[ivo]

out=put.... dam keyboard

[Worrazen]

I did a cleanup of user-compiled shaders (fxo, meta, etc) and MissionEditor data in both places as well as user MagVar files. And then repair. Seemed to help for a while but then keeps going on as I keep using it normally.

 

There were no exit errors, as soon as the first freeze with ME happened, it a also started crashing on exit.