In Build 226, importing maps exported from that build will work, but when I try to import a map from beta 14, it crashes
As a side note, that warning message about invalid layers is REALLY annoying
Importing Maps
Hm. I'll bet it's another of those pointer problems...
The overabundance of warnings is easy to fix.
But, hey, it's still better than crashing, no?
Saffith wrote:The overabundance of warnings is easy to fix.
But, hey, it's still better than crashing, no?
Um, no. Not when the message pops up every time you switch screens. Perhaps a ZQuest option to show that warning only when you import a map, or don't show it at all?
If this bug is still happening in the latest build, could you please send me one of these b14 maps so I can debug with it?
With Build 254, there's still a problem with importing. With maps from older builds, they only partially import, meaning that some screens work, and some will crash ZQuest when you try to select them. Importing maps saved in 254 will make ZQuest crash on any screen you click on, and in both cases, no error messages appear
why do people compare beta's against other beta's? THEY ARE BETA, why would you want a beta version to be compatible with another beta version? thats not the focus here, the focus is to fix bugs with official static releases and the latest beta.
no offense intended (if im right with what i said then wouldn't a general announcement explaining this be helpful o_O?)
old beta's are only helpful for pin pointing when something occurred etc.
franpa wrote:why do people compare beta's against other beta's? THEY ARE BETA, why would you want a beta version to be compatible with another beta version? thats not the focus here, the focus is to fix bugs with official static releases and the latest beta.no offense intended (if im right with what i said then wouldn't a general announcement explaining this be helpful o_O?)
old beta's are only helpful for pin pointing when something occurred etc.
However, giving as much information as possible can help the developers find the problem and hopefully solve it. If something isn't compatable with a newer beta when it should be, that could be considered a bug that needs to be fixed. If it goes unnoticed, it could appear in the final version, which is not good at all
no, you should only be finding bugs that are related to official releases then narrowing down when tho's bugs first occurred.
a problem with importing stuff from one beta to the other shouldn't be considered a bug, cause you shouldn't be building quests with unstable versions.
adding support for all alpha/beta's would make the source code rather insane to navigate.
The point of beta testing is finding things that are broken. Importing maps from one version to another means that something is probably not working properly. Comparing problems with previous betas is just as useful for testing as it is with comparing them with full versions. As I said before, not doing so could result in undiscovered bugs that make their way to a full version
not doing so would result in bugs which relate only to beta's between official releases creeping into the official release thus intensifying the need to make quests only in official versions.
franpa, it sounds like you're saying we should only beta test the full versions. I'm not saying we should be making quests in the betas. I'm simply reporting a feature that worked in a previous beta, and now it no longer does
What's the status of this *b*?
Still a problem?
Duplicate of http://www.armageddongames.net/forums//thread/98848/ and fixed.