So basically my computer had some major issues, I backed up my Documents folder that had my mod in it..I forgot that the toolset uses databases and didn't back that stuff up so when I reformatted I lost my actual mod works stuff..
I still have the exported mod which still runs in game..but I had a couple things to edit and finish then I was going to release it..
Is there a way to import everything back into the toolset? (I am guessing no..but figured it was worth a try at asking)
Thanks!
Lost Database - Way to import from exported mod?
Débuté par
NewYears1978
, nov. 26 2009 06:06
#1
Posté 26 novembre 2009 - 06:06
#2
Posté 26 novembre 2009 - 03:02
Friendly (page moves to fast) bump
#3
Posté 26 novembre 2009 - 03:08
I have been wondering that too.. created a thread about it but no one responded
#4
Posté 26 novembre 2009 - 04:27
Freindly bump for my friend NewYears. Will be good to know the answer to this, officially, but here is my 2 cents. From the wiki, under the troubleshooting tab, when I was having trouble connecting to the database, here is one of the lines for helping fix the issue:
To me, this means that the database was stored inside you c:\\Program Files\\Dragon Age\\tools\\toolsql folder, which probably isn't one of the ones that you "backed up".
I hope I am wrong, however.
Some users report that the installer fails to create the SQL database (e.g. your Dragon Age\\toolssql\\data folder is empty). You can enter the following command to try restoring the database manually (Change the paths to bw_dragonage_content.bak and your Dragon Age folder as appropriate): "C:\\Program Files\\Microsoft SQL Server\\90\\Tools\\Binn\\"sqlcmd -S .\\BWDATOOLSET -E -Q "RESTORE DATABASE bw_dragonage_content FROM DISK = 'C:\\Program Files\\Dragon Age\\tools\\dbbak\\bw_dragonage_content.bak' WITH MOVE 'bw_dragonage_content' TO 'C:\\Program Files\\Dragon Age\\tools\\toolssql\\Data\\bw_dragonage_content.mdf', MOVE 'bw_dragonage_content_Log' TO 'C:\\Program Files\\Dragon Age\\tools\\toolssql\\Data\\bw_dragonage_content.ldf'"
To me, this means that the database was stored inside you c:\\Program Files\\Dragon Age\\tools\\toolsql folder, which probably isn't one of the ones that you "backed up".
I hope I am wrong, however.
#5
Posté 26 novembre 2009 - 04:35
Remember you can use export Builder to Builder too, which is a good thing to also backup your mod, in case you lose the database again
#6
Posté 27 novembre 2009 - 04:33
Well I WAS going to use builder to bulider to back it up..but didnt get around to it before the crash..will try the above.
#7
Posté 27 novembre 2009 - 04:43
Hrm..not sure teh above works as sicne like you said I formatted my drive..so didnt backup that..
There must be a way to import from the exported mod..wish a Dev would reply.
There must be a way to import from the exported mod..wish a Dev would reply.
#8
Posté 27 novembre 2009 - 04:52
If you didn't back up the database, and didnt back up your 'designer resources' in another manner (exporting, b2b, dazip, etc), then you are probably screwed.
If you are able to enter your raw .are and .erf files into the database, one should be able to do the same with the OC areas and resources. Which I made a post on asking for SQL gurus
If you are able to enter your raw .are and .erf files into the database, one should be able to do the same with the OC areas and resources. Which I made a post on asking for SQL gurus
Modifié par Nodrak, 27 novembre 2009 - 04:54 .
#9
Posté 27 novembre 2009 - 03:49
Well I have my EXPORTED mod..that is working in my game right now...
But I need to reverse the process...I just assume there is no way to do this since they are "encrypted" sorta..which is the point of builder to builder..but I figured there would be some way to do it..I mean all the data is in the exported mod so I would have thought there was some way to reverse the process..my mod is small and simple..not custom areas or anything. I could remake it but I really would rather not..one of the scripts took too long to write and figure all out to have to do it over
But I need to reverse the process...I just assume there is no way to do this since they are "encrypted" sorta..which is the point of builder to builder..but I figured there would be some way to do it..I mean all the data is in the exported mod so I would have thought there was some way to reverse the process..my mod is small and simple..not custom areas or anything. I could remake it but I really would rather not..one of the scripts took too long to write and figure all out to have to do it over
#10
Posté 27 novembre 2009 - 03:55
I encountered this problem too.. after hours upon hours of trying to get our teams database to be viewable by others (familiar with mysql, mssql is just a pain in the @ss) I ended up screwing up the DB, and had to do a full reinstall and ended up losing the progress I had already made. I ended up losing probably a weeks worth of work.. it was horrible.
Although I wish I could fix your problem, I cannot offer any tips on it.. Just wish you the best of luck and hope you can find away to fix it.
Although I wish I could fix your problem, I cannot offer any tips on it.. Just wish you the best of luck and hope you can find away to fix it.
#11
Posté 27 novembre 2009 - 06:14
Seems dumb if you can export and have the mod that works..but no way to put that mod back into the database...gotta be some way...maybe after this holiday week a dev (the toolset guy, name escapes me) will post a reply.
Modifié par NewYears1978, 27 novembre 2009 - 06:17 .
#12
Posté 27 novembre 2009 - 06:35
well only way to get anything back would be if you packaged your nss-files into the dazip and didn't exclude them - in that case you'd still have the scource for them:
extract dazip - its just a zip file.
open the erf-files in it with the toolset and look for any .nss files
extract dazip - its just a zip file.
open the erf-files in it with the toolset and look for any .nss files
#13
Posté 27 novembre 2009 - 06:40
Well I didnt do a dazip.
The only thing I have is my Documents Add ins directory (that the toolset creates) by exporting without dependent resources..so all the files needed to run the mod are there..just not in the form that the toolset uses for modifying I guess?
May be lost in which case I will just forget about it, do not want to have to start over..
The only thing I have is my Documents Add ins directory (that the toolset creates) by exporting without dependent resources..so all the files needed to run the mod are there..just not in the form that the toolset uses for modifying I guess?
May be lost in which case I will just forget about it, do not want to have to start over..
#14
Posté 27 novembre 2009 - 07:36
Unfortunately exporting the resources is similar in principle to compiling source code into an executable. In _theory_ you could recover a lot of it by reversing the process, but in practice it would take a great deal of work to write a tool to do that and it would still lose out on a lot of the formatting that makes stuff understandable by humans. You might be able to dig some of it out manually, I've never tried so I don't know how easy that'd be.
I'm afraid if you've lost your database and didn't make backups (either of the database itself or via builder-to-builder) then you've probably lost the source for good. For future reference to hopefully prevent this sort of loss again, there's a couple of little batch files in Program Files/Dragon Age/tools/DatabaseUtilities/Backup_Restore that will hopefully make it easier to make a backup before doing anything that might blow away the database. It's not the most polished of utilities, for example I don't think it handles backups that are stored in paths with spaces in the directory names, but it's what I use internally when working with the end user toolset database.
I'm afraid if you've lost your database and didn't make backups (either of the database itself or via builder-to-builder) then you've probably lost the source for good. For future reference to hopefully prevent this sort of loss again, there's a couple of little batch files in Program Files/Dragon Age/tools/DatabaseUtilities/Backup_Restore that will hopefully make it easier to make a backup before doing anything that might blow away the database. It's not the most polished of utilities, for example I don't think it handles backups that are stored in paths with spaces in the directory names, but it's what I use internally when working with the end user toolset database.
Modifié par BryanDerksen, 27 novembre 2009 - 07:38 .
#15
Posté 27 novembre 2009 - 10:12
Thanks for the reply. I probably won't redo the mod as it was quite a bit of work and took me awhile to even get it where I wanted it..lol. My wife was riding me about backing up our pictures and music so I made sure to do that..and in the process didn't think about my mods database...just backed up the exported version..it didn't hit me til after I had formatted...woops. I could remake the mod but the big problem is one of my scripts had about 15 items with exact placement that I REALLY wouldn't want to do over. At least with my dialogue and codex entries I can get those in game and remake them..but that one script I don't wish to remake
#16
Posté 27 novembre 2009 - 11:05
Your scripts may have been exported as .nss files (in addition to their compiled counterpart). If they are .nss, then they are the raw scripts, and you just have to open them.
#17
Posté 28 novembre 2009 - 01:10
Yeah the scripts are there..as are all the individual files like the palceables (.utp and .utc) and even the .mor morph and .ure area..but of course when you laod those they are just like xls files in the editor..not sure if there is a way to get the data back in without manually entering it?
im willing to do it manually now that I have my scripts..shouldn't take but a fwe minutes..but still be easier if I could import it some way..but I guess that isn't doable?
im willing to do it manually now that I have my scripts..shouldn't take but a fwe minutes..but still be easier if I could import it some way..but I guess that isn't doable?
#18
Posté 28 novembre 2009 - 05:59
Woo hoo, got everything rebuilt..lukily I had the scripts..and the the plo file which had my huuuge codex entry ...etc.
Got it all reentered and working...just testing now.
Got it all reentered and working...just testing now.
Modifié par NewYears1978, 28 novembre 2009 - 06:15 .





Retour en haut







