Hello,
While rendering in Picture viewer, I quite often forget and press Ctrl + R, to get the viewport rendered, this pops up a "can't render" dialog and something about "Cuda device" then it renders black frames in PV, or sometimes it locks down cinema, does not crash, just freezes, not even shift + shift + delete doesn't work, is it possible to make this avoidable? (yes I know I should not run render while rendering...)
Win 7, R16, 2.24.1 R3
Thanks,
Sandi
C4D freeze, PV + Render View
Moderators: ChrisHekman, aoktar
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
Try to don't presss to ctrl+R on unoptimised scenes for Final Render. Appearently you are using all movable in LV and not similar method for Final Rendering. Either select "All movable" in render settings or make some objects as movable and use "Manual assignment". If you cause to generate lot of static meshes for Final Render, it will consume a lot memory and resulting high triangles.
Also check your subdivisions for rendering. LV uses viewport subdivisions not final output.
Also check your subdivisions for rendering. LV uses viewport subdivisions not final output.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Hm, I think don't follow you, I am talking about rendering in Picture Viewer and accidently pressing Ctrl + C, thus rendering in the viewport, I dont have LV open at all.
When I do that, it breaks the rendering going on in Picture Viewer (Same for render queue).
I just made a simple test, animating a cube from left to right, render to Picture Viewer, and press Ctrl + C, it simply breaks the rendering in the Picture Viewer and instantly spits out last rendered frame till it gets to the end. (and sometimes it freezes c4d)
I would only like to have a failsafe so it doesn't break the render. I know it is my error - trying to start a second render, but I am use to doing this with c4d renderer, since it can render in viewport while rendering in Picture Viewer no problem.
When I do that, it breaks the rendering going on in Picture Viewer (Same for render queue).
I just made a simple test, animating a cube from left to right, render to Picture Viewer, and press Ctrl + C, it simply breaks the rendering in the Picture Viewer and instantly spits out last rendered frame till it gets to the end. (and sometimes it freezes c4d)
I would only like to have a failsafe so it doesn't break the render. I know it is my error - trying to start a second render, but I am use to doing this with c4d renderer, since it can render in viewport while rendering in Picture Viewer no problem.
Plugin makes control if any Picture Viewer or viewport rendering is in progress. I'll test as you say but it shouldn't allow to send second render.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
-
poutoupoutou
- Posts: 19
- Joined: Fri Apr 20, 2012 7:44 pm
I do often this mistake too.
It would be really nice if the region render function will be customizable to attribute ctrl R
It would be really nice if the region render function will be customizable to attribute ctrl R
Xeon E5 2650/4*TITAN/ Windows 10 64bits
Ok. I see what you mean. I have tryed to avoid this double time calling of vpost renderings. Had no success on this. I'm not sure that's possible.
Our plugin is not fitting any concept of cpu rendering. So not safe to use it also in viewport with/without render region.
Our plugin is not fitting any concept of cpu rendering. So not safe to use it also in viewport with/without render region.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Ok, thanks for checking it out, I will try to restrain myself from calling ctrl + r.
But I wonder, as a workaround, is it possible to get information by python, if PV or Queue is rendering, a simple script (assigned to Ctrl + R) would solve this. If anyone has some up front info on how to get the info, do share, in the meanwhile I will try to look for it myself, when I find some time.
Thanks!
But I wonder, as a workaround, is it possible to get information by python, if PV or Queue is rendering, a simple script (assigned to Ctrl + R) would solve this. If anyone has some up front info on how to get the info, do share, in the meanwhile I will try to look for it myself, when I find some time.
Thanks!