If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Exciting News: Chaos acquires EvolveLAB = AI-Powered Design.
To learn more, please visit this page!
New! You can now log in to the forums with your chaos.com account as well as your forum account.
I am on location now; so cannot check, but I know the last time I was using IPR. Swapping textures while using IPR is common. Would be ideal if those worked in tandem.
I managed to reproduce the issue - it seems to happen when there are more than one VRayBitmaps that load the same texture. Even if you delete the duplicate node, the issue persists. However, a fresh VRayBitmap with another texture will update fine. Can you confirm this?
I managed to reproduce the issue - it seems to happen when there are more than one VRayBitmaps that load the same texture. Even if you delete the duplicate node, the issue persists. However, a fresh VRayBitmap with another texture will update fine. Can you confirm this?
Confirmed: instanced vraybitmaps do not -ever- refresh the contents of the pathed file.
Edit:
Workaround: Show the map in viewports, that will force a cache update, and in the process unlock the cache for the rest of the instance bitmaps, for which then a "reload" or "view image" will work as intended.
P.s.: the offline render is unaffected, regardless, and always renders with the latest version of the maps.
I managed to reproduce the issue - it seems to happen when there are more than one VRayBitmaps that load the same texture. Even if you delete the duplicate node, the issue persists. However, a fresh VRayBitmap with another texture will update fine. Can you confirm this?
You can do one of two things: show the map/material in viewport, or start an offline (i.e., non-IPR) render.
Either action will invalidate the cache and allow for the refreshing.
You can do one of two things: show the map/material in viewport, or start an offline (i.e., non-IPR) render.
Either action will invalidate the cache and allow for the refreshing.
Comment