6 réponses à ce sujet

[StrikerBPBio]

Hello everyone!

I am trying to learn how to use the DA toolset. Things works just fine, what I do on my pc just looks like the tutorials. Then when I want to leave the toolset I click the save all button and close it, The next time I re-open the toolset I have to restart from scratch. I open my module and it is as blank as when I created it.

Is there anything special I need to do to have my module being saved or loaded back again if it was saved?

Thanks!

[Beerfish]

You are opening the areas in your toolset correct? When you open your module after saving it seems that not always will the area you were working will be there by default. Look for your area in the palette window and see if it is there.

[CID-78]

well you must be carefull with art resources such as levels they are saved seperatly and you must be sure you save those to a file you know where to find. because they aren't technically a part of the module. they are just used by the module. So if you want to keep working on a level you must simply open the file you saved last time. it won't appear in a list anywhere.

[st4rdog]

Are you talking about custom levels/rooms only? Like CID said, the .lvl file you save isn't part of the toolset and you have to open it with File > Open. Only the exported Level/room becomes part of the toolset's database.

[StrikerBPBio]

I guess this is my newbieness with the toolset, i just needed to select OPEN RESOURCE to see them again and i remade the same tutorial 3 times before finding that out, LOL.



I still have alot of problem finding what I want but maybe one day I will get it.



Thanks for your answers guys!

[Proleric]

There's an important concept here - toolset commands generally apply to the resource you're currently working on.

So, Save doesn't save the module, it saves the current area, creature, item or whatever you can see on the screen. Fortunately, as you've discovered, closing the toolset doesn't necessarily mean your work is lost, but it's wise to save each resource as you go.

You'll find the same applies when you export for testing - what's exported is the current resource, not the module, so you need to ensure that you exported everything. To simplify this, you can Export With Dependent Resources on each area.

[BryanDerksen]

Also, even if you're working on your own and have no need of "collaboration" tools, you should try to check in your changes on a regular basis. Each time you check in your resources the toolset saves that revision separately in the database, so in the future you can use the "resource history" command to view past revisions of the resource and restore them or copy them to new resources. You should also check everything in before making a backup of the database, if you choose to make a backup of the database at any point.



(I've noticed that on my developer toolset I sometimes have to view a resource's resource history twice in order to see it, BTW - the first time just gives me a blank history window. Just in case that's a bug that's affecting the end user toolset as well).