There seems to be some ui bug as well, or maybe it just shows what actually happens. If I set a node to be hdr high precision 32f, it still shows 16f on the node. It doesn't happen on all nodes, but on some of them.
Hey. I just renewed my license and updated to the latest version of Substance Designer, and I'm noticing some serious precision issues. Some nodes (maybe all, I haven't confirmed yet) straight ignores the bit depth setting, even when I start with a specific precision. I noticed this on warp nodes but theres probably more.…
I am personally so accustomed to all those Designer quirks and puzzles I stooped pay attention already. No sbs older than half a year works for me. 32 bit is not working in half nodes on my side too . Thus half of height blending operations is messed in my old files. Setting pixel processors inside to 32bit helps…
Yes, it worked. I went into the perlin noise and linear gradient nodes, changed their precision to be relative to parent, resaved them, and now it works. But this is awful wtf. As far as I see, a whole bunch of nodes has this issue. Thanks for the suggestion though!
Yeah, it sucks pretty hard - i can only assume it's done for performance reasons and they're betting that most users won't notice. I'd advise making copies into your own library rather than saving over the built in nodes as you'll lose changes with new updates and also occasionally there's a complete replacement of a node…
Now I will try and see if I manually set the precision of those nodes inside them, and resaving, will resolve this issue, but I guess it will. I'll post the results soon.
The precision is fixed on some nodes rather than being inherited - why is anyone's guess. I generally just build a new version if I need the extra numbers (basically copy it and fix the wrong bits) re the viewport filtering artefact - have a look for settings related to SVT I've not examined the latest Designer but Painter…