Quote - I've got a couple of Python scripts, both publicly available in freestuff and some not-ready-for-release scripts on my hard drive. You're welcome to use any and all of my Python scripts as a roadmap for this functionality.

Greatly appreciated, I'll check them out as soon as I get the opporunity :)

Quote - Something that could be useful: a multiple delete tool. Ockham has/had some Python scripts out for deletion of multiple props/figures, I've adapted one of those scripts, and I use them on a regular basis. Could be extremely useful.

I like that.. I also like the idea of being able to move, rotate, delete, rescale, etc..  items selected
from a list that are not necessarily parented to one another.  Avoid the hassle of parenting an object to make it easier ot move and then unparenting it later to avoid any problems that the parenting may cause down the line (like visibility, etc).

Quote - While it seems obvious to me that the regular (sort of) documented features of CR2 rigging should be supported and implemented in FAST/Rigging, maybe these undocumented tricks shouldn't be included.

As for the inner workings of rigging, morphs, bones and joint parameters, I can highly recommend the book "Secrets of figure creation" by B.L. Render. It clearly describes how it all works, so it could give you a good idea how to implement it all in FAST.

Lol.. well if the undocumented stuff is included it will probably be later on, need to focus on the stuff that is documented first and work into the trial and error realm later.  But FAST should have a smart, powerful, easy to use rigging system.  It is the one area that most other applications truly do lack, while many of them have rigging systems I haven't seen too many that I really like and almost all of them lack features I consider to be essential.

Quote - The library database feature looks cool! There might be some problems though. How do you keep the database synced with the actual folders? How do you handle libraries on removable devices or on a network, libraries that aren't always available? What about content that doesn't follow the rules when it comes to object/texture references (many, many freebies, and some older marketplace items don't use the correct relative reference scheme)?
I'm not saying it's impossible, I'm just saying it requires some thought, and it probably requires a resident folder monitoring utility - which will be OS dependent.

Yes, the removable drive thing does present a bit of a challenge, but not top bad overall.  At the moment everytime you open a poser directory it does a directory list from the OS and then displays the results.

The database will work in a similar fashion, when retrieving a list from the database it will check for the existence of the "CR2" file along the indicated path, if it doesn't exist it will still be listed, but possibly greyed out to indicate that it is on a removable drive/path.

If you click on it to load it while it is in this state, the program could check to see if the path itself existed, a dialog would pop up indicating that either the path is there but the file was not found or that the path was not accessible indicating it's probably a network/removable drive that is not currently accessible.

In future releases it might even be possible for the system to get a bit smarter, include a flag in the database for items on removable drives (like DVD or CD's) and have a "reference hint" field, if you select an item in the database that is so marked it will prompt you to load the DVD/CD in question and use the "reference hint" field so that it could give you information on how that particular DVD/CD might be labeled as well.  For example, if you were to create a collection of DVD's that were numbered, when you add the DVD content to the database you could tell the system that this is on a removable drive, and put tell it the # you have printed on the DVD label.

The system would then add all the content on the DVD, flagging it in the database as being on a removable drive and setting the string stored in the reference field to something like "Please insert the DVD/CD labeled "Poser Content Disk #1" into your DVD drive"  The string would be fully editable of course, so you could have that particular prompt say anything you'd like when you try to access content stored on removable media.

-Never fear, RenderDog is near!  Oh wait, is that a chew toy?  Yup. ok, nevermind.. go back to fearing...