Hm, I've set the setting to 0 in my ini and if I press the [PRINT] key, only the the ENB screenshots are get saved. Maybe this tweak ;Displays screenshot notification as a console message Screenshot Notification To Console = true in PO3's Tweaks is also handling it? Nevermind, the message is there and that's what you meant - still the screenshots aren't created. Will download your solution.
I guess even if you disable the message with powerofthree's tweaks, the game still attempts to create a screenshot even if, for whatever reason, it can't (such as disabling in ini - surprised it works for you, maybe it's dependent on version).
If you can unbind the screenshot key in the GUI from that mod, then just use that. Otherwise you will have to manually copy+paste the lines from this .txt in the .txt generated by that.
Unfortunately, this mod disables the usable hotkeys in the Creations menu from the 1.6.1130.0 game update that happened the day after this mod was published. Would you consider resolving this in a mod update?
What hotkeys are you talking about? This mod only unbinds screenshotting, but it's possible that the update added new lines to the control map that now need to be added into this mod as well. If you can send me a copy of your controlmap.txt, I'll have a look at it. You'll need to extract Skyrim - Interface.bsa somewhere and send me this file -> interface\controls\pc\controlmap.txt Or you could even just paste it in a spoiler.
The latest update added a Creations menu in place of the old Mods/Creation Club menus. And the hotkeys are found along the bottom of the screen there. Stuff like Shift, T, O, X, etc. Here's a pastebin link for my copy of the 1.6.1130.0 version of interface\controls\pc\controlmap.txt in the Interface.bsa: https://pastebin.com/vFdww1t6
SE way is to make [Display] sScreenShotBaseName=? tweak because no file with "?" in its name can be created. This is known since... well, since we know about bAllowScreenshots.
tweak because no file with "?" in its name can be created. This is known since... well, since we know about bAllowScreenshots.
This is an incredibly hacky solution that only half-works. You are correct that the screenshot does not get saved. However, Skyrim still attempts to take a screenshot: you get the message that a screenshot has been created, and the game has that momentary couple-frame freeze as it collects pixel data.
Barring disabling the function itself (which is possible via Skyrim.ini in LE, but not SE), the only correct way is to completely unbind the key. Whether that should be done as a hardcoded tweak (easy to implement and diagnose conflicts) or as a .NET framework dll plugin (arcane to me, but theoretically better potential compatibility) is the only thing up for debate.
21 comments
Hm, I've set the setting to 0 in my ini and if I press the [PRINT] key, only the the ENB screenshots are get saved.
Nevermind, the message is there and that's what you meant - still the screenshots aren't created. Will download your solution.Maybe this tweak
;Displays screenshot notification as a console message
in PO3's Tweaks is also handling it?Screenshot Notification To Console = true
Would you consider resolving this in a mod update?
You'll need to extract Skyrim - Interface.bsa somewhere and send me this file -> interface\controls\pc\controlmap.txt
Or you could even just paste it in a spoiler.
And the hotkeys are found along the bottom of the screen there. Stuff like Shift, T, O, X, etc.
Here's a pastebin link for my copy of the 1.6.1130.0 version of interface\controls\pc\controlmap.txt in the Interface.bsa:
https://pastebin.com/vFdww1t6
Anyway thanks for the mod, finally
[Display]tweak because no file with "?" in its name can be created. This is known since... well, since we know about bAllowScreenshots.sScreenShotBaseName=?
This is an incredibly hacky solution that only half-works. You are correct that the screenshot does not get saved. However, Skyrim still attempts to take a screenshot: you get the message that a screenshot has been created, and the game has that momentary couple-frame freeze as it collects pixel data.
Barring disabling the function itself (which is possible via Skyrim.ini in LE, but not SE), the only correct way is to completely unbind the key. Whether that should be done as a hardcoded tweak (easy to implement and diagnose conflicts) or as a .NET framework dll plugin (arcane to me, but theoretically better potential compatibility) is the only thing up for debate.