I have two areas in my module. Area 1s layout is ost101d and area 2's is ost1012d. After I save the module and restart the computer the layout on area 2 disappears and I have reinput all of the waypoints and objects. Once this happened after my computer shut down from a blue screen of death (it was after it freaked out from having the toolset and the game opened at once) and the other time this didn't happen. Am I saving it wrong or something?
As a side note has anyone else got the BSOD, is this cause for concern?
Why does my area not save?
Débuté par
elkwolf
, déc. 14 2009 10:57
Retour en haut
#2
Posté 15 décembre 2009 - 02:02
DMDraos
-
- Members
- 12 messages
There are two pieces to this:
1. Level editor
2. Area editor
When using the level editor, you're not adding placeables and the like generally. If you add models and update the layout, then save, that'll commit your changes to the *.lvl file for that level.
However, when adding placeables and waypoints via the Area Editor, I'm pretty sure you need to do an export with dependents to fully save/commit everything. I had similar experiences with objects either not saving, or not showing up in game when adding and saving the area. Until I saved, then did the full export tasks, it wasn't working.
Hopefully someone more knowledgeable swings through and clears this up, in the event I'm mistaken.
1. Level editor
2. Area editor
When using the level editor, you're not adding placeables and the like generally. If you add models and update the layout, then save, that'll commit your changes to the *.lvl file for that level.
However, when adding placeables and waypoints via the Area Editor, I'm pretty sure you need to do an export with dependents to fully save/commit everything. I had similar experiences with objects either not saving, or not showing up in game when adding and saving the area. Until I saved, then did the full export tasks, it wasn't working.
Hopefully someone more knowledgeable swings through and clears this up, in the event I'm mistaken.
Modifié par DMDraos, 15 décembre 2009 - 02:02 .
#3
Posté 15 décembre 2009 - 04:53
Quaxo
-
- Members
- 164 messages
Simply saving it won't do. The entire thing must be exported again.
#4
Posté 15 décembre 2009 - 05:07
TimelordDC
-
- Members
- 923 messages
Actually, saving the area is enough. It should preserve all your work.
Did you create a new area and insert all the placeables and creatures by creating new resources specific to that module? Or did you reuse existing ones? Asking so I can try the same options and see what happens [the tests I have made so far are with new resources]
If what you are experiencing is not replicable, either it was a one-time glitch or you forgot to save the area.
Did you create a new area and insert all the placeables and creatures by creating new resources specific to that module? Or did you reuse existing ones? Asking so I can try the same options and see what happens [the tests I have made so far are with new resources]
If what you are experiencing is not replicable, either it was a one-time glitch or you forgot to save the area.
#5
Posté 15 décembre 2009 - 12:00
elkwolf
-
- Members
- 54 messages
I think I created new resources. When you say that I need to export it all do you mean just the area or everything in my module or just the area and everything in the area?
#6
Posté 15 décembre 2009 - 03:55
TimelordDC
-
- Members
- 923 messages
You have to export everything if you need to test your module - at least the dependent area and associated objects (like scripts, creatures, etc.). Make sure the area with the start waypoint is also exported.
If you just want to save your work to continue another time, you can just click save and it should save the area with whatever is in there (assuming the individual objects like creatures/placeables were also saved). If the save didn't occur, there likely was an issue with the database connectivity or there was an error that isn't being caught by the toolset code. Areas are designer resources and hence, stored in the database.
Is this happening regularly?
If you just want to save your work to continue another time, you can just click save and it should save the area with whatever is in there (assuming the individual objects like creatures/placeables were also saved). If the save didn't occur, there likely was an issue with the database connectivity or there was an error that isn't being caught by the toolset code. Areas are designer resources and hence, stored in the database.
Is this happening regularly?
Modifié par TimelordDC, 15 décembre 2009 - 04:05 .
