The dreaded disappearing cursor is back - New issue.
kyoto kid
Posts: 41,023
...yes [the disappearing cursor is] it's back again after over a decade of not having it occur (I remember back in the 2.0/2.3 days it was a very common occurrence for which the only solution was to blindly navigate the menu bar to save your work, shut the programme down then restart again.
I've been using 4.21.0.5 since it was released, and only in the last few sessions, the disappearing cursor has mad an unwanted return much to my frustration.
So is there any way to avoid having to shut Daz down every time? to fix it?
ETA:
It happned twivce in the same evening.. Again no Idea what caused it.
Post edited by kyoto kid on
Comments
It is considerably less than ten years since the issue was addressed. It probably isn't the same issue, assuming it is a DS issue and not something else, but without steps to reproduce it will be hard to resolve.
Happens all the time for me now too. You don't have to shut down Daz, blindly move around until you get the button in the viewport that has perspective view and your other cameras and click that, the cursor will come back. Or sometimes it works if I click on Microsoft Edge or whatever other program I have open, the cursor reappears, I tab back into Daz and it's back as well.
That was the way I ever used to get the cursor back, however, this issue has long gone from me since 2 years ago, all of a sudden.. I've got no idea why why...
...thanks I rarely run anything else while I'm working in Daz to conserve system resources (11 year old tech going on 12.). I'll try the viewport method next time it happens.
Yeah, the past couple of years it hasn't really happened and the last couple of months it's been back with a vengeance.
Faint...
I've seen it too in 4.21 but it's rare that it happens. It seems to occur when using the parameter dials but not sure what triggers it. I'm using Mouse Without Borders and thought it might have something to do with that as I haven't heard others complain about it until now.
...for myself it happens almost anywhere on either the viewport or menus.(I have a dual display setup).
However, benniewoodell's suggestion works like a charm.
Haven't had it happen for a while.
If I recall, I used to hit ctrl to get a blip where the invisible cursor was.
Ctrl-S to save the scene, then restart Studio. But that was using Studio 4.12.
...apologies for resurrecting this thread though this is somewhat related.
Apparently if you are working in Iray View mode when the cursor vanishes, the image in the viewport pixilates and remains so even after getting the cursor to it reappear. Switching to say Texture Shaded mode and back to Iray View doesn't fix this. Saving, closing and reopening the scene doesn't fix this either. The only way to clear it is to exit the programme, wait for it to clear from system memory, then reopen it and reload the scene which is something of a bother.
This happened twice in the same session tonight.
Anyone else experiencing this?
Pixelates or is noisy? The latter would sound like a GPU droping out of rendering for some reason, which does get fixed by a restart.
Pixellation is a low-res look, as if each pixel in the image is bigger than the display pixels, noise is a random scatter of light and dark pixels of the usual size.
...the viewport defiantly pixelises. Again It only occurs when the cursor disappears. from the UI, not during other operations, when I'm working in Iray mode. Even though there is a quick fix for the cursor, it requires a programme shutdown to reset the Iray viewport. It also causes the issue if the cursor disappears in Texture Shaded mode and I switch to Iray View later in the session.
Didn't happen in 4.16 (with which I was running on the same GPU). Looking back, the issue also didn't occur with the early beta versions of 4.20 (one of which I still have installed). I'm also using the recommended driver for 4.21.0.5 so that should not be an issue either
Until I can scrape up the 940$ for the needed upgrade I cannot replace the GPU with a newer one as the BIOS on the MB is so old (11 years out of date) it won't recognise the RTX 3060 I have.