Aller au contenu

Photo

SOLVED: Sharing Compiled Levels


  • Veuillez vous connecter pour répondre
8 réponses à ce sujet

#1
dbecker

dbecker
  • Members
  • 9 messages
I'm working on a project with multiple people and I want to share my compiled levels, or areas with them. Is there anything else, any other files, I need to provide in addition to a Builder to Builder Export with the area resource.

I tried this and it was unsuccessful, so I thought I might need to provide the level resource as well. I would like to provide a compiled version though so that they don't have to compile the levels themselves each time. If there is a compiled level file, where would it be located?

I wasn't able to locate anything on the wiki about sharing compiled (Do All Local Posts) levels, any suggestions?

Thanks.

Modifié par dbecker, 27 janvier 2010 - 08:48 .


#2
Bibdy

Bibdy
  • Members
  • 1 455 messages
Oh, I didn't see this thread before posting in the other one. I don't think there is a way to do it. You just have to send them the .lvl and .erf file for your level and they'll load it into their toolset and do the Local Post themselves.

#3
dbecker

dbecker
  • Members
  • 9 messages
I figured it out.

It looks like the compiled map is saved as a .ARL file in the "BioWare/Dragon Age/AddIns/###/core/override/toolsetexport/" folder. This file can then be shared. It will be the same 8 characters or less name you used when naming the layout.

I just got it to work, so I'm not 100% sure everything works, but I'll keep looking at it. Feel free to post here if you have questions about it and I'll see if I can answer them.

Of course, the areas can be sent using Builder to Builder Exports and they will reference the layout file (.arl).

Modifié par dbecker, 27 janvier 2010 - 08:46 .


#4
-Semper-

-Semper-
  • Members
  • 2 256 messages
i don't think that will work. in my opinion the compiled level is stored within the database and so it can be used as an area layout. if you just copy the arl file then this entry is still absent and therefor the layout won't shop up.

Modifié par -Semper-, 27 janvier 2010 - 09:30 .


#5
dbecker

dbecker
  • Members
  • 9 messages
Well you will need to have an area that uses the layout and that will need to be shared using the builder to builder export. When the area references the layout file, I believe that information is what will be contained in the database. I have successfully shared a compiled level (layout file) with our sound guy and he was able to use the layout in an area he created.



If you have a chance to give it a shot I'd be interested to hear if it worked for you or not and if you ran into any problems.

#6
-Semper-

-Semper-
  • Members
  • 2 256 messages
gratz, sounds cool ;)

#7
dbecker

dbecker
  • Members
  • 9 messages
Just another note about this, if it's not working it might be worth transferring the entire folder for the layout. This probably isn't an elegant solution, but it gets it done. I'll keep posting here if I find better ways to do this.

#8
Craig Graff

Craig Graff
  • Members
  • 608 messages
Just a quick confirmation that area layouts are not part of the database, only the references to them within areas.

#9
dbecker

dbecker
  • Members
  • 9 messages
That's how I understood it, areas reference layouts. Layouts are Art Resources and not part of the database.



How does that method of transfer sound? Is that the way to do it or is there a better method?