Remember Paths?

[y0himba]

Is DLSS-Updater supposed to remember paths? I need to re-enter each launcher path each time I launch.

If this is by design, can the updater read from a text file that is created on first run? With an optional switch to recreate it, or if it is a text file, then it could be edited...

Or maybe I could create the file myself with one path per line and it could be read from by the program?

I am not a programmer, so I have no idea if any of this is possible.

After the paths are entered, the program works swimmingly for me. Wonderful!

[Recol]

As of now, it does not, there are 2 reasons why this is the case, so that it is dynamic and flexible.

If it were the case that paths were to be remembered this would as of now lock out users with multiple drives who have games stored across in different folders who need to rerun the tool.

Yes, it's definitely possible to implement, but this is a chicken and egg situation where everything has a consequence, and the approach introduces more problems than it solves for users, generally (It does not support this functionality, it would need to be added).

Fundamentally this isn't a easy thing to solve in order to have both requirements be true at the same time, if I were to allow remembering paths then I would also need to figure out on how to go about it with the current feature support.

I'm moderately fine with the current integration in that whilst this can be annoying, i would rather it be slightly more that, than locking out features entirely for the reverse, that doesn't mean it's not the final version, but it's a "fine for now" state, I will take a more holistic view about this section specifically over the long term.

[y0himba]

I am actually one of those users. I have multiple nVME drives with games as well as a couple SSDs and 2 HDDs. I have been gaming for many, many years. I have just over 4000 games between all the launchers, and probably 30 installed? I think? LOL.

How about an option to remember? Sort of a statement when it launches that says "If you would like to remember paths create a txt file named "something.txt" with one path per line and place it in the updater directory. "

That way the flexibility is retained, but the choice is there for horrible typists like myself?

[Recol]

@y0himba Feasibly, this is more or less impossible - due to the way the update mechanism works the old folder structure is overwritten, effectively replaced, so as soon as someone updates the program they would need to manually create it every time, so any implementation like this has to be well, done by me to avoid the situation. It's a limitation of the architecture in that fundamentally it's designed to remove as much user input as possible, and i'd like to keep within that realm, as deviating creates confusion, which leads to more problems.

I won't action anything on this specifically for the near/medium term as it's a multi-faceted problem, with not a lot of easy solutions, it's more or less just a engineering challenge to do well.

[y0himba]

It works perfectly for me either way, I am just lazy. I love how I've gone from DOS, to MSDOS, to Windows, back to MSDOS. Except now my hands are too old to use it quickly.

Thank you for the replies and honest responses! I mean that. I am not a galaxy brain so I have no idea how it's done. So again, thank you!

[Recol]

@y0himba Not a problem! I appreciate the idea/feedback it's very useful, it is something that I want to do, just time mostly :)

[github-actions[bot]]

Stale issue message