PostPosted: 07 Oct 2011, 14:41
I've finally managed to reproduce it! However, it did not happen every time even with the same steps. I believe it is caused by an invalid memory access.
Some questions of either or both of you:
- Does it occur when you also have a map loaded in my editor? (when you can see the terrain with grass, trees, etc. in the map part of the screen, not just grey) If not, please always load the map before using my editor. (it was never really designed to work without a map loaded, I would not be surprised if this crashed it)
- Does it work for any multiplayer and singleplayer missions? (the one you select in the "New" dialogue, try it with both)
- Does it occur for maps/missions that have NO connection to the KaM Remake? e.g. if you open an original KaM mission/map, or create a new mission using an original KaM map.
Some questions of either or both of you:
- Does it occur when you also have a map loaded in my editor? (when you can see the terrain with grass, trees, etc. in the map part of the screen, not just grey) If not, please always load the map before using my editor. (it was never really designed to work without a map loaded, I would not be surprised if this crashed it)
- Does it work for any multiplayer and singleplayer missions? (the one you select in the "New" dialogue, try it with both)
- Does it occur for maps/missions that have NO connection to the KaM Remake? e.g. if you open an original KaM mission/map, or create a new mission using an original KaM map.
