Mtoa 3.0.0.1
Warning "root: could not read ARRAY parameter "disp_map" #" if use isolate selection after create remap HSV node in maya 2018.2
and mtoa not view remap HSV in isolate selection, if ramp with sampler info node connect to remap color
// Connected ramp1.outColor to remapHsv1.color. //
// Warning: root: could not read ARRAY parameter "disp_map" //
https://www.dropbox.com/s/pfhrodylvb16tke/2018-04-12_22-17-14.mp4?dl=0
after that, I have error after create nodes in hypershade
// Error: line 1: lsThroughFilter: Object 'DefaultMaterialsAndShaderGlowFilter7' not found. //
// Error: listNode command failed //
https://www.dropbox.com/s/2fefnoj30cyexar/2018-04-12_22-32-16.mp4?dl=0
New warning if render peregrine yeti # Warning: pgYetiMaya1Shape: could not set POINTER parameter "disp_map" #
I'm not understand where does he get this "disp_map" attribute?
I have the same problem, with no fix yet. I was 10 seconds into render when it bugged out, the renderview went black and that error appeared -- // Warning: root: could not read ARRAY parameter "disp_map"
But a warning isn't going to abort a render
Hi Stephen, I also have this problem in most of my renders that use yeti with displacement maps. I believe its related. My renders dont usually abort, however they 'finish' rendering with many unfinished buckets left to go, therefore I see a heap of black squares all over my image and need to rerender these frames again. However when i do so usually the frames work then, in other words when and why the buckets stop rendering seems unclear. All I know is that if i remove the displacement map from yeti the render works, however this isn't an option always.
Thanks in advance for any help!
Peter
00:00:00 1623MB WARNING | MID_FUR:Yeti_earsShape: could not set POINTER parameter "disp_map"
00:00:00 1862MB WARNING | MID_FUR:Yeti_whiskersShape: could not set POINTER parameter "disp_map"
Sorry, so it does also happen on yeti hair without displacement. Less often it would seem, but the problem is still there. Hide the yeti hair and the problem is gone.