Loading...
> >

What is this "black field", distorting the entire UI while loading? (DS 4.21)

j_gelbrich_911c36bf16j_gelbrich_911c36bf16 Posts: 8
in Daz Studio Discussion

Hi all

I don't even have a name for this, other than a "black field" coming "into" the viewport from the right, which then distorts the entire UI for as long as it takes to load a scene, or to render a scene.

Version DS 4.21, and latest NVIDIA drivers, W10.

This "black field" does not give any error messages in the log file. Anything else seems still to work. But neither do I find anything about it anywhere.

It does not break my workflow, but this is just weird

Any comments highly appreciated

 

Comments

  • Richard HaseltineRichard Haseltine Posts: 101,482

    Please don't post iamegs of nude figures.

    I have not seen other reports of that so I don't have any ideas - my suspicion would be some kind of window organiser utility getting confused by the pop-up render window.

  • LiliumVALiliumVA Posts: 19

    I too am getting this now after updating both my geforce drivers, and from 4.21 to 4.22. Regardless if it's loading a saved scene, switching from iray to another view, it seems to come up. I would assume, based on what you posted, and what I have, it must be a geforce issue. It is always the right side, and it sqishes Daz studio, freezes the program, and then comes back up. However, it continues to do this over and over. my system isn't the issue, I have a 4080, 64gb of ram, and 6 different harddrives (some are SSD) which none are full, and Daz is on it's own SSD.

    ss.jpg
    2536 x 1366 - 565K
  • ZiconZicon Posts: 335

    This happens in assorted games as well, it's not unique to Daz Studio. I suspect it's a peculiarity of the current drivers. It's not harmful in any way since it only happens during loading when the GUI is unavailable anyway, it just looks odd.

  • j_gelbrich_911c36bf16j_gelbrich_911c36bf16 Posts: 8

    Update, now on DS 4.23: it came back again, just same thing, with the latest NVIDIA driver for Nov. 12. Before that, the problem was gone for good (at least I hoped).

    Aha, so I need to wait for the next driver update ...

Sign In or Register to comment.