Hi, I had a tricky time diagnosing why and when exactly this is happening, but it seems to be when you have a material using an invalid file path to an image texture. Indigo loads the material settings but gives you an error that the file is missing when you try to render. but if you click into the texture settings for the missing image and "browse" to replace it, selecting the new file causes Indigo to immediately crash.
if instead you switch the texture slot in the material to "none" first (removing the file path to the image) and then loading in a new image texture it seems to avoid the problem.
so this is not the biggest problem and the workaround seems fine, but it might be more intuitive to allow the invalid image to simply be replaced through the file browser.
Feature requests, bug reports and related discussion
2 posts • Page 1 of 1
Who is online
Users browsing this forum: Google [Bot] and 1 guest