OTOY Forums

Ok, no problem. I created a subset of the objects to merge multiple times. If I need larger groups I can create subsets of multiples and then merge them. Does instancing conserve the amount of textures that need to be loaded compared to merging the same objects multiple times?

Does instancing conserve the amount of textures that need to be loaded compared to merging the same objects multiple times?

I don't think there would be any difference for textures - Octane will only store a texturemap in VRAM once, regardless of on how many objects it is used.

Paul

face_off wrote:The has been reported previously, and it appears that instancing has never worked, and is listed as "Unsupported" in the manual (https://docs.otoy.com/?manual=manuals/p ... imitations). I have looked at it, but there is no simple solution, so it's still on the list of things to fix.

In the meantime as a workaround you can use the DAZ Studio Geometry Shells to have multiple copies of the same object in the scene without increasing the needed VRAM space.

Update / Edit:
Unfortunately this workaround only seems to apply to objects that only have one surface zone.
In earlier V2 builds geometry shells may also have worked with objects that have multiple surface zones.

compare:
viewtopic.php?f=44&t=54582

- - -

Following is a test release of the plugin built with Octane 3.01. I have not posted it to the top of this thread as a formal release, due to the large number of internal changes made to try to catch the Image Browser opening crash.

3.0.22.23
- Resolved issue where updates would stop being applied after pausing and resuming a render
- Potential fix to random crash when material picking
- Added code to attempt to catch the crash occurring when opening the Image Browser (or clicking the "..." button).
- Added "Authentication" button to the OctaneACM application to allow activating and deactivating the plugin
- Fixed issue where the resolution was incorrectly being set to 1024x512 when rendering animations
- Fixed issue where texturemaps name from Poser content would be lost when the scene is next loaded into DAZStudio

https://render.otoy.com/customerdownloa ... _Win64.exe

This people find this release robust, I will post it as a formal release.

Paul

Fantastic! Thanks for the update.

I'm currently rendering with the latest build and so far the few rendered frames seem fine and are the correct size. Another 556 to go. I'll report back if any problems occur.

Cool so far much better but haven't got around much yet! still miss the jpeg feature, but it's ok Photoshop it will do thanks

I think I've found a small render passes bug, if you have the Post Processing render pass turned on, it's no longer included in the main combined beauty pass, like other passes are.

I'm currently using R3.0.20.22 and I believe this was working fine in Alpha R3.0.6.16, which is the last time I used render passes, so I'm guessing it's stopped working some time after that.

face_off wrote:The has been reported previously, and it appears that instancing has never worked, and is listed as "Unsupported" in the manual (https://docs.otoy.com/?manual=manuals/p ... imitations). I have looked at it, but there is no simple solution, so it's still on the list of things to fix.

On the subject of instances, I have a vague memory that they were "fixed" (fixed being a relative term in that era of OcDS) in the 2.2 test release and tried them out at the time (and I've used them a few times since, although they certainly don't work perfectly), I searched back in the forums and the 2.1 release notes say they'll be back in the next release, unfortunately you whipped T_3's 2.2 release notes post when you took over the plugin, so I can't check that for sure.

You're also assuming t_3 kept the manual anywhere close to up to date, looking at the OcDS limitation page, those look like they're from the 2.1 release, as geo grafts were more or less completely fixed in 2.2.

Also, when I use that link to the limitations in the manual, it goes to the Rhino plugin limitations, not the Daz Studio plugin limitations.

On the subject of instances, I have a vague memory that they were "fixed" (fixed being a relative term in that era of OcDS) in the 2.2 test release and tried them out at the time (and I've used them a few times since, although they certainly don't work perfectly)

The code is actually present in the plugin to handle "instances" however it does not work correctly. And if I change any of the code, DAZStudio crashes. So it's not trivial to fix. But it's still on the todo list as a high-priority, as I haven't given up completely yet.

I searched back in the forums and the 2.1 release notes say they'll be back in the next release, unfortunately you whipped T_3's 2.2 release notes post when you took over the plugin, so I can't check that for sure.

I just "unstickied" it - so it should still be in this forum.

Also, when I use that link to the limitations in the manual, it goes to the Rhino plugin limitations, not the Daz Studio plugin limitations.

All the manual links have changed so I need to update these - sorry.

Paul

I'm a bit short on time, but I did a quick test session for feedback:

face_off wrote:3.0.22.23

- Potential fix to random crash when material picking
no problems so far, needs further observation, but I'm carefully optimistic

- Added code to attempt to catch the crash occurring when opening the Image Browser (or clicking the "..." button).
strangely enough I never had problems with this - probably did something wrong...

- Fixed issue where the resolution was incorrectly being set to 1024x512 when rendering animations
fixed for stills rendered "final", too.

- Fixed issue where texturemaps name from Poser content would be lost when the scene is next loaded into DAZStudio
yes! materials from an existing scene have to be corrected once, but after that they reload on file open correctly.