OTOY Forums

Random crash when switching from the TEXTURES tab to MATERIALS with scene loaded.

DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4.6\QtCore4.dll" at 0033:000000005B093816, QString::QString()+6 byte(s)

vortex3d wrote:Random crash when switching from the TEXTURES tab to MATERIALS with scene loaded.

DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4.6\QtCore4.dll" at 0033:000000005B093816, QString::QString()+6 byte(s)

randomCrash_01.png

the update i'm about to post is going to sort these random crashes out. the single reason for them all is my attempt to handle material and texture processing in different threads/multithreaded. up until this next update i wanted to test if it may work out or not - apparently it doesn't. the main problem in achieving this is that the daz api is not "thread safe" and there is no real way to make it such, but change it (hello daz ); apart from that the more tasks the plugin needs to accomplish (like now also managing all maps in studio and octane), the more likely this leads to problems, also depending on the overall system performance.

to put it short: mat and texture processing is shifted back to work non multithreaded = no more crashes because of that...

More duplication fun

Basic "Genesis 2 Female" objects appear multiple times when using Quick Edit to select an image map by object.

vortex3d wrote:More duplication fun

Basic "Genesis 2 Female" objects appear multiple times when using Quick Edit to select an image map by object.

QuickEditMapDupes_01.png

QuickEditMapDupes_01a.png

one time for each map this is sorted out - 'am currently typing the post...

Thank you for your prompt replies, hard work and update. I'll post new issues when found. =D

vortex3d wrote:Thank you for your prompt replies, hard work and update. I'll post new issues when found. =D

so speak to you soo, ups

My mouse cursor dissapears in 3430. Seems to happen when generating ocd materials. It still works, cursor is just invisible while over any Daz window. Set material generation to manual, hasn't happened since.

I'm also getting a LOT of hot pixels when rendering scattering materials now. Could anything have changed here?

t_3 wrote:

vortex3d wrote:Random crash when switching from the TEXTURES tab to MATERIALS with scene loaded.

DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4.6\QtCore4.dll" at 0033:000000005B093816, QString::QString()+6 byte(s)

randomCrash_01.png

the update i'm about to post is going to sort these random crashes out. the single reason for them all is my attempt to handle material and texture processing in different threads/multithreaded. up until this next update i wanted to test if it may work out or not - apparently it doesn't. the main problem in achieving this is that the daz api is not "thread safe" and there is no real way to make it such, but change it (hello daz ); apart from that the more tasks the plugin needs to accomplish (like now also managing all maps in studio and octane), the more likely this leads to problems, also depending on the overall system performance.

to put it short: mat and texture processing is shifted back to work non multithreaded = no more crashes because of that...

This post is pretty useful to read ... Can't wait for the next update!

Ps T_3 have you seen my post about the name that are not shown properly etc etc ?

Thanks!

DrHemulen wrote:My mouse cursor dissapears in 3430. Seems to happen when generating ocd materials. It still works, cursor is just invisible while over any Daz window.

funny. i mean of course not. can you get it back by alt-tab to another running application and back to studio?

imo this is a problem with Qt, a blocked ui and mouse moves; i will add a general cursor restore method which kicks in at the end of the mat conversion process, which will hopefully avoid that (will send you a pm with a test version)...

Attack of the clones!

Shared materials split randomly on load and saving at this point will make matters worse.
I don't know what triggers this behavior, but I can't duplicate it with single items or basic scenes.

FYI: This test scene was stripped of previous Octane data using the plugin's function. Could that add to the problem?