Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
I think this update may have solved my longstanding "NVIDIA Error Type 3 subtype 2" oh no crashproblem on my Quadro 5000 24 gig vram(notebook) and 6000's 32 gig vram(desktop)on simulating longer animations... let's see. Here's hoping.
I will be politely vocal about anything I find to the contrary here, since I see this is where the devs can see "mundane" user's input. (not snark, just can't find better words)
Mundanes. Or Muggles. What these programmers do sure feels like magic to me…
I did it as soon as possible tho.
But i'm also tired of that crap. Time to move lol.
Hi, I'm having a problem with some assets in this last Daz version.
For example: if I load a Genesis 1 figure and I also add a hair to it then it works fine... until I use some morphs like "neck lenght". If I increase the neck length to the maximum (1) the hair is distorted and it looks like in the image attached.
However, doing exactly the same in the previus version produce the expected result: a genesis figure with a long neck and not affected hair (see the other picture attached).
This is a base case of a generic group of issues I'm having with this version when loading my scenes, there are distortions in some elements when they shouldn't.
Is this a known issue? Where should I report it?
Thanks
Submit a help request
I've been getting the follow on and off (at least once or twice a week) where I'll go to render the render will start to prep to render and then I get an error pop up that says "there was an error during rendering". This started up two beta's ago. I was annoyed to get it this morning and see that it hasn't been fixed :/
The log file shows me the following:
2020-10-18 08:34:21.670 Rendering image
2020-10-18 08:34:29.734 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [WARNING] - API:DATABASE :: 1.0 API db warn : Transaction is released without being committed or aborted. Automatically aborting.
I then go to try and render again and I get an error message of "Unable to Render. Renderer is already in use"
Checking the log file after that error shows no new additional messages. I can quit Daz and reload it, but if I use both Iray Preview and then go to render, I'll get the same error message. I find the only way to completely alleviate this is to do a reboot. But then again it's only going to be another 2 or 3 days before this error pops up again.
I'm pretty sure it's not a vram issue, as I have a Titan RTX.
Driver version? I've not (yet) run into this issue with a 2080Ti, so I'd suspect there is some other compounding factor. Whata re your system specs, and what security software are you using?
Driver version is 451.67, but this has existed since the summer and I've updated drivers 3 times to newer ones as they've become available in the hopes that it fixes this. Directx is version 11
Security software is the base Windows Defender, OS is Win7 64bit Pro, 64gb of memory, i7-7700K processor.
What happened to the environment/Tone setting in the Render settings? I know they're not disabled due to the setting being baked into my scene files, but is this a permanent thing or are you guys working on improving them? Thanks in advance for any info on this.
Never mind, I found out that you have to create it and/or it's in the scene tab as a "prop..." which is curious as it doesn't seem to add anything to Daz Studio, except changing around interface items yet again for the sake of changing around the interface items...
It's already fixed. Update your beta.
Newest beta makes my pc lag just moving the mouse inside the viewport makes daz use 100GPU on my 2070s
What video driver is installed?
456.71 and windows 10
It would be nice if in the DAZ Studio we had an dockable/undockable subwindow Gizmo on the bottom left hand side of the Viewport that showed the current 'Interface' settings and allowed us to change them on that dockport gizmo correctly. It's sort of important for those of us that want to use Filament in the viewport or use iRay Preview in the Viewport.
I don't think it would be that tough to add to the code.
- I will make a feature request in CS - #349947
Is there something that you want that this dropdown doesn't do?
My system keeps freezing up when switching between panes in the animation timeline - using the new Beta - used Task Manager to fix. Had to uninstall and reboot to remove the problem.
Still having sporadic freeze issues running older versions of Studio - even though the Beta is uninstalled. Never had these problems before??
I wonder if some common files may have been updated - and not reverted with a uninstall?
Or - could just be me!
I know, check my edit, (You quoted my original unedited post) thanks for the info though.
Not exactly , it is easy to calibrate your Filament PBR to match Iray , you just don't touch Iray Enviorment settings of your scene to do that , there of course will be difference since Filament PBR is not rendering reflections from other objects or Global illumination from other objects but only IBL lighting , for that reason is is a draw mode and very useful for setting up a scene or shader , just give it a time and play with the Filament Option node as that all you have to do.
Below some examples I did inearly releases of the beta , it is a accurate as in other programs I use, remember PBR is based on reflections , so some shaders may not looks exactly the way it should with it, especially if parameters are mixed
Mine came after installing the latest beta and is now in the none beta also now and no clue what happend
Yes, that dropdown is not what I'm talking about. I want a 'redundant' Preferences openGL HW Inferface as a headsup in the bottom lefthand corner embellished also with system RAM and GPU RAM usage where I can change the openGL settings and see RAM usage. It's sort of 'game enginey' I know but it's very convenient configuration wise to be able to change at your fingertips in a very convenient location and exposes RAM usage changes as you change the openGL HW Interface settings, add or change or delete various diffuse, normal, bump, displacement and other images on the surfaces of various models in the scene or add or delete models from the scene.
Also it would be a debugging aid to customers and DAZ CS troubleshooting RAM usage crash dumps which do tend to be out of RAM situations in most cases.
My first observation on Filament draw mode: It's a very fast way to determine what materials are still using 3DL, as they don't show up correctly in this draw mode. Alternately, if you're trying to convert anything to 3DL materials for a 3Delight scene, Objects showing up nicely will show what you have left to change over to 3DL.
It's also a super fast draw mode. After about 10 minutes of tinkering, my impression is favorable.
...thank you.
Crikey, I'm five updates behind, still on 4.12.0.47. However, I had coruption issues with the IM for nearly a year, that forced me to do manual downloads, which were finally cleared up with the latest IM update so until recently I had no access to Beta downloads.
This also has me a bit concerned as I have two Maxwell GPUs (750 Ti and Titan -X) running on CUDA version 7.0 and the last applicable Driver version is 430.86.
Did you update your GPU drivers when installing the Beta?...
Display drivers are just like any other software, the latest is not always the best and there is no garantie against new problems
No i did not i just updated the beta the driver that i have is from the 7 month its the latest.
I updated daz beta that is all i did i have not touched my system at all.
https://www.daz3d.com/forums/discussion/comment/6105227/#Comment_6105227
Minimum driver requirement (to properly support both CUDA 11 and OptiX 7.1) is 451.48 on Windows.
In 4.12.2.54, Filament PBR still showing magnified bump maps (they look like they are loaded in low resolution and then upscaled at least 4 times, looks awful on skin, most visible on torso).
Seems like your not allowed to write anything in this snow
Dont you understand i run the latest driver i run 456.71 that is the latest driver
Oh by the way, 456.71 Studio Driver is out:
How do you expect us to understand when you wrote "the driver that i have is from the 7 month its the latest."
Month #7 is July.
What is your problem with beta anyway? Did you check if there is an update for Octane perhaps? Maybe it can't work unless updated to match the new beta.