Universal Tool Causes Lags on viewport?
Hi everyone, today I'm having a problem with my application, but I can't found out what cause it.
So, when I use universal tools on my viewport (or any tools that uses XYZ axis), I will end up lagging on my vieport, everthing lags very bad, I almost can't move around the scene, even when it's empty
But when I use Scene navigator, or Node Selector Tool, it didn't lags at all and I easily move around as I like, even doing translate and transforms.
I didn't change anything on the setting, I just opened it this morning and it's just stuck like that, and I never experienced something like this before
So, did anyone know what happened? I tried digging through forum and I can't came up with anything :(
Thank you so much in advance
Comments
I'm having the same issue, any help would be appreciated!
This is odd, mine works fine. same speed regardless of universal or node selection tool. What version of studio are you both using?
Do you have items loaded which have a Smoothing Modifier applied? If an item does there will be a Mesh Smoothing group in the Parameters pane when you select the figure.
I'm using 4.8 (still hearing horror stories of losing years worth of Categories being lost, AND nervous about privacy issues discussed on these forums, having been victim of ID theft, so still nervous about upgrading). Yes, I have smoothing modifiers running, but I know what they look like (there's a % bar at the bottom that runs when that process runs...this delay is NOT that process). I've also heard the whole "Aux Viewport set to Iray" thing, and again, this delay is NOT that.
BTW, thank you both for replying!
No, igustingurahrayibhimantara has described it the best so far. I click on anything in the regular viewport using any tool with an XYZ axis, then I wait for the computer to "catch up" with the process I started with the mouseclick (anywhere between 5 and 15 seconds, depending on how much content is loaded into that scene, no % completed bar showing progress, just.......lag). Any clicks that happen outside of the viewport are not affected, but going back between different tabs where one click involves the viewport ALWAYS produces the lag igustingurahrayibhimantara and I have described.
Any insight/help would be greatly appreciated!
For me, the biggest slowdown the viewport is caused by having the geometries set to High rather than Base. The reaction time of the program improves (but not to 100%) by turning off High Resolution for each object, as well as any smoothing modifier/collision higher than normal. The posing resolution also has an effect, but just having the mesh set to High Resolution seems to account for a certain percentage of the slowdown. For me, the lag can be half a second or so, which is still an eternity when you trying to tweak.
While a few people had issues, most didn't - and the 4.9 database tables are separate from the 4.8 tables anyway. If you have custom categories you should, in any event, be making backups by exporting user data from the Content DB Maintenance dialogue launched from the Content Library option menu.
I'm not sure what you mean here - DS stores no personal data, other than any name or other autorship details you enter (which need not be real) and won't communicate over the internet with anything unless you tell it to (though if you don't let it connect once you will get a dialogue on each launch asking you to authenticate).
Thanks for the reply! Yes, I'm making regular backups of my user data. If I understand correctly, I copy those backups into my Runtime/Support folder, then run Import Metadata, making sure to check the User Data files at the top of the list. This should bring all my Categories into the new Daz Studio menu, although there are instances documented in these forums where that process didn't work. I've rebuilt Categories twice in my life, and don't intend to do it again. I wish Daz Studio would include a function in its manual installation to migrate those category settings automatically...
I'll look at the Geometry/Smoothing settings as well. I know in some scenes I have used higher settings than others, but again, I'm pretty sure I've seen the difference between a Geometry lag and the one described in this thread.
As for my comments about privacy, they revolved mainly around Daz Connect in 4.9. "Privacy" might not have been the best word choice, but hard experience has taught me to be suspicious of what/who has access to my computer...
I'm still hopeful I hear back from a few Daz techies I've reached out to, maybe they know how to fix this. Again, thanks for the comments!
In general you shouldn't need to do anything - having a back up is insurance against the odd case where you do. If you are still using Valentina as the database engine you will need to run the Convert Valentina to PostgreSQL utility (which makes a PostgreSQL format copy of the Valentina database), but as long as you are using PostgreSQL already the process is usually transparent.
Connect isn't mandatory (except for encrypted content, and you couldn't use that in 4.8 at all so moving to 4.9 and not using Connect won't affect your options).
I don't use 4.9.x.166 release, only the beta, and I can verify that except for the nag alert that appears at startup if it can't connect to the CMS, Studio does not try to rearrange content when it shouldn't, which would be very bad for me because I have very carefully crafted some 30+ runtimes with content based on both function and project. I have no idea what would happen if use Connect, but as I don't use any encrypted content anyway, I just leave the CMS not running.
However, tcnkk_e2d2dc4e8b is using the CMS - that's what the categorisation is. The CMS is needed by Connect, but they are not the same thing and the reverse is not true.
OK, how do I tell which database engine I'm using?
Never mind, I found it...just needed to read a little further down the FAQ..."Connected to CMS: PostgreSQL 9.3.4, compiled by Visual C++ build 1600, 64-bit"
igustingurahrayibhimantara, I may have some answers via help from Daz tech support. Take a look at your drivers, specifically ones associated with Intel Rapid Storage Technology and the BIOS firmware for your computer. I ended up updating both of these on my Dell laptop, and it seems to have solved my lag time issues with the universal tool...hope this helps.
Oh my I'm really sorry, I didn't check back to forum for quite a bit, I ended up adapting to using "Node Selection" tool and just using manual translate. I use 4.9 Version
Thank you, I did try to use lower res, and my item doesn't have smooting modifier, so it didn't work
Thanks for keeping an eye on the problem, I think mine is not the driver, since a while back it did fixed itself (not lagging anymore), but a while ago it lagged again. The issue came up whenever I restarted, or at random times. I'll try to find any driver that might not be updated yet, and maybe ask tech support on this issue.
Thanks again :3
Also, thank you everyone for helping with the Issue
I am having the exact problem as the first post. This is with ver 4.9.4.117.
Here's further description of the problem:
1) Start up DAZ
2) With nothing loaded, select universal tool or any tool that uses xyz axis
3) Move mouse anywhere except viewport and there is no lag.
4) Move mouse anywhere in viewport, 5 or more seconds lag starts. The lag is anywhere in the DAZ window, not just the viewport, but move it out of DAZ and there is no lag.
5) Once lag is over, I can repeat step 4 again.
No problems with scene navigator and node selection tool.
tbh I'm still having this problem, and you just describe it more clearly, so thank you :)
I'm still looking for a way to fix it too tbh, any solution posted above did pretty much nothing. Though sometimes my lags gone after a random amout of restart or standby.
Hi, I am facing the same problem than described here, and it is not the firs time!
The Universal Tool is the switch that enables or not such lags, but only if you experience this issue.
I recently resolved this issue by pressing the power-off button on boot-time just before Windows 10 fully loaded, until the PC switched off.
The result is a much longer boot-time the first time after such a dangerous operation, but it solved this issue during many months, until some MS updates!
Please, do try to solve this issue: Daz Studio is useless when this happens!
Sorry for my poor English.
This time, this trick did not worked.
However, I have exactly the same lags in Photoshop 11.0.1.
I never noticed the correlation before today...
And it is not a memory problem, my PC 32 gb are mostly empty...
I think it have something to do with the registry or some sort, since for me I kinda know when it happen and also how it will happen :/
I think I found a solution for this issue. There were absent drivers for PCI controller Simple Communications after I installed Windows 10. For some reason Windows can't install it automatically. I used guide from Youtube to fix that. A problem with an Universal tool in DAZ also gone.