Indeed panning through RGB node which will all of a sudden modify the value is quite bad. And this is somrthing I can confirm here
Will mark this as confirmed.
Thanks for the report. I can confirm
Hi, thanks for the report. I can confirm (introduced between 3.1-3.2 release). Raising the priority even though its a not very recent regression. cc @antoniov
Hi, thanks for the report. Do you use some USD viewer software to verify it? I imported back the file in blender, I noticed the color socket is passed to alpha socket of principled BSDF. So…
Hi, Winerror you get is same as mentioned in #99440
Fix for it is still not known to us.
In #99440, rjg
has mentioned some tests to perform. See if that solves the issue.
I'll close this…
Thanks for the update. Likely an add-on is causing this issue. Could you disable them one by one to find out the culprit?
Hi, I'm able to confirm the error in 3.5 In prior versions, I caught up with out of memory issue. Will raise the priority since this looks like a regression from comments.
Hi, can you reshare the file with low resolution textures? Without textures error is not appearing here. This report could be same as #105442
Hi, 3.4-branch no longer receives bug fixes so I'm closing this report. Feel free to reopen the ticket or open a new report if problem happens in master/3.5
@hamed.desighn hi, can you check again in recent 3.3 build?: https://builder.blender.org/download/daily/
ANy difference with factory preferences?: File > Defaults > Load Factory Settings
Alright ! That was not without a sweat but I finally managed to commit it :
@nathan.hild hi, can you submit PR for it? @ideasman42 , can you…
Caused by 5876573e14f434a4cd8ae79c69afbe383111ced9 @HooglyBoogly ^
Hi, thanks for the report. Actually a patch was submitted for this error: https://archive.blender.org/developer/D10572 I'll close this ticket for now. FYI, this issue is being tracked here: #86080