It might actually be fixed, but remeber that studio has no been updated since December. That's six months.
That seems to be true for some other problems. I recently downloaded the latest Hexagon which still has problems with the DAZ Studio - Hexagon Bridge. It turns out that at least one fo those problems is fixed in DS 4.11 which has not yet been released. However, a search for the term "mouse" revealed nothing:
It might actually be fixed, but remeber that studio has no been updated since December. That's six months.
That seems to be true for some other problems. I recently downloaded the latest Hexagon which still has problems with the DAZ Studio - Hexagon Bridge. It turns out that at least one fo those problems is fixed in DS 4.11 which has not yet been released. However, a search for the term "mouse" revealed nothing:
It might actually be fixed, but remeber that studio has no been updated since December. That's six months.
That seems to be true for some other problems. I recently downloaded the latest Hexagon which still has problems with the DAZ Studio - Hexagon Bridge. It turns out that at least one fo those problems is fixed in DS 4.11 which has not yet been released. However, a search for the term "mouse" revealed nothing:
The reason I searched for "mouse" was because, according to the investigation done by AlienRenders, it is clearly a mouse handling problem. Searching for "jump", as you say, tells us nothing about this issue.
Since my last post in this thread, I have changed my mouse (to one having a supposed better sensor) and the viewport problem is still there. I use other software suites as well, but ONLY in Daz do I face this problem.
Just to reitterate:
Was using Win 7 up till Jan 2018 - no issues.
Changed to Win 10 during Jan 2018 - everything goes to hell in a handbasket.
Others' mileage may vary.
What I really don't like is how such a persistent issue, which I bet affects more people than who have voiced their concerns here, is left to exist for months without getting patched out. Things break in any program, sometimes with no fault of the program's developers since Microsoft or Apple throws down some patch from their end and ruins the show for everyone. But I expect Daz's team to sort out their priorities and resources to focus more on fixing what is broken in their software rather than daily store sales.
It's certainly not a critical bug but it's right up there in the tier which would make me want to just dump this software altogether, if the problem is left unresolved. And I am not going to be forced to change OS/devices/hardware/instal 3rd party solutions/etc. for an issue which can/should be settled from inside Daz itself.
The problem can only be rectified if you do a very detailed report and tell them exactly what you are doing and the steps taken to accomplish that. You have to submit a report giving a step by step. If they can't reproduce it they can't fix it.
Just an FYI, my ticket was closed where I asked for an update. I was told the info was already sent to the developers. So we'll have to wait and see (maybe 154 is the fix?).
Hi, just wanted to join in to make the DAZ people realize that many people are having this issue ... we should keep this NOT SOLVED thread active.
I had this problem on 2 different computers with 4 different mice now. I'm also using blender, maya, zbrush and substance painter. None of these apps show anything like that.
Its extremely annoying and turns content development into a battle against the software. For me this is the biggest issue DAZ studio has. The autohotkey fix doesn't help much for me. (I cannot find an acceptable delay value, that I don't notice but solves the problem.) I don't plan to use a space mouse. DAZ studio should work with standard mice like any other 3D app.
The problem can only be rectified if you do a very detailed report and tell them exactly what you are doing and the steps taken to accomplish that. You have to submit a report giving a step by step. If they can't reproduce it they can't fix it.
AlienRenders has done exactly that, twice. His analysis of the problem is about as complete and accurate as it can be without code access. I think there is nothing more we can do here. Now the DAZ developers have to work ...
It looks like its fixed in Public Beta, 4.11.0.171 !
At least I was not able to reproduce the problem after trying for some time. Could other users who have this issue please confirm ?
For me it's much improved but not 100% fixed. The event loop for the viewports needs massive optimizations. If for example, I choose the Translate Tool or the Universal Tool to use in the Viewport the Viewport becomes very laggy, although DAZ Studio 4.11.x is improved from DAZ Studio 4.10.x, it is still not as fast as DAZ Studio 4.9.x was. I can instantly get rid of the viewport lag by changing from the Universal or Translate Tool to the Geometry Editor, as an example. I have not tried & tested all combinations of active gizmos with regard to how they affect DAZ i/o responsiveness related to the viewport.
Apart from (or rather, as well as) the problems listed here, I've been getting increasingly frustrated with the unwanted drag & drop action that happens quite often when I click on something in the Scene panel (Tree View).
I've never encountered this jumping viewport problem but I can confirm that trying to select some node in the Scene pane can result in unwanted parenting like a drag&drop or multible selected items like a Shift+click if something else was selected before.
I think it could also be related to the mouse event handling since I had the suspicion its only happening under heavy CPU load and if the mouse gets moved slightly after perssing the mouse button down and before the button is released in the Scene pane (with "if the mouse gets moved slightly" I mean some amount that would move the mouse cursor maybe one pixel on sceen).
Apart from (or rather, as well as) the problems listed here, I've been getting increasingly frustrated with the unwanted drag & drop action that happens quite often when I click on something in the Scene panel (Tree View).
I've never encountered this jumping viewport problem but I can confirm that trying to select some node in the Scene pane can result in unwanted parenting like a drag&drop or multible selected items like a Shift+click if something else was selected before.
I think it could also be related to the mouse event handling since I had the suspicion its only happening under heavy CPU load and if the mouse gets moved slightly after perssing the mouse button down and before the button is released in the Scene pane (with "if the mouse gets moved slightly" I mean some amount that would move the mouse cursor maybe one pixel on sceen).
I think you are right about the possible slight movement. Perhaps also about the CPU load and perhaps the two are indeed related. I've experimented with the new beta release and the viewport seems more stable but there are other issues. In my case, I have logged a bug report about the Active Pose tool causing DAZ Studio to crash.
some thing to explore... is this problem more prevelant on high end machines?
Are our machines moving faster than daz can keep up...
a variation that happens a lot is clicking on something in the scene list and daz taking a second or two to highlight it?
---
are there still some functions deep inside that reflect windows xp level coding?
----
in the meantime am installing your fix...
this was something I thought would go away when I up graded the machine and basically got worse
some thing to explore... is this problem more prevelant on high end machines?
Are our machines moving faster than daz can keep up...
a variation that happens a lot is clicking on something in the scene list and daz taking a second or two to highlight it?
---
are there still some functions deep inside that reflect windows xp level coding?
----
in the meantime am installing your fix...
this was something I thought would go away when I up graded the machine and basically got worse
I've been using the Beta (or public build as it's called) for a few days. I haven't seen any jumping issues yet. It appears they fixed the centering bug at least which was part of the problem. However, if you happen to click the right mouse button while navigating, your pointer is gone forever and you have to restart the app.
About the selection bug in the scene pane, that's been there forever. And yeah, it's still buggy in the beta.
My problems started when I was prompted to upgrade to 4.11. (And I didn't intend to upgrade, I may have clicked the wrng button)
I had no issues with 4.10.
Since the 4.11 upgrade, the scroll-wheel on my mouse (and I've tried different mouses) causes the viewport scene to jump around, half the time.
At best, it slows down work and operating ability.
Scene size (weight) doesn't seem to have anything to do with it.
4.11 is still a beta, the release build remains 4.10.0.123 - if that has chnaged it's definitely not DS, since the beta doesn't affect the release build.
Sorry to kind of necro a thread, but I wanted to chime in and mention I am now having this issue seemingly out of the blue. Was there ever a fix beyond "hope the developers sort this out"? Editing interface settings hasn't saved me and it is borderline impossible to create a scene right now. :(
Sorry to kind of necro a thread, but I wanted to chime in and mention I am now having this issue seemingly out of the blue. Was there ever a fix beyond "hope the developers sort this out"? Editing interface settings hasn't saved me and it is borderline impossible to create a scene right now. :(
Which issue? Are you uisng DS 4.10.0.123 or 4.11.0.136?
Sorry to kind of necro a thread, but I wanted to chime in and mention I am now having this issue seemingly out of the blue. Was there ever a fix beyond "hope the developers sort this out"? Editing interface settings hasn't saved me and it is borderline impossible to create a scene right now. :(
Which issue? Are you uisng DS 4.10.0.123 or 4.11.0.136?
The jumping viewport and sliders. I'll try to rotate my view and it jumps, clicks through things in the scene if I try to use the universal tool, and will randomly blow up a slider to 6x the max value if I slide it manually instead of typing. Using Daz 4.10, haven't tried the beta yet to see if it fixes it.
I just started experiencing the jumping sliders problem a few days ago. This is with the latest 4.10 release. What seemed to trigger it for me was my system upgrading to Windows 10 1809.
FWIW, I've had the viewport jumping problem for quite some time now, but I am so used to it that it doesn't really bother me. I expect to get it, and work around it.
Yes, this seems to be a Windows/mouse issue. Some people have found that pressing the mouse button, then waiting a moment before moving it, will greatly reduce the problem.
Comments
That seems to be true for some other problems. I recently downloaded the latest Hexagon which still has problems with the DAZ Studio - Hexagon Bridge. It turns out that at least one fo those problems is fixed in DS 4.11 which has not yet been released. However, a search for the term "mouse" revealed nothing:
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_11_0_101
Try searching for "jump" instead http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_11_0_148 . Note, however, that this is not the jumping viewport issue but a jumping figure issue, which was a DS bug.
The reason I searched for "mouse" was because, according to the investigation done by AlienRenders, it is clearly a mouse handling problem. Searching for "jump", as you say, tells us nothing about this issue.
Since my last post in this thread, I have changed my mouse (to one having a supposed better sensor) and the viewport problem is still there. I use other software suites as well, but ONLY in Daz do I face this problem.
Just to reitterate:
Was using Win 7 up till Jan 2018 - no issues.
Changed to Win 10 during Jan 2018 - everything goes to hell in a handbasket.
Others' mileage may vary.
What I really don't like is how such a persistent issue, which I bet affects more people than who have voiced their concerns here, is left to exist for months without getting patched out. Things break in any program, sometimes with no fault of the program's developers since Microsoft or Apple throws down some patch from their end and ruins the show for everyone. But I expect Daz's team to sort out their priorities and resources to focus more on fixing what is broken in their software rather than daily store sales.
It's certainly not a critical bug but it's right up there in the tier which would make me want to just dump this software altogether, if the problem is left unresolved. And I am not going to be forced to change OS/devices/hardware/instal 3rd party solutions/etc. for an issue which can/should be settled from inside Daz itself.
The problem can only be rectified if you do a very detailed report and tell them exactly what you are doing and the steps taken to accomplish that. You have to submit a report giving a step by step. If they can't reproduce it they can't fix it.
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_11_0_148
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_11_0_154
Just an FYI, my ticket was closed where I asked for an update. I was told the info was already sent to the developers. So we'll have to wait and see (maybe 154 is the fix?).
Hi, just wanted to join in to make the DAZ people realize that many people are having this issue ... we should keep this NOT SOLVED thread active.
I had this problem on 2 different computers with 4 different mice now. I'm also using blender, maya, zbrush and substance painter. None of these apps show anything like that.
Its extremely annoying and turns content development into a battle against the software. For me this is the biggest issue DAZ studio has. The autohotkey fix doesn't help much for me. (I cannot find an acceptable delay value, that I don't notice but solves the problem.) I don't plan to use a space mouse. DAZ studio should work with standard mice like any other 3D app.
AlienRenders has done exactly that, twice. His analysis of the problem is about as complete and accurate as it can be without code access. I think there is nothing more we can do here. Now the DAZ developers have to work ...
Have you tried the nwe Public Beta, 4.11.0.171?
No, usually I don't use beta versions. If the release notes don't say anything about this fix its probably a waste of time ...
Edit: actually there are some entries about mouse handling in the Change Log, so I will try it out.
It looks like its fixed in Public Beta, 4.11.0.171 !
At least I was not able to reproduce the problem after trying for some time. Could other users who have this issue please confirm ?
For me it's much improved but not 100% fixed. The event loop for the viewports needs massive optimizations. If for example, I choose the Translate Tool or the Universal Tool to use in the Viewport the Viewport becomes very laggy, although DAZ Studio 4.11.x is improved from DAZ Studio 4.10.x, it is still not as fast as DAZ Studio 4.9.x was. I can instantly get rid of the viewport lag by changing from the Universal or Translate Tool to the Geometry Editor, as an example. I have not tried & tested all combinations of active gizmos with regard to how they affect DAZ i/o responsiveness related to the viewport.
So far I didnt notice any viewport lagging ...
But anyway, this thread is about a very specific viewport jumping problem, that is caused by a bug. Not about viewport lagging.
@ marble I was involved in a discussion about that (February 2017): Problem with items moving in Scene tab
I'm currently using DS 4.10.0.123 on Windows 7.
I've never encountered this jumping viewport problem but I can confirm that trying to select some node in the Scene pane can result in unwanted parenting like a drag&drop or multible selected items like a Shift+click if something else was selected before.
I think it could also be related to the mouse event handling since I had the suspicion its only happening under heavy CPU load and if the mouse gets moved slightly after perssing the mouse button down and before the button is released in the Scene pane (with "if the mouse gets moved slightly" I mean some amount that would move the mouse cursor maybe one pixel on sceen).
I think you are right about the possible slight movement. Perhaps also about the CPU load and perhaps the two are indeed related. I've experimented with the new beta release and the viewport seems more stable but there are other issues. In my case, I have logged a bug report about the Active Pose tool causing DAZ Studio to crash.
some thing to explore... is this problem more prevelant on high end machines?
Are our machines moving faster than daz can keep up...
a variation that happens a lot is clicking on something in the scene list and daz taking a second or two to highlight it?
---
are there still some functions deep inside that reflect windows xp level coding?
----
in the meantime am installing your fix...
this was something I thought would go away when I up graded the machine and basically got worse
Good inquiries.
When the beta will be released as final build?
I don't use betas, I had problems in the past with them.
No-one knows - see https://www.daz3d.com/forums/discussion/comment/941002/#Comment_941002 for some guidance on how the decision might be made.
I've been using the Beta (or public build as it's called) for a few days. I haven't seen any jumping issues yet. It appears they fixed the centering bug at least which was part of the problem. However, if you happen to click the right mouse button while navigating, your pointer is gone forever and you have to restart the app.
About the selection bug in the scene pane, that's been there forever. And yeah, it's still buggy in the beta.
Ok, thanks! I'll check it.
Thank you so much!!! I was almost insane because of this problem for a month.
I not only solved this jumping problem, but also got much smoother movement.
Thank you very much!!!
My problems started when I was prompted to upgrade to 4.11. (And I didn't intend to upgrade, I may have clicked the wrng button)
I had no issues with 4.10.
Since the 4.11 upgrade, the scroll-wheel on my mouse (and I've tried different mouses) causes the viewport scene to jump around, half the time.
At best, it slows down work and operating ability.
Scene size (weight) doesn't seem to have anything to do with it.
4.11 is still a beta, the release build remains 4.10.0.123 - if that has chnaged it's definitely not DS, since the beta doesn't affect the release build.
Sorry to kind of necro a thread, but I wanted to chime in and mention I am now having this issue seemingly out of the blue. Was there ever a fix beyond "hope the developers sort this out"? Editing interface settings hasn't saved me and it is borderline impossible to create a scene right now. :(
Which issue? Are you uisng DS 4.10.0.123 or 4.11.0.136?
The jumping viewport and sliders. I'll try to rotate my view and it jumps, clicks through things in the scene if I try to use the universal tool, and will randomly blow up a slider to 6x the max value if I slide it manually instead of typing. Using Daz 4.10, haven't tried the beta yet to see if it fixes it.
I just started experiencing the jumping sliders problem a few days ago. This is with the latest 4.10 release. What seemed to trigger it for me was my system upgrading to Windows 10 1809.
FWIW, I've had the viewport jumping problem for quite some time now, but I am so used to it that it doesn't really bother me. I expect to get it, and work around it.
Yes, this seems to be a Windows/mouse issue. Some people have found that pressing the mouse button, then waiting a moment before moving it, will greatly reduce the problem.
Is it worth getting a wired mouse and/or switching to the 4.11 beta? I know those worked for other people, I'm just so hesitant to use a beta release.
You'll likley have better results upgrading to the 4.11 beta. I'm using a wired mouse and the jumping is present in both 4.10 Beta and Pro.