Matrix Games Forums

Has this occured to anyone before? What have i done wrong?

I modified an existing scenario and did the following: I selected clear map. Now all units have been removed from the map as a consequence and i began to redraw the map as i intended. I saved the scenario, but didn't redeploy any unit (the map wasn't finished yet).
When i wanted to open the scenario again the editor crashed with the following message, followed by a windows termination of the programm:

Just as a guess, I would say that there were subdivided units that were deployed, and when all the pieces got picked up, the OOB went into a tizzy.

ORIGINAL: JAMiAM

Just as a guess, I would say that there were subdivided units that were deployed, and when all the pieces got picked up, the OOB went into a tizzy.

That would explain it, but it isn't. I edited the OOB (renamed some units) just before i deleted the map.

Hm. I made some hexes unplayable - maybe it is related with entry points now probably being in unplayable hexes. Could that be?

Maybe it simply got corrupted by the evil windows while saving.

Fortunately it's a very small one - and i still have the unedited version.

ORIGINAL: Telumar

ORIGINAL: JAMiAM

Just as a guess, I would say that there were subdivided units that were deployed, and when all the pieces got picked up, the OOB went into a tizzy.

That would explain it, but it isn't. I edited the OOB (renamed some units) just before i deleted the map.

Hm. I made some hexes unplayable - maybe it is related with entry points now probably being in unplayable hexes. Could that be?

Maybe it simply got corrupted by the evil windows while saving.

Fortunately it's a very small one - and i still have the unedited version.

Can you post the editied version?

Do you per chance have two or more units with identical names, with one or some of them in the reinforcements schedule?

Thank you for answering.

Ralph, i am currently not at home, but i will post it tomorrow (my time).

Nemo, this is indeed the case. Two identical named units in the same formation, both in the reinforcements schedule. Mince!

Here it is - probably the smallest toaw scenario ever. Converted from Vol.I to III.

Somehow the unit called I/LSSAH is marked as being on the map, but it isn't on the map<g>.

It was on hex 8,4. I'd guess that when you cleared the map, you managed to do that somehow.

Ralph

I saw&nbsp;this error a couple years ago&nbsp;in COW, but not in the editor. It was during a game.&nbsp; As Ralph said the program thinks a unit is on the map (you can even "select" it and manipulate the pathfinding arrow) but it's not really there.

Okay, the mystery is solved. Thanks Ralph. Will have to redoe the few tiles i did in the editor then.

Raindem - Nemo and I encountered this some weeks ago in a PBEM game, it happened in an overcrowded (unit-wise) area.

ORIGINAL: Telumar

Okay, the mystery is solved. Thanks Ralph. Will have to redoe the few tiles i did in the editor then.

Raindem - Nemo and I encountered this some weeks ago in a PBEM game, it happened in an overcrowded (unit-wise) area.

Let me know if you can reproduce it.

ORIGINAL: ralphtrick

ORIGINAL: Telumar

Okay, the mystery is solved. Thanks Ralph. Will have to redoe the few tiles i did in the editor then.

Raindem - Nemo and I encountered this some weeks ago in a PBEM game, it happened in an overcrowded (unit-wise) area.

Let me know if you can reproduce it.

It was in a CoW game, with a Bioed-ed executable. I'll dig out the save file and try to reproduce it (we were able to by then).

I found my file, a turn 20 .sal file. Go to hex 35/50 (Nijmegen) - there is the "invisible" unit. Yet no crashes, but iirc it should crash on the turn end. You can also ask for nemo's password and open the allied turn 20 pbl. It should crash when you select the unit from the german side.

Argh - it's 16 (!) KB too big as a .rar file with the best compression!!

Okay, i split the archive and attach it as two separate .txt files. Here's part one.

And here is part two. [:)]

I see it, and if it was an ongoing game, I could fix it, but I'm not sure what caused it.

ORIGINAL: ralphtrick

I see it, and if it was an ongoing game, I could fix it, but I'm not sure what caused it.

You need not to - i did the turn again and it never occured in this scenario again. We've progressed up to turn 33.