OTOY Forums

The new version is too sluggish when you scrub the timeline..
Even in simplest scene.
back to 3.14

oguzbir wrote:The new version is too sluggish when you scrub the timeline..
Even in simplest scene.
back to 3.14

same prob..

back to 2.21 :/

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...

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?

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.

oguzbir 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.

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 now

Incredibul it appears to be running great now - same scene, runs great..

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