Aller au contenu

Photo

DAZips and DAUpdater: Can't export my mod properly


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

#1
FergusM

FergusM
  • Members
  • 460 messages
So I'm trying to release my mod. It's a separate 'campaign'. I tried to use the 'builder to player' package option in the toolset. I left everything selected. I got an error message saying that levela.gpu.rim had an invalid name. Researching this, it turns out that the packager doesn't like names with two dots in them, even though that file extension was the toolset's choice, not mine.

Anyway, since I can't really rename these files, I decided to try adding them to the zip after the fact. I unticked all the files with two dots in their name. This included:

-levela.gpu.rim files
-levelb.gpu.rim files
-sounds.fev.seq

I then took the resulting dazip and renamed it to zip. I opened this with winrar. I put all the levela.gpu.rim and levelb.gpu.rim files in contents/addins/modulename/module/env/(levela or levelb), which is where all the regular levela.rim and levelb.rim files seem to be located. I put sounds.fev.seq in contents/addins/modulename/module/audio/sound, which is where sounds.fev and sounds.fsb are located.

I then renamed the file to a dazip and used daupdater to install it on a machine with a fresh install of dragon age. When I tried to start the mod through "Other campaign", it booted me back to menu with "Unable to load module."

However, I am sure the problem is in the dazip/daupdater process. I uninstalled the mod from my second computer and then manually installed it by copying across the addins/core override folders from the computer with the toolset (also editing addins.xml). When I installed it in this fashion, it worked fine.

How can I get .dazip to work with .gpu.rim files and .fev.seq files?

#2
Proleric

Proleric
  • Members
  • 2 363 messages
According to the wiki, your workaround should have done the trick. Maybe try something other than winrar?

#3
FergusM

FergusM
  • Members
  • 460 messages
I'll try it next time I get a chance to repackage everything, but I have to say I doubt it's the problem.



Perhaps it's a problem with the packager in general rather than just the insertions of extra files. Anyone have any idea about general problems the process could encounter?

#4
FergusM

FergusM
  • Members
  • 460 messages
It turns out that .gpu.rim and so on were working fine. The problem is something to do with the .erf files; if I replace the .erfs with the actual files in the dazip, it works okay. I suspect it has to do with a .bik movie I have, which perhaps cannot play from within an .erf.

#5
FergusM

FergusM
  • Members
  • 460 messages
So as far as I can tell, it is not to do with the .bik movie. There seems to be some general problem with the .erf files. If I have .erfs in the data folders, it will not load. If I have the individual files that get packed into the .erf instead, it works fine. It doesn't seem to be leaving anything out of the .erfs, so I don't know what the issue is.



To work around this, I've decided to open up the .dazip, navigate to where the .erfs are, delete them and simply dump the contents of the appropriate override folder in that location. Haven't fully tested it yet, but I think it will work.