Wait a second...  Two additional plud-ing, one to let you work with cloth, one to let you make cloth...  What does the base do again?

Quote - Isn't Poser an expensive hobby anyways? Content isn't free... :)

No, but Wings and blender are! :closedeyes:

Quote - > Quote - Isn't Poser an expensive hobby anyways? Content isn't free... :)

 

No, but Wings and blender are! :closedeyes:

That's true, but how many people make their own stuff?

I really don't know how many people make their own stuff.  I know that I've made things I couldn't find a few times, and used things I found that I could have just as easily made.  I suppose the common wisdom is that people who make their own stuff do it in other programs, only working in Poser or Studio if they're in the content biz.  I have a hard time believing there aren't at least a few Poser users who model everything themselves and neither buy, sell, or share content.  If I can ever find the time to get the hang of zBrush, maybe I'll be in that category someday.  If Truespace, blender or Studio don't lure me away, and I'm not expecting anything to change in that area any time soon.

For being supposed entry level programs, it's especially hard to make your own stuff in Poser or Studio, IMHO.  Everyone seems to use a handful of smaller tools in addition to or even instead of the provided rigging tools.  What does that point to?

Well, Poser's original function was for artists to not have to use studio models.

I wish that Poser had some sort of modeling capability in it... maybe even including something like Virtual Fashion.

I'm trying to break away from Poser use myself and get into Cinema and ZBrush :)

Quote - I see that they give away the 3D Starter Pack too for free, wonder if its for Studio or Poser?

Doesn't matter - D|S will use either one :)> Quote - I'm sticking to Poser. I find the DS interface too confusing. Eww.

So change it (yes, you can...)> Quote - Nope, not that I know of but with the SDK on sale for $99.00 (regularly $1000.00) I'm sure someone may take a stab at doing Python for Studio if it's even possible. Considering that DAZ was considering using Python in the beginniing and I believe that there was a conflict with using the open sourced QT libraries that prompted them to take a different direction all together. But you never know!!!

Since DAZ|Script is ECMA-compliant, I'm sure it wouldn't take much to build in direct Python support (or to just use DAZ|Script, since it's fairly easy to translate to). OTOH, one couldn't simply drop-in Poser Python scripts, if that's what you're thinking, at least not w/o a translation layer of sorts. The other question ab't why Python didn't get used had nothing to do w/ Qt, as someone else aptly covered (After all, KDE on Linux is written in Qt, and Python works just fine in there).> Quote - Are you absolutely positive about the $99 for the D|S SDK? Won't that make the other developers a bit peeved after paying $1000 for it?

Nope - the dough IIRC gets refunded after selling x amount of stuff through the DAZ Store. ...reading further down the thread... be back in a few. /P

Quote - No problem. It's support should be added in the future though. It exists for specific reasosn and uses.

I'm kind of curious - what did the taper dial really do aside from traverse the hierarchy and, well, taper something (IIRC - haven't used it in years). > Quote - Python should give you access to all those things, and you can combine it with ordinary C/C++ code (PoserPhysics is one plugin that does that). Do you have something specific in mind? If you want to do something that's not available from Python, make sure to send a feature request to e frontier.

I want a Linux port! Oh, hehe - sorry... couldn't resist. You're right; Poser's Python does reach pretty deep in there. OTOH, I gotta question - and set aside me for a minute here. Thing is, Poser could use an SDK. Seriously, how d'ya do a combination of Python and C/C++ without adding extra cycles? Doesn't matter what kind of proggie we're talking here: Compiled code will almost always run hella faster than just scripts, and when you're banging algorithms about with a couple dozen thousand vertices, the differences tend to pile up. Even off-loading the more burdensome loads onto an external (faster) binary still requires the translation layer, and startup time, etc. Then there's the whole external proggie vs. native hooks that a compiled plugin enjoys. I guess what I'm getting at is, a full-on SDK for Poser (w/o a big pricetag) would be kind of useful, y'know? Just my two cents is all, and I won't bug you further ab't it, I promise. /P

Ya Studio 1.7 is very cool but after installing it I can't get poser 7 to work no mater what I do. Even uninstalling Studio and reinstalling poser didn't work. I am reay sorry I installed Studio 1.7. If you are running Poser 7 be careful installin 1.7 it might happen to you too. I have sent a message to Studio tech support hope to hear from them soon.

Quote - > Quote - They didn't say anything about Cinema on the Collada front page... so I assume it's either buried or we're just left out in the dark?

Unfortunately C4D still hasn't implemented Collada, but believe me I am going to be hounding Maxon about that at siggraph ;)

Pssstttt . . . . bug the Newtek guys too! ;)

Quote - Ya Studio 1.7 is very cool but after installing it I can't get poser 7 to work no mater what I do. Even uninstalling Studio and reinstalling poser didn't work. I am reay sorry I installed Studio 1.7. If you are running Poser 7 be careful installin 1.7 it might happen to you too. I have sent a message to Studio tech support hope to hear from them soon.

Works fine here

Quote - Seriously, how d'ya do a combination of Python and C/C++ without adding extra cycles?

Which is kinda my beef as well. Python just isn't practical for a lot of things. Like say if i wanted to write a better joint system or a more advanced posing interface (both of which are much needed in poser), i cant expect the user to wait while the script precalcs the interaction or something. Or jumps to an external app that is outside poser. It has to be done near realtime within the GUI, and that requires compiled code with direct access to Poser's API.

And since i'm hoping, I also want them to adopt Renderman's sl language for custom shaders in firefly. That is supported by most renderman compliant renderers and there is no reason firefly shoudn't.

OK guys. I didn't want this thread to turn into a debate about what program is better.  I see a bit of that trickleing in here and there.  This is a discussion about the DAZ Studio release.  If you dont' like the program then don't post here!

Moogal, the dynamic cloth engine is basic but will still allow one to fully pose and render, standing, sitting, animation and the like but adding things like wind effects and other functions will be available in the first of the 2 new plugins.  Then there is the 2nd plugin that will allow for clothing creation, I'm guessing directly in DAZ Studio.  I think that's one of the reasons for the new tabbed rooms as there will be a need for the extra room so the end user can "spread out" if need be.   That's a plus with the rooms.  Studio is set up to allow each room to be set up individually.  So no one room need be the same as any other room unless you so desire. 

PS: I'm not being an ass hole about my statement above but I started this thread and I asked nicely at the beginning for this conversation NOT to devolve into a debate about who's got more their money.  So please respect my wishes and if need be start your own thread if you so desire and have at it but please not here.  Thanks!  

Attached Link: http://docs.python.org/api/api.html

Here's a secret: Python code gets compiled. If you've seen .pyc files around, this is compiled Python bytecode that doesn't need to be parsed any more. Granted, it's not as fast as optimized C, but it's pretty fast. > Quote - Even off-loading the more burdensome loads onto an external (faster) binary still requires the translation layer, and startup time, etc. Then there's the whole external proggie vs. native hooks that a compiled plugin enjoys.

There is no need for an external program. If you turn a C or C++ library to a Python extension, it runs in the same address space and same process as Poser itself. Using a scripting language to connect C++ modules is not uncommon: if you examine a Maya installation, you'll notice that it's using MEL for a lot of the UI. > Quote - I guess what I'm getting at is, a full-on SDK for Poser (w/o a big pricetag) would be kind of useful, y'know?

I do agree that a plain C++ SDK would be convenient for those who don't want to learn Python or make a wrapper for C++ code (although its ridiculously simple with SWIG). My point is though that Python is faster than probably most people think it is and it's capable of many things. for a C++ SDK, I can only recommend sending an email to e frontier, including details about what killer plugins you would write if such an SDK were available. If there are enough requests for it, you never know. In any case...this is probably the wrong thread to go further into detail about this - it's about DAZ Studio, so for further discussion we should take this to a new thread if not the Python forum.

Quote - In any case...this is probably the wrong thread to go further into detail about this - it's about DAZ Studio, so for further discussion we should take this to a new thread if not the Python forum.

Fair 'nuff... I knew Python could be compiled, just never saw it in action. (...as long as it isn't as slow on load as compiled Java is --see also Open Office-- it could be useful.) I'll be a pest ab't it in the technical forum when I finally get off my butt and scrounge enough time to sit down w/ it :) Thx, /P

Quote - Tom Wrote: I'm kind of curious - what did the taper dial really do aside from traverse the hierarchy and, well, taper something.

Okay not trying to be a smart ass, but not seeing the usefulness of Taper, is a bit like not seeing the usefullness of "Scale"(which just scales) or "Point At"(which just points at). :)

Taper, being one of the 5 scale dials, has the unique attribute of scaling one end while fading off. Obviously, unless the figure, whether human, animal, mechanical or otherwise, is set up for proper scaling, the dial isn't going to be fuctional.

However, I'll list some simple examples of it's uses.

You can use it on humans get more complex shapes to the head, teeth, tongue, finger tips, etc. It can be used on eyes to just shrink the iris or on horns, etc for shaping without morphs.

In clothing, it can be used to point shoes, flair skirts and cuffs, widen/loosen boots, heels, etc etc etc.

On animals, it can be used to fine tune and customize the subtle shapes of snouts, ears, tails, wings, hooves, etc etc, etc, etc

On enviornmental cr2 based figures, it can be used for more abstract/toonish proportions along buildings, railings, staircases, etc etc etc.

On mechanics, it can be used to re-aligns mechanical parts or be animated for various recoil effects.

On particle based figures it can be used and animated for barrel flash, stobe, etc.

On hair, it can resize bangs, reshape lengths, flair strandsor locks, puff ponytails, etc etc etc

... all without the burden of unneccesary non-linear morphs... or more burdensome magnets.

So yes it tapers, :) thus the name, and perhaps it is easy to dismiss something easily when so few figures have ever been set up for proper scaling.

However, if we start picking and choosing to dismiss Poser code, and then down the road, it is found to be useful, people will be stuck with legacy issues and compatibility limitaions. Daz has never really taken scaling seriously, so I can see why they probably don't understand the practical uses of a dial that allows transition scaling. :)

Just one dial anyhoo. They should just write it in to be thorough and complete. I think not adding it was just an oversight really.

Does wonders on plants cr2's. Didn't mean to leave out our leafy friends. :)

Ya seems to be just me, after 8 hours of messing eith the PC i still can't get poser to work anymore. I've even uninstalled all the 3D stuff and reinstall poser to no avail.

Quote - > Quote - Tom Wrote: I'm kind of curious - what did the taper dial really do aside from traverse the hierarchy and, well, taper something.

Okay not trying to be a smart ass, but not seeing the usefulness of Taper, is a bit like not seeing the usefullness of "Scale"(which just scales) or "Point At"(which just points at). :)

No worries - "point at" is useful for things like eyes, cameras, lights... and it doesn't deform anything. "Scale" is great (IMHO) for tweaking clothing (either type), and for touching up those bits of figure that don't have interaction problems w/ adjoining conformed mesh, and great for props when done in moderation. I'm just curious as to how Taper coule be useful. Good examples, BTW. > Quote - So yes it tapers, :) thus the name, and perhaps it is easy to dismiss something easily when so few figures have ever been set up for proper scaling.

I'm thinking it's due to burden vs. benefit, mostly. > Quote - However, if we start picking and choosing to dismiss Poser code, and then down the road, it is found to be useful, people will be stuck with legacy issues and compatibility limitaions. Daz has never really taken scaling seriously, so I can see why they probably don't understand the practical uses of a dial that allows transition scaling. :)

Prolly because linear scaling can be done pretty quickly and easily in D-Form (albeit not as easily as spinning a dial, but...) In D|S, there isn't the lag that you normally get with magnets, so there really isn't any penalty for using one to do it (plus you can tweak the results much easier). Just a guess, though. As for what bits to leave in or out as per Poser code, well... D|S isn't Poser; it just happens to load and run figures built for Poser, and has its own setup. If enough people shift to it over time, then there would be no point in trying to stay within Poser's limits. While I'm not saying that Taper is a limitation per se, it does illustrate something programmers have to deal with any time they write a new version of anything: Cruft. Little-used and/or little-implemented features are a pain to maintain or keep as priority sometimes when you're busy shifting how everything behaves underneath the app. Sure, it sucks that a certain number of folks can no longer use a given feature, but if it's obscure anyway, and has functionality that can be handled else-wise (in this case by D-Form), then why? Microsoft Windows Vista is currently suffering under a ton of bloat and under high hardware requirements because of this principle in extremis, where Microsoft is trying to keep every little API and function it has in Windows, while at the same time trying to simultaneously add new features, modernize what's underneath, and secure the thing. In the end, they got a product that is still incompatible with the majority of 3rd-party apps, has not much more security than XP, and weighs in at a metric ton or so. I would expect that Poser will have to go through some of these changes too at some point, or end up like Vista. A development team can only rely on Moore's Law for only so long, y'know. There comes a point in any app or OS's life where the bloat will begin to show, and that something, somewhere, is going to have to give. Apple had to go through this when it went from MacOS to OSX... five years later, it (IMHO) was the right thing to do for them. /P

Quote - > Quote - Tom Wrote: I'm kind of curious - what did the taper dial really do aside from traverse the hierarchy and, well, taper something.

Okay not trying to be a smart ass, but not seeing the usefulness of Taper, is a bit like not seeing the usefullness of "Scale"(which just scales) or "Point At"(which just points at). :)

Taper, being one of the 5 scale dials, has the unique attribute of scaling one end while fading off. Obviously, unless the figure, whether human, animal, mechanical or otherwise, is set up for proper scaling, the dial isn't going to be fuctional.

However, I'll list some simple examples of it's uses.

You can use it on humans get more complex shapes to the head, teeth, tongue, finger tips, etc. It can be used on eyes to just shrink the iris or on horns, etc for shaping without morphs.

In clothing, it can be used to point shoes, flair skirts and cuffs, widen/loosen boots, heels, etc etc etc.

On animals, it can be used to fine tune and customize the subtle shapes of snouts, ears, tails, wings, hooves, etc etc, etc, etc

On enviornmental cr2 based figures, it can be used for more abstract/toonish proportions along buildings, railings, staircases, etc etc etc.

On mechanics, it can be used to re-aligns mechanical parts or be animated for various recoil effects.

On particle based figures it can be used and animated for barrel flash, stobe, etc.

On hair, it can resize bangs, reshape lengths, flair strandsor locks, puff ponytails, etc etc etc

... all without the burden of unneccesary non-linear morphs... or more burdensome magnets.

So yes it tapers, :) thus the name, and perhaps it is easy to dismiss something easily when so few figures have ever been set up for proper scaling.

However, if we start picking and choosing to dismiss Poser code, and then down the road, it is found to be useful, people will be stuck with legacy issues and compatibility limitaions. Daz has never really taken scaling seriously, so I can see why they probably don't understand the practical uses of a dial that allows transition scaling. :)

Just one dial anyhoo. They should just write it in to be thorough and complete. I think not adding it was just an oversight really.

Well then I would for SURE love to see Studio support taper then.  Mind if I use your examples for my plea in the bug reporting area where there is a feature request option to choose Anton??  You have them all nailed and you said it best!!  I won't quote you and use your name but the list is really important for the arguement to be justified!!!

Thanks muc!!

I find taper most useful on wrists ancles, elbows etc when you need to see part of the limb but are getting pokethrough on the concealed end. Such as the knee is sticking out but the ancle is visible taper is great to shrink the knee because you can't just hide the shin/knee. Other than that I have never used it much but for that alone I have always found it usefull.

There is an issue in Studio where Apollo's eyes can not be resized properly because of the lack of Taper being present.  So it would come in handy for that most of all for my needs of such a thing being present!!

I can't wait to try the new studio. :)  I often switch between the two.

If I may digress into a quick studio to poser question... I thought I saw a utility that makes it possible to transfer a pose from studio to Poser? Or any studio files back to poser...
I mich prefer to do posing in studio, because it allows you to select multiple body parts. Awesome for hand grips, or torso twists!
I'm drawing a tital blank on this issue.

Attached Link: Index of free DAZ|Studio scripts

One is called the Poser Format Exporter.  You can find it on the linked page above along with all the other fabulous scripts for Studio!!  Not sure if Richard's updated it in a while but it looks pretty thorough!!

HUGZ!!

Awsome! Thankees for that info RAMWolffee :)

Yer Welcome!!

Just be be clear, Apollo's eyes scale fine. On the eyes Taper was used to scale the iris larger and smaller. No huge loss in Studio.

That is fine Richard. You can use those examples. I am sure they already have read this thread but go fot it.

If Studio does turn out to be to porting tool of choice to other apps like Carrara, Bryce, etc, and it doesn't support Taper, I would be concerned about that ability being lost to those other apps too, especially apps being designed by Daz.

Studio isn't Poser. True. But most definately is the Poser file format. Either support the cr2 format completely, or do something original. Just because Daz doesn't use the Taper code does not mean they should make that decision for those who know how.

In reality I think they just never realized it was useful because they don't use the figures they make, V4 being the first of their figures, in 12 years and as many figures, that can even begin to scale properly.

Okay that is my pitch for Taper support. Either they will or they won't.

Annibel, if you buy the Finder plug-in for Sudio things are much easier to find than in Poser.  In fact I open Daz Studio frequently to search for content using finder.  It's worth it's weight in GOLD!

Quote - Studio isn't Poser. True. But most definately is the Poser file format.

True, which is why *.daz is the native format in D|S :) > Quote - Either support the cr2 format completely, or do something original. Just because Daz doesn't use the Taper code does not mean they should make that decision for those who know how.

Perhaps, but it got me to thinking: Very few 3rd-party proggies support the .cr2 format fully in the first place. Not talking about plugins or direct add-ons, but external proggies, like Vue, Bryce, things like that. Transposer > Carrara I think came the closest. I'm thinking it's most likely because Poser is closed-source (and to be honest, so is D|S). Because of this, how exactly Poser handles the morph/dial and translates the results is largely a secret - at least programmatically. Unless you call it directly in Poser.exe/.app (say, via Python), you won't replicate the results perfectly, if at all. Unless the function is vital, it is far easier/safer to leave a feature out than to throw a ton of time and cash at emulating it - especially if the results are at best not going to be perfect, IM(Professional)O. > Quote - Either they will or they won't.

Pretty much. /P

***Quote - Very few 3rd-party proggies support the .cr2 format fully in the first place. ***

But very few programs are seeking from scratch to emulate Poser to the extent Studio has.

Quote - Because of this, how exactly Poser handles the morph/dial and translates the results is largely a secret - at least programmatically.

*** ***Not really. They already cracked everything else in the cr2 and duplicated it's fuction and performance. I doubt there is anything dubious about "taper".

***Quote - Unless you call it directly in Poser.exe/.app (say, via Python), you won't replicate the results perfectly, if at all. ***

*** ***
Tom think about it. If that was true, none of these pose packs and character packs would work. Of course the tracking is plottable. Once you know what off and what 100% is, it is easy to define all the percentages in between.

Quote - Unless the function is vital, it is far easier/safer to leave a feature out than to throw a ton of time and cash at emulating it - especially if the results are at best not going to be perfect

Well techically "Scale" can be achieved with x.y.z scale so it is even less vital than taper, being it is completely reduntant. After 5 years and what I am sure is over a million in expense, I don;t think supporting "taper" is going to bring the company down financially.

They already have an example of how it works so ditching it's emulation, while choosing the emulate the rest of the cr2 makes it likely they either forgot or foolishly have dismissed it's use.  I can't see anything "unsafe" or baffling about "Taper".

There is no reason the results can't be emulated just as well as they did with Scale, Xscale, Yscale, Zscale, PointAt, Joints, etc, etc, etc.

Thanks Anton for permission.  I just wanted you to know I was interested in using your words but not your name so as to not make anyone uncomfortable.  It's funny, they must really be gearing up quickly for this release that contains the dynamics engine in it.  I had 2 issues resolved, one of them saying that the issue that I was having fully using RKane's (Roberts) add on morph pack for Apollo but was not showing up correctly in Studio has supposedly been resolved (we shall see) but I also got on Assigned and it's the taper dial issue I requested be fixed or implemented back in April (sheesh, how time fly's!)  so I'll just follow it up with this information to make sure they know I'm watching with anticipation!! LOL  Like that will make any difference!! LOL

Quote - But very few programs are seeking from scratch to emulate Poser to the extent Studio has.

IIRC, Poser is only a starting point due to existing inventory. If you look at the rest of what DAZ bought up lately: Carrara & Hexagon, Bryce, etc etc... all signs point to independence. > Quote - Not really. They already cracked everything else in the cr2 and duplicated it's fuction and performance. I doubt there is anything dubious about "taper".

I'm not sure about that... The .cr2 is in ASCII and most (not all) of its functionality is fairly easy to grok (not easy to code, but easy to understand), and its various functions can be tested against. As an example you've mentioned yourself, scale is pretty easy to do. Quaternion Rotations (joints and such) are a well-defined mathematical expression. It's the out-of-the-way stuff that gets to be a pain. > Quote - Tom think about it. If that was true, none of these pose packs and character packs would work. Of course the tracking is plottable. Once you know what off and what 100% is, it is easy to define all the percentages in between.

Sure, if all you're doing is importation. Going the other way as well, is where things get ugly. > Quote - > Quote - Unless the function is vital, it is far easier/safer to leave a feature out than to throw a ton of time and cash at emulating it - especially if the results are at best not going to be perfect

Well techically "Scale" can be achieved with x.y.z scale so it is even less vital than taper, being it is completely reduntant. After 5 years and what I am sure is over a million in expense, I don;t think supporting "taper" is going to bring the company down financially.

I doubt it by itself would either, but look at the whole of what I wrote there. Wait - it's prolly not well-defined, my apologies. I'll expose it from a different angle: if it is easy to figure out, okay... chuck it in. If it's not-so-easy, then you have a decision: is it worth doing priority-wise, or not? Cost vs. Benefit starts kicking in at that point. > Quote - There is no reason the results can't be emulated just as well as they did with Scale, Xscale, Yscale, Zscale, PointAt, Joints, etc, etc, etc.

It can be emulated (I can almost construct the chain in my head as I type this). That said, can that emulation be exportable (so that it works as predicted in Poser) as well as importable? Me, I don't mind either way... I'm still waiting for a native Linux port of it (don't ask - long story :) ). OTOH, I'm just pointing out the ugly programmatical aspects that come up. Not impossible, but when you're paying for code-monkey time at the rates that DAZ pays 'em, that time gets precious indeed. /P

if you can emulate then write us a script that can access that portion of the cr2 and translate it for us!! LOL 

PURTY PLEASE!! (in the voice of Elmer Fud)

I just reopened the issue as it was NO WHERE to be found in the date base after it was supposedly assigned to Nathan Blunt.  So I resubmittd and copy pasted your reasons, Anton, into the text area and gave a brief reason WHY I was leaving such a long list and for them to please consider this a bit more carefully.  I also asked why the newly assigned issue seemed to have been dropped, nowhere to found in the data base, as least the stuff I can see there.

We shall see said the blind poet to the deaf mute!!

Quote - if you can emulate then write us a script that can access that portion of the cr2 and translate it for us!! LOL 

I wouldn't mind, but personally, I'd rather do it as a compiled plugin. Much faster that way. ...well, after I get a few bits and bobs that I've been dying to do :) . For instance, I'm beating up on a means of real-time deformation on soft objects once a harder object collides against it (currently half done, but it works) and a second one which DAZ already has a chunk of code-wise considering how long ago I started on it (concerning clothing and collision detection between cloth and underlying figure*), but any further work on my part there looks to be made redundant pretty soon now. * nope - can't claim it beyond possible contribution; others were working on it --even back then-- as well. I think I know what route(s) they finally went with to get it done, though. /P

Just a little tip to those who don't like the tree structure of the libraries: You can switch to a list structure that's more like Poser's, only better.

Click the little arrow pointing right, next to the content tab and select "View folders as list". I really don't understand why this is not the default because it is so much better and easier to use imo.

The thing about the DAZ libraries that bugs me is the lack of a scrolly arrow like Poser has ... It just involves too much back buttoning to get anywhere and too much scrolling to find the right listing.

What 'scrolly arrow' is that, GoM? The one down the side? DS has that, plus mouse-wheel scroll. You can also hit Home or End to go to top/bottom of a library folder. You've got back/forward/up buttons at the top, and you can use small icons for less scrolling, if your libraries have tons of stuff in them. Not sure what else they could add, to tell the truth.

Re the list structure - As default? Well, not for me, thanks. I always set mine to tree. But everyone's different.

mac

Quote -
Re the list structure - As default? Well, not for me, thanks. I always set mine to tree.

I use the List view, but owning a Macintosh will do that to a guy... makes an OSX user feel right at home that way (Also notice that the tree view emulates Windows' left-hand "Explorer" bar? It's sort of why they were done-up like they were, so that it wouldn't look much different from whatever default file-poking-around layout that a user would normally be accustomed to).

/P

I like this about Poser 6 though. Earlier ones too, I think.

Right, I see what you're saying, GoM. It could be an interesting addition to DS, although to be honest, it's pretty similar to the list view. You could always request it in the tracker.

Re Home/End - They should work inside any content folder, assuming the folder itself is in focus. If the focus is on the folder list above, it'll still work, but go to the 1st/last folders. 

Does it work for you in any other panes? Try expanding a figure in the scene pane. Home/End should take you to the top/bottom of the hierarchy. Same thing in Surfaces.

mac

It is similar to the list view but it is just quicker. My biggest gripe is going from poses to characters (and scrolling) to poses (and scrolling) and then back to face (and scrolling) or something. It just is ponderous. Repeat that for clothes (minus the face part) and it just eats up time and adds to my frustration. Plus the scrolling grabber is more finicky since it is small makes it even more of a challenge.

The back and forward and scroll thing just is so much slower for me. I am not sure why the home and end didn't work last night but it works today.

well a lot of that scrolling back and fourth is becouse you are using those runtimes for poser as well as studio which limits how you can arrange your content. if for example you put all of your V4 clothing directly under v4 in the library and all of the materials for that clothing directly under that, and things like that you would find using the studio library system a lot faster.

Yeah but I don't have anything in the Content :) Whatever the default is is pretty much what I have. Then you just have to go back and forth a lot (which is annoying on it's own).

Well last night I had a "defining moment".  As I already said, I've been using Poser since day one and I've been a loyal customer, even when others ranted and complained, I patiently continued to stick with it.  But last night after a horribly frustrating session of trying to work with 4 figures inside a hallway set, I said "ENOUGH!"

I've dabbled with D|S for a few weeks now, but not really doing any serious work with it.  That changed last night, I loaded the scene I was having so much trouble with from Poser and got the job done within 10 minutes!

I am astounded at how much easier D|S is to work with.
I've jumped ship.  I've switched sides.  I'm playing for the other team now! (no sexual referenced intended) :)

Is anyone else here jazzed as I am?  Has anyone else seen the light and not looking back?
(yes exporting to other software would be nice, but my frustration factor went from 10 to 0 in posing and setting up scenes)

Welcome aboard!!   Not to say Poser doesn't have it's uses in my arsenal but with the soon to come Carrara 6 I don't think I'll even need it for the few little things I was using it for.  I think someones even working on an export as cr2 script if I'm not mistaken.  So, yea... end of an era for me too it seems.  Perhaps I'll upgrade with version 8, perhaps not! 

JeeZ! Just when I think I understand all the ins and outs of Poser(6.& 7) Now I don't know what to think! I have learned more from reading this thread about Poser, then I ever thought I knew. But Dang if D/S isn't a bitch to nail down. Any advice on how to do the cross over just to try it out? When I switched fro PSP to PS, it took 2 long years to even understand the locations of the common tools! Duh! I'm not saying I am a blond or anything.... But I get bummed thinking that all my hard work is about to go back to Newbie square one! *sigh....

Oh BTW...can someone tell me the size limit of D/S? I normally render in an extremely large format for art. 7000x4600, 350 DPI Can D/S handle that?

Ariana

Quote - JeeZ! Just when I think I understand all the ins and outs of Poser(6.& 7) Now I don't know what to think! I have learned more from reading this thread about Poser, then I ever thought I knew. But Dang if D/S isn't a bitch to nail down. Any advice on how to do the cross over just to try it out? When I switched fro PSP to PS, it took 2 long years to even understand the locations of the common tools! Duh! I'm not saying I am a blond or anything.... But I get bummed thinking that all my hard work is about to go back to Newbie square one! *sigh....

Oh BTW...can someone tell me the size limit of D/S? I normally render in an extremely large format for art. 7000x4600, 350 DPI Can D/S handle that?

 Ariana

I was pretty confused at first too.  
Two things helped me.  I downloaded the PDF manual, printed it off and started reading it.
And secondly, I had a specific project I wanted to get done, so that helped me figure out a lot of the functions of D|S with a specific goal in mind (mostly by trial and error)

IMHO, it's definetly worth taking the time to learn.  The posing features alone have already saved me hours of frustration.... and many grey hairs!

Wow, I saw daz studio on http://www.download.com/DAZ-Studio/3000-6677_4-10717524.html?tag=lst-0-5   38,000 downloads!  not too bad.

Don't forget the Mac users: 5888 :P

Quote - Don't forget the Mac users: 5888 :P

I think a lot of that is because not a lot of Mac users go there as a general habit.

All those dl's are from download.com, which I think is a bit of a roundabout way of getting daz studio. I wonder how many people downloaded it from DAZ!
Unless DAZ download goes through them too - if it does, I didn't notice.