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 log is not up to date then, as DS2026 has been in beta for quite some time.
edit: there's no title with "beta" in the log page, but the switch to beta is actually recorded in section about build 6.25.2026.2920
The first screenshot shows a pointlight? Press Ctrl and L (or Window - Preview Lights)
i switched the preview lights with no luck
i reloaded the scene with the figure only with the same issue
Still acting like Alpha
I get far more common crashes on random general viewport work with DS6 than DS4.24, just like the public alpha previously
So no improvement in the user experience for me, therefore no chance of using it as my regular tool.
Most of the scripts probably don't work. But in theory you should be able to just copy it from the one folder to the other as long as you haven't done anything else. Problem is you probably shouldnt't over write the menu or toolbar files that puts the customactions into the layout.
ouch !. i do not test ds5 preview. no script compatibility is a problem !
Ah, thank you. That is very helpful. I can see why people might point to that. If it fixes it, I will be happy. But I don't think it will.
Relying on a brand new OS feature to make something that used to work, work again, isn't really the right answer. I do not think any professional software engineer would believe that is a good answer, and neither do I think Daz is offering that as a solution. It's not how I read it anyway. I hope they are saying it's something might help people while they sort it out properly.
I say this partly because my 3090 did not need a low latency profile to move the iRay viewport smoothly, even with reasonably complex scenes. Also partly because my 5090 which has problems running DS6 does not need a low latency proifile to edit 4K HDR H.265 video, something it can do slightly faster than the 3090 can.
But the main reason I say it is that the low latency profile appears to work by allowing the CPU to run at a higher clock speed under some circumstances, so my immediate question was whether this is CPU-bound. No, not in my case. Not a single core is maxed out, they. They max out when I let go of the mouse and it catches up, but that is because it's rendering. It is the same story with the GPU. It doesn't start working until the viewport catches up. So basically, it's not doiing much, and that is why there is lag. I cannot see why making the CPU run more quickly is going to help if Daz isn't asking the CPU do do enough to max it out, and the KB doesn't even mention the GPU.
BUT, as I said, I will be very pleased if it does work, and these things are complicated. Maybe it will work and I don't care about being wrong it it makes Daz work again!
And I should also say some positives. I am really impressed with how quickly things load compared to before. It's a massive step torwards IMO. Once the teething troubles are ironed out, I'm really looking forward to getting back into things.
A positive I haven't seen mentioned (maybe I missed it) is the new "Adaptive Displacement" setting on Iray Uber. This generates polygons to support displacement and it's going to incredibly enhance the use of that moving forward.
A negative I must reiterate is these viewport problems. I'm highly dubious that a Windows update will resolve this. Microsoft is an easy scapegoat but maybe fix problems like these BEFORE launching your product?
So, now DS works with RTX5090? How about dual RTX5090?
Is it still the case that the speed doubles with two GPUs but the video memory remains that of the single card?
Viewport Lag?!?
Are you kidding me? That's the single biggest concern I have had with ALL PREVIOUS versions! So, what else is new? I had really hoped the abominable slowness of the Viewport might finally be addressed... I guess not, :(
I was actually hoping for some direct implementation of Nvidia Omniverse, to maybe get DAZ closer speed-wise to what I can see in Character Creator.
So you installed through DIM and it isn't showing an uninstal option? Is it showing anything (that seems a very short list in the screenshot)? If it really isn't showing anything after trying to uninstall then you can simply delete the application folder (which will remove the plug-ins too, if you had installed them) though that is rather drastic and definitely a last resort.
Funnily enough, I can't use Daz 6 for anything currently cause now I have to wait for the octane render plugin to be updated for this version. Maybe by the time that's done other plugins will be updated as well. I also really like the new texture shaded viewport. It is a bit choppy for me but nothing too bad. I suspect it will probably continue to be worked on.
What are your settings in Render Settings>Hardware? Have you tried a really simple scene, like a primitive?
I thought perhaps that, but it is not listed in the installed area, though it is listed under Advanced Settings -> Applications.
The package in DIM is an update, so you should probably install it (you might back up the current zip first if you are concerned - you could then reinstall that version by replacing the new zip wiith the old in the DIM Downloads folder, then running DIM Offline to install).
Even then, that would be the Windows XP path - I think it was WIndows 7 that switched to /Users/Documents/ - and XP is not supported. But I think the question was what files/folders were being placed there?
Focus seems to matter mor than it did in DS 4, but that isn't wholly a bad thing as it stops unwanted aplication of key-presses (e.g. people hated that using a key to jump to the first item starting with that letter in a content pane also triggered a Viewport move if Keyboard Navigaction was on)
It's closer to what you see in Blender, and I really like being able to toggle different textures by type. Gonna take some getting used to but the pros far outweigh the cons. Looking forward to enjoying it when Daz sorts out these viewport issues.
Whether or not scripts are compatible will vary - it is plug-ins that definitely won't be without a new version.
I'm not sure anyone has tried, and I believe the new cards have chnaged the way that they communicate (no need for an nVlink widget) so depending on your system pooling memory for materials may be possible.
It's wholly bad as far as I can tell. Shortcuts must work no matter what pane is active. If there's a special case, like the cursor is in some text field that people can type in, then Daz Studio needs to treat that as a special case and disable keyboard shortcuts then and there. Anything else is backwards.
Case in point, my Camera Manager plugin uses number keys to change to cameras quickly. If the plugin is in focus, or a viewport or the Content Library, it works fine.If the scene or parameters pane are active, it doesn't. There's no world where that is acceptable.
So when you edit a parameter you want the camera to switch 3 times when you type 1 5 0?
Could swear I just mentioned that shortcuts need to be disabled when people are typing into textboxes? Which by the way works just fine in DS4. I never had an accidental camera change when typing stuff
I had the same issue initially. Check the Geneal render settings in DAZ 6 and turn off Auto Headlamp.
The only issue that I have had so far is that I can't get Riversoft Arts Turbo Loader Manager for G9 to work in DAZ 6.
Also, a minor issue ...I don't really see the point of the Colour Node option in the Scene tab. Is there a way to remove that?
I'm not going to read five pages of comments to find out if anyone else has this issue (I'm sorry, just don't have the time right now). But I just installed Daz Studio 6 and Iray Preview doesn't work at all. The character stays gray (it has textures and you can see the textures in other previews like texture shaded and Filament), it's a Genesis 9 character. Iray preview doesn't work at all. I have a 5070 Ti if that helps. It also doesn't load the Environment and Tone mapping nodes when I switch to Iray preview (other versions of Daz Studio have always loaded those automatically as soon as I switch to Iray Preview. Is anyone else experiencing this issue?
EDIT: I found the issue. I had the Strand-Based Hair Editor Tool selected /doh! Apparently, if you have that selected, then Iray Preview is disabled. Once I switched back to the Universal Tool Iray Preview works again.