- Posts: 8
LUT issue with ver 4.0.2
2 years 10 months ago #6 by Mark A
Replied by Mark A on topic LUT issue with ver 4.0.2
If the modifiers have been keyed in properly (setting in left box and value in right), it looks like I'll have to stick with v3.4.1 
.
. Please Log in or Create an account to join the conversation.
2 years 9 months ago #10 by Lanvali
Replied by Lanvali on topic LUT issue with ver 4.0.2
Hello,
As I were quite impatient I re-installed 3.4.1 until I could find a solution.
I looked at your replies, and something I don't understand.
In my textures files, my LUT texture is 1024x32.
I also checked my ReShade.ici file in the [GENERAL] section : there's no specific path for LUT, but the Effect Search path and Texture Search path, and they both correspond to the right files.
Where should I check?
Thank you for your help
As I were quite impatient I re-installed 3.4.1 until I could find a solution.
I looked at your replies, and something I don't understand.
In my textures files, my LUT texture is 1024x32.
I also checked my ReShade.ici file in the [GENERAL] section : there's no specific path for LUT, but the Effect Search path and Texture Search path, and they both correspond to the right files.
Where should I check?
Thank you for your help
Please Log in or Create an account to join the conversation.
2 years 9 months ago - 2 years 9 months ago #11 by Daodan You can override these values with the global preprocessor definitions (the fLUT* ones):
Try naming your LUT a unique name and add that to the preprocessor definitions.
Then enable the LUT technique and check in the Log tab for any errors.
If you see something like thatyou need to check if there's any error in the search paths and/or the LUT name.
Replied by Daodan on topic LUT issue with ver 4.0.2
...there's no specific path for LUT, but the Effect Search path and Texture Search path, and they both correspond to the right files.Which LUT is used is decided from within the LUT shader:
Where should I check?
#ifndef fLUT_TextureName
#define fLUT_TextureName "lut.png"
#endif
#ifndef fLUT_TileSizeXY
#define fLUT_TileSizeXY 32
#endif
#ifndef fLUT_TileAmount
#define fLUT_TileAmount 32
#endif Try naming your LUT a unique name and add that to the preprocessor definitions.
Then enable the LUT technique and check in the Log tab for any errors.
If you see something like that
ERROR | > Source "myLUT.png" for texture 'V__texLUT' could not be found in any of the texture search paths.Please Log in or Create an account to join the conversation.
2 years 9 months ago #12 by Lanvali
Replied by Lanvali on topic LUT issue with ver 4.0.2
Hey, thank you for your reply !
I tried it with the name "myLUT.png" like your picture and it still found it in the textures files, but there's still no effect.
In the statistics tab, it showed this for LUT:
Not sure if it can help...
I also tried with the name "lut-pink.png" but it didn't work...
You can override these values with the global preprocessor definitions (the fLUT* ones):
Try naming your LUT a unique name and add that to the preprocessor definitions.
Then enable the LUT technique and check in the Log tab for any errors.
If you see something like thatyou need to check if there's any error in the search paths and/or the LUT name.ERROR | > Source "myLUT.png" for texture 'V__texLUT' could not be found in any of the texture search paths.
I tried it with the name "myLUT.png" like your picture and it still found it in the textures files, but there's still no effect.
In the statistics tab, it showed this for LUT:
Not sure if it can help...
I also tried with the name "lut-pink.png" but it didn't work...
ERROR | > Source "lut-pink.png" for texture 'V__texLUT' could not be found in any of the texture search paths.Please Log in or Create an account to join the conversation.
2 years 9 months ago #13 by Daodan
Replied by Daodan on topic LUT issue with ver 4.0.2
Not sure why it doesn't work for you but here's a setup with a greyscale LUT that works.
Maybe it helps you.
Maybe it helps you.
Please Log in or Create an account to join the conversation.
2 years 9 months ago #15 by Lanvali
Replied by Lanvali on topic LUT issue with ver 4.0.2
I tried to figure out the difference between 4.0.2 LUT and 3.4.1 LUT, and it seems like I had both LUT and LUTAtlas files, and the difference is made only if I have them both files available.
In 3.4.1 LUT file, there are these lines in more than 4.0.2 one :
But if I add these lines like how there are disposed in 3.4.1 lut file, when I launch my game it says "failed to compile" or something like that.
Any clue?
In 3.4.1 LUT file, there are these lines in more than 4.0.2 one :
Warning: Spoiler!
But if I add these lines like how there are disposed in 3.4.1 lut file, when I launch my game it says "failed to compile" or something like that.
Any clue?
Please Log in or Create an account to join the conversation.
