The new version is too sluggish when you scrub the timeline..
Even in simplest scene.
back to 3.14
v3.02 - 3.16 TOO SLUGGish
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)
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)
My Portfolio
windows 10 Pro. |1070 + 1070 + 1070 + 1070 | i7 @4.5Ghz
windows 10 Pro. |1070 + 1070 + 1070 + 1070 | i7 @4.5Ghz
same prob..oguzbir wrote:The new version is too sluggish when you scrub the timeline..
Even in simplest scene.
back to 3.14
back to 2.21 :/
3dmax, zbrush, UE
//Behance profile //BOONAR
//Octane render toolbox 3dsmax
//Behance profile //BOONAR
//Octane render toolbox 3dsmax
Just checked it, even with not the simplest scene. No difference at all.
There are no changes in the plugin itself between 3.14 and 3.16 that may affect this. The biggest change - the new 3.02 Octane rendering core. So, perhaps some conflict between it and hardware/drivers on your machine...
Unfortunately your "bugreport" does not have enough information to guess the reason or even reproduce it...
There are no changes in the plugin itself between 3.14 and 3.16 that may affect this. The biggest change - the new 3.02 Octane rendering core. So, perhaps some conflict between it and hardware/drivers on your machine...
Unfortunately your "bugreport" does not have enough information to guess the reason or even reproduce it...
really if this is the best you can do.. better don't answer at all..
the plugin has been sluggish since 2.21 that is why I keep on using it .. on 2 systems, windows 7 and windows 10..
OK, what alternatives did you guys suggest here - redshift right?
..this shit is never going to get fixed..
- next major upgrade for me is very well going to be to a different render package, as it is the same shift as going for v2 to v3.. no compatibility with materials
.. with development steps getting longer with each iteration, it is becoming clear that there is nothing more to expect, there will be no magical update, only more bugs, and promises of better future
- obviously, we, the users are assholes, and who gives a fuck right?
the plugin has been sluggish since 2.21 that is why I keep on using it .. on 2 systems, windows 7 and windows 10..
OK, what alternatives did you guys suggest here - redshift right?
..this shit is never going to get fixed..
- next major upgrade for me is very well going to be to a different render package, as it is the same shift as going for v2 to v3.. no compatibility with materials
.. with development steps getting longer with each iteration, it is becoming clear that there is nothing more to expect, there will be no magical update, only more bugs, and promises of better future
- obviously, we, the users are assholes, and who gives a fuck right?
3dmax, zbrush, UE
//Behance profile //BOONAR
//Octane render toolbox 3dsmax
//Behance profile //BOONAR
//Octane render toolbox 3dsmax
For me it has been the opposite since I update to 3.x, I used to be unable to watch youtube/videos at the same time as I was rendering because my GPU was too busy, but now for some reason I can do it without any slowdown, yet the device is not set to low priority.
Hi,
I didn't have the time to prove my bug report. like installing older version and newer version. And recording the viewport.
But I can say is the issue has been resolved updating the new 4.0 test version.
I didn't have the time to prove my bug report. like installing older version and newer version. And recording the viewport.
But I can say is the issue has been resolved updating the new 4.0 test version.
My Portfolio
windows 10 Pro. |1070 + 1070 + 1070 + 1070 | i7 @4.5Ghz
windows 10 Pro. |1070 + 1070 + 1070 + 1070 | i7 @4.5Ghz
I've ragequitted the 3.xx versions like every time now because of this (usually followed by a hard crash after waiting for minutes for the scene, and PC to unfreeze) .. will test this one nowoguzbir wrote:Hi,
I didn't have the time to prove my bug report. like installing older version and newer version. And recording the viewport.
But I can say is the issue has been resolved updating the new 4.0 test version.
3dmax, zbrush, UE
//Behance profile //BOONAR
//Octane render toolbox 3dsmax
//Behance profile //BOONAR
//Octane render toolbox 3dsmax
Incredibul it appears to be running great now - same scene, runs great..
3dmax, zbrush, UE
//Behance profile //BOONAR
//Octane render toolbox 3dsmax
//Behance profile //BOONAR
//Octane render toolbox 3dsmax
Hi,
This issue was likely caused by sundry stability issues, which are being continuously identified and resolved.
Duplication of the bug in the 3.16 release, as Jim pointed out, has turned up nothing. If this issue pops up again (or if anyone still on 3.16 is consistently experiencing this issue), as much detail as possible would be greatly appreciated for finding and resolving this case.
Cheers,
Azen
This issue was likely caused by sundry stability issues, which are being continuously identified and resolved.
Duplication of the bug in the 3.16 release, as Jim pointed out, has turned up nothing. If this issue pops up again (or if anyone still on 3.16 is consistently experiencing this issue), as much detail as possible would be greatly appreciated for finding and resolving this case.
Cheers,
Azen