Screenshot Bug (Err on First post)

[Deadguy454]

Hello ZDoom, I would like to let people know there is an error with autosaving screenshots in GZDoom 4.13.1b. This bug I found is by conflicting screenshot save files, the AshesStandalone file and the save function of GZDoom4.13.1. I was confused to find the screenshot folder not within what folder I extracted GZDoom in, expecting to find screenshot I captured while playing Eviternity. Instead, I found it in another screenshot folder that autosaves all AshesStandalone screenshots. Upon using the same launch icon by dragging files into said folder and utilizing the screenshot function without seperate directory names (before understanding this problem) it creates a conflict within Windows file explorer. No one would notice this unless they inspect the screenshot folder and see it conflict within the file explorer. This causes the entire Windows Explorer to fail and unable to display names, directories and modular icons to appear. In this instance you would simply need to have a screenshot file that auto saves within that folder as you screen capture within Doom. I believed I moved the screenshot folder from AshesStandalone and placed it conveniently within the default picture directory. So the autosave directory from GZDoom4.13.1b and AshesStandalone saved within the same file. Has anyone else bumped into this? It would not crash my file explorer if I did not open that autosaved screenshots of both Ashes and GZDoom 4.13.1b.

[Graf Zahl]

We cannot do much about this. It seems like AshesStandalone just comes with an unaltered EXE - so it inevitably shares all config data with GZDoom. If the publisher of such standalone games does not change the configuration path it will inevitably clash with GZDoom.

[Enjay]

For a user-end solution, would using a portable ini with one of the games, and setting the screenshot_dir path in there work?

I guess the "problem" has some crossover with what I was asking about here: viewtopic.php?t=79675

i.e. some way of being able to set ini names and locations (and other things, like screenshot directories) as a mod feature (GAMEINFO, whatever) so that people could make stand alone games that don't conflict with a standard GZDoom install without having to compile their own exe.

However, I can understand any reluctance that might exist for enabling modders to be able to specify new folders etc on an end-user's machine.

[Graf Zahl]

You cannot do that because of the chicken-and-egg problem. The config path comes first so you cannot set it based on data that needs the config to be loaded.
It is also very hard to deal with other people's carelessness when releasing a standalone game without actually testing what they released. Best solution here: Default the config name to the EXE name, but that will cause other problems better avoided, e.g. if you got gzdoom.exe, gzdoomd.exe and gzdoomrd.exe you still want them to use the same config file.

[Enjay]

Understood. I figured it was a situation that would come with its own set of problems. Thanks for the answer.