OTOY Forums

SimonWM wrote:I had DAZ Studio open but not rendering. The second time it was closed. I'm about to upgrade my GTX 580s drivers to GeForce 332.21 Driver, the latest. See if that takes care of the problem.

one thing to note is, that as long as octane /e.g. the plugin is active the card can't enter deep sleep modes for the 3d cores as it usually would; this may play a role when having the pc on over night. but in general i don't see a direct connection between the updates and this behavior...

Ok, still with the 'original beta' version (I'll be grabbing the latest beta in a moment) so these may have been dealt with ...

With OcDS active the Reality plug-in fails with follow logged messages:

DEBUG: 0: Toolkit found: C:/3D/DAZStudio4/scripts/Reality/RealityToolkit.dse
DEBUG: 1: Toolkit included
DEBUG: 2: Reality Toolkit v.2.0
WARNING: Unhandled error while executing DAZ Script.
WARNING: QScriptEngine::popContext() doesn't match with pushContext()

Intermittent behaviour in Del key not removing item(s) selected in Scene tab.

DS not closing fully - just noticed I had 3 versions running ... only noticed when trying to move plugin out to test it's absence and was told it could not be moved as DS was still running!

SimonJM wrote:Ok, still with the 'original beta' version (I'll be grabbing the latest beta in a moment) so these may have been dealt with ...

With OcDS active the Reality plug-in fails with follow logged messages:

DEBUG: 0: Toolkit found: C:/3D/DAZStudio4/scripts/Reality/RealityToolkit.dse
DEBUG: 1: Toolkit included
DEBUG: 2: Reality Toolkit v.2.0
WARNING: Unhandled error while executing DAZ Script.
WARNING: QScriptEngine::popContext() doesn't match with pushContext()

Intermittent behaviour in Del key not removing item(s) selected in Scene tab.

DS not closing fully - just noticed I had 3 versions running ... only noticed when trying to move plugin out to test it's absence and was told it could not be moved as DS was still running!

oh-oh

since ds is intercepting del key presses on the highest possible level, to always delete scene content, and the (quite understandable) wish was raised to delete nodes/materials in the plugin context, the older versions did intercept it on system api (=windows) level. obviously this is not portable to a mac version, so i switched to a Qt standard method named shortcut-override, to redirect del key presses to the plugin - given the octane tree in the mat tab has the focus, or the nge. apparently reality doesn't expect to not have daz content deleted once the del key press has "entered" studio (as this now happens).

the only measure to avoid this would be a reality compatibility switch that turns off del key capturing in my plugin (so you need to use the context menu for deletions).

ps: i of course can not allow the del key press to bubble further down the road in studio as it would mean that using del to delete some octane stuff will also delete the currently selected scene node...

I fully understand the issue with the Del key and just what and where it was supposed to be used on!

That's really a side-issue, I was more concerned over the not fully shutting down and the 'nuking' of Reality

SimonJM wrote:I fully understand the issue with the Del key and just what and where it was supposed to be used on!

That's really a side-issue, I was more concerned over the not fully shutting down and the 'nuking' of Reality

once sthg went wrong in studio, or in particular with 3rd party code, this is to be expected rather more than less often...

Looks like I have some problem with the

-Browse recent

The window don't appear.

Material previews are not updating, you have to click another then go back to get the update.
Also when you highlight a texture in the material tab it shows the file location at the bottom of the DAZ window but half of the text is missing.

Ok, I'm getting several bugs (some leading to DS crashing) while creating the Mix material from scratch. It seems to always involve adding another mix material within a mix material.

1. When creating a Mix Material consisting of: mat1:mix, mat2:glossy, it doesn't lead to a crash, but I'm unable to change mat1 from mix back to any other.
2. When creating a Mix Material - mat1:glossy, mat2:mix, when I tried to changed the second material to mix, DS crashed on me several times in a row. Funnily enough, now, after I played around with several material variants, I can't reproduce the bug, as it seems to be working.

Can't really find a way to reproduce the bug 100%, but the first few times it worked like this:
1. Create a cube primitive
2. Change its material to Mix (mat1:glossy, mat2:mix) while attempting to change mat2 to mix, DS crashes

Hope this helps

Jazbee wrote:Ok, I'm getting several bugs (some leading to DS crashing) while creating the Mix material from scratch. It seems to always involve adding another mix material within a mix material.

thanks for the detailed description. i already had a few reports circling around sthg. happening when working with mix mat nodes - hope to be able to reproduce it along your directions. if so it should be possible to have it in the next update ~tomorrow...

michael_g wrote:Material previews are not updating, you have to click another then go back to get the update.

correct - though not intended

michael_g wrote:Also when you highlight a texture in the material tab it shows the file location at the bottom of the DAZ window but half of the text is missing.

honestly i have already forgotten that file names are sent to the status info panel (have it off usually) - will take care of it; guess there could be more info, like long material names, that would be helpful to have there...