remap node different on CPU and GPU

[oglu]

im testdriving vray next and have some strange issues here.
i get diffrent resulsts on some shaders here and i think its the remap node.
it does look diffrent on CPU and GPU if i use the IPR debug shading i also see the diffrence.
im using this texture in the reflection ior.

if you switch between CPU and GPU you have to restart the IPR to use the right engine.

[jasonhuang1115]

Sorry if my post isn't helpful, but It's probably official that CPU and GPU will produce different results going forward.
Personally, I'd love to see "result-parity" between CPU and GPU as a high priority (when a scene using features that are supported by both), but it's up to devs to decide. For now, probably should start with CPU or GPU and stick with that.

[oglu]

Its a remap node.. They should look the same.. Doesnt matter which software its a math node..

[yolov]

I'd love to see "result-parity" between CPU and GPU as a high priority (when a scene using features that are supported by both), but it's up to devs to decide.

If only it was up to a simple decision, and not technology

[yolov]

Its a remap node.. They should look the same.. Doesnt matter which software its a math node..

I'll have a look, thanks for the report. There might be something not working quite right. I'll let you know once I have some results.
And just a note - it's actually expected to not be able to switch between engines on the fly. We have a note to disable the option while IPR is running.

[yolov]

Yes, I'm getting the same thing here, I'll log a bug report. In the meantime - if it doesn't break the result for you - try setting the input Max to be equal to the output max - that fixes it for me.