Jump to content

Mod instillation issue on vortex


Recommended Posts

 

testin a pre released version of the fallout 4 mod annex the commonwealth and heres the link to it Annex The Commonwealth at Fallout 4 Nexus - Mods and community (nexusmods.com)

anyway I did the instillation of the mod via vortex but it didn't work as it is displayed in the screenshot

since it puts the02 - Replacement Vanilla Workshop Borders\Meshes\Workshop into Data when it shouldn't be so

the author of the mod said if you want the copy of the xml file jus PM him

 

 

Link to comment
Share on other sites

As the mod author I can tell you the issue isn't the xml, it's Vortex - it's looking for the wrong element names. He already brought the issue up to me, I told him to post it here because it's strictly a Vortex issue. MO2 handles it correctly, the FOMOD Creation Tool actually wrote the XML (so it's machine generated). The issue is definitely Vortex.

Edited by 1000101
Link to comment
Share on other sites

Guest deleted34304850

you may want to send this feedback to the vortex devs as they may not see this. three dots, top right.

Link to comment
Share on other sites

As the mod author I can tell you the issue isn't the xml, it's Vortex - it's looking for the wrong element names. He already brought the issue up to me, I told him to post it here because it's strictly a Vortex issue. MO2 handles it correctly, the FOMOD Creation Tool actually wrote the XML (so it's machine generated). The issue is definitely Vortex.

 

That's a misnomer, MO2 doesn't handle it correctly. In fact the reason it works in MO2 is because MO2 handled FOMODs incorrectly (I'm not just saying it either, Tannin explained this to me).

 

More info on the issue and how to fix it: https://modding.wiki/en/vortex/developer/mod-installer-repair

Link to comment
Share on other sites

Guest deleted34304850

 

As the mod author I can tell you the issue isn't the xml, it's Vortex - it's looking for the wrong element names. He already brought the issue up to me, I told him to post it here because it's strictly a Vortex issue. MO2 handles it correctly, the FOMOD Creation Tool actually wrote the XML (so it's machine generated). The issue is definitely Vortex.

 

That's a misnomer, MO2 doesn't handle it correctly. In fact the reason it works in MO2 is because MO2 handled FOMODs incorrectly (I'm not just saying it either, Tannin explained this to me).

 

More info on the issue and how to fix it: https://modding.wiki/en/vortex/developer/mod-installer-repair

 

i thought that was a bit suss. i took a quick look at the xml in question before work and it didn't sit well with me. glad to see that it's been identified.

Link to comment
Share on other sites

  • 3 weeks later...

fwiw, it turns out there were two minor deviations in the xml from the schema however, neither of which was what Vortex complained about and what Vortex complained about wasn't an issue or incorrect at all. Anyway, fixing the two actual deviations stopped Vortex from throwing the incorrect error.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

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