Hi,
After I edit the bitmap using photoshop and save it as a jpeg, and then I click the “Reload” button in VRayBitmap, the texture did not update, even I click the 3 dot button and re-attach the bitmap also not working. The only way I can update the texture is to delete or clear the VRayBitmap from VRayMtl slot and re-apply VRayBitmap and then click the 3 dot button to re-attach the texture. is it VRayBitmap bug?
Works fine on my end (tested with V-Ray 6, hotfix 3). Maybe there’s a delay when storing on a shared network storage? Try doing it locally and see if there’s any difference.
Hi,
I am doing it locally, I have one machine only
We have the same issue, though I haven’t tried it in a while. If you select a completely different bitmap and the click on it again to go back to the desired bitmap that always works.
VRayBitmap suck! it always no update in viewport, and cannot get any solution from here either…I have give up and use the 3ds max defualt Bitmap
I am use VRay 6, your method did not work for me
Odd, that is what I use every day to switch bitmaps in vray 6. I choose some other image, or a different version of the image. Apply it and close out of everything. Then click to replace it again and choose the correct image.
Doing this all from Slate in case that matters. The old material editor drives me nuts.
Hi,
Any update for this?
Yeah same here.
If I am tweaking a bitmap back and forth I just save version A and version B iteratively, and select the newest one each time until I get the tweaking done. Do you are loading as new bitmap each time.
Yeah that’s what I do too, but that’s just plain stupid it should work
It works just fine for me.
If we cannot repro it, we can’t possibly fix it, you’ll need to give us something more.
If any of you would be so kind to contact support, and then submit a proper report, with the hardware details, the format of the image (if it matters, as it doesn’t for me, all i tried update instantly.), the configuration of Max’s drivers and Viewport modes, and so on, we’d be very grateful.
Weird that you can’t reproduce. It’s been like this for years. Normal bitmap node works fine. VrayBitmap, no.
We load textures over the network of course (letter mapped drive, but inside sceneassets/images/).
While IPR is going, file updates are blocked on purpose.
Other than that, without anything else going in the Max UI, my vrayBitmap/vrayHDRI has *always* updated as it should have, since its inception.
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.
Perhaps this is the difference.
No really…I have the same taught, so I disable IPR and try again, the issue still remain
Could you share a video where you reproduce the issue?
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 will have to test, but last time I encountered the error I was indeed loadng the same texture twice.
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.