hi @nathanletwory i remember having to set RhinoCycles.BumpStrengthFactor to something much higher for this to work in v8 now the bump does not change at all, setting between bump 1 and hundred in the regular bump setting makes almost zero difference beside some slight different shading effects and tweeking RhinoCycles.BumpStrengthFactor makes also close to zero difference.
setting it any softer or even stronger, is basically not possible in that case, changing RhinoCycles.BumpStrengthFactor or even RhinoCycles.BumpDistance does nearly to nothing.
i tried with grid bump texture see attached but i also experimented with noise with the same effect is there anything more i can try or did you introduce some changes? this started happening in the last 2-3 versions i am not entirely sure but it might not be that long.
thanks @nathanletwory, since @andy did not respond and it still is broken i wonder if anyone feels responsible for it? Rhino is unusable to render since then… neither V8 nor Wip 9 work, the bump is so heavy and exaggerated its practically useless now.
so guys, rendering is not very reliable since v8, suddenly (i mean not now suddenly but for a long time suddenly without fixing it properly) all the bumps are different, negative bumps were or are still missing etc. v8 looked great in be beginning but steadily went downhill with bump failing completely then it got fixed through applying obscure stuff in the advanced settings but it never looked the same as in v7. now bump is not adjustable and hung up at some arbitrary setting for many many moons already basically 5 months broken bump is strange.
so is anyone going to ever fix this? if not why not and why was it changed/broken at all, why did you not leave it as it was most functional now i have to render in the slowmo v7 to get things out at all.. its really a pity and kind of unbelievable.
I also don’t understand why this was not solved right when the bug was discovered. When I open Rhino8 files, containing render scenes with products, that I had spent a lot of time setting up, they now look completely wrecked. I rely on producing the exact same render images as back then, of course. Since I now can’t reproduce the exact images, I now have to re-render over 1400 images instead of just adding some 100 new ones. I think this is unacceptable for any professional software. Because of this, I don’t think McNeel is in a place where they should even mention its renderer as a feature.
Is there any progress on this topic? My bumps are way increased compared to how they should be (similar to how others have reported it). Pushing the bump percentage down to 1%, decreasing the contrast on the bump map and taking its multiplier down to 0.1 results in this raytraced view (the object is 100 mm). Changing the RhinoCycles.BumpDistance and RhinoCycles.BumpStrengthFactor does not do the trick. I saw in the bug report that this works in WIP and on mac (which is good), but you need to fix it for win Rhino 8 as well.
which version was that announced in? was that just very recently? i gave up on that issue a long time ago. i am just completely amazed how ghosted it is for a very essential stop ship issue for rendering both R8 and R9
It fits very well into the pattern where things break in Rhino after some time, yet the mcneel team refuses to fix it with the argument, one could just use the wip instead.
Rhino 8 rendering capabilities are specifically advertised for, see here. Bump mapping is a basic rendering feature, yet it is broken.
This is absolutely unacceptable and imo, this is already lawsuit territory.
While I don’t think this is a legal issue, I do think if it is a feature, that it should have better user integration via an exposed multiplier function.
That is a great answere! This already lightens my rhino-mood.
I know the RH9 development is important for you but please keep in mind that neglecting bugs of the current rhino version, especially if basic features are impacted, can have real world/work consequences for your users. it may be more fun for you to work on the new shiny thing and less exiting to keep coming back to the old thing but it is a product that people use for work and have paid for.
I hope this is resolved with the next service release and we won’t have to ask about this again.
