rajib wrote:face_off wrote:I don't have an answer to these questions - sorry. Remind me again once the 3.08 version of the plugin is available and I will take a look.
No worries, will remind you once the 3.08 comes out.
face_off wrote:The oczdb files that contain the presets are Sqlite databases, which you can open with any sqlite browser.
Paul
Thanks for that. I use sqlite in my own projects. Will explore.
Hi Paul,
I think I have figured it out why after the
Render missing thumbnails is clicked, though the thumbnails show in that session, why they go missing after Daz Studio is closed and opened again. Within the same session I think it is using memory references to show the thumbnail and though the thumbnail files are being generated, no "insert / update" is done to the
OctaneRender_presets.oczdb with the newly generated files with the
Key set to indicate "
Preview" image entry in the
Data table.
I had deleted all the "
Preview" entries from the preset database and after I clicked the
Render missing thumbnails and the files got generated, I check the database again and found it still did not have any
"Preview" entries. Which means when we do a
"Copy to My Presets", it does insert the record for the preview but not when the thumbnails are generated using the
Render missing thumbnails. I think the easy fix will be to add the insert / replace command after the preview thumbnail image file is saved on the disk.
You may have to check if the preview record exists. And if it does do a update otherwise do a insert.
Or an easier step might be delete the record for that ID and key="200" and then insert the preview record. That way you do not need to check if the preview record exists or not.
I am not sure how the plugin checks for the missing thumbnail. Whether the "Preview" entry is missing in the database or if the physical thumbnail file is missing. I think a robust check would be to check for both, if either is missing, generate the thumbnail and insert/update the database preview entry.
One other thing I noted when you click the
Render missing thumbnails, the plugin seems to be generating all the thumbnails in memory at one go (without writing a single thumbnail file to the disk) and on my system it used up around 99GB of memory (I have 128GB RAM). And then I saw the orange bar appear at the bottom of the Octane Pane and the files started to being written to the disk. I think this should be changed so that the thumbnail is written to the disk as soon as it it generated (and the preview record inserted into the preview database) and then the memory cleared and a new memory allocated for the next thumbnail and the loop continues. That way it will not use up a lot of RAM. On system with a lot less memory, there is be huge amount of disk I/O as the memory gets paged and it will be extremely slow using the current method. Maybe with few present, it does not matter much but when one has fairly large number of custom textures and preset entries, it becomes extremely slow process to regenerate the thumbnails.
I hope this helps you in some way. Btw. I can confirm some of the entries are being wrongly generated - does not contain the actual texture image. Even after deleting the
MaterialPreview cache and then all the "Preview" entries in the database and regenerating everything via the
Render missing thumbnails, I still saw many duplicate thumbnails. This should not be happening as all the textures are unique.
Cheers,
Rajib