What features would you like to see appear in dazstudio 5?

1666769717289

Comments

  • davesodaveso Posts: 7,014

    the ability to render iray FAST without the use of an nvidia video card ...via CPU. i have this feeling that v5 will put me out of the DAZ Studio use, as I can barely render G8 stuff .... and the last update slowed my renders down more. 

  • Once again fix the Libraries for example look at Poses there are folders named Poses scattered every where make a single Pose folder with subfolders same with environments and props there are props in enviroments and environments in props and props in the People folders

    You mean perhaps having something like a People folder, then in that a folder for each figure, and then folders within that for clothes, poses, characters etc.?

    In any event that is a matter for content creation and packaging, not an application thing.

    Not exactly more like this

    A folder for People with  figure folders containing Characters and clothes.

    A Pose folder with sub folders for anything posable,

    Props for buildings furniture vehicles,furniture

    Enviroments for landscapes rocks plants

  • NathNath Posts: 2,807

    Once again fix the Libraries for example look at Poses there are folders named Poses scattered every where make a single Pose folder with subfolders same with environments and props there are props in enviroments and environments in props and props in the People folders

    You mean perhaps having something like a People folder, then in that a folder for each figure, and then folders within that for clothes, poses, characters etc.?

    In any event that is a matter for content creation and packaging, not an application thing.

    Not exactly more like this

    A folder for People with  figure folders containing Characters and clothes.

    A Pose folder with sub folders for anything posable,

    Props for buildings furniture vehicles,furniture

    Enviroments for landscapes rocks plants

    But I keep Poses with People. Furniture is a subset of Interiors, which is a subset of Places (which is both landscapes and buildings). Etc.

    No pre-defined structure is ever going to capture all the ways we each like to organise our content. So, I'd prefer to keep the loose, but customisable arrangement of files we have now.

  • Richard HaseltineRichard Haseltine Posts: 100,949
    edited January 2018

    Once again fix the Libraries for example look at Poses there are folders named Poses scattered every where make a single Pose folder with subfolders same with environments and props there are props in enviroments and environments in props and props in the People folders

    You mean perhaps having something like a People folder, then in that a folder for each figure, and then folders within that for clothes, poses, characters etc.?

    In any event that is a matter for content creation and packaging, not an application thing.

    Not exactly more like this

    A folder for People with  figure folders containing Characters and clothes.

    A Pose folder with sub folders for anything posable,

    Props for buildings furniture vehicles,furniture

    Enviroments for landscapes rocks plants

    Well, I would vote against having poses away from the figure they are made for (or the prop etc. they are made to go with) since it would involve more ascending/descending the folder tree - but again, it's a content request not a DS request. It should also be handled already by Smart content - with the item selected and Filter by Context checked look in the Pose Category

    Post edited by Richard Haseltine on
  • Robert FreiseRobert Freise Posts: 4,444
    edited January 2018
    Nath said:
    No pre-defined structure is ever going to capture all the ways we each like to organise our content. So, I'd prefer to keep the loose, but customisable arrangement of files we have now.

    I agree I'm just suggesting something more logical than the shotgun approach that might make it easier for beginners to find things and for customizing for the rest of us

    I've got about 14000 items from Daz alone and I don't know how many from other stores some of which are no longer in business (3d Commune,Poser Pros etc) so organization is very important to me.

    Edit to fix to low file number

    Post edited by Robert Freise on
  • Once again fix the Libraries for example look at Poses there are folders named Poses scattered every where make a single Pose folder with subfolders same with environments and props there are props in enviroments and environments in props and props in the People folders

    You mean perhaps having something like a People folder, then in that a folder for each figure, and then folders within that for clothes, poses, characters etc.?

    In any event that is a matter for content creation and packaging, not an application thing.

    Not exactly more like this

    A folder for People with  figure folders containing Characters and clothes.

    A Pose folder with sub folders for anything posable,

    Props for buildings furniture vehicles,furniture

    Enviroments for landscapes rocks plants

    Well, I would vote against having poses away from the figure they are made for (or the prop etc. they are made to go with) since it would involve more ascending/descending the folder tree - but again, it's a content request not a DS request. It should also be handled already by Smart content - with the item selected and Filter by Context checked look in the Pose Category

    Has never worked on any of my machines don't know why I finally gave up on it

    Support wasn't able to help

  • NathNath Posts: 2,807
    Nath said:
    No pre-defined structure is ever going to capture all the ways we each like to organise our content. So, I'd prefer to keep the loose, but customisable arrangement of files we have now.

    I agree I'm just suggesting something more logical than the shotgun approach that might make it easier for beginners to find things and for customizing for the rest of us

    I've got about 1400 items from Daz alone and I don't know how many from other stores some of which are no longer in business (3d Commune,Poser Pros etc) so organization is very important to me.

    Oh yes... but keeping it simple for beginners may be the hardest part of all that.

  • kyoto kidkyoto kid Posts: 41,057
    edited January 2018
    daveso said:

    the ability to render iray FAST without the use of an nvidia video card ...via CPU. i have this feeling that v5 will put me out of the DAZ Studio use, as I can barely render G8 stuff .... and the last update slowed my renders down more. 

    ...not sure if that would be possible while preserving Iray's high/photoreal render quality as it employs physically based lighting which involves a heavier amount of calculation (particularly in interior scenes) compared to the version of 3DL Daz uses.  Anything that could be done to speed it up would compromise render quality just like with LuxRender.

    Post edited by kyoto kid on
  • Serene NightSerene Night Posts: 17,647
    edited January 2018

    Soft body physics. Right now characters impale each other when hugging and you have to prevent everything from trulytouching  or parts bisect. Flesh parts of the body need to compress fat parts of  arms and fingers and stomachs  and chests need go in where they touch and curve rather than through

    oh and please do something about male elements. We are striving towards realism so making bulges that look all the same and defy gravity are about as silly as designing Vicky with no nipples. Imagine if Vicky only had one chest morph.

    Post edited by Serene Night on
  • I'm well aware of Daz' progress throughout the 4.x tree. I know other programs have one major and a .5 and then the next major. Some only do whole numbers, others skip entire minors (Bryce 5.5 to 6.2). Still others only do x.x because it looks or sounds cool to them (like 2.0 even though it's absolutely stupid).

    And I'm not getting the whole "as it relates to the 4.5 SDK" comment. So they'd have to update that version number as well. OK...? 

    Version Checking is something you add to an SDK to ensure everyone's buying the New Hotness. It's not Federal Law, it's not Gospel, it's not Do Or Die. It's something that one software developer implemented decades ago and everyone else jumped on that bandwagon and took it as one of the Habits of Successful People. This is how Pythagoras got away with his crap.

    If you don't put in the Version Check to ensure x plugin was made in the new SDK, it's not going to generate an error unless you did something really stupid like moved stuff around rather than just appending the new stuff to the end.

     

  • I'm well aware of Daz' progress throughout the 4.x tree. I know other programs have one major and a .5 and then the next major. Some only do whole numbers, others skip entire minors (Bryce 5.5 to 6.2). Still others only do x.x because it looks or sounds cool to them (like 2.0 even though it's absolutely stupid).

    And I'm not getting the whole "as it relates to the 4.5 SDK" comment. So they'd have to update that version number as well. OK...? 

    Version Checking is something you add to an SDK to ensure everyone's buying the New Hotness. It's not Federal Law, it's not Gospel, it's not Do Or Die. It's something that one software developer implemented decades ago and everyone else jumped on that bandwagon and took it as one of the Habits of Successful People. This is how Pythagoras got away with his crap.

    If you don't put in the Version Check to ensure x plugin was made in the new SDK, it's not going to generate an error unless you did something really stupid like moved stuff around rather than just appending the new stuff to the end.

    SDK changes do break plug-ins. That doesn't mean they can't make changes, if you look at the change log you will see they have while retaining 4.5 as the minimum required, but the sort of chnage that would make a DS 5 (such as moving to a new version of the Qt framework) would not be possible without requiring plug-ins to be recompiled at the very least as far as I am aware.

  • polmearpolmear Posts: 33

    How about voice activated natural language processing for posing as in : 'Vicky, sit on the chair, look at me, hold the sword in your left hand'.

  • I'm well aware of Daz' progress throughout the 4.x tree. I know other programs have one major and a .5 and then the next major. Some only do whole numbers, others skip entire minors (Bryce 5.5 to 6.2). Still others only do x.x because it looks or sounds cool to them (like 2.0 even though it's absolutely stupid).

    And I'm not getting the whole "as it relates to the 4.5 SDK" comment. So they'd have to update that version number as well. OK...? 

    Version Checking is something you add to an SDK to ensure everyone's buying the New Hotness. It's not Federal Law, it's not Gospel, it's not Do Or Die. It's something that one software developer implemented decades ago and everyone else jumped on that bandwagon and took it as one of the Habits of Successful People. This is how Pythagoras got away with his crap.

    If you don't put in the Version Check to ensure x plugin was made in the new SDK, it's not going to generate an error unless you did something really stupid like moved stuff around rather than just appending the new stuff to the end.

     

    So basically you don't agree that a new software version and SDK should ever remove obsoleted functions just so a plug-in developed for an older version can continue to function. If that's the case, why not just continue with the current version of the software and increment as needed, which is what has been done for the last seven years now.
  • nonesuch00nonesuch00 Posts: 18,131
    polmear said:

    How about voice activated natural language processing for posing as in : 'Vicky, sit on the chair, look at me, hold the sword in your left hand'.

    Yes! At least as a fast shortut to more fine tuned posing.

  • wolf359wolf359 Posts: 3,828
    edited January 2018

    "Soft body physics. Right now characters impale 
    each other when hugging and you have to prevent 
    everything from trulytouching  or parts bisect. 
    Flesh parts of the body need to compress fat parts of  
    arms and fingers and stomachs  and chests need go 
    where they touch and curve rather than through"

    What you are asking for is a global system of collsion dynamics
    to be running constantly in Daz studio for this to be Automatic.

    The software would have to constantly be in a state of collision
    calculation which would be very hardware intensive.
    Collission dynamic engines tend to be binary for very good reason.
    that being so you can assign maps or tags or scene item checklist
     states to only the items to have collisions calculated by the engine.

    Also such a system would have to make on the fly determinations 
    of what of a "soft" body and what is a "rigid"  body
    and considering that the human body is a mass of wildy varying soft bodies
    ( my finger tips) mixed with rigid bodies( my knuckles) and semi rigid bodies ( my ear cartilage)

    you would need an Entirely new Class of figure rig design
    (years beyond genesis)  before you could
    even begin to manually assign such widly varying collision properties
    to say nothing of having the software calculate them automaticly 
    &in real time.

    Post edited by wolf359 on
  • nonesuch00nonesuch00 Posts: 18,131

    Something like this would be interesting in DS 5

    http://zivadynamics.com/character-platform-beta

  • kyoto kidkyoto kid Posts: 41,057

    ..nice however that looks like it would take some reasonable horsepower to drive.

  • kyoto kidkyoto kid Posts: 41,057

    ...from the other "Future of Daz3D" thread:

    ...expanded file format import support, like .3ds, .lwo, .stl, etc,

    ...improved 3DL capability.

  • kyoto kid said:

    ...from the other "Future of Daz3D" thread:

    ...expanded file format import support, like .3ds, .lwo, .stl, etc,

    ...improved 3DL capability.

    We don't NEED a new version of DAZ Studio for this; we just need folks willing to write the plug-ins for them.
  • Serene NightSerene Night Posts: 17,647

    Please a way to stop spot render if you forget to click new window. The pain of trying to drag the marquee really small to avoid it taking forever before you can cancel  is real. wink

     

  • kyoto kidkyoto kid Posts: 41,057
    edited February 2018
    kyoto kid said:

    ...from the other "Future of Daz3D" thread:

    ...expanded file format import support, like .3ds, .lwo, .stl, etc,

    ...improved 3DL capability.

     

    We don't NEED a new version of DAZ Studio for this; we just need folks willing to write the plug-ins for them.

    ...but if best laid plans don't com to fruition, always good to have a backup.

    Post edited by kyoto kid on
  • SixDsSixDs Posts: 2,384

    Since I mentioned something along these lines way back when this thread was initiated, I'll reiterate again, as it is "near and dear" to my heart, so to speak. Pul-lease institute a proper update patch system so that we do not have to reinstall the whole application three or four times a year for simple bug fixes. That is simply arcane. Who else does that? Service releases, OK. Minor patches, no.

  • PetercatPetercat Posts: 2,321
    SixDs said:

    Since I mentioned something along these lines way back when this thread was initiated, I'll reiterate again, as it is "near and dear" to my heart, so to speak. Pul-lease institute a proper update patch system so that we do not have to reinstall the whole application three or four times a year for simple bug fixes. That is simply arcane. Who else does that? Service releases, OK. Minor patches, no.

    YES!
    Get the bugs out of one version before moving to the next!
    By coming out with a new version two or three times a year, we are guaranteed to be dealing with bugs in perpetuity.
    And please try to maintain backwards compatibility, it's bad enough that G8 can't be used even in early versions of 4.9,
    but now some scenery and and scripts can't, either?
    Why even have encrypted scripts?

  • Petercat said:
    SixDs said:

    Since I mentioned something along these lines way back when this thread was initiated, I'll reiterate again, as it is "near and dear" to my heart, so to speak. Pul-lease institute a proper update patch system so that we do not have to reinstall the whole application three or four times a year for simple bug fixes. That is simply arcane. Who else does that? Service releases, OK. Minor patches, no.

    YES!
    Get the bugs out of one version before moving to the next!
    By coming out with a new version two or three times a year, we are guaranteed to be dealing with bugs in perpetuity.
    And please try to maintain backwards compatibility, it's bad enough that G8 can't be used even in early versions of 4.9,
    but now some scenery and and scripts can't, either?
    Why even have encrypted scripts?

    You're going to get bugs no matter what; sometimes some bugs will appear to be fixed, but resurface some time later. And the encrypted scripts aren't really that; it's more like a minimum version check to ensure certain functions are available for the script or some other aspect of a product. For example, Genesis 8 used certain features of Iray in the material presets that don't exist in the versions of DAZ Studio prior to the one that was released at the same time, so they attempted to lock it to that version by a script.
  • nicsttnicstt Posts: 11,715

    Doubt it needs a new SDK, so before version 5, the ability to use AMD's new renderer; renders can be done with CPU, and either or both AMD and Nvidia cards.

  • nonesuch00nonesuch00 Posts: 18,131
    nicstt said:

    Doubt it needs a new SDK, so before version 5, the ability to use AMD's new renderer; renders can be done with CPU, and either or both AMD and Nvidia cards.

    This is very important to get a PBR renderer that is reliant on openCL standards so that it runs fast on INTEL, AMD, & nVidia PBR renderers. Also AMD GPU will be integrated directly on a future intel CPU. 

    DAZ as a hobby will loose future customers at the current price point of the current nVidia & AMD GPU products.  

  • nicstt said:

    Doubt it needs a new SDK, so before version 5, the ability to use AMD's new renderer; renders can be done with CPU, and either or both AMD and Nvidia cards.

    This is very important to get a PBR renderer that is reliant on openCL standards so that it runs fast on INTEL, AMD, & nVidia PBR renderers. Also AMD GPU will be integrated directly on a future intel CPU. 

    DAZ as a hobby will loose future customers at the current price point of the current nVidia & AMD GPU products.  

    The problem is, which OpenCL version should it support? Look at the problems people are having with dForce not being supported by their hardware and it only requires OpenCL 1.2.
  • nicsttnicstt Posts: 11,715
    nicstt said:

    Doubt it needs a new SDK, so before version 5, the ability to use AMD's new renderer; renders can be done with CPU, and either or both AMD and Nvidia cards.

    This is very important to get a PBR renderer that is reliant on openCL standards so that it runs fast on INTEL, AMD, & nVidia PBR renderers. Also AMD GPU will be integrated directly on a future intel CPU. 

    DAZ as a hobby will loose future customers at the current price point of the current nVidia & AMD GPU products.  

     

    The problem is, which OpenCL version should it support? Look at the problems people are having with dForce not being supported by their hardware and it only requires OpenCL 1.2.

    Software versions not supported is a perenial problem, but it does off the opportunity to be supported in a later update.

    With hardware issues, the same can't be said to be possible.AMD cards will not get Nvidia support, although we could hope.

  • SylvanSylvan Posts: 2,711

    Basic modeling tools other than D-former.

  • kyoto kidkyoto kid Posts: 41,057
    nicstt said:

    Doubt it needs a new SDK, so before version 5, the ability to use AMD's new renderer; renders can be done with CPU, and either or both AMD and Nvidia cards.

    This is very important to get a PBR renderer that is reliant on openCL standards so that it runs fast on INTEL, AMD, & nVidia PBR renderers. Also AMD GPU will be integrated directly on a future intel CPU. 

    DAZ as a hobby will loose future customers at the current price point of the current nVidia & AMD GPU products.  

    ...AMD already released a Ryzen CPU with integrated GPU capability.

    agreed with the final point. Granted two years ago none of us would have expected this to occur. Oh maybe a modest price increase for the next generation GPU cards but not 2 to 3 times the MSRP like we are seeing these days.

    As I suggested, maybe Daz needs to consider approaching DNA to allow for more advanced features of 3DL to be unlocked and vendors may have to start accommodating 3DL materials again.

Sign In or Register to comment.