Bump map values?
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Images are working OK for me. This was a random image (a previous render I think) that I plugged into the bump - and it had little variance in the image - but the details are clearly visible.
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
is it possible you are running out of texture slots and the bump map is being treated as black?
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
I agree with OP. I have dealt with diminished bump maps, although I think Fooze did have a good solution: the color correction node.
I think that bump maps, by nature of the file format, are typically LDR with a maximum value of 1, however I think the algorithm accepts larger HDR values, which is why the generators seem to have such a pronounced effect.
An elegant solution would be to change the multiply node (or the whole category for that matter) to be able to have values higher than 1. Right now the Multiply node can only produce equal or darker pixels because the maximum value is again 1. Many times I've wanted to multiply something by 3 or 4, just because it needs to be stronger. an HDR RGB node would be even better. The pipeline is already there I don't expect it should be that hard.
I think that bump maps, by nature of the file format, are typically LDR with a maximum value of 1, however I think the algorithm accepts larger HDR values, which is why the generators seem to have such a pronounced effect.
An elegant solution would be to change the multiply node (or the whole category for that matter) to be able to have values higher than 1. Right now the Multiply node can only produce equal or darker pixels because the maximum value is again 1. Many times I've wanted to multiply something by 3 or 4, just because it needs to be stronger. an HDR RGB node would be even better. The pipeline is already there I don't expect it should be that hard.
GTX 1080Ti 11GB (3x), Water-cooled
Intel i7-5820K 6-core @ 3.3GHz
Windows 10 Pro 64-bit, 32GB RAM
Intel i7-5820K 6-core @ 3.3GHz
Windows 10 Pro 64-bit, 32GB RAM
- FrankPooleFloating
- Posts: 1669
- Joined: Thu Nov 29, 2012 3:48 pm
I do agree with Alec that bump could use more oomph. In one case though, I applied the bump map to spec and roughness (in addition to bump) and inverted them - and it did help some in that case.
Win10Pro || GA-X99-SOC-Champion || i7 5820k w/ H60 || 32GB DDR4 || 3x EVGA RTX 2070 Super Hybrid || EVGA Supernova G2 1300W || Tt Core X9 || LightWave Plug (v4 for old gigs) || Blender E-Cycles