Daz Studio Pro BETA - version 4.9.3.166! Release Candidate 5 (*UPDATED*)

mjc1016

josephlemons69_4db0991b45 said:

mjc1016 said:

josephlemons69_4db0991b45 said:

Rodrak said:

We are getting closer... (from change log for version 4.9.3.151):

Update to NVIDIA Iray 2016.3 Release Candidate (278300.4305); addresses the AMD SSSE3 ILLEGAL_INSTRUCTION crash; enables support for OS X compute capabilities (still has a dependency on CUDA/driver)

Does this mean we are close to Release??

Nope...but maybe closer to another Beta release.  Going from past experience, it will be a couple of weeks, yet...

Is 4.9 the last release before 5.0?

The next release will be 4.9.3.something...after that who knows.

Widdershins Studio

I've not used the betas before - does this run side by side with the current release or does it overwrite it please ?

hphoenix

Widdershins Studio said:

I've not used the betas before - does this run side by side with the current release or does it overwrite it please ?

Side-by-side.  It's the only way to run an older release (like 4.8 or 4.7) and the current release (4.9) without overwriting.  Either the older one, or the current one, has to be a beta release.  Then you can have both on the same machine.

 

Widdershins Studio

Great thanks.

Eustace Scrubb

hphoenix said:

Widdershins Studio said:

I've not used the betas before - does this run side by side with the current release or does it overwrite it please ?

Side-by-side.  It's the only way to run an older release (like 4.8 or 4.7) and the current release (4.9) without overwriting.  Either the older one, or the current one, has to be a beta release.  Then you can have both on the same machine.

No it doesn't.  mjCasual (Jacques) has DS versions 1-4, including 4.9, running live.  I had DS 2 as well as 3 and 4 running on my machine (I couldn't run more than any two at a time) until recently, when I culled v.2 and some of the older versions of v.4.  Right now, I've got one DS3 (x86), and DS4 (x64) in versions 4.0, 4.5, 4.6, 4.7, 4.8, 4.9 and 4.9 PB (for Public Beta).  I've even got 32-bit versions of 4.7 and 4.9 on here.

mjc1016

Eustace Scrubb said:

hphoenix said:

Widdershins Studio said:

I've not used the betas before - does this run side by side with the current release or does it overwrite it please ?

Side-by-side.  It's the only way to run an older release (like 4.8 or 4.7) and the current release (4.9) without overwriting.  Either the older one, or the current one, has to be a beta release.  Then you can have both on the same machine.

No it doesn't.  mjCasual (Jacques) has DS versions 1-4, including 4.9, running live.  I had DS 2 as well as 3 and 4 running on my machine (I couldn't run more than any two at a time) until recently, when I culled v.2 and some of the older versions of v.4.  Right now, I've got one DS3 (x86), and DS4 (x64) in versions 4.0, 4.5, 4.6, 4.7, 4.8, 4.9 and 4.9 PB (for Public Beta).  I've even got 32-bit versions of 4.7 and 4.9 on here.

The full version difference (2-3, 3-4) have always been able to run together.   It's the 4, 4.5, 4.6, etc that can be problematic, as they will use the same folders for things like the temp file.  Also, 32/64 bit versions have different enough locations to allow them to work together.  And while you can actually get them to run, it isn't recommended because of this.  There are other problems that can crop up, too...

namffuak

mjc1016 said:

josephlemons69_4db0991b45 said:

mjc1016 said:

josephlemons69_4db0991b45 said:

Rodrak said:

We are getting closer... (from change log for version 4.9.3.151):

Update to NVIDIA Iray 2016.3 Release Candidate (278300.4305); addresses the AMD SSSE3 ILLEGAL_INSTRUCTION crash; enables support for OS X compute capabilities (still has a dependency on CUDA/driver)

Does this mean we are close to Release??

Nope...but maybe closer to another Beta release.  Going from past experience, it will be a couple of weeks, yet...

Is 4.9 the last release before 5.0?

The next release will be 4.9.3.something...after that who knows.

I expect 5.0.<whatever> to be fairly disruptive - among other things, I expect to see QT version 5 as the gui toolkit, and that in itself is a major disruptive upgrade, and then there will be whatever add-ons and changes DAZ marketing and software development decide to add in. I wouldn't be at all surprised to see a 4.10.<something> series before we get to 5.0.

josephlemons69_4db0991b45

namffuak said:

mjc1016 said:

josephlemons69_4db0991b45 said:

mjc1016 said:

josephlemons69_4db0991b45 said:

Rodrak said:

We are getting closer... (from change log for version 4.9.3.151):

Update to NVIDIA Iray 2016.3 Release Candidate (278300.4305); addresses the AMD SSSE3 ILLEGAL_INSTRUCTION crash; enables support for OS X compute capabilities (still has a dependency on CUDA/driver)

Does this mean we are close to Release??

Nope...but maybe closer to another Beta release.  Going from past experience, it will be a couple of weeks, yet...

Is 4.9 the last release before 5.0?

The next release will be 4.9.3.something...after that who knows.

I expect 5.0.<whatever> to be fairly disruptive - among other things, I expect to see QT version 5 as the gui toolkit, and that in itself is a major disruptive upgrade, and then there will be whatever add-ons and changes DAZ marketing and software development decide to add in. I wouldn't be at all surprised to see a 4.10.<something> series before we get to 5.0.

You mean 5 right lol, after 4 comes 5 not 4.10 lol 

namffuak

josephlemons69_4db0991b45 said:

We are getting closer... (from change log for version 4.9.3.151):

Update to NVIDIA Iray 2016.3 Release Candidate (278300.4305); addresses the AMD SSSE3 ILLEGAL_INSTRUCTION crash; enables support for OS X compute capabilities (still has a dependency on CUDA/driver)

Does this mean we are close to Release??

Nope...but maybe closer to another Beta release.  Going from past experience, it will be a couple of weeks, yet...

Is 4.9 the last release before 5.0?

The next release will be 4.9.3.something...after that who knows.

I expect 5.0.<whatever> to be fairly disruptive - among other things, I expect to see QT version 5 as the gui toolkit, and that in itself is a major disruptive upgrade, and then there will be whatever add-ons and changes DAZ marketing and software development decide to add in. I wouldn't be at all surprised to see a 4.10.<something> series before we get to 5.0.

You mean 5 right lol, after 4 comes 5 not 4.10 lol 

Nope. Major version 4, minor version 10, update x, change y.  Or 4.10.x.y; we could, theorectically, see a 4.20.x.y but that probably won't happen. In any case the numbers are a version tracking system numbering, with each level separated by periods.

TheKD

2016-12-09 05:35:03.724 WARNING: dzneuraymgr.cpp(307): Iray ERROR - module:category(IRAY:RENDER):   1.0   IRAY   rend error: Cannot render: found no usable devices.

Any clue what that might mean? I have my 960 checked in photoreal devices.

DoctorJellybean

TheKD said:

2016-12-09 05:35:03.724 WARNING: dzneuraymgr.cpp(307): Iray ERROR - module:category(IRAY:RENDER):   1.0   IRAY   rend error: Cannot render: found no usable devices.

Any clue what that might mean? I have my 960 checked in photoreal devices.

Which OS and if Windows do you have the latest NVIDIA drivers installed?

rbtwhiz

The Public Build of Daz Studio Pro 4.9.3.153 BETA (Release Candidate) is now available via Install Manager.

Notice that the title of this thread, as well as the contents of the first post has been updated. Be sure to read the first post again as its contents has changed.

Before continuing to dicuss any of the issues that you may have encountered with a 4.9.3.x build, please be sure that you are using this latest build (4.9.3.153) and that you have verified that the issue remains in this build.

-Rob

rbtwhiz

Has the NVIDIA Iray renderer been updated?

Yes, it has.

*Note: The entries below come directly from the NVIDIA Iray 2016.3 release notes. Some entries, such as the mention of Iray Realtime, etc, currently have no bearing on Daz Studio itself but are included for completeness.

---

Iray 2016.3, build 278300.4305

Added and Changed Features

• Iray Bridge
  • Rendering in batch scheduler mode now supports canvases with more than one layer. This is needed for single pass VR renderings.
  • Rendering in batch scheduler mode now heeds the camera sub-window settings. This makes it possible to render an image in multiple passes with different sub-windows..
• Iray Photoreal
  • Noise levels for most environment lighting setups have been improved.
• Iray Interactive
  • Support for all compute capabilities on MacOS has been added.
• Material Definition Language (MDL)
  • The behavior of IFunction call::create_variants() has been changed. Defaults not explicitly specified are no longer copied from the prototype and made explicit defaults of the variant, but will implicitly use the defaults of the prototype. If such a default of the prototype is later changed, the change also affects the variant. To maintain the previous behavior, pass explicit defaults when creating the variants, e.g., start with the defaults of the prototype or the arguments of the material instance/function call instead of with an empty expression list, and then change the defaults as desired.
  • The loading of pixel data from textures stored in MDL archives is now done lazily as with textures not stored in MDL archives.
  • The MDL compiler now properly checks the uniform/varying property of material parameter attachments and warns if an expression computing a varying value is attached to a uniform parameter.
  • Note that this is a real error, the rendering will not show what is expected. This warning might turn into an error in future versions of Iray.
  • The new methods get_prototype() on IFunction_definition and IMaterial_definition provide the name of the prototype for variants.
  • The new method IFunction definition::is_uniform() allows to tell apart uniform and varying functions.

Fixed Bugs

• ​General
  • The maximum line length supported for .ies files has been increased to 4096. Proper error handling for lines exceeding this limit has been added.
  • A bug has been fixed that occured when the connection to the license server was lost. Iray using FlexNet licensing crashed due to FlexNet’s internal behavior when losing the connection to the license server.
  • When rendering over Iray Bridge in batch scheduler mode under some circumstances the scene could stop acting on updates. In IView this could be triggered by rendering a scene in batch mode only until the end criteria for the scene was reached.
  • A bug in Iray Bridge has been fixed where cloud render contexts could have returned the wrong error code on video errors. Now -15 is returned.
• Iray Photoreal & Iray Interactive
  • Wrong intensity scaling of spectral color attachments has been fixed. It could occur in cases were the same expression was used multiple times in a material.
  • A potentially incorrect constant folding in cases of multiple color operations {=,-.*,/} with a total of one varying input has been fixed.
• Iray Photoreal
  • High bit depth texture interpolation has been fixed.
  • Materials that feature a perfect specular component and different front/backside materials (if CUDA is used) have been fixed.
  • Precision issues for some difficult instancing special cases have been fixed.
  • A regression has been fixed that caused Iray Photoreal to stop reporting convergence updates to the progress callback.
  • The orientation of the uv layout on classical light sources has been fixed.
  • A CPU vs. GPU rendering discrepancy with builtin noise functions in the case of non-finite uv input has been fixed.
  • Excessive noise when dynamically increasing light source intensity starting from zero has been fixed.
  • Irradiance buffer intensity artifacts when the caustic sampler is enabled have been fixed.
  • In contrast to the fake ground plane, matte objects with purely specular materials didn’t receive shadows. This has been fixed.
  • Support for SSE2-only capable CPUs has been fixed.
  • An occasional GPU failure when rendering with the caustic sampler enabled and emitting geometry has been fixed.
  • A crash with directional lights and otherwise empty scenes (if instancing was off) has been fixed.
• Iray Interactive
  • A bug has been fixed that caused undefined behavior when running out of GPU memory during a scene update.
  • Stripe-shaped artifacts when rendering with multiple hosts with irt cloud have been fixed.
  • A bug has been fixed that caused only a part of the IES light profile data to be used.
  • An incorrect implementation of df::spot edf (which never yielded a spot but only got bright with smaller spread) has been fixed.
• Material Definition Language (MDL)
  • The MDL exporter no longer generates strict-relative file paths for pre-MDL 1.3 modules.
  • A serious slowdown when parsing very long annotations has been fixed.
  • A rare crash if DB elements of type IFunction_call were overwritten by function calls with a different return type has been fixed.
  • A potential crash with many duplicate textures in displacement has been fixed.
  • The MDL compiler now checks that the MANIFEST of MDL archives is valid.
  • The generation of version numbers in the MANIFEST of MDL archives has been fixed.
  • The missing execution of the dependency check for MDL modules loaded from MDL archives has been fixed.
  • The retrieval of "export.* keys in the MANIFEST of MDL archives were not reported in all cases.
  • The MDL compiler has been fixed to accept dates without a note in MANIFEST values.
  • The parsing of comments in the MANIFEST of MDL archives has been fixed.
  • The parsing of UTF-8 characters inside the MANIFEST of MDL archives has been fixed.
  • The MDL compiler now checks the rules for character positions inside the MANIFEST of MDL archives.
  • The parsing of module exports inside the MANIFEST of MDL archives that was failing if the module name was shorter than 3 characters has been fixed.
  • A crash in Iray has been fixed that occurred if a MDL function containing a partial write to a struct or vector value like v.x = expr; was inlined into a compiled material.
  • An error is now also issued on Windows when an MDL archive should be created from a non-existing directory.
  • The file name reported by IModule::get_filename() has been fixed for MDL archives.
  • The error check on Windows when an MDL archive was to be created from a non-existing directory has been fixed.

kyoto kid

...so do all the "Added and Changed Features" affect the version of the engine embedded in Daz Studio?

I don't remember any "batch" process.

nicstt

josephlemons69_4db0991b45 said:

mjc1016 said:

josephlemons69_4db0991b45 said:

Rodrak said:

We are getting closer... (from change log for version 4.9.3.151):

Update to NVIDIA Iray 2016.3 Release Candidate (278300.4305); addresses the AMD SSSE3 ILLEGAL_INSTRUCTION crash; enables support for OS X compute capabilities (still has a dependency on CUDA/driver)

Does this mean we are close to Release??

Nope...but maybe closer to another Beta release.  Going from past experience, it will be a couple of weeks, yet...

Is 4.9 the last release before 5.0?

no idea, after 4.9 comes 4.10.

5 will happen when there is a change to the DSK iirc, from what was posted.

Software updates follow specific rules, or should do.4 to 5 would indicate a ground-breaking or major change in some way.

Leana

josephlemons69_4db0991b45 said:

namffuak said:

mjc1016 said:

josephlemons69_4db0991b45 said:

mjc1016 said:

josephlemons69_4db0991b45 said:

Rodrak said:

We are getting closer... (from change log for version 4.9.3.151):

Update to NVIDIA Iray 2016.3 Release Candidate (278300.4305); addresses the AMD SSSE3 ILLEGAL_INSTRUCTION crash; enables support for OS X compute capabilities (still has a dependency on CUDA/driver)

Does this mean we are close to Release??

Nope...but maybe closer to another Beta release.  Going from past experience, it will be a couple of weeks, yet...

Is 4.9 the last release before 5.0?

The next release will be 4.9.3.something...after that who knows.

I expect 5.0.<whatever> to be fairly disruptive - among other things, I expect to see QT version 5 as the gui toolkit, and that in itself is a major disruptive upgrade, and then there will be whatever add-ons and changes DAZ marketing and software development decide to add in. I wouldn't be at all surprised to see a 4.10.<something> series before we get to 5.0.

You mean 5 right lol, after 4 comes 5 not 4.10 lol 

Version numbers are not decimal numbers, you can totally have a 4.10.

Chohole

Leana said:

josephlemons69_4db0991b45 said:

namffuak said:

mjc1016 said:

josephlemons69_4db0991b45 said:

mjc1016 said:

josephlemons69_4db0991b45 said:

Rodrak said:

We are getting closer... (from change log for version 4.9.3.151):

Update to NVIDIA Iray 2016.3 Release Candidate (278300.4305); addresses the AMD SSSE3 ILLEGAL_INSTRUCTION crash; enables support for OS X compute capabilities (still has a dependency on CUDA/driver)

Does this mean we are close to Release??

Nope...but maybe closer to another Beta release.  Going from past experience, it will be a couple of weeks, yet...

Is 4.9 the last release before 5.0?

The next release will be 4.9.3.something...after that who knows.

I expect 5.0.<whatever> to be fairly disruptive - among other things, I expect to see QT version 5 as the gui toolkit, and that in itself is a major disruptive upgrade, and then there will be whatever add-ons and changes DAZ marketing and software development decide to add in. I wouldn't be at all surprised to see a 4.10.<something> series before we get to 5.0.

You mean 5 right lol, after 4 comes 5 not 4.10 lol 

Version numbers are not decimal numbers, you can totally have a 4.10.

yes,  I seem to remember having Windoze 3.11 on a PC at one time

Richard Haseltine

Chohole said:

Leana said:

josephlemons69_4db0991b45 said:

namffuak said:

mjc1016 said:

josephlemons69_4db0991b45 said:

mjc1016 said:

josephlemons69_4db0991b45 said:

Rodrak said:

We are getting closer... (from change log for version 4.9.3.151):

Update to NVIDIA Iray 2016.3 Release Candidate (278300.4305); addresses the AMD SSSE3 ILLEGAL_INSTRUCTION crash; enables support for OS X compute capabilities (still has a dependency on CUDA/driver)

Does this mean we are close to Release??

Nope...but maybe closer to another Beta release.  Going from past experience, it will be a couple of weeks, yet...

Is 4.9 the last release before 5.0?

The next release will be 4.9.3.something...after that who knows.

I expect 5.0.<whatever> to be fairly disruptive - among other things, I expect to see QT version 5 as the gui toolkit, and that in itself is a major disruptive upgrade, and then there will be whatever add-ons and changes DAZ marketing and software development decide to add in. I wouldn't be at all surprised to see a 4.10.<something> series before we get to 5.0.

You mean 5 right lol, after 4 comes 5 not 4.10 lol 

Version numbers are not decimal numbers, you can totally have a 4.10.

yes,  I seem to remember having Windoze 3.11 on a PC at one time

Which was also labelled 3.1.1 as I recall.

TheKD

Figures, day after I install beta, new beta released and have to install again lol.

mjc1016

TheKD said:

Figures, day after I install beta, new beta released and have to install again lol.

That shouldn't be too bad...try a few hours.  One of the late DS3 or early DS4 betas, literally, no more than an hour passed between my installing and the next one coming out.

TheKD

That happened to me with a game recently, a bit larger of an update download, I was not a happy camper lol. At least downloading and installing beta takes like 10 minutes. Updating my nvidia drivers took a while, wouldn't install, needed to google around and found a tool to uninstall, then I could install. Hopefully this new driver doesn't mess anything up lol.

On topic, what is the spectral rendering setting supposed to do? Is it one of those only use in a specific type render like caustics? Not seeing much of a difference, slight saturation difference maybe.
 

mjc1016

TheKD said:

On topic, what is the spectral rendering setting supposed to do? Is it one of those only use in a specific type render like caustics? Not seeing much of a difference, slight saturation difference maybe.
 

Not sure...I haven't been able to play with the beta, as I have an AMD CPU that is affected by the bug in the last beta and I'm in the middle of stuff, so I can't download this latest release, yet.

TheKD

So spectral render setting is top secret then I guess? Lol.

 

Ok here is another one. In the beta, I cannot see the shot frame in the viewport, until I change the render size a few times, then it works like normally.

almahiedra

Leana said:

josephlemons69_4db0991b45 said:

namffuak said:

mjc1016 said:

josephlemons69_4db0991b45 said:

mjc1016 said:

josephlemons69_4db0991b45 said:

Rodrak said:

We are getting closer... (from change log for version 4.9.3.151):

Update to NVIDIA Iray 2016.3 Release Candidate (278300.4305); addresses the AMD SSSE3 ILLEGAL_INSTRUCTION crash; enables support for OS X compute capabilities (still has a dependency on CUDA/driver)

Does this mean we are close to Release??

Nope...but maybe closer to another Beta release.  Going from past experience, it will be a couple of weeks, yet...

Is 4.9 the last release before 5.0?

The next release will be 4.9.3.something...after that who knows.

I expect 5.0.<whatever> to be fairly disruptive - among other things, I expect to see QT version 5 as the gui toolkit, and that in itself is a major disruptive upgrade, and then there will be whatever add-ons and changes DAZ marketing and software development decide to add in. I wouldn't be at all surprised to see a 4.10.<something> series before we get to 5.0.

You mean 5 right lol, after 4 comes 5 not 4.10 lol 

Version numbers are not decimal numbers, you can totally have a 4.10.

Exactly. You can even see something like 4.999999 and all the nines that DAZ would want. Dot is not the decimal dot. It is like chapter 4 section 9 subsection 3, then you can to have nine hundred ninety nine thousand nine hundred ninety nine sections in the chapter four without any problem.

SpottedKitty

namffuak said:

I expect 5.0.<whatever> to be fairly disruptive - among other things, I expect to see QT version 5 as the gui toolkit, and that in itself is a major disruptive upgrade,

Argleblargle. Don't remind me — there are still changes to the GUI between D|S3 and D|S4.0 that I've never really got used to and I'll never really like. And I never understood the oft-repeated explanation of "the new Qt version in 4.0 doesn't let us do that any more".

mjc1016

SpottedKitty said:

And I never understood the oft-repeated explanation of "the new Qt version in 4.0 doesn't let us do that any more".

Don't worry, it will be just like that for 5...because Qt 5 makes a bunch of things that were in Qt4 very obsolete...but it does bring some fun new features...like support for modern displays/resolutions, so the various problems like text not resizing correctly and pop up windows being off screen will be reduced/eliminated.

FusionLA

I just installed the new beta using a Mac.

Under Render mode, I no longer can select Interactive, Photoreal is the only option to choose.

I do see the new Spectral Spectral Rendering option.

Glad to see that the wierd displacment issue was fixed, close up render from last beta was giving me some strange outlines around the lips of some characters.

3anson

mjc1016 said:

TheKD said:

On topic, what is the spectral rendering setting supposed to do? Is it one of those only use in a specific type render like caustics? Not seeing much of a difference, slight saturation difference maybe.
 

Not sure...I haven't been able to play with the beta, as I have an AMD CPU that is affected by the bug in the last beta and I'm in the middle of stuff, so I can't download this latest release, yet.

 

 

 

i had the same issues with both previous beta versions ( my CPU is a Athlon 2 quad ) just installed this new version, and the bug seems fixed. rendered fine  :))

almahiedra

mjc1016 said:

SpottedKitty said:

And I never understood the oft-repeated explanation of "the new Qt version in 4.0 doesn't let us do that any more".

Don't worry, it will be just like that for 5...because Qt 5 makes a bunch of things that were in Qt4 very obsolete...but it does bring some fun new features...like support for modern displays/resolutions, so the various problems like text not resizing correctly and pop up windows being off screen will be reduced/eliminated.

QT 5!!!!  ay!! ay!! very god/bad news...my dear plugings!   

Then,   Near Future == DS5/Genesis 4?

Is there any thread about QT5 here in the forum?

Zilvergrafix

TheKD said:

On topic, what is the spectral rendering setting supposed to do? Is it one of those only use in a specific type render like caustics? Not seeing much of a difference, slight saturation difference maybe.
 

https://en.wikipedia.org/wiki/Spectral_rendering