Does instances to objects do what I hope it does...?
https://www.daz3d.com/instances-to-objects
Details
To lower the amount of resources used by scenery and environments, the use of instances came to Daz studio. This is one of the best features added to Daz Studio. The only downside is that when exporting scenes using instances to another 3D software, the instances are not exported.
This Daz Studio script will be of help if you want to export a Daz Studio scene that uses instances to another 3D software, for example Vue or Poser, or any of the big 3D systems out there.
The script will turn instances into objects, which makes them exportable.
The script is very straight forward to use, it shows a list of of all objects that has been instantiated and the number of instances of each object that exist in the scene. You just select which of these you want to convert into objects, and click Execute.
The script will warn you if you are trying to convert too many instances, which can be both very time consuming and also consume an unhealthy amount of system resources.
Another use for this script is when you have used for example Ultra Scatter or Instances Plus to create a scenery, and want that exported to be able to add other manually created objects like for example ivy using a different 3D application.
-----------------------------------------------------------------
You guys already know I've been hunting for a solution to (easily) populate a scene with lesser-memory items as "props" or OBJECTS.
I've wanted to do this with people. Especially people.
I'm looking at this and thinking I could create some people (or a single person) and leave them in an empty scene. Instance them.etc....
Use this script to either:
EXPORT just that person-turned-object or...(to import as a static object/prop later on)
export the whole scene...and Open a new SCENE (with landscape and the real 3-d rigged figures etc) and MERGE (instaed of file/open) the object filled scene created with this script and get the lesser-resource-using "people as static objects" into the picture.
* The problem was clothes coming off the figure when trying to turn characters into props.
* This looks like it will now understand, as an instance, everything is included and turn the WHOLE-SHEBANG into a static object, ready to export....
* With a lot less resources and finally allow for easy multi-figure scenes....
Do I understand this product's capabilities correctly?

Comments
Without wishing to undermine the vendor, that does seem an unnecessarily complex route to convert a figure to a prop whgen Rob already has a sample sceript to do the job http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/nodes/convert_figure_to_props/start .
This script is really the opposite of something to help with more effective memory use within DS, and is used to convert instances into separate objects, not the other way round. From what I have read it is mainly aimed at people needing to export a scene with instances to another program.
What you want is already available inside DS, use Edit>Figure>Rigging>Convert Figure to Prop
If you want to convert all the figures in a hierarchy, eg a fully clothed figure into a prop then use the script on this page:
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/nodes/convert_figure_to_props/start
This should dramatically reduce the memory needed by DAZ to load the scene, but will not reduce the VRAM requirements of iRay. To do that, you need to instance the figure.
The script is bacially mosty for those wanting to export a DAZ Scene to another 3D program or a game engine. Scenes will take much more memory in DAZ Studio.
I wrote it to solve a complex issue with a set I was working on, where I wanted instances, but at te same time wanted to use IvyGrover to grow Ivy over those instances.
/ Totte aka Code 66
I got an error running it on SM's Wintercastle and then it just duplicated the instances.
still no actual objects
I was hoping it would solve my issues exporting instanced stuff to iClone, Carrara, Poser etc
<anonymous>()@F:/My Library/Scripts/Code 66/Instances to Objects.dse:568
2017-05-18 00:30:20.031 Error in script execution: F:/My Library/Scripts/Code 66/Instances to Objects.dse
2017-05-18 00:30:23.801 Loading script: F:/My Library/Scripts/Code 66/Instances to Objects.dse
2017-05-18 00:30:38.506 Script executed successfully: F:/My Library/Scripts/Code 66/Instances to Objects.dse
I tested it on another set by another Vendor and it worked
so it seems an error just with Stonemason's set.
I solved it
I had to group sibling instances first
but
sadly the rocks do not end up in the same spots as the instanced ones
SM's Wintercastle - I don't have that, hmm... I had do do some special stuff for when instances where intermixed with props and grouped, it might be one case I failed to test for. I'll see if I can get that set and test on it.
The promo description is all about exporting. What I was wondering was, can you just turn an instance into a seperatly poseable copy and use the converted figure in the scene.? In Poser you can copy a figure and it becomes just another figure. I haven't found a way to do that in Studio, all I can do is create instances that follow the pose, morph and textures of the original.
https://www.daz3d.com/winter-castle
is the set I ran into the issues with
yes it works on other sets and I love the warnings I got just looking at the memory use for Harpwood trail (never intended actually trying)
Edit -> Duplicate -> Duplicate Node Hierachies in DS does just that. (Can be in some other menu depending och which theme is used,)
Lol - I always try add to some humour in my softwares.
I did an inhouse-use only software for a client and he asked me speicifically to give a warning if he wanted to run reports but didn't actually check any reports to run, I did. I turned volume to max and then played a sample from I think Full Metal Jacket where the drill sergeant shouts "What is your major malfunction numb nut?"
Do I have to mention he had Harman Kardon soundsticks attached to his system.....
And yes - I have it on my wishlist, just a little pricy right now, but I might get it soon to test on it. I did run on every set I have that uses instances, just don'thave that one, yet.
Parent the clothes to the figure then the instance will include them.
I'm working on fixing the issue now.
TY
hope you did not buy Winter Castle full priced just for that though Stefan probably would be chuffed!
I did, used my $6 off PC cupon though, and the bug is fixed, now just let it move through the update chain, but probably s**n, not DAZ s**n ;-)
I've tried the script on several different scenes, and whether I selecet one or several instances to convert to objects, I keep getting the same error message: 'An error occurred while reading the file, see the log file for more details.' Any ideas? Also, where's the log file? Was looking forward to getting these scenes intact into Cinema4d.
Thanks in advance for your help.
Mike
Probably the same bug I just fixed and is in progress of testing. It was silly but in a certain config of hierachy a test went bad, fixed when I had a set which triggered that combination.
it may the initial issue I found when like instances were not grouped
select all the instances and under edit instances group like sibling instances before running the script.
Most not all PA sets have them grouped but if you create your own you need to do it too.
Thanks all, but I just tried your suggestions on the new Island House set. Deleted everything in the scene except the tree instances, grouped like sibling instances, and tried the script. Still got the same error message. I'm running Studio 4.9.2.70 Pro 64-bit on Windows 7 Pro 64-bit. This product was really gonna save me a lot of time importing into Cinema4D, but so far, I haven't got it to work with a single scene. Hopefully, we'll get a fix soon.
Thanks
Fix is submitted and in QA queue. Island House is also one of the sets I don't have and could not test with, but from your description it's the bug I found with Winter Caste, was easy to find and fix, just that it only triggered when the heirachy was in a certain way. The bug wasn't a coding bug either, but a typo (and as it's a script language the code isn't ran until all the overlaying conditions are met), which reminds my why I hate interpreting languages compared to compiling languages.
So, I guess QA beginning next week, simple tests and then an updates into DIM.
Being a perfectionist with my coding I really hate when this happens, but I guess you have understood that by now ;)
This weeK I read an article about some Welsh farmer who accidentally bred the world's hottest hot pepper, so hot it could possibly cause death, and how "chuffed" he was about it. First time I ever saw that word and I was like "Chuffed? What's that? Chagrinned?" I had to look it up and so I learned something. And here it is again just a few days later! Like a sign from the heavens to work it into my own conversations!
cannot say I ever used chadgrinned in any context
I have read, heard and used chuffed for years, I guess its just what you are exposed to, in fact one of my sayings is she is totally chuffed and puffed up about it, refering to an attention seeking workmate, not sure how grammatically correct that is though
usually said sarcasticly.
chuffed British, informal origin around the 50s meaning very pleased "I am chuffed to bits" or "I am dead chuffed to have won" or similar.
I think usage and knowledge of the word "chuffed" shows age ;-)
also location, origin and class You would possibly hear "ehh lad I were reet chuffed when that 'appened" but you are not likely to hear "I say old chap I was exceedingly chuffed when that occurred"
The Cassell Dictionary of Slang agrees on 1950s and says it came from the military
Update to 1.0.1 now in DIM!
Hate to be a pain, but downloaded the updated script and tried running it on Stonemason's Winter Castle. I got the same error message as before. I finally located the log file and the last entries were:
2017-17-27 12:17:20.831 Loading script: C:/Users/Public/Documents/My DAZ 3D Library/Scripts/Code 66/Instances to Objects.dse
2017-17-27 12:17:24.994 WARNING: Script Error: Line 657
2017-17-27 12:17:24.994 WARNING: TypeError: Result of expression 'oNode.duplicate' [undefined] is not a function.
2017-17-27 12:17:24.994 WARNING: Stack Trace:
<anonymous>()@C:/Users/Public/Documents/My DAZ 3D Library/Scripts/Code 66/Instances to Objects.dse:657
Maybe this will help.
Thanks
Mike K, did you install with Daz Connect? I got similar errors on the UltraScatter update when installing with Daz Connect. Supposedly (not tested by me) the UltraScatter update works with DIM.