OcDS PROBLEMS RESULTING IN CRASHES - read & post here...

DAZ Studio Integrated Plugin (Integrated Plugin maintained by OTOY)

Moderator: BK

Forum rules
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.
Post Reply
User avatar
orion_uk
Licensed Customer
Posts: 713
Joined: Tue Oct 25, 2011 2:56 pm

@UruMike & t_3..

Regarding scenes not being able to be re-opened after crashes, leading you to have to re build from scratch..

I have found that when Daz crashes (only to get a message about not being able to re-open it), Try opening the scene in Daz Studio 32 bit (re save the scene) and then open it in DS 64 bit.. Cant guarantee it will work for you UruMike but it works for me :)

EDIT: It does seem like I loose some of my Octane mats/textures & env light settings during this process and have to re-apply them though :(
Last edited by orion_uk on Sat Apr 13, 2013 7:09 pm, edited 2 times in total.
http://www.Neil-Isted.com
Intel i7 870/2.93 GHz
RAM 16GB
1x Titan (6GB)
2x GTX 660Ti 2GB
Win10 Pro 64-bit
Carrara 8.5 Pro
Carrara - OR4C
OctaneRender™ for Blender
Ds pro
OR Standalone V4
Poser Plugin
User avatar
t_3
Posts: 2871
Joined: Tue Jul 05, 2011 5:37 pm

orion_uk wrote:I have found that when Daz crashes (only to get a message about not being able to re-open it), Try opening the scene in Daz Studio 32 bit (re save the scene) and then open it in DS 64 bit.. Cant guarantee it will work for you UruMike but it works for me :)
i read it, but i can't believe it :shock: i mean, good if this helps, but the reasons why this could help at all would be very, um, weird. in fact it would mean that there is a memory allocation problem somewhere, since the main difference between 32 and 64 bit applications is the address range... will write you a pm during my next break...
The obvious is that which is never seen until someone expresses it simply

1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
User avatar
orion_uk
Licensed Customer
Posts: 713
Joined: Tue Oct 25, 2011 2:56 pm

NP t-3 :)

Could have just been a fluke/coincidence (but twice!, with the same result of opening a file in 32 bit that wont open in 64 bit, then re-opening in 64 bit after saving in 32!), you would know though, you work on a much higher dimension than us mere mortal newbies ;)

Maybe I am adding 2+2 and getting 6 again :P
http://www.Neil-Isted.com
Intel i7 870/2.93 GHz
RAM 16GB
1x Titan (6GB)
2x GTX 660Ti 2GB
Win10 Pro 64-bit
Carrara 8.5 Pro
Carrara - OR4C
OctaneRender™ for Blender
Ds pro
OR Standalone V4
Poser Plugin
User avatar
t_3
Posts: 2871
Joined: Tue Jul 05, 2011 5:37 pm

orion_uk wrote:NP t-3 :)

Could have just been a fluke/coincidence (but twice!, with the same result of opening a file in 32 bit that wont open in 64 bit, then re-opening in 64 bit after saving in 32!), you would know though, you work on a much higher dimension than us mere mortal newbies ;)

Maybe I am adding 2+2 and getting 6 again :P
in fact i felt very mortal during the last months ;) anyway - it is a possibility (in the end it is "soft"ware - nowhere near what moses got from above :lol: ). and it might lead the search for some of the instability issues into a slightly different direction... let's see... i'll need to do some additional checks. usually it is not easy to force it crashing if you just want it to. only happens when you don't expect it...
The obvious is that which is never seen until someone expresses it simply

1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
User avatar
orion_uk
Licensed Customer
Posts: 713
Joined: Tue Oct 25, 2011 2:56 pm

t_3 wrote:in the end it is "soft"ware - nowhere near what moses got from above :lol:
Lol.. Thats the beauty of being a programmer, NOTHING is set i stone :P
http://www.Neil-Isted.com
Intel i7 870/2.93 GHz
RAM 16GB
1x Titan (6GB)
2x GTX 660Ti 2GB
Win10 Pro 64-bit
Carrara 8.5 Pro
Carrara - OR4C
OctaneRender™ for Blender
Ds pro
OR Standalone V4
Poser Plugin
SimonJM
Licensed Customer
Posts: 198
Joined: Tue Mar 19, 2013 12:28 am

Not sure if it is the same issue or not but I have had a couple of crashes involving OcDS and finding that on re-starting DS I am unable to load scenes, getting a message in the log which I now cannot recall, sadly. I think it suggested that something could not be initialised correctly. The upshot was that any scene would fail to load.

But, if you shut DS and do something else for a few minutes, the restart DS things will be back to normal, and scenes will now load up fine.
User avatar
t_3
Posts: 2871
Joined: Tue Jul 05, 2011 5:37 pm

SimonJM wrote:Not sure if it is the same issue or not but I have had a couple of crashes involving OcDS and finding that on re-starting DS I am unable to load scenes, getting a message in the log which I now cannot recall, sadly. I think it suggested that something could not be initialised correctly. The upshot was that any scene would fail to load.

But, if you shut DS and do something else for a few minutes, the restart DS things will be back to normal, and scenes will now load up fine.
thanks for the additional info! this seems to indeed tell the same story. memory allocation might fail on high memory load, and after a few minutes, when the system has freed up resources, it starts working again. or using 32bit ds4 instead, which (simply put) can't use the upper memory anyway, it might work instantly.

i will let you know as soon i have found a possible cause...
The obvious is that which is never seen until someone expresses it simply

1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
User avatar
larsmidnatt
Licensed Customer
Posts: 499
Joined: Tue Sep 25, 2012 12:28 pm

I think I read someone post something similiar, but I can't recall. On occasion I've been crashing DS when trying to load a scene file IF I already have a scene open. I'll send you a PM with the log files.

The scenes open perfectly fine after the crash, or if I load them after a fresh launch of DS. Does not always happen. Somewhat random, but replicable.
Win10 x64
i9 10900k 64GB
2080S 8GB
DS 4.15 OcDS Prime ^_^
User avatar
Midnight_stories
Licensed Customer
Posts: 11
Joined: Sat Feb 09, 2013 1:20 pm
Location: Brisbane, Oz

I'm afraid mine crash every time I just installed the plugin today and there just noway to open the scenes

This one comes up every time.

DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\octane.dll" at 0033:000000000F4BED90, Octane::NullEmission::create()+444752 byte(s)

cheers!
User avatar
t_3
Posts: 2871
Joined: Tue Jul 05, 2011 5:37 pm

Midnight_stories wrote:I'm afraid mine crash every time I just installed the plugin today and there just noway to open the scenes

This one comes up every time.

DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\octane.dll" at 0033:000000000F4BED90, Octane::NullEmission::create()+444752 byte(s)

cheers!
hi! there will be a new version up somewhere between today/tomorrow; there were a bunch of changes in the plugin and also the octane sdk which should solve quite some crashes - so, if it is ok for you, let's wait for this one, and see if this can solve the issu. btw, did you update to any of the other versions out until release?
The obvious is that which is never seen until someone expresses it simply

1x i7 2600K @5.0 (Asrock Z77), 16GB, 2x Asus GTX Titan 6GB @1200/3100/6200
2x i7 2600K @4.5 (P8Z68 -V P), 12GB, 1x EVGA GTX 580 3GB @0900/2200/4400
Post Reply

Return to “DAZ Studio”