There's a script by Code66 (Instances to Objects), that converts items that are instanced in a scene into individual geometry objects. The result increases the scene size naturally, depending on what was de-instanced. Might there be a similar script that just gives just the point information where the instances are placed? Or even just outputs to points via OBJ as ultimately that's what I'm wanting.

Seems that UltraScatter already has to perform that calculation, but I'm not seeing a function that give the user access.

_____________________________________________________
There are though a few other options in UltraScatter™
when it comes to rotations that rotates using other positions
than the origin, and that information cannot be
obtained by Instances to Objects which causes those
scatters to not be correctly transformed, which right now
is nothing that can be fixed unless that information becomes
available in the resulting scatters.
_____________________________________________________

I own several of Code55 products, can you explain what you mean by points. Does this mean a specific location?

I own several of Code55 products, can you explain what you mean by points. Does this mean a specific location? Draagonstorm has a Instances Plus+ that gives you more control as far as the placement of the items. There is also a video you can watch to see how it works.

I think the request is to create something like a null at the location of each selected item, which should be scriptable - however, I am not sure what the final object of having those nulls would be since the instances are already using very little memory beyond that needed for the base item.

Hi folk,

Yes, Richard's comment is what I'm after, but not for DS.  With the points info exported, (Daz has different terminology & ways of doing this I guess), but I can then use those in Lightwave to generate instances. i.e., I wouldn't have the convert to Objects in DS first. Ideally they'd have a surface or such to distinguish things.

@DocPhoton- I always forget that you like to export your work and then import into Lightwave, and since I do not use Lightwave I know nothing about the processes in that program.  The thing about instances that I have become aware of in Daz Studio is once you create the instance any change you make to it changes all of the instances of that type, so basically you have to make multiple individual  instances of an object and change them. Example  You have two different types of trees. TreesA and TreesB. You will make instances of TreesA and apply shaders or whatever to the original of set, then you  make instances of TreesB and apply shader or whatever to the original of the set. All of Trees A will look the same and all of TreesB will look the same. Explaining this to people that may be following this thread.  You can not make changes to the instances, but just to the original item.

No reason ya should remember really.

I'm looking for a method to NOT export the geometry but just the position information really. Scaling, rotation, etc., I can do in LW when it creates the instances.  That information has to be generated somewhere in order for the instances to be placed in DS initially. And as RHaseltine suggests, should be scriptable. But by someone adept at that sort of thing, not me.

Probably a product in there with that as Lightwave is making a resurgence and renewed interest in Daz products. Maybe Code55 would be interested.

depending on the export format, you actually get nulls in some software for the instances, I know iClone 6 using FBX I can send duplicates to those "bones" if I export a whole scene
maybe Alienator will work otherwise replacing your instances with tiny triangles or plane primitives (a triangle is half a plane primitive created using the geometry editor if polycount an issue)

I  guess I could test Alienator Pro and somehow get it to use a minimal item.  Will have to re-study the manual as I've not used it for some time.