Adding to Cart…
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2026 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2026 Daz Productions Inc. All Rights Reserved.
Comments
The content from RuntimeDNA are not "DAZ Content" as such (yet) and must be categorized differently from the standard "DAZ Content" for 2 reasons:
1) RDNA was primarily a Poser outlet with a smattering of DazStudio compatible items.
2) During a time of consolidation there is expected to be a period of time where the absorbed stock is integrated into the current inventory system and those items may be miscategorized or mislabeled. This occurs in physical outlets as much as virtual.
Anything migrating from RDNA should be highly suspect as to its compatibility with DS at all. From what I can tell, the vast majority of RDNA items that are Poser items are listed as Poser items in the store. I have seen that there have been issues where PMD files are part of the package, but that is a caveat expected from anything coming from a Poser Environment that deals with the Generation4 content.
With that being said, as the thread title clearly states, this is about new DAZ Studio native releases and not about older integrations.
Kendall
...and what of older content being broken by updates. The AoA Atmospheric and Graphic Art Cameras as well as the Advanced Lights (Flagging SSS surfaces) were all broken in the 4.7 update. There were scripts provided to make them work properly again (save for the flagging issue with the lights) in 4.8 but 4.9 broke that. As I and many others still use 3DL because we cannot afford expensive GPUs with a lot of memory and don't care to have our systems tied up for days rendering, losing use of these valuable tools (that we paid for) is an issue.
...excellent point.
As others have noted, in general, if you chose not to upgrade any software, you are also assuming the risk that trying to use anything created for use in the newer version may not work properly (or at all) in the older version. Also, if you chose to upgrade you are also assuming the risk that the new software will "break" something that worked perfectly fine in the old software.
This is nothing new, and the problem is not unique to DAZ. I wish I had the hundreds of hours back that I have spent over the past 30 years fixing things that new versions of software broke (or finding work arounds for those time when fixing wasn't an option). 3rd party plugins, user definable settings, and user based modifications are always prime candidates to "break" with software upgrades.
I'll just throw this out as a suggestion. Maybe someone who is still using 4.8 would be willing to start and maintain a thread where people can post about new content that doesn't work properly in DS 4.8xxxx? It would give a convenient place for those who haven't upgraded to check to see if a new item works in 4.8.
...I just checked and all the Advanced lights say "Compatible with Daz Studio 4.9 even though the SSS Flagging is still broken . The Atmospheric Cameras say the same even though they needed scripts for the depth, Vignette and Colour cameras to work in 4.8. The Graphic art cameras are the only ones that state they just work in an older version fo the programme (4.6) which cannot be run concurrently with newer updates. So basically 10$ now wasted for what was a very useful tool and another 53$ for items which no longer function completely as they are supposed to. Not easy to "write off" when on a tight budget.
OR .....Daz3d.com can do what Renderosity does and require PAs to state very clearly on the product's page which version/s the item has or has not been tested in.
Two things worry me.
1. No official announcement has been made that certain products may not work in pre 4.9 versions of DS. We won't tell you which.
2. What was initially identified as a fault of one product now appears to have blown out to a suggestion that this is now the new future.....like it or lump it.
As I said, items are guaranteed to work only in the version they were created under. I would imagine, as this is a cost for the PA to update, if it doesn't work in new versions, it should be pulled from the market. As this is a PA item, only they are the ones that can fix it and I haven't seen the PA release items in some time so it may just be a dead product going forward. I only used the product once, but it was way slower than what I can use in iray, so that's probably another reason why it wasn't updated.
Unfortately this won't happen, PAs depend on the program to stay the same and those with large catelogs don't have time to constantly test all their products against new products. Even rendo can't force vendors to do that, they're not their employees and they balk at that an not do it. If you put in a ticket for a product that is over a year older and the PAs doesn't update it, it's not much you can do.
Just to chuck my two pennies into the ring .... as a few have stated, I'd expect (I'm an 'old lag' with DS) scripts to have issues even if they are readable in an earlier version (the encrypted/binary thing). Shaders likewise, though to a lesser degree. Content I'd generally expect/assuem to work within a major version/release (stuff created in 4.*, etc.) so kind of surpeised by this. In a perfect world you should obtain support for any product you ever bought, but practicalities dicatate that ain't gonna fly - may parents had to get a new gas boiler some yaers ago as there was no one left who knew how to service the 'old clunker' they had ;) A lot of software companies will actively support current version (with luck!!!), plus current -1, and sometimes current -2.
The 'compatible with' flagging of products is, sadly, a bit of a joke (DAZ dropped the ball with the DIM categories - so much potential!) as it will (I think automagcially) always be the latst, greatest release number shown: so, as soon as a new DS release rolsl out ALL of my content is, theoretcially, no longer supported until, or unless, I upgrade the program. I generally approve of sing the latest version, but I do so with a degree of lag to see what gremlins are shaken out of the tree and have often waited for the next release/upgrade before installing.
My suggestion would have been for a 'created with/for version' indicator, which may have been of some use. Unless, of course, this is a bug within the content creation mechanism of DS4.9!
Appears to be some missing weight mapping that only got noticed in an older version of DAZ Studio. Not exactly sure if that constitutes a "bug" or not.