Closed ruby-R53 closed 1 year ago
ruby-R53
commented
1 year ago oh yeah, i also noticed that when i open the module on protracker the other way, not only it doesn't load protracker.ini, the window title also changes from "ProTracker 2 clone v1.55" to "ProTracker 2 clone v1.50" for some reason.
8bitbubsy
commented
1 year ago Not sure what OS you use, but protracker.ini is getting loaded when I double-click on .MODs associated with the PT2 clone EXE in Windows, so no problems here. Also, if you get a different version in the window title, then it suggests that you have an earlier version floating around somewhere on your drive that is being used for some reason.
ruby-R53
commented
1 year ago "Not sure what OS you use" oh yeah, forgot to mention that, currently using windows 10. "if you get a different version in the window title, then it suggests that you have an earlier version floating around somewhere on your drive that is being used for some reason." yeah, for some VERY ODD REASON, because i'm explicitly choosing v1.55 when i open the file with protracker.
ruby-R53
commented
1 year ago so now the problem was windows itself and not protracker. even though i was clearly choosing the latest version, windows insisted on using the earliest version i had, v1.50, which had the default settings. now i deleted the old versions and kept only the latest one (v1.55). damn you, windows >:(
8bitbubsy
commented
1 year ago Yeah, this is why I recommend just overwriting the EXE (and SDL2.DLL if needed) in the directory when you update to a newer version, don't put different versions in different directories. I'm glad you sorted it out, though.
if i open protracker, and select the module i wanna edit/ play, it obviously loads protracker.ini first as it should, but if i right click on a module and select "open with..." and then choose protracker, protracker loads but without protracker.ini, so it uses its default settings instead.