Re: OcDS PROBLEMS RESULTING IN CRASHES - read & post here...
Posted: Tue Apr 09, 2013 3:49 pm
Deleted this post as it was no longer relevant to the issue concerned!
Community Forums for OTOY Customers
https://render.otoy.com/forum/
Hello t_3t_3 wrote:sorry to hear that!UruMike wrote:Ok, this gets annoying, it happened a few times now...
Sometimes when setting up a scene and changing the kernel from PMC to Direc Light or vice versa Studio crashes.
AND I CANNOT REOPEN THE SCENE!
I have found no workaround to make these scenes work again.
Hours spent setting something up and badabum - start from scratch...
& two important points about that: if opening a scene file results in a crash, this is not necessary the end. if a bug is fixed, there is a pretty good chance that this will also allow to reopen a scene that was crashing before. and the 2nd point: i need crash reports - otherwise i'm not able to help or find the reason. whenever it happens, whenever possible - please send me crash reports, log files, descriptions, whatever. we are 13 days into the public beta, and as much as i'd like to have it mature and stable already - it will need a little more time to get there...
I just thought I was getting something wrong as I only began to use the cue after advice from t_3 but..I set them to 500, clicked on "get current Camera..." in the anim tab and hit Start Animation. It started rendering with the default 2000 samples.
I can confirm that, I just had the exact same issue.orion_uk wrote:I just thought I was getting something wrong as I only began to use the cue after advice from t_3 but..I set them to 500, clicked on "get current Camera..." in the anim tab and hit Start Animation. It started rendering with the default 2000 samples.
Confirmed, I just thought I was going ga ga but yes... sometimes, changing the samples is NOT seen when made in the cue or render settings, for me, it seems to default to 5000 samples tho!
I just `re-installed` OcDS UPDATE v1.0.111.2158 and may have a new issue and one fixed (almost) !
Now my frames are rendering with out the `film grain effect` and I have had no crashes since copying the new plugin file to my plugins folder, BUT render animation only render 3 frames then does nothing after the third frame is complete, well, it does not complete the third frame..it `sits` at 477/500 s/pix! A couple of times I have clicked render animation button and it just said WAITING and did nothing!
Yes, I get the exact same thing when rendering stills (open viewport) in mat tab and have to close DS with task manager..It opens, but all I see is the circle saying Creating Geometry or something like this. Forever. Had to kill Studio...
no probUruMike wrote:First my apologies for the tone I used in my posting.
I was just majorly sauer because I spent some hours setting something up.
Again, I'm sorry for that.
Thanks t_3, I just tried that and still not getting past frame 3, frame 4 does not start rendering and the orange scrolling bars just scrolls away to no end. Also, This means that I cant open viewport in mat tab (or any other tab) as that does what UruMike was saying about forced close:(@both of you (and others): iwill have a look into that anim issues (the old one and the new one) soon. since there were similar issues in the closed beta, i need to find a better way for the ffwd sequence timing
sounds annoying. will see what a can do. if you try the older version, you might have a look if fixed time rendering helps to get rid of the incomplete frames...orion_uk wrote:Thanks t_3, I just tried that and still not getting past frame 3, frame 4 does not start rendering and the orange scrolling bars just scrolls away to no end. Also, This means that I cant open viewport in mat tab (or any other tab) as that does what UruMike was saying about forced close:(
Nope, using the default installer from my downloads section (has need to press clay button twice to load mats/textures) does not help with incomplete frames (for my for my problematic scene, but some newly created scenes animations render fine!) however, does allow me to render from other tabs with viewport.t_3 wrote:sounds annoying. will see what a can do. if you try the older version, you might have a look if fixed time rendering helps to get rid of the incomplete frames...orion_uk wrote:Thanks t_3, I just tried that and still not getting past frame 3, frame 4 does not start rendering and the orange scrolling bars just scrolls away to no end. Also, This means that I cant open viewport in mat tab (or any other tab) as that does what UruMike was saying about forced close:(