Refresh Surfaces Texture Images?
marble
Posts: 7,500
This has been an issue since day one with me but I've always worked around it. However, maybe someone knows how to fix it so I'll ask.
I change an image - let's say the Cutout Opacity overlay image - in the Surfaces tab and decide that the image isn't quite right. I take the image back to an image editor (Gimp, for example) and make changes and then save thus overwriting the previous opacity mask. However, the new one is not seen by DAZ Studio - it clearly caches the original image and I don't know how to refresh that cache. The only way I can get it to use the adjusted image is to either rename it or to exit DAZ Studio and start over.
Any ideas, anyone?
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Click the hamburger icon in the Surfaces pane. Do you have "Automatically Refresh Images" checked? Have you tried manually refreshing images (CTRL+I ("eye"))?
There is a "Refresh Images" (CTRL-I) on the Surfaces tab context menu, but I don't seem to get consistent results. There is also a "Purge Memory" script in Scripts/Utilities that should clear the cache, but, again, I seem to get inconsistent results. I do know it trims the list of bitmaps to choose from down to those actually in the scene. YMMV...
Well I didn't know about these options (or had forgotten) but, unfortunately, they do nothing. I have Auto refresh checked and I have tried to force the refresh but the old image persists. Interestingly, if I look at the image in the Cutout Opacity selector it has changed - the change is not seen in the viewport, however.
In texture shaded? That can't really be trusted when it comes to opacity. Try a render, or at least Iray preview, if you haven't.
Yep, I tried - same in IRay. If you ever have a minute to spare, give it a try. I might be missing something obvious. As I say - the image in the Cutout Opacity selector is correct but the viewport (or render) is still using the original image. If I load the scene again fresh, it works fine because there are no cached images.
I don't know what to tell you, because I did the same thing you're doing a day or two and it worked fine for me.
Yes I understand. I suspect there is something about my DAZ Studio installation that is not quite right. I seem to have problems that others don't. For example, The top bar with all the icons to launch various tools is organised to suit me but if I minimise DAZ Studio to the task bar and then restore it - they are all rearranged. If I minimise it again and restore it, they are back to where they were. Then there's the times when all my panels (those with tabs to open them like Content Library or Scene or Surfaces, etc.) also get rearranged. Unfortunately there is no quick fix ofr this - I have to manulally drag them back to where I had them.
This is a little OT, but since you're the OP and you raised UI issues with minizing . . .
I like to make the Content Library window undockable so that I can minimize it and have it be very large when restored. The problem is that when I do minimize it, it disappears completely. If I minimize DS and then restore it, the Content Library is displayed again (not minimized).
This is under 4.15.0.2, Windows 10 on a 4K display. I'm guessing/hoping this will be dealt with when DS moves to 5.x and a newer version of QT.
- Greg
I've always noticed this issue, and have been working around it for years by saving the edited image with a new name. I figure it has something to do with the way DAZ caches the images, and have just always worked around it.
Yes, exactly as I do too. Sometimes I end up with multiple images and then have to be careful to delete the versions I don't want.
I think we are all hoping a lot of issues will be fixed by the new QT. Another is the mysterious case of the vanishing mouse cursor (which actually happens if you accidentally click both mouse buttons at the same time).
The vanishing cursor mouse is the worst. I've also figured out what seems to cause it, but have never been able to get it working again. I always just save what I'm working on and restart DAZ.
The quick workaround is to blindly navigate in the viewport to the selector which chooses which camera (or Perpective) and click on that. The mouse cursor re-appears.
Check if purge memory script ( from script/utilities) can help you . I`ve been using it to quick clean up unused MAP