Viewport curiosity

[SimonJM]

Along with the 'Shutting down threads' lock-up of Daz Studio (4.6, 64-bit) when loading a scene prior to OcDS upgrade I am also now seeing something bizarre. Start DS, load a figure (thus far it has been Aiko 5), swap to any other tab (such as Lighting/Cameras). Viewport goes black. In fact viewport stops updating, so if I Alt-Tab from this screen back to DS I can still see this screen (see attached) ... Uninstalling OcDS stops this happening.

[t_3]

what you see after alt-tab is an issue between Qt and windows 7 (or windows 7 in general) if areo is disabled;
i expect you won't see this, if you have aero enabled (and of course don't let the plugin disable it).

why the viewport goes black when switching tabs i have no explanation.
it would be interesting if this also happens with aero on; what else would be good to known:
- before switching tabs does loading content into the scene work?
- does this happen with any older scene when adding content?
- only with old scenes?
- do you have gpu priority enabled or not
- what is your nvidia driver version
- what is your Qt version
(to check this, please find the QtCore4.dll in your studio root dir, right-click > properties > details > file version)

[SimonJM]

This happens as and when I create a new scene form a fresh load of DS4.6 with OcDS installed. Load DS, load Aiko, switch tabs and ... as the image shows. Do exactly the same but with OcDS removed and it doesn't happen - no other changes made to system.

QtCore.dll is file version 4.8.4.0
GPU prioritry has not been touched (vanilla install of OcDS)
gfx cards are dual 4GB NVIDIA GeForce GTX 680M with driver version 9.18.13.668
There is a small lag when loading, say, Aiko 5 (who is acting as my crash test dummy in this ... she did sign a waiver ) in the OcDS-less trials. With OcDS back in place I am not sure if there is much of a lag as the viewport does not refresh for a long while and may only do so as/when 'nudged' by doing a Ctrl-F (to frame the selected item), but presumably other things to force a refrech may also work.

[t_3]

This happens as and when I create a new scene form a fresh load of DS4.6 with OcDS installed. Load DS, load Aiko, switch tabs and ... as the image shows. Do exactly the same but with OcDS removed and it doesn't happen - no other changes made to system.

QtCore.dll is file version 4.8.4.0
GPU prioritry has not been touched (vanilla install of OcDS)
gfx cards are dual 4GB NVIDIA GeForce GTX 680M with driver version 9.18.13.668
There is a small lag when loading, say, Aiko 5 (who is acting as my crash test dummy in this ... she did sign a waiver ) in the OcDS-less trials. With OcDS back in place I am not sure if there is much of a lag as the viewport does not refresh for a long while and may only do so as/when 'nudged' by doing a Ctrl-F (to frame the selected item), but presumably other things to force a refrech may also work.

ok. thanks!
this means 4.6 brings a new qt version with it. don't now if i in particular like that, since the current daz sdk still uses 4.8.1(!), ds4.5latest did use 4.8.3 and now we have 4.8.4.

apart from that some more questions:
- do you load a5 from default content or from a user file/saved scene?
- when you say "viewport does not refresh" - which one... octane or ds?
- in case you load from content and have the octane viewport open when loading a5
- - different behavior if the viewport it closed and opened later?
- - what if you turn off auto mats and live geometry prior loading? (and get into the game with reload first, and create missing)

[SimonJM]

Let me close-up the stuff I am in the midst off with DS and I'll see what I can do to provide the info ...

[t_3]

Let me close-up the stuff I am in the midst off with DS and I'll see what I can do to provide the info ...

whenever you find the time - thanks!!

[SimonJM]

Ok, let's see what we have ...

All tests have been done loading basic Aiko 5 figure from Smart Content into a blank scene.
By viewport I refer to the Daz Studio one.
The tests, thus far, have been done with the OcDS pane/viewport inactive.
Same thing happens with OcDS active (if I move the OcDS dialog pane around it leaves 'trails' behind.

Ahah, bingo! Turned off the auto geometry updates and auto mat updates and ... issue is gone! Let me fiddle to see if it is one, or both ... *cues Greensleeves to play ...*

With auto mat update active and auto geometry inactive, all is well
With auto mat update inactive and auto geometry active, all is well

Seems to only happen when BOTH are active. If either one is unchecked the problem does not appear.

Hope that helps!

[SimonJM]

Forgot to add, as I forgot to include the test ... turning off one of those auto update options also seems to clear the 'threads closing' hang issue when loading an 'old' scene.

[t_3]

i again have this "simon" issue - am currently haveing "the other" simon with exactly the same issue questions in another thread.

thanks for checking the combination out - that would have been exactly my next question. it for sure helps to track that issue down. what'd also help: if you force the issue, but keep windows areo activated - do you still see this trails/whatever weird stuff?

i have the same issue with an internal debug window of octane (of course nothing that tangles normal users), but it only happens if aero is off; so i think that under some circumstances Qt has a problem processing ui events. if the issue you noticed points into the same direction it would be an additional clue where to look for problems...

[SimonJM]

I know, I saw the other thread but, in the interests of not having your brain melt, opted not to comment ...

Here is where I hang my head in shame. Despite looking and looking (and vaguely recalling having done so on another W7 computer) I have NO IDEA of where and how to turn Aero on/off ..