The version in Daz Central should be the updated version - Daz does not generally do patches, it's a full replacement.

Hi, I got an eMail saying that the new Daz Studio 4.16 was now available... but when I click the link to update, it brings me to the download page of Daz Central. Same version that I already have. And opening Daz Central only confirms that I have the Daz Studio 4.15.1 installed, there is nothing about the 4.16 version.
Did I miss Something?

How can I get the latest version?

By the way those, those offers are often not so clear, I made some purchases yesterday and got OK deals but not as advertized. Probably my bad, I am French and some times reading English is not so obvious to  me. But still, I believe that it could be made easyer for Daz buyers to get what is advertized with having to go through a bunch of hurdles. Or maybe someone could publish a "Reading Daz 3D publicity for dummies".
Just saying...

nonesuch00 said:

PerttiA said:

nonesuch00 said:

What agravates me is something like this situation:

2) Now, almost a year after purchase, the Genesis 8 Female Centaur shows up for no good reason this week as needing installed via DAZ Connect? Why? 

Because you are logging/signing in to DS, that is the trigger for DAZ Connect to go and check your purchases and notify you that you haven't installed them with DAZ Connect.

If you want your eye to stop hurting, stop poking it with your finger. 

No, I'm not poking it, poking here means to bag. It's DAZ 3D that's bagging those metadata and product files. The problem needs fixed by DAZ, not by me refusing to use DAZ Studio in way it was intended to be used.

The only reason to log in/sign in to DS, is to use DAZ Connect within DS to install content.
If you then notified that there is something you haven't installed with DAZ Connect, that is what it is supposed to do.

You need to choose your installation method and act accordingly, ie. if you use DAZ Central/DIM/Manual installation => Do not log in/Sign in to DS.

Don't forget that Daz Central can roll mutliple files into one entry, if it is failing as a high percentage like that it is probably installing the application correctly and having issues with one of the accompanying sets.

I get the same error when I try to upgrade DAZ Studio with DAZ Central. I installed the older Daz Install Manager and I find that works just fine.

Michaelrdavis said:

Yes, but I don't think those installers include upgrades, which I belive DAZCentral is supposed to do.

DAZ Studio is an amazing piece of software.

DAZCentral? Not so much.

Why do I have to seek wokarounds because DAZCentral feils to do what it exists for?

Which 'upgrades' are you talking about?

The manually downloadable files are always the latest ones released, DAZ Central doesn't install/update any newer versions.

Hi folks- after getting the same errors, I got it to work in Unreal v4.26.2 (cold re-install of Daz Central, Daz v16, and Unreal v4.26.2)- then installed plugin. Note, under settings in Daz Central, the path of the install for unreal may have to be switched). Using the install from Daz, not the download mentioned above. Windows 10 pro.

Tried same for other versions of Unreal- no dice. 

cheers!

I must be dyslexic. For far too long I had Daz Connect and Daz Central confused with each other, and thought that they were the same thing. I saw warnings against using Daz Connect and to stick with DIM, and thought that since I wasn't using Daz Central I was doing things right. Oops.

Now I need to uninstall all of that Daz Connect stuff. So many cloudy items! Is there a quick and easy way to do that?

Central is kind of DIM with training wheels; I kind of wish it didn't exist because people who are apt to use it need the flexibility of DIM.   I do want to mention that the metadata of Categories is one of the easiest things to back up so you don't ever have to loose your organization if you don't want to.

Thank you, that does answer my questions. I figured Central was meant to replace DIM (which I always used before), but I guess I should uninstall my content and put it back in with DIM (there's not a ton installed anyway, as I rebuilt my machine earlier this year).  I don't really mess with Categories though, not because they aren't useful, but I've lost all the organization I put into them twice over the years due to weird Studio updates, so I'm not wasting time doing it again.

Richard Haseltine said:

johndoe_36eb90b0 said:

Richard Haseltine said:

The change in Iray is deliberate, and will presumably remain, as the old behavior was not physically correct.

That's not really helpful.

Physically correct or not, the new Iray behavior breaks so many products, some of them (like ghost lights) central to everyone's workflow.

Majority of the broken products probably won't be updated by the original vendors because that would break them for users who haven't updated DAZ Studio (often because they can't due to older hardware no longer being supported).

That leaves end users, 99% of whom have no clue on how shaders work to try to fix it in all their scene files they accumulated over years.

The least NVIDIA could do if they won't provide some sort of legacy mode is to provide us with a detailed, step-by-step, instructions for DAZ Studio Iray implementation on how to get the same visual results we had before the change.

The change log does show that Daz is trying to mitigate the impact of the change. I agree that allowing some of these non-physical behaviours, at least as an option 9e.g. through the advanced node properties function) would be useful, but all Daz can do is make representations to nVidia.

But my point was that DAZ shouldn't be the one fixing this -- it should be NVIDIA, because they have broken your product with this change of their paid Iray SDK.

I assume that DAZ didn't have custom math on top of Iray that caused it to render light and transparency differently before, but instead used default implementation provided by NVIDIA Iray.

Now that implementation has changed, with a good reason I admit, but also with a blatant disregard for hundreds of thousands of 3D assets and scenes created with the previous Iray implementation in mind.

Unless DAZ workaround can also fix existing scenes and not just newly created ones it is worthless.

DAZ should really escalate this to Iray product manager Alexander Fuchs at NVIDIA, I doubt the Iray team is aware of how much damage they did to your ecosystem with this change.

Sorry for misunderstanding.
In the purchasing process, right after payment, you'll get the options to use a link to DAZ Central or to download via DIM. There is no link to Manual downloads as it used to be.
I'd just like to have that back.

After paying for your Product, you'll get the options using DAZ Central or DIM for downloading your items, but where is the link for manual downloads?
I can't find it.
Please bring it back, or make it easier to find. Thank you.

Where are links to download the versions?

All I ever find is DAZ Central which I have no intention of installing. Just want the actual insall .exe for DazStudio.

I did not see in my products list.

Thanks

johndoe_36eb90b0 said:

Richard Haseltine said:

The change in Iray is deliberate, and will presumably remain, as the old behavior was not physically correct.

That's not really helpful.

Physically correct or not, the new Iray behavior breaks so many products, some of them (like ghost lights) central to everyone's workflow.

Majority of the broken products probably won't be updated by the original vendors because that would break them for users who haven't updated DAZ Studio (often because they can't due to older hardware no longer being supported).

That leaves end users, 99% of whom have no clue on how shaders work to try to fix it in all their scene files they accumulated over years.

The least NVIDIA could do if they won't provide some sort of legacy mode is to provide us with a detailed, step-by-step, instructions for DAZ Studio Iray implementation on how to get the same visual results we had before the change.

...apparently UHT2 and Skin Builder are broken as well.  I looked to see if any render tone mapping, specular, or surfaces settings were off from what I have in 4.15.0.30 and none were. The only thing I can think of is it must have something to do with an error in the shader mixer regarding those two utilities, but that literally is a "can or worms" I'd rather not mess with.

There is no Mouth Open morph for G8.1, it is a G8 morph that comes available when the dummy files have been removed.

If you remoced the dummy files and didn't get the G8 mouth open morph dial, you have those dummy files installed in multiple places - Have you installed/updated Genesis 8 Starter Essentials also within DS? or how are you installing your content?

If you install/update content within DS (Using DAZ Connect), the files will be installed into ...\Data\Cloud\[Product identification\ and they will get priority over all the other installation methods [DIM/DAZ Central/Manual Installation]

daz to c4d was working perfect in the previous build. I updated the c4d bridge to daz central's current build and tried sending a model from daz into Octane and they all end up like this regardless of my settings. Any way to revert to an older build of the bridge to finish my projects? 

johndoe_36eb90b0 said:

Richard Haseltine said:

The change in Iray is deliberate, and will presumably remain, as the old behavior was not physically correct.

That's not really helpful.

Physically correct or not, the new Iray behavior breaks so many products, some of them (like ghost lights) central to everyone's workflow.

Majority of the broken products probably won't be updated by the original vendors because that would break them for users who haven't updated DAZ Studio (often because they can't due to older hardware no longer being supported).

That leaves end users, 99% of whom have no clue on how shaders work to try to fix it in all their scene files they accumulated over years.

The least NVIDIA could do if they won't provide some sort of legacy mode is to provide us with a detailed, step-by-step, instructions for DAZ Studio Iray implementation on how to get the same visual results we had before the change.

The change log does show that Daz is trying to mitigate the impact of the change. I agree that allowing some of these non-physical behaviours, at least as an option 9e.g. through the advanced node properties function) would be useful, but all Daz can do is make representations to nVidia.

Richard Haseltine said:

The change in Iray is deliberate, and will presumably remain, as the old behavior was not physically correct.

That's not really helpful.

Physically correct or not, the new Iray behavior breaks so many products, some of them (like ghost lights) central to everyone's workflow.

Majority of the broken products probably won't be updated by the original vendors because that would break them for users who haven't updated DAZ Studio (often because they can't due to older hardware no longer being supported).

That leaves end users, 99% of whom have no clue on how shaders work to try to fix it in all their scene files they accumulated over years.

The least NVIDIA could do if they won't provide some sort of legacy mode is to provide us with a detailed, step-by-step, instructions for DAZ Studio Iray implementation on how to get the same visual results we had before the change.

Nel frattempo "ha" uscita la versione 4.16.03, che sconosco interamente ma che l'eccellente Central mi ha fortemente spinto a installare.

Finora sembra andare bene, è cambiato lo splash screen (). Il tutto per la verità mi pare un filino più lento, ma il mio sistema è di per sé così "meditativo", che non ci faccio più molto caso.

Qualcuno sa dove trovare il changelog?