2 réponses à ce sujet

[FollowTheGourd]

My current goal is this: take the Demo module that comes with the
toolset and export it  - without exporting files not related to the Demo module at all (that I can make sense of). My basic understanding of the export process comes from this page on the wiki: http://social.biowar...ndex.php/Export

If I do a full export, it appears to want to export the entire database's resources instead of just exporting the resources specific to the Demo module like the wiki would seem to indicate: "this option exports every resource associated with the module."

If I export with dependent resources, then for whatever reason, it's still dumping core scripts and plo files (not associated with the Demo module) into My Documents/BioWare/Dragon Age/packages/core/override/toolsetexport.

This could just be because I don't know what the basic unit of "moduleness" is in the toolset. To even get the "export resources" group of options to show up in the menu "Tool->Export", I have to select one of the folders in the resource palette. I selected the one named "Demo", but I don't know what difference that would make, since I thought those folders were basically more like views than anything else.

If I only select a module from the module manager, then directly go to the "Tools -> Export" menu, I don't have any proper export group of options (like full export, export with dep resources etc). There just isn't any "module" resource I can select, so I'm not sure what else I should be doing.

Could it also be that the database keeps track of core/global resources and their dependencies that have been changed (or at least checked out and in again) and it'll export those into all my modules now? I could nuke the database and start over to find out, but I'd rather just learn what I'm supposed to actually be doing here.

Modifié par FollowTheGourd, 08 novembre 2009 - 06:40 .

[Eizneckam]

The export function is, as you've noticed, a bit aggressive in exporting dependencies. So far the best way I've found to export just your resources is to use the Builder -> Builder to Player Package option to build a DAZIP package, which can be installed through the DAUpdate tool.

[FollowTheGourd]

Thanks for the confirmation and suggestion. B2P seems like an easy enough way, but if I ever start modifying core scripts, I think it'll still be a pain to sort through the files in the core directory.



And I'm still not honestly sure how to export everything in a module... the wiki just tells you how to do it for an area, but so far the toolset has dumped all of them out anyway when I select the resource folder instead of an area resource. I'm just not sure if that's going to come back and bite me if and when it doesn't actually export something from the module - maybe from another resource category - that I thought it should.