Viewport gone black
n.parolini_71065d8cc4
Posts: 10
Ok I changed my mobo, made the necessary adjustements to Windows 7, and now Daz decided I am not interested in seeing a viewport at all. Everything else works fine. Opening existing scenes does not change anything. I've attached a screenshow - you can see what is available of the viewport in that tiny grey upper left corner.
Updated GPU drivers... no luck.
Reinstalled DAZ... no luck.
Tried the latest 4.9 public... won't even start.
This makes DAZ completely unusable of course.
Any idea?
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
under help what does it say under about your video card, looks like it is not seeing one
you can if you have a nvidia one (unsure about others) rightclick on your desktop bring up the nvidia control panel and under manage 3D settings program settings tab find or add DAZ studio and manually set it to use it
It is listing the correct card.
I tried adding it manually, no changes :(
If you look in the flyout menu (upper right hand corner of the viewport) you can find out what DS thinks it should be showing. That may help track down the problem.
Single view with preview light on. As it should be I think.
PS: tried changing that, if I use more panels it just shows the same stuff replicated.
So, looks like it's not black, it's simply not drawn. Changed theme from aero to standard, and shows whatever is below it. Any idea?
And after updating my nVidia driver (375.63?), and updating to the latest beta build (now with Pascal support for my 1080), I'm seeing the same issue.....
Most of the viewport (multiplied for any multi-pane views), shows all black except for the upper left corner of each view pane. If I pan, orbit, etc., the little rectangle in the upper left shows the grid lines moving, but the rest of the view pane is simply NOT being drawn.
(Edit: The fact no-one responded further about the issue does NOT fill me with confidence.....)
Well, I tried downgrading my nVidia driver to 372.90, the issue remains. I also then downgraded to 372.70 (ASUS specific current driver for the 1080-8G STRIX), still the same.
I've attached a screencap of the UI. Both the Viewport and the Aux Viewport show the issue. You can see the grid-lines are visible in the small rectangle, along with the background color. If you resize the viewport down enough, you'll even see other parts drawn within that tiny rectangle in the viewports.
Any help on resolving this issue? Or do I need to file a bug on it?
Have you tried turning off OptiX where you select your Gpu if is checked?
Yep. No effect. Not surprising, as the Optix optimization only applies to Iray rendering. This is an OpenGL viewport (I'm not using Iray Interactive for my viewport.)
Did you try to reload your workspace layout? Or load another (like Highway, Self-Serve, Dark) and see if that is showing?
Maybe you collapsed your viewport accidentally. I did that once and didn't know how to get it back but a reload of my workspace did the trick. Of course that won't work if it is really a graphic card issue.
I am not a tech-savvy person so feel free to ignore my thought.
Tried changing workspace layout and style. No change. Viewport is showing, tried closing it and re-opening the pane, resizing it, undocking it, etc. No changes.
Try playing with OpenGL options from Edit - Preferences and than Interface. Try changing option there and than restarting DS.
Try full screen mode (shift + F11).
I think the main thing to remember here....a small part of the viewports ARE rendering. Look at the screen capture I attached in a prior post. But the rest of it isn't. If I pan around in the viewport, or orbit, zoom/dolly, etc.....I can see the grid lines moving. That means it IS rendering, it just isn't rendering the full viewport, only a tiny rectangle of it.
Because of this, I don't think it's a driver issue. It's either a windows issue or a DS (or QT) issue.
It is like it thinks the viewport is really small, despite its actual size. But it DOES resize (you see it in the very small rendered portion changing as you resize) so it is recognizing the size of the viewport.....but it's drawing only a tiny portion.
Needless to say, this makes DS virtually useless..... (what we in the biz refer to as a SHOWSTOPPER bug.)
Well, since it appears no-one on here has any further ideas, I'll just file a bug report on it........
Looks like the OP gave up, and probably abandoned DS....
The thing to remember...this is a beta release. It is not intended to be a final version, so problems like this are to be expected...and really the purpose of beta releases.
The OP posted about his issue way before, and was using the public release. I don't think this is limited to just this beta release.....
I was talking specifically about your issue...and yes, do file a bug report. I'm not entirely sure that both your problem and the original are one and the same, but could be. If you still have the previous version (non-beta) installed, does it do the same thing?
I never installed the non-beta version on that machine, as I knew the beta would be where I would first get pascal-based support. This machine has a 970, has an AMD CPU, and is running 4.8.
(My new machine, is a i7-6800 CPU watercooled, ASUS Maximus VIII Hero Alpha MB, 32GB DDR4-3000 RAM, SSD, HDD, Blu-ray Burner, ASUS 1080-8G STRIX GPU, with a 1200W Corsair 80+Gold PS, Running Win7Pro-64)
I'll try installing the current public build later tonight to see if it has the issue. I won't be able to render Iray with it (pascal GPU) but the viewport should just be OpenGL which should run fine.
Right..OpenGL should be fine. The Pascal card just won't be recognized as a valid render card, if it all works as it should.
Well, the bug has been submitted to support. I'll try to update here with any useful responses....
Well, the Support issue has been passed on from CS to Dev. I exhausted all of CS's solutions.....some of which were already suggested here (and I did include a link in the initial report.)
Hopefully the Devs will be able to track down the issue further....it's quite a puzzling issue. But since at least one other person had it, it isn't JUST me......
Hello! I had the same issue, but I could solve the problem modifyng the windows registry.
Take a look at this video and try to follow the instructions
Hope it will solve your problem too :-)
Hello ihave the exact same problem :(
Same Problem here. Does anyone know more about this? I don't think that I want to edit my registry, not knowing what I'm doing....
Has anyone found a solution by now or knows exactely what caused this issue?