It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
I was wondering if anyone had any insight about a problem I have when attempting to install the "DragonAgeToolset1.01Setup.exe". The installation process goes normal until an error message appears stating the uninstall portion of the toolset cannot be found (I ignored). The toolset is installed but when launched this appears "location of game build either not specified or the update program was never run to copy the build onto your computer. Run the toolset configuration program and verify your settings" I tried some basic regedit fixes (the custom script also) but none have worked. If anyone has any solutions that would be greatly appreciated!
Attachments:
captu1re.png (297 Kb)
Post edited December 24, 2020 by Deathknight5405
This question / problem has been solved by olnortonimage
I don't use Galaxy, or even the GOG version of the game, so this may be no help at all but...
Possibly that registry entry is good enough for the game, but the toolset looks for the DAO entry in a specific place.
For my disc version that is in HKLM\SOFTWARE\WOW6432Node\BioWare\Dragon Age
You could try creating a new key there, and then a new string with your path
See Pic
Attachments:
daoreg.jpg (219 Kb)
avatar
olnorton: I don't use Galaxy, or even the GOG version of the game, so this may be no help at all but...
Possibly that registry entry is good enough for the game, but the toolset looks for the DAO entry in a specific place.
For my disc version that is in HKLM\SOFTWARE\WOW6432Node\BioWare\Dragon Age
You could try creating a new key there, and then a new string with your path
See Pic
I seem to be having trouble editing the Regedit, here is what I have (image below). The program seems to have installed correctly but it wants me to run the config software, maybe this information helps any? Thanks for helping me out!
Attachments:
capture.jpg (50 Kb)
capture2.png (65 Kb)
Post edited December 25, 2020 by Deathknight5405
The path showing in that pic is different from the path that was shown in your original pic.
Where is the game actually installed?

If you go to the install folder, then tools and run ConfigureToolset.exe it should show your actual path to the Dragonage folder.
See the pic of mine.
Attachments:
avatar
olnorton: The path showing in that pic is different from the path that was shown in your original pic.
Where is the game actually installed?

If you go to the install folder, then tools and run ConfigureToolset.exe it should show your actual path to the Dragonage folder.
See the pic of mine.
The game is installed in "C:\GOG Games\Dragon Age Origins\tools" for mine, the game runs perfectly normal as well.
Attachments:
capture.jpg (26 Kb)
So after that you clicked on next, then excepted the default database and then finish, but the toolset still says it can't find the game?
avatar
olnorton: So after that you clicked on next, then excepted the default database and then finish, but the toolset still says it can't find the game?
Yep, I used the same file location and clicked next using the default database. Ill attach some images, that may help. Thanks again for all of the support! Link: https://drive.google.com/drive/folders/1D0lGmJcDzF4tstnO3JtehMBA3Igq8Aog?usp=sharing
Post edited December 25, 2020 by Deathknight5405
In the screenshot of your registry, it shows the path to the Dragonage folder in "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BioWare\Dragon Age\Toolset" (did you put it there?)
Is it also in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BioWare\Dragon Age
Like in my screenshot
avatar
olnorton: In the screenshot of your registry, it shows the path to the Dragonage folder in "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BioWare\Dragon Age\Toolset" (did you put it there?)
Is it also in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BioWare\Dragon Age
Like in my screenshot
Yes, I manually put both of those entry's in. I may have done them wrong and this may be causing the issue
The Dragonage path doesn't need to be in ...toolset, only that SQL is installed and the path to the database. See pic.
The Dragonage path needs to be 1 step up in Dragon Age. See pic in post number 2
Attachments:
toolset.jpg (178 Kb)
avatar
olnorton: The Dragonage path doesn't need to be in ...toolset, only that SQL is installed and the path to the database. See pic.
The Dragonage path needs to be 1 step up in Dragon Age. See pic in post number 2
Ok thanks! I moved the paths around but still get the same error message. Ill give an image of the exact content in the specified path. I am sending it to the bin_ship folder, I believe that is correct. I am quite stumped about why this isn't working, thank you so much again!
Attachments:
capture5.png (118 Kb)
capture6.png (119 Kb)
capture7.png (281 Kb)
Well the bin_ship seems like it should work, but given that it isn't (and it isn't in my path for which the toolset does work), try removing it from the path and just use the Dragon Age Origins folder
Then run ConfigureToolset.exe again leaving out the bin_ship folder
Post edited December 25, 2020 by olnorton
avatar
olnorton: Well the bin_ship seems like it should work, but given that it isn't (and it isn't in my path for which the toolset does work), try removing it from the path and just use the Dragon Age Origins folder
Then run ConfigureToolset.exe again leaving out the bin_ship folder
Thanks you!! It worked by removing the bin_ship haha!
Just as well, I was running out of ideas.
Enjoy your modding, and Merry Christmas.
For anyone reading this, I just downloaded the Toolset from GOG.
It comes with a Windows Command Script regkey-switch.cmd
You right click and run the script as administator, and press Y to add the registry entries the toolset is looking for when first run.
After the toolset starts, don't forget to run the script again to modify the entry or EA Origins will bork your game.
The toolset will continue to work after the registry is changed back.