


If you grab a finger and move it, sometimes it behaves similarly but on top of it the finger snaps into a different pose first before accepting your posing. A couple seconds later the hand finally moved. For example you have the universal tool activated, grab a hand, click and move but nothing happens. So maybe some sort of memory leak? I can't reliably reproduce that behavior, it just either happens or it doesn't.Īdditionally to that quite often posing also bugs out a bit. Opening that made Studio freeze for 10 minutes (which is somewhat understandable) but after that it was in that forementioned sluggish state until I closed it and reopened it together with the scene. For example just a couple minutes ago the big scene (which makes Studio use about 12GB or RAM) worked fine until I opened the Property Hierarchy panel. For example the highlighting while hovering over parts lags behind the mouse one or two seconds if things get really bad. Something else: How does Studio run for you guys with quite heavy scenes? Since upgrading to Wine 7.2 (and my new system overall) I've noticed that Studio is running fine until something happens and suddenly everything is getting really sluggish, especially the viewport. yeah, as of now you seem to need my nvidia-libs package to get that working This function needs to be called for nvcuda to work with CUDA 11.4, and is NOT included in upstream staging/lutris versions of wine.

Ill do some digging and see if that it actually IS the case tho.ĮDIT: Just looked at my logs from DAZ 4.20 - 010c:trace:nvcuda:Unknown7_func0_relay (11040, 0圆22ddca9, 0x101ef78) Just saying if you use lutris version of wine + nvoptix and still experience problems, you could give the nvidia-libs package a try for the tweaked nvcuda version. Staging fails running most these samples, but it does ofc not automagically mean it will not work with DAZ. The nvidia-libs package i have put together have some cuda tweaks yet to be upstream, and actually works with most of the CUDA SDK 11.4 stuff. If that is really the case, the staging (or lutris) implementation of this may fail. Well, i spotted this line in the Daz 4.20 logs: Iray - IRAY:RENDER :: 1.1 IRAY rend info : Your NVIDIA driver supports CUDA version up to 11.6 iray requires CUDA version 11.4 all is good.
