tomtheclone Posted March 29, 2019 Share Posted March 29, 2019 You can try not having the backups saving and see if vortex is ok with that.- personally I like having backups cause I know the 2 or 3 times I actually needed them it was nice to have.Which is why I use Git, but committing isn't a one step process due to this feature. Link to comment Share on other sites More sharing options...
soupdragon1234 Posted March 29, 2019 Share Posted March 29, 2019 Vortex sees the hard link as broken because the file gets moved like that. With same file name it knows to ask if you want to keep changes. Older versions (pre 0.17.x) you got two options in that case: save the changes or revert to before the change. With subsequent versions you get an extra option - it states "update available" and do I want to update, save, or revert. I've not idea where this "update" springs from and to be honest I'm not sure how to precede, I usually default to what I've been doing previously which is select "save" and that seems to be working... I think. Do you mean "use newer version?" It means keep the changed file deployed, but don't update staging. In other words, it tells Vortex to shut up (for now), and nothing changes. Ah, right, I tried that and its working... I think. (newer version, yes you're right) thanks. Link to comment Share on other sites More sharing options...
tomtheclone Posted March 29, 2019 Share Posted March 29, 2019 Vortex sees the hard link as broken because the file gets moved like that. With same file name it knows to ask if you want to keep changes. Older versions (pre 0.17.x) you got two options in that case: save the changes or revert to before the change. With subsequent versions you get an extra option - it states "update available" and do I want to update, save, or revert. I've not idea where this "update" springs from and to be honest I'm not sure how to precede, I usually default to what I've been doing previously which is select "save" and that seems to be working... I think. Do you mean "use newer version?" It means keep the changed file deployed, but don't update staging. In other words, it tells Vortex to shut up (for now), and nothing changes. Link to comment Share on other sites More sharing options...
HadToRegister Posted March 29, 2019 Share Posted March 29, 2019 Vortex sees the hard link as broken because the file gets moved like that. With same file name it knows to ask if you want to keep changes. Older versions (pre 0.17.x) you got two options in that case: save the changes or revert to before the change. With subsequent versions you get an extra option - it states "update available" and do I want to update, save, or revert. I've not idea where this "update" springs from and to be honest I'm not sure how to precede, I usually default to what I've been doing previously which is select "save" and that seems to be working... I think. Just pick SAVE. Don't ever pick Revert because that just loads the unedited version of the ESP you spent time editing and will undo every change you made to the mod Link to comment Share on other sites More sharing options...
tomtheclone Posted March 29, 2019 Share Posted March 29, 2019 Vortex sees the hard link as broken because the file gets moved like that. With same file name it knows to ask if you want to keep changes. Older versions (pre 0.17.x) you got two options in that case: save the changes or revert to before the change. With subsequent versions you get an extra option - it states "update available" and do I want to update, save, or revert. I've not idea where this "update" springs from and to be honest I'm not sure how to precede, I usually default to what I've been doing previously which is select "save" and that seems to be working... I think. Just pick SAVE. Don't ever pick Revert because that just loads the unedited version of the ESP you spent time editing and will undo every change you made to the mod One of these days, I'll do that, and I will hate myself. I do, however, keep whatever I'm using to edit with (CK or TES5Edit) open in the event that happens. Link to comment Share on other sites More sharing options...
HadToRegister Posted March 30, 2019 Share Posted March 30, 2019 One of these days, I'll do that, and I will hate myself. I do, however, keep whatever I'm using to edit with (CK or TES5Edit) open in the event that happens. I make a folder in the Data folder called BACKUP ESPS FOR EDITING And copy and drag the esps I know I'm going to be editing in Xedit into that folder so I have a backup Link to comment Share on other sites More sharing options...
tomtheclone Posted March 30, 2019 Share Posted March 30, 2019 One of these days, I'll do that, and I will hate myself. I do, however, keep whatever I'm using to edit with (CK or TES5Edit) open in the event that happens. I make a folder in the Data folder called BACKUP ESPS FOR EDITING And copy and drag the esps I know I'm going to be editing in Xedit into that folder so I have a backup I have all my stuff in Git repos so there is no need for that for me. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.