Jump to content

Starfield Extension has been updated to 0.4.0


insomnious

Recommended Posts

I've gotten a hotfix ready that removes the symlink altogether and doesn't strip comments out of the ini files when it checks them. The main 'problem' that this will cause is that there won't be a Data folder in Documents anymore but at least the user can do what they like with that then and it'll quickly remove the OneDrive problem. Thoughts?

 

If anyone could post some of their more complicated StarfieldCustom.ini files that would be super useful so I can run them against tests. More complicated the better with comments and anything else.

 

Will test more tomorrow before we push this out - thanks for your patience!

Mine just had a few lines in there. When I get home I can send it if it's helpful (the ini stuff).

 

On the topic of the mydocuments / data folder. For me it's not even about "onedrive". I had bakas tool setup so I didn't have to use that folder at all and everything was setup and fine in the starfield data folder. Baka specifically stops the game from running when it detects a data folder in the mydocuments/mygames folder. So I disabled that hoping it would solve it. Yes, that message went away, but then SFSE said it couldn't find dll's and such. So I just couldn't get it to run anymore. I could launch starfield alone but that would of course mean no sfse mods and potentially render my save file unusable as well.

 

My suggestion is give the users the option.

 

1. Mygames/Starfield/Data uses your intended design to function

2. Starfield/Data would be an option where we just define the location manually it makes NO other changes other than where to deploy files to.

Link to comment
Share on other sites

I wasn't going to chime in but...... The obvious solution is to roll the extension back to v.0.3.0 (turn off automatic updates for now) and use the Bakka fix. Suggest the dev contact that mod author and adopt their fix into Vortex. Also, please provide a reason for messing with people's ini files and perhaps stop this behavior as it doesn't seem necessary.

Link to comment
Share on other sites

Guest deleted34304850

i really don't have the words for this.

 

who would release an update that doesn't test one drive, which microsoft are desperately trying to integrate as a main part of windows?

who edits ini files with no backup and removes comments?

 

who does that?

 

if you're going to edit something - back it up first

if you're goinig to change a value for something - change it and comment the change so people know whats changed, by whom and when.

 

if you can't do that - then leave the file well alone until you can do it safely.

 

this is basic stuff.

Link to comment
Share on other sites

I've gotten a hotfix ready that removes the symlink altogether and doesn't strip comments out of the ini files when it checks them. The main 'problem' that this will cause is that there won't be a Data folder in Documents anymore but at least the user can do what they like with that then and it'll quickly remove the OneDrive problem. Thoughts?

 

If anyone could post some of their more complicated StarfieldCustom.ini files that would be super useful so I can run them against tests. More complicated the better with comments and anything else.

 

Will test more tomorrow before we push this out - thanks for your patience!

I would incorporate the Bakka fix instead. Also, I would stop messing with StarfieldCustom.ini. It doesn't seem necessary.

Link to comment
Share on other sites

I would incorporate the Bakka fix instead. Also, I would stop messing with StarfieldCustom.ini. It doesn't seem necessary.

 

This solution is quite sensible. I would encourage the developers to seriously consider it.

 

As for my Vortex installation, v0.4.0 works fine because I uninstalled OneDrive ages ago. (I may be paranoid, but I do not trust intrusive cloud storage or any other kind of cloud storage.) Furthermore my StarfieldCustom.ini was untouched.

 

That said, OneDrive users obviously need help and are owed a solution ASAP.

Link to comment
Share on other sites

The team is working on trying to find a solution.

 

However, for all the people saying to just roll the Baka fix into the process, this is the Baka fix: https://www.nexusmods.com/starfield/mods/1599

 

It specifically states on the page that it only works with the Steam version of the game and requires SFSE in order to work:

 

First, download and install the Starfield Script Extender. (Required, and only compatible with the Steam version of the game.)

 

 

Any solution needs to work for both Game Pass players and Steam players of Starfield, and we definitely do not want to make our Vortex support of Starfield dependent on SFSE in order to work.

 

Thus, rolling Baka fix into Vortex is definitely NOT a good idea.

 

There's a lot of lessons for the Vortex team to learn from this fiasco, but the solution a lot of you are touting as "easy" is NOT a good solution and would make things worse, not better, for our users.

Link to comment
Share on other sites

It should be noted that Vortex backs up EVERYTHING before making the changes so recovery shouldn't be a big issue.

 

Has the Nexus staff had any contact with Bethesda regarding what kind of monkey wrench Creation Club is going to throw in all this? If the CC stuff goes in the My Documents folder will the Vortex solution work with that?

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

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