Adding to Cart…
![](/static/images/logo/daz-logo-main.png)
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
I'm still nto sure what you mean - Parent in Place on/off is a setting that cotnrols what happens when you chnage the parent of an item (whether it stays where it is or moves to the parent's origin. It has nothing to do with what the PA did, it's a setting in DS that you can change.
If you are saying that these sets have copies of the same item, each loaded anew and with its own zero position that places where it needs to be then yeah, that will break any attempt to replace the props with instances and yes, it seems a bad idea.
yes in some cases a huge list of identical parented props that if unparented change position
if only there was a way to unparent and keep the current positions
others as you said the 0,0,0 is not the position of the prop, that type are worse and just hopeless
I'm still unclear about this. Go ahead and give a product example.
well I actually did in my post with the blue text, it's a link
all the doors including the tapdoor and letterbox ones are out of kilter if unparented
Thanks, I see it now. I don't own that or anything by that artist.
If you unparent them with Parent In Place on they should stay put, if they don't it isn't that the vendor did the dirty on you. Is there scaling on the original parent (grand-parent, etc.)?
no scaling, they stay the same size just change positions
and Parent in Place is on? That is odd, but I don't have the set to see if I can figure out why.
does that make a difference?
I may need to test that
this is not the only set like that, just the example I used, would need to look through for others
update, no it makes no difference
I am ready to move on from that set
it has caused me nothing but grief![crying crying](https://www.daz3d.com/forums/plugins/ckeditor/js/ckeditor/plugins/smiley/images/cry_smile.png)
Instancify works great on other sets I have tried![yes yes](https://www.daz3d.com/forums/plugins/ckeditor/js/ckeditor/plugins/smiley/images/thumbs_up.png)
Hello All,
I have seen this come up on sale in the 70% section, but was unsure of what it really does. Since I don't have time to read all three pages of responses here, I think I somewhat got the gist of it, but asking just to be sure:
So this will only help those that create multiple instances of a particular item in a render, like many columns (windows, doors, etc) on a building, or a row of light fixtures down a corridor and they have to be in the same "pose" facing the camera in the same direction?
Thanks,
Geo
No, they don't need to be in the same "`pose," the limitation is that they need to have the same material, and the script will replace any duplicate with an instance that will have the same transformations (position, orientation, scale) as the prop it will replace. Fairly useful in old scenes that weren't optimized, and the most relevant example would be a library where most of the books are the same prop copied over and over.
I have this script, and it does work well. The main disadvantage is that it completely messes up any grouping that was already in place with the set, as the script needs to regroup everything, for reasons I don't really understand why. Thus if all the books are grouped with the bookcase they are with, so they can be moved around together, that will be messed up. If you don't need to customise or modify the set after running the script, this is not an issue, but it is a real pain otherwise.
We got a horribly inefficient PC+ freebie, Celestial Host, with gobs of duplicate props gobbling up GPU RAM. Instancify got rid of 85% of the polygons with no loss of quality in the product. One of the things you can learn from PC+ freebies is which PAs make efficient Daz Studio products and which don't, so you can base some of your future purchase decisions on this knowledge.
Before Instancify:
2021-09-13 00:28:24.626 Iray [VERBOSE] - IRAY:RENDER :: 1.7 IRAY rend stat : Geometry memory consumption: 811.612 MiB (device 0), 0.000 B (host)
2021-09-13 00:28:25.878 Iray [VERBOSE] - IRAY:RENDER :: 1.7 IRAY rend stat : Texture memory consumption: 282.854 MiB for 53 bitmaps (device 0)
2021-09-13 00:28:25.879 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : Importing lights for motion time 0
2021-09-13 00:28:25.881 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : Initializing light hierarchy.
2021-09-13 00:28:27.804 Iray [INFO] - IRAY:RENDER :: 1.7 IRAY rend info : Light hierarchy initialization took 1.923s
2021-09-13 00:28:27.809 Iray [VERBOSE] - IRAY:RENDER :: 1.7 IRAY rend stat : Lights memory consumption: 24.355 MiB (device 0)
2021-09-13 00:28:27.813 Iray [VERBOSE] - IRAY:RENDER :: 1.7 IRAY rend stat : Material measurement memory consumption: 0.000 B (GPU)
2021-09-13 00:28:27.813 Iray [VERBOSE] - IRAY:RENDER :: 1.7 IRAY rend stat : Materials memory consumption: 999.035 KiB (GPU)
After Instancify:
2021-09-13 00:30:39.142 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Geometry memory consumption: 117.278 MiB (device 0), 0.000 B (host)
2021-09-13 00:30:40.358 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Texture memory consumption: 282.854 MiB for 53 bitmaps (device 0)
2021-09-13 00:30:40.359 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Importing lights for motion time 0
2021-09-13 00:30:40.361 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Initializing light hierarchy.
2021-09-13 00:30:42.261 Iray [INFO] - IRAY:RENDER :: 1.5 IRAY rend info : Light hierarchy initialization took 1.900s
2021-09-13 00:30:42.265 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Lights memory consumption: 24.359 MiB (device 0)
2021-09-13 00:30:42.268 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Material measurement memory consumption: 0.000 B (GPU)
2021-09-13 00:30:42.268 Iray [VERBOSE] - IRAY:RENDER :: 1.5 IRAY rend stat : Materials memory consumption: 509.887 KiB (GPU)
Now we need a tool to weed out solid black metallicity maps.
Okay, I'm trying to instantify a scene built with Cheirocrates, and for some reason, Instancify is disappearing che_gr_sd_walk_2_321 out of the instantified scene. I saw a pop-up message say something about removing the duplicates, and... BOOM, the particular sidewalks were gone. 0o It looks like the new instances of it are there, but the original prop those point to is gone.