Author Topic: Polyworks ate my map (again)  (Read 955 times)

0 Members and 1 Guest are viewing this topic.

Offline ultraman

  • Flagrunner
  • ****
  • Posts: 797
Polyworks ate my map (again)
« on: November 28, 2006, 02:54:00 am »
Well one fine day I tried to load my latest map, I get this error:

Then after closing that window I get this one:

Then upon closing Polyworks I get this one:

Grrrr...

Offline jrgp

  • Administrator
  • Flamebow Warrior
  • *****
  • Posts: 5037
Re: Polyworks ate my map (again)
« Reply #1 on: November 28, 2006, 08:14:21 am »
Maybe, restart?

Check if directx is installed?

Back up the folder Maps that is inside the polyworks folder, reinstall polyworks, then copy that folder into the new installation.
There are other worlds than these

Offline Anna

  • Soldier
  • **
  • Posts: 213
    • my dev blog
Re: Polyworks ate my map (again)
« Reply #2 on: November 28, 2006, 10:05:59 am »
Does this happen only when you try to load a certain map? I can try to recover it again if you want.

It seems to be a serious error but I don't know what could be causing it yet. Are you using the clear unused scenery function often?

Offline numgun

  • Veteran
  • *****
  • Posts: 1032
Re: Polyworks ate my map (again)
« Reply #3 on: November 28, 2006, 04:55:08 pm »
This happens when I undo scenery with ctrl + Z. Not sure fully but thats when it always happened to me.

Maybe you should do a automatic unused scenery clear funtion that erases the crap every 5-10 secs.

Offline Anna

  • Soldier
  • **
  • Posts: 213
    • my dev blog
Re: Polyworks ate my map (again)
« Reply #4 on: November 28, 2006, 05:58:40 pm »
I did a little test just now, I'm able to break a map by following these steps:

- place some scenery of different types
- delete a few of them
- clear unused scenery
- undo (error!)
- save

So I think clear unused scenery + undo is the problem. I'd suggest that you only do clear unused scenery at the end of a mapping session, and don't save after you get that D3D error because it means the the map data is corrupt. I'll have a fix for this in the next version (probably I'll make it clear the undo history after clear unused).