Editor crashes again and again and ....

[FAFGFirewall]

Hello guys and gals,

 

It's been quite a while I got some issue with the mission editor.

It was already the case with my old PC (NVidia 1080 + win 7) and I thought that with my new PC things would be different, but nope !

 

I have roughly 10 crash per hour, whatever the mission, whatever the action, sometimes simply clicking on the menu bar after opening it is enough to crash.

 

I didn't plan to come and post something, until today. I spent around 20 hours on a mission, and the editor crashed during file saving, as you may guess, the mission was lost...

 

So here are some file from the crash dump cmd (I got 8 others if needed), if that could help in anyway.

 

• When you encountered the crash: I was saving a mission
• In what game mode (MP/QMB/campaign/scenario);   Mission Editor, Cooperative scenario.
• In what mission;  Normandy Summer
• What did you do before the crash;  Clicking on the "Save" option in menu
• What happened in the mission before the crash;  Nothing, everything was fine until I  saved
• Additional info you think is relevant to the crash SEE BELOW.

 

• OS: Windows 10 x64 Home
• RAM: 32GB DDR4 RAM 'Corsair'
• CPU: Intel i7 11700K 3.5GHz
• GPU: NVidia Geforce RTX 3080

 

STEditor_exe.18100.zip

Edited March 12, 2023 by FAFGFirewall

[Sketch]

Don't use 4k resolution. It crashes the editor. If your save fails to open, try to load the msbin file instead. Sometimes it can be opened when the mission file can't. If you have version control, use it often. Good luck. The mission editor is a pita sometimes.

 

Edited March 13, 2023 by Sketch

[AEthelraedUnraed]

12 hours ago, Sketch said:

If your save fails to open, try to load the msbin file instead. Sometimes it can be opened when the mission file can't.

Or the other way around - delete (or rename) the .msnbin file so the game loads from the .mission file

[FAFGFirewall]

Thank you to both of you guys, it's really appreciated.

 

@SketchI switched my graphic resolution to 2K, but how do you open msbin file ? I tried with the mission editor (replacing the *.mission extention with the *.msbin one) but it didn't work. So I tried to open it from outside (right click -> Open with) the editor and this time I got an error message : File not found Graphics/shaders/trash/Atmsphere.fr (?)

 

@AEthelraedUnraed That's the problem, it's the *.mission file that is corrupted, the *.msbin file looks ok (at least I can play the mission in its unfinished state ?)

[JimTM]

20 hours ago, FAFGFirewall said:

Thank you to both of you guys, it's really appreciated.

 

@SketchI switched my graphic resolution to 2K, but how do you open msbin file ? I tried with the mission editor (replacing the *.mission extention with the *.msbin one) but it didn't work. So I tried to open it from outside (right click -> Open with) the editor and this time I got an error message : File not found Graphics/shaders/trash/Atmsphere.fr (?)

...

 

It's not .msbin, it's .msnbin. Note that *.* in the File Name box will work too; it will just show you everything in the folder and you can select the .msnbin file that you want.

Edited March 14, 2023 by JimTM
Added "File Name box"

[IckyATLAS]

I work only in 4K because I have a 43" screen and I want to be able to use the area the best possible to display very complex and loaded maps, and have the most possible large view on the map. I found a way to avoid crashes.

The crashes happen when you have the map displayed. For whatever reason when you pan, zoom etc. you can have crashes. If you open missions on top of missions to copy paste stuff etc. all this leads to crashes in a completely random way. No real solution was found and the devs don't give a damn a bout it most probably because they work on HD screens where it seems there are less crashes or not at all. 

The solution I found which by the way seems to avoid crashes is to work mostly without the map by typing ALT F9. I then display the map only when necessary. When I save and open a new mission file first ALT F9 and then do the operation.  We do not need always the map. When cutting pasting, importing new groups etc. I do it without the map. This has made my way of working very reliable. But never forget to always do CTRL S whatever solid the system seems to  be. Still I need from time to time the map and then a crash may always happen.

 

I dream that a definitive solution is found one day. I think I would prefer this update instead of a new plane.

 

[Jaegermeister]

5 hours ago, IckyATLAS said:

most probably because they work on HD screens where it seems there are less crashes or not at all.

 

This... ?

 

I work in the ME many hours a day now and I can't remember the last time it crashed. I always close all groups before saving or opening a new file.

No 4k and all updated drivers once a week. That's it.

 

If you have to have your big screen I think you're on your own.

 

[FAFGFirewall]

 @JimTM I was not able to follow your advice as I have a dropdown menu with only *.mission extension. I was not able to add manually *.msnbin (or *.*). But I found that :

 

On 3/5/2015 at 3:16 PM, ST_ami7b5 said:

Or simply type in the first letter(s) of the mission name and all files starting with that letter(s) will appear in a drop-down list, including .msnbin, which you can then select.

See:

http://forum.il2sturmovik.com/topic/14893-missions-sharing-corner/?do=findComment&comment=240012

 

And it worked !!! I get my mission back.

 

@No601_Swallow I do. I have a lot (like a lot a lot) of groups. I plan to share them with the community when they will be cleaned (correct labelisation, text files with some explanations because even for me it's sometimes hard to recall what I wanted to do ?).

 

Anyway, thank you to all of you for your patience and your help ?

[IckyATLAS]

4 hours ago, Jaegermeister said:

If you have to have your big screen I think you're on your own.

Unfortunately. But this big screen is also for flying. And in that case you are nearer to a 1:1 virtual cockpit size. Immersion is much better.

[Jaegermeister]

5 hours ago, IckyATLAS said:

Unfortunately. But this big screen is also for flying. And in that case you are nearer to a 1:1 virtual cockpit size. Immersion is much better.

 

No doubt. That's why I use VR, true 1:1. I realize not everyone can or wants to.

 

Your speculation is correct though, there are basically no crashes with a standard monitor if you follow some simple habits. Maybe it would help to get a second smaller monitor for working in the ME?

Edited March 14, 2023 by Jaegermeister

[IckyATLAS]

7 hours ago, Jaegermeister said:

No doubt. That's why I use VR, true 1:1. I realize not everyone can or wants to.

That's indeed the ultimate solution. One day will come where I will make the jump. But not ready for it yet.

[Jaegermeister]

7 hours ago, IckyATLAS said:

That's indeed the ultimate solution. One day will come where I will make the jump. But not ready for it yet.

 

You should go ahead and do it. The resolution is good enough to read the cockpit instruments without zoom now on various models. You would not regret it and you would never be able to go back to a flat screen. It really is that much better, as long as you don't get vertigo or mind a headset for an hour at a time or more.

[Gambit21]

On 3/13/2023 at 7:36 PM, Jaegermeister said:

 

This... ?

 

I work in the ME many hours a day now and I can't remember the last time it crashed. I always close all groups before saving or opening a new file.

No 4k and all updated drivers once a week. That's it.

 

If you have to have your big screen I think you're on your own.

 

 

 

That was a fine excuse 5 years ago...but in this day and age damn thing needs to work in 4k.

The problem has only been reported for what now...7 years? It's ridiculous.

 

 

 

 

 

 

 

 

 

Edited March 15, 2023 by Gambit21

[WillyWacker]

On 3/13/2023 at 9:46 PM, IckyATLAS said:

I work only in 4K because I have a 43" screen and I want to be able to use the area the best possible to display very complex and loaded maps, and have the most possible large view on the map. I found a way to avoid crashes.

The crashes happen when you have the map displayed. For whatever reason when you pan, zoom etc. you can have crashes. If you open missions on top of missions to copy paste stuff etc. all this leads to crashes in a completely random way. No real solution was found and the devs don't give a damn a bout it most probably because they work on HD screens where it seems there are less crashes or not at all. 

The solution I found which by the way seems to avoid crashes is to work mostly without the map by typing ALT F9. I then display the map only when necessary. When I save and open a new mission file first ALT F9 and then do the operation.  We do not need always the map. When cutting pasting, importing new groups etc. I do it without the map. This has made my way of working very reliable. But never forget to always do CTRL S whatever solid the system seems to  be. Still I need from time to time the map and then a crash may always happen.

 

I dream that a definitive solution is found one day. I think I would prefer this update instead of a new plane.

 

Once Jesus and the Devil made a contest to build an Il-2 mission in 4k within an hour with 20+ planes each side and 50+ ground groups with min 4 units each side. After 50 minutes both systems crashed, as normal. After the hour was over Jesus delivered his mission ready. Devil asked "WTF???" - Jesus: "saves".

Edited January 16, 2024 by Gerhard68