Just wondering if anyone else is getting crashes with the latest version of the plugin.
What happens to me is that I will work on a scene, save it. Then try to re-load it the following day and Daz studio will crash. It does not always happen, so i don't know what steps to take but something i must be doing is corrupting my files. If i turn off the octane plug, i can then load the scene with out errors.
This is all i have to go on in the log file.
Thanks
Nick
2014-12-24 09:06:50.220 42872 b4330 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2014-12-24 09:06:50.221 42872 b4330 +++++ Plugin started.
2014-12-24 09:06:53.913 42872 b4330 +++++ Plugin running.
2014-12-24 09:07:14.658 42872 b4330 Tried to access attribute via invalid ID A_SIZE (136)
2014-12-24 09:07:14.660 42872 b4330 Tried to access attribute via invalid ID A_TYPE (157)
error loading files version Plugin v 2.15
Moderator: BK
Forum rules
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.
- larsmidnatt
- Posts: 499
- Joined: Tue Sep 25, 2012 12:28 pm
well for me I have had this happen a lot too, but I'm not sure for the same reasons. I had a few files that would only open after trying to load them 4 or 5 times. So maybe you can try loading loading them a few times in a row and see if you get lucky?
Win10 x64
i9 10900k 64GB
2080S 8GB
DS 4.15 OcDS Prime ^_^
i9 10900k 64GB
2080S 8GB
DS 4.15 OcDS Prime ^_^
It happens to me if the scene gets too complicated, when i try to re-open it crashes. Some files if i retry multiple times, eventually they will open, other files will not open no matter how many times i re-try.
Asus Z97-A / usb 3.1 - Windows 10 - 980 ti - Titan Black - Titan Z - Daz Studio
i just have found about at least one particular reason; the plugin needs to migrate 1.2 to 1.5, 1.2 to 2.x, and also 1.5 to 2.x - and at least for the latter it misses a mapping because of bug in one of the earlier releases; a bug that affected plugs with octane 1.55 as well as 2.12 and is only corrected when going from 2.12 to 2.15, but not from 1.55 to 2.15 (to be precise it is only corrected when going from pre 4330 2.x builds to the 2.x 4330 build, so the latest 1.55 version will probably cause the same problem); will need to fix that with the next update.
if you like to get it loading already now (without oc data) by editing
if you like to get it loading already now (without oc data) by editing
%HOMEPATH%\OctaneRender\Data\OctaneRender_switches.cfg
right in the top section there is a line DisableEmbed.v2xLoad = 0
set it temporary to 1 (needs to be set before ds starts) and the scene should load. if you like to bring the mats over you can export the scene as .ocm with the previous 1.55 build (not orbx, since you don't need the embedded geometry and maps) and then import the .ocm back in to the cleaned scene. and if you do that, don't forget to set that switch back to 0 after closing ds...„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
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
- larsmidnatt
- Posts: 499
- Joined: Tue Sep 25, 2012 12:28 pm
yeah i had a file that was causing issues. finally got it to render. then deleted a bunch of stuff and saved a version. that version never has issues loading whatsoever...so i do think the more stuff the more likely the issue is to show up.alaman64 wrote:It happens to me if the scene gets too complicated, when i try to re-open it crashes. Some files if i retry multiple times, eventually they will open, other files will not open no matter how many times i re-try.
Yeah that may be one reason but I'm working with clean (from scratch) files for 2.x because there is no point in me opening my old files right now since they aren't supported anyway. Hopefully you can find the other reasons toot_3 wrote:i just have found about at least one particular reason;

Win10 x64
i9 10900k 64GB
2080S 8GB
DS 4.15 OcDS Prime ^_^
i9 10900k 64GB
2080S 8GB
DS 4.15 OcDS Prime ^_^