LarryG on 23/1/2011 at 05:54
I'm not using mis files, only cow when working. The mis files I have generated after the 2009 error have worked just fine ... I expect that the next one I generate after this will work too. After all, the file with the error happening is never saved. It crashes Dromed. But what is "the Sim"? And how did it get altered?
nicked on 23/1/2011 at 08:08
I think that's where you simulate difficulty settings in Dromed, for testing. If you save after that, it'll save the position of everything almost as if it was a game save, and royally screw up the level.
Nameless Voice on 23/1/2011 at 09:59
It's not the difficulty. If you set the "game_mode_backup" variable to 0, then DromEd won't restore your mission after entering game mode. Instead, you'll get your mission as it was after you've already been playing it. The Player object will exist, all difficulty settings will have been processed, any items you've moved or taken will stay moved or taken. The mission basically becomes a saved game of the game you were playing while in game mode.
Clearly, that's not suitable for a shipped mission anymore, you'd need to spend forever trying to undo all the things you'd done in-game.
Haplo on 23/1/2011 at 11:59
Quote Posted by Nameless Voice
It's not the difficulty. If you set the "game_mode_backup" variable to 0, then DromEd won't restore your mission after entering game mode. Instead, you'll get your mission as it was after you've already been playing it. The Player object will exist, all difficulty settings will have been processed, any items you've moved or taken will stay moved or taken. The mission basically becomes a saved game of the game you were playing while in game mode.
Clearly, that's not suitable for a shipped mission anymore, you'd need to spend forever trying to undo all the things you'd done in-game.
This.
To see the difference, start your mission in Thief, play a bit, knock out a few people, quicksave, quit, open DromEd and enter the command 'edit_load_game saves\quick.sav'. You will see how the objects change.
Nameless Voice on 23/1/2011 at 12:38
Or just type "set game_mode_backup 0" in DromEd, then go into game mode, play for a bit, and switch back to editor mode. Just never, ever save after doing this.
qolelis on 23/1/2011 at 13:08
Quote Posted by LarryG
I got this on 8/13/2009
[ATTACH]883[/ATTACH]
and then it didn't happen again until today.
[ATTACH]882[/ATTACH]
So what's with this? And where do I find a mission surgeon, assuming it really needs one? It seems just fine so far.
That happens to me sometimes when I exit game mode and quickly press F11 ("save mission"), i.e. before edit mode has really kicked in. The correct answer is "No!", and then I usually also restart DromEd just to be safe.
LarryG on 10/3/2011 at 00:10
I hate this error. It seems to crop up around stairs and the use of multibrushes. The only solution I have found is to delete and recreate the area. :(
[ATTACH]904[/ATTACH]
R Soul on 10/3/2011 at 00:58
That happened to me a while ago, for the same reason. In my case it didn't happen immediately so it took a while to find the cause.
Think of it as a blessing in disguise. Dromed is actually trying to ask if you really want to use the same pattern of brushes over and over again.
LarryG on 10/3/2011 at 02:26
It only showed up after a "Complete Processing." Investigating it from saves, I can do any number of Portalizings, but as soon as I do a Complete Processing the error shows up. So my suspicion is that the optimizing code has a bug in it, going a little above and beyond what is needed.
The troublesome stairs were made by subtractive carving out with air brushes. The replacement stairs will be additive placement of solid brushes. Hopefully that will satisfy the optimizer. Grrrr, :grr:
Edit: Nope! It doesn't like that either. Again, the problem only shows up after Complete Processing. Weeeeel, it's time for a ladder. :erg:
Edit 2: Not even a ladder was enough to placated DromEd. I'm now dismantling another staircase nearby.:mad:
Edit 3: Not even redesigning the whole neighborhood is enough to make it stay away. As soon as I connect two levels in this place it comes back. :mad: I may have to give up on this path. :grr:
qolelis on 13/3/2011 at 16:30
Quote:
Z-Bias value -10 is out of the [0,16] range (File: d6Intfc.cpp, Line: 1086)
Inline Image:
http://i757.photobucket.com/albums/xx211/mazqin/DromEd/ZBiasValueOutOfRange.jpgDromEd 2 v1.18
There's not much to say about this error; it's pretty straight-forward. It occurs when entering game mode. When I ignored it, other objects and also stars were in some cases visible through solid terrain brushes.
