I have been working on some areas with a friend of mine and, unlike with the .lvl files, I can't figure out how to send him the files, or where they are saved to.
Is there no way to send the area files themselves, and if so, how do you share the files?
Sending Areas to Another Computer
Débuté par
Nerdsturm_
, déc. 01 2009 01:12
Retour en haut
#2
Posté 01 décembre 2009 - 10:09
XtopherWa
-
- Members
- 13 messages
I'm still working this out myself, but from how it looks you can send the .lvl file to your friend, and he can open it, render lightmaps and pathfinding and whatnot, and integrate it into his project. There may be a more elegant way to do that which I have not discovered yet.
good luck!
good luck!
#3
Posté 02 décembre 2009 - 01:07
Ashmaran
-
- Members
- 52 messages
If you want to send across the arl file and other related stuff (what you build from the .lvl) they get exported to a directory here:
\\Documents\\BioWare\\Dragon Age\\AddIns\\*your module name*\\core\\override\\toolsetexport\\*your layout name*
I think if you just zip up that folder and give it to someone and they extract it to the same folder in their mod it should be accessible as an area layout.
Similar deal if you mean the actual area files you are tweaking in the toolset (with adding creatures / placeables etc the .are and .lst files) it's just instead of the core folder in your module, they are in the module folder.
\\Documents\\BioWare\\Dragon Age\\AddIns\\*your module name*\\module\\override\\toolsetexport
\\Documents\\BioWare\\Dragon Age\\AddIns\\*your module name*\\core\\override\\toolsetexport\\*your layout name*
I think if you just zip up that folder and give it to someone and they extract it to the same folder in their mod it should be accessible as an area layout.
Similar deal if you mean the actual area files you are tweaking in the toolset (with adding creatures / placeables etc the .are and .lst files) it's just instead of the core folder in your module, they are in the module folder.
\\Documents\\BioWare\\Dragon Age\\AddIns\\*your module name*\\module\\override\\toolsetexport
#4
Posté 02 décembre 2009 - 03:41
Ranlas
-
- Members
- 96 messages
What you're looking for is the feature called Builder to Builder create/load. This article describes the B2B process: http://social.biowar...lder_to_builder.
In a nutshell, a Builder to Builder package is is similar in concept to a .erf file in the NWN toolset: it's a package of exported resources intended to be sent to another builder or archived.
Using Builder to Builder Create will make one of these files, and then your friend would use Builder to Builder Load to import them. The wiki article only shows one way of exporting a single resource (by right clicking on it), but you can also export groups of resources by using Tools -> Builder ->Builder to Builder Create.
In a nutshell, a Builder to Builder package is is similar in concept to a .erf file in the NWN toolset: it's a package of exported resources intended to be sent to another builder or archived.
Using Builder to Builder Create will make one of these files, and then your friend would use Builder to Builder Load to import them. The wiki article only shows one way of exporting a single resource (by right clicking on it), but you can also export groups of resources by using Tools -> Builder ->Builder to Builder Create.
#5
Posté 03 décembre 2009 - 09:43
BryanDerksen
-
- BioWare Employees
-
- 273 messages
Or by selecting multiple resources and using the right click menu. I've updated the B2B page a bit to mention those missing options, thanks. 
