ReShade +Framework 18.0 "Shared Shader Toggle key"
- Cloudbill
- Topic Author
Please Log in or Create an account to join the conversation.
- Ganossa
Cloudbill wrote: I'm getting an "undeclared identifier - shared shader toggle key" error whenever I start a game.
Do you have this line
#define SharedShader_ToggleKey RFX_ToggleKey
in your ReShade/SweetFX_settings.cfg?
Please Log in or Create an account to join the conversation.
- Cloudbill
- Topic Author
Should I add that line between these two lines :
#define ReShade_ToggleKey VK_SCROLL //Set the key that should toggle the effects On/Off
#define ReShade_DepthToggleKey VK_MULTIPLY //Set the key to toggle the depth view On/Off
In the Global settings?
Like so:
#define ReShade_ToggleKey VK_SCROLL //Set the key that should toggle the effects On/Off
#define SharedShader_ToggleKey RFX_ToggleKey
#define ReShade_DepthToggleKey VK_MULTIPLY //Set the key to toggle the depth view On/Off
My bad the previous lines were from 17.0.
In 18.0 there is still no "#define SharedShader_ToggleKey RFX_ToggleKey" . Should I add it in the same way only after the "#define RFX_ToggleKey VK_SCROLL //Set the global key that should toggle the effects On/Off" ?
Please Log in or Create an account to join the conversation.
- JBeckman
(Further updates seem to be planned but that will probably change it to 0.18.1 and so on until the next major update to I guess 0.19.0.)
/*----------------------------------------------------------.
/ Shared Shaders settings /
'----------------------------------------------------------*/
//Below you can find all shared shader and their settings
#define SharedShader_ToggleKey RFX_ToggleKey
Also ReShade32.dll should be version 0.18.0.832 and ReShade64.dll 0.18.0.833 as the very first release accidentally used a older build.
Please Log in or Create an account to join the conversation.
- crosire
That's because the underlying ReShade didn't change. It's still 0.18.0, with the framework shader pack being updated or not .JBeckman wrote: 0.18.0 has been updated about three times since it's initial release I believe, fixing some smaller bugs mostly but it keeps the version number the same so it's easy to miss a update if you don't check the ReShade release thread thoroughly.
Please Log in or Create an account to join the conversation.
- Cloudbill
- Topic Author
I just checked and it is working as it should. Thank you for pointing the issue out to me JBeckman. I didn't have the time or forethought to check any posts about changes in the initial 18.0 release.
Please Log in or Create an account to join the conversation.
- crosire
Please Log in or Create an account to join the conversation.
- JBeckman
crosire wrote:
That's because the underlying ReShade didn't change. It's still 0.18.0, with the framework shader pack being updated or not .JBeckman wrote: 0.18.0 has been updated about three times since it's initial release I believe, fixing some smaller bugs mostly but it keeps the version number the same so it's easy to miss a update if you don't check the ReShade release thread thoroughly.
That makes sense.
Cloudbill wrote: Maybe that's the issue. I am going ahead and d/l'ing the release that's was uploaded on 2015-04-20 02:49:57. Hopeful that's what is wrong. I'll edit this post either way with the results.
I just checked and it is working as it should. Thank you for pointing the issue out to me JBeckman. I didn't have the time or forethought to check any posts about changes in the initial 18.0 release.
I actually just checked the ReShade files myself as well just to see if there had been any further updates and it turns out I was missing a update to Util.h in the Common folder which corrected a "else" definition to "#else" for the screenshot file format functionality.
Please Log in or Create an account to join the conversation.