For some reason I cannot save images all of a sudden.
I was changing resolution a few days ago. and suddenly I have a black bar on the bottom of my preview all the time, and as soon as I try to save an image, I crash.
I don't know what happened. or what has changed?
Is octane live able to make changes to software, etc...? was something done?
I'm kinda screwed till I find out how to fix it on one file, because it's been done in pre23 and I can't open in 22 (not backwards compatible?).
Dave
pre23- Kind of a serious problem- crash on img save suddenly
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
It may be that it's just this one file, but I thought I had it on other ones, however now when I check I don't see it elsewhere. no idea, but if anyone else has seen this happen, please let me know.
I'll see if I get it again. or if it's just some sort of screwed up file?
Dave
I'll see if I get it again. or if it's just some sort of screwed up file?
Dave
CPU - i7-950 3.06 Ghz, 24GB Ram, Win7 x64, 2 display monitors, GeForce GTX 580 3GB Classified. I'm glad to say I LOVE OCTANE!
Probably it is a bug, maybe to do with the unfinished supersampling code.
Had it done many samples when you changed resolution?
Did you make the res bigger or smaller?
Was there a lot of vram used by the scene + film size when you tried to save?
Perhaps you are reloading it from .ocs file and continuing to render more samples?
Does it give the line and save problems if you load the same scene by .obj instead?
Just asking questions to help with a a diagnosis.
How about if you change the res after you load the .ocs but before you start actual rendering by click on the node - I guess you changed on the fly last time.
We have seen a similar black line problem on image res change before and it was fixed.
Maybe its back and causes an additional issue with saving.
Had it done many samples when you changed resolution?
Did you make the res bigger or smaller?
Was there a lot of vram used by the scene + film size when you tried to save?
Perhaps you are reloading it from .ocs file and continuing to render more samples?
Does it give the line and save problems if you load the same scene by .obj instead?
Just asking questions to help with a a diagnosis.
How about if you change the res after you load the .ocs but before you start actual rendering by click on the node - I guess you changed on the fly last time.
We have seen a similar black line problem on image res change before and it was fixed.
Maybe its back and causes an additional issue with saving.
i7-3820 @4.3Ghz | 24gb | Win7pro-64
GTS 250 display + 2 x GTX 780 cuda| driver 331.65
Octane v1.55
GTS 250 display + 2 x GTX 780 cuda| driver 331.65
Octane v1.55
Somewhere, you are lucky, because I got the black bar the first time I rendered with 2.3, and I have never been able to save a png without crashing Octane... It happens every time.and suddenly I have a black bar on the bottom of my preview all the time, and as soon as I try to save an image, I crash.
French Blender user - CPU : intel Quad QX9650 at 3GHz - 8GB of RAM - Windows 7 Pro 64 bits. Display GPU : GeForce GTX 480 (2 Samsung 2443BW-1920x1600 monitors). External GPUs : two EVGA GTX 580 3GB in a Cubix GPU-Xpander Pro 2. NVidia Driver : 368.22.
pixelrush is right. It does have to do with architectural changes done for supersampling.
the safest right now is to use a pow of two resolution with one GPU.
/M
the safest right now is to use a pow of two resolution with one GPU.
/M