Adding to Cart…
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
To handle the stacking width wise, it will always use the same base prop in one stack, and otherwise the distance between stacks will cause all kinds of problems.
So Ts will be ontop of Ts (as the width and depth of that prop is used to calculate the offset to the next stack.
Ok, thanks for the explanation, Totte.
How did you stack all those books of different sizes and widths? Can you stack books of different sizes and widths vertically (books lying flat with their cover parallel to the ground)?
I've just though of a way to do that, or two ways.
(1) make several one level high stack rows and manually stack them
(2) I think I will add a "full random mode" that uses the box of the largest prop for spacing that can allow any of the available props to end up in any space, I put this on my update list as well.
As they are only one row high, each book will have it's own stacking width. To stack bocks as piles, stack a row, then rotate it 90 degrees.
I'm working on a update, so far I have implemented to following enhancements
- add prop now saves last directory used
- add material now saves the last directory used
- global random seed value, same value gives the same result
In the works:
- optional 90 degrees prerotate when making walls (if the prop is rotated the wrong way)
- flat mode (props spaces are calculated from the largest prop), for Artini's letters, to make it possible to put any prop in any location
Thanks a lot for the updates, Totte.
That will be great to have.
Books, books and books...
Added a little mess...
The mess looks nice. How did you do that?
Nice stacks Artini
Hi,
Added a "rotate 90" option for wall stacks to build walls if the prop is rotated 90 degrees wrong.
Added a free base space mode to break the follow first item per stack rule (I don't have any good letters for this , I used the flat hollyword ones)
Will submit the update today after some final tests
Thank you very much, Totte, and excellent news about updates.
In Unity, then exported as a Collada file and imported to Daz Studio for rendering.
For such things, one needs workable physics. Hope, at some point Daz Studio will get it...
The update to version 1.1 has been submitted to DAZ.
I really like the suggestions here, the more versatile it becomes the more creative you all can be!
Might be useful to create a clothing store :)
I tried that but my "Racks of clothes" props are for some reason not all at floor level (issue with the prop, not the Stack 'Em scripts) so some were floating 4 feet of the ground when Stack 'em brought them in. Which looked odd to say the least. But the idea is sound if you have a good variety of props that work for it.
Maybe something to add for another update, adjust props down? Are they floating even after yo try drop to floor on them? (Which says of they have a bad origin offset or are just placed high), but I think DrJellyBean has a lot of props ;-)
How did you guess LOL.
More like dropping them to the ground, not move the origin, and yes, so far I haven't seen any issues with my tests.
My connections at GHCQ told me so ;-)
>> NSA: Not GHCQ, NSA
Some of the racks were for a set I had that had steps going up from the origin to a boutique one level up and the racks were on that floor level. So they were intended to load high, with a Y-axis value to raise them to the right spot. So they could be dropped but I made a lot of them and I would have had to individually select them and drop them to ground one by one.. Perhaps if all the instances of a certain type were grouped then you could easily select them and drop them all at once. As it was, too tedious for what was just a simple experiment. If I had a real render in mind, I would have gone through and done it the hard way. But probaly it's as simple as having a "drop to floor" option for just the original prop when the script loads it. Then the instances would run properly, and stack properly too. That would be really helpful for such cases.
I add that to my 1.1.1 update list.
So I was a bit of a fan when you first showed us the preview. All this extra work made it into a "must have" for populating all sorts of details into the scene!
Thank you!
I'm a coder at heart and I've been doing "user driven development" since long before it even existed as a term. All this "new buzz" around Scrum, Agile Development & Sprints, just fancy words for it.
You can never figure out what needs the users really will have, and sometimes I forget that Windows isn't always as friendly as macOS (when it comes to things like rememeber the ten last directories you opened files from).
So, updating the first version a few iterations until it has all the stuff people need is much better that trying to figure that out beforehand.
I know the feeling. :) The first "rendering egine" I used was one I wrote in fortran in college about ... well ... let's just say "many" years ago. ;) You always learn SO MUCH once your end users start using something you wrote. Keep up the good work, will be looking forward to your new products.
Thank you very much, Barbult.