I grow tired of staring at my desktop..*sigh*
So here is the quest the map is from. It should look familiar, I was using it to test scripts. And here is the map. It was crashing regardless of what quest I was trying to import it to. I just opened zq and went to import on the last attempt and kaboom. The bugs can smell fear.
I know that I have more problems with maps than anyone on the planet, but is this verified or unverified?
I just tested this yet again in windowed mode and recieved a "zq has encountered a problem and needs to close". The links are in the first post. The map bugs have nowhere left to hide now. 😛
There is a problem with importing maps for sure, that's why I also bumped up 2 of *b*'s import map posts, and there is one of my own where I supplied DarkDragon with the map, .til, and .cmb files to test.
I was trying to get as much about importing maps bumped up front here as possible so he could compare all the problems and maybe see what the solution should be.
Yep, it's curtains for the map import bugs now. 😉
WTF? Looking at the code I don't see how map importing could have ever. ever worked - half of the data, the actual combos used on the screen, aren't even saved in a .map, and random garbage from memory is used instead.
Fixed in the next build.
Forget about your old .map, they are hopelessly incomplete.
DarkDragon wrote:WTF? Looking at the code I don't see how map importing could have ever. ever worked - half of the data, the actual combos used on the screen, aren't even saved in a .map, and random garbage from memory is used instead.
I'm glad you took the time to investigate this matter in more detail. Seriously, I was half-expecting another "well it works for me" reply by someone. Then Gleeok goes crazy.
I was successfully able to export then import a map in build 548. Nice to see this one fixed!
Me too, worked perfectly.
Have a beer DarkDragon!