Jump to content

Status Of Dragon Age Origins Vortex Support?


Zanderat

Recommended Posts

DAO seems to be supported by Vortex. But trying to install Qwinn's Fixes (analogous to the UOP's for Bethesda games) https://www.nexusmods.com/dragonage/mods/4689? it seems to fail. I don't see the files (hard links) at the expected file paths on the log (or at all). Here is my log:

*** Vortex mod report for: QUDAO Fixpack v3.5
<This report was automatically generated by Vortex using the information from the reporter's installation, including any alterations - intentional or otherwise - they may have made to the data.>
**************************************************
* Mod details
**************************************************
Mod name: QUDAO Fixpack v3.5
Version: 3.5
Archive: QUDAO Fixpack v3.5-4689-3-5-1550475932.zip
Mod type: dazip
Managed game: dragonage
Mod intended for: dragonage
MD5 checksum: f4029384cecf3b547de741d5e3d8aebf
Download source: nexus (mod 4689, file 1000006176)
Last deployment: Fri, 17 Jul 2020 19:05:02 GMT
Deployment method: hardlink_activator

**************************************************
* Deployed files
**************************************************
AddIns\qwinn_fixpack_3\core\audio\sound\alistair_main.fev (09b18d7813676b3017b3dfc3dda3620a)
AddIns\qwinn_fixpack_3\core\audio\sound\alistair_main.fsb (9adc91f889138047ac66ed938ca5c4b9)
AddIns\qwinn_fixpack_3\core\audio\sound\alistair_main_qwinn.fsb (3911dadc5714184cb5666e29b799abbc)
AddIns\qwinn_fixpack_3\core\audio\sound\cli300_bodyguard.fev (9e5023ff8f2ca4f88582ee1b66a09240)
AddIns\qwinn_fixpack_3\core\audio\sound\cli300_bodyguard_qwinn.fsb (ae5c266aa23d4d2c9ca1da8f2030ac96)
AddIns\qwinn_fixpack_3\core\audio\sound\den220_pick4_seneshal.fev (156c86aa880bacdb59f9113e185cadfe)
AddIns\qwinn_fixpack_3\core\audio\sound\den220_pick4_seneshal_qwinn.fsb (fa46b717a7a871c09bbaf23810eb648b)
AddIns\qwinn_fixpack_3\core\audio\sound\den220_pick4_sen_grd_fnky.fev (b85ba6c69271a28c9785fef4f82aad0e)
AddIns\qwinn_fixpack_3\core\audio\sound\den220_pick4_sen_grd_fnky.fsb (5283d3efced0a13bf54987657f96db9d)
AddIns\qwinn_fixpack_3\core\audio\sound\den_herren.fev (325ba5a558f00af038e492cc03998234)
AddIns\qwinn_fixpack_3\core\audio\sound\den_herren.fsb (79ba72abe36ea517569df534b160e673)
AddIns\qwinn_fixpack_3\core\audio\sound\morrigan_main.fev (c226660f8e1be0faf34e7a45e60b51af)
AddIns\qwinn_fixpack_3\core\audio\sound\morrigan_main.fsb (c18fd832ac5c61fde9a2001989eb5e4e)
AddIns\qwinn_fixpack_3\core\audio\sound\ntb100cr_lanaya.fev (cd7bacad81bf84a245d49248731a4dd7)
AddIns\qwinn_fixpack_3\core\audio\sound\ntb100cr_lanaya.fsb (904c337a066b94d7c562c4d8c401131e)
AddIns\qwinn_fixpack_3\core\audio\sound\ntb100cr_lanaya_qwinn.fsb (06e2bc729ea1074cc1221b9aee345956)
AddIns\qwinn_fixpack_3\core\audio\sound\ntb100cr_sarel.fev (a164bce4c62c1bdfc4b1e9f2936eb746)
AddIns\qwinn_fixpack_3\core\audio\sound\ntb100cr_sarel.fsb (e3ff9aae3fb09c06d087361fb46ab755)
AddIns\qwinn_fixpack_3\core\audio\sound\ntb100cr_sarel_qwinn.fsb (d10f76cd2978544bd151eaaa9ffad954)
AddIns\qwinn_fixpack_3\core\data\qwinn_fixpack_3_modcore.erf (e2d35900dbd58412016e96bb216445ab)
AddIns\qwinn_fixpack_3\module\qwinn_fixpack_3.cif (4cfb1bafd72a97641080311507d48a75)
AddIns\qwinn_fixpack_3\module\data\qwinn_fixpack_3_module.erf (ac2b77a2b66472687f63d5e829e3b946)
packages\core\data\qwinn_fixpack_3_package.erf (93817639221fe26960b7d662c15a605e)

**************************************************
* Files overwritten by other mod
**************************************************
<None>

**************************************************
* Files not deployed
**************************************************
AddIns\qwinn_fixpack_3\manifest.xml

**************************************************
* Files that are supposed to be deployed but weren't found
**************************************************
<None>

**************************************************
* Files that are present but couldn't be read
**************************************************
<None>

 

 

edit: Found the files. It's all good for now. Had a brain freeze. FYI, file path is \Documents\BioWare\Dragon Age NOT the actual game folder.

Link to comment
Share on other sites

We need a real clear description - somewhere - of exactly which games have to be installed on the same drive as Documents.

That is somewhat of a maintenance nightmare, given that most users have Documents on C: - and no room for games on the boot drive.

Link to comment
Share on other sites

We need a real clear description - somewhere - of exactly which games have to be installed on the same drive as Documents.

That is somewhat of a maintenance nightmare, given that most users have Documents on C: - and no room for games on the boot drive.

 

 

Games like DAO don't NEED to be installed on the same drive as Documents, Zanderat is talking about how some game have their mods put in the Documents Folder, and it's usually EA Games and Bioware Games, that usually have their Mods put in the DOCUMENTS folder rather than the Game Folder.

Such as The Sims, Neverwinter Nights etc

 

I have NWN 1 and 2 installed on my D:\ drive, however, the Mods go in the Documents Folder on C:\, which leads to some confusion as to where the Mod Staging Folder goes for those games, should it go on D:\ with the GAME, or C:\ with the Mod (Documents) folder?

Link to comment
Share on other sites

So only symlink deployment for those games? And the game does not need to be on the same drive as Dcuments?

 

Exactly.

However, I don't know if the Mod Staging Folder should go on the same drive as the Game, or the Documents folder for those particular games.

I assume the same drive as the game, however, when I tried to use Vortex to mod the Sims 4, I couldn't get any mods to show up in the game, and Sims 4 is one of those games that puts the Mods in "Documents", instead of the game folder.

 

 

 

 

Link to comment
Share on other sites

My DAO game folder is on mt C: drive, as is my Docs folder and staging folder. I am using hard link deployment.

Link to comment
Share on other sites

@rmm200 If you go to settings->mods and click the "Suggest" button alongside the staging folder it will always suggest a path that is on the same drive as the (primary) mod directory such that hard links would be applicable. Imho that is preferable to a documentation somewhere on a wiki or something that users may miss and that will be outdated half the time.

 

re "and no room for games on the boot drive": Well, if the game requires mods to be installed in documents you would require that disk space if you manually installed the mods anyway, so it's not like Vortex limits you in something that other approaches wouldn't.

symlink deployment or usvfs however let you stage the mods on whatever drive you have free disk space. As long as the game supports it I would say symlinks are the best solution.

 

@HTR Sims 4 definitively works fine when the staging folder is on a different drive, not sure why the mods wouldn't show up in your case.

Link to comment
Share on other sites

It is worth pointing out that I have had to repack several mods to work with Vortex. Also, Vortex can't handle .override files.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...