Something is very wrong with version 3.14, upgraded my Forest Pro to version 5.0.7 Beta, and installed the latest Octane 3.14, and now interactivity is super slow. Installed 3.12 back and interactivity is really fast again. At first I thought it was maybe the new Forest Pro Beta, but it's not slow on 3.12 and I also tried a scene without Forest Pro and same thing, 3.12 is super fast and 3.14 is super slow! Version 3.14 also slows down all of max almost to a halt when Octanerender Viewport in open.
Windows 10 x64
Titan X
Ram 32gb
Nvidia Driver 365.10
Octane render plugin 3.00 - 3.12
3dsmax 2016 x64
3.14 version interactivity very slow!
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)
Thank you.
This is important to know if 3.13 is still OK for you or not.
And it could be good if you give me the scene (the one that does not use Forest Pack and as you say is slow now), and a description of where exactly it is slow (only with Octane viewport running, or just moving the scene inside Max viewport without Octane running)...
This is important to know if 3.13 is still OK for you or not.
And it could be good if you give me the scene (the one that does not use Forest Pack and as you say is slow now), and a description of where exactly it is slow (only with Octane viewport running, or just moving the scene inside Max viewport without Octane running)...
3.13 Runs fine also, just 3.14 is really slow. max is not slow unless Octanerender Viewport is open. Then Octanerender Viewport and 3dsmax is both really slow in interactivity. I've attached a scene, it's very simple so it doesn't run that slow, but if you compare it to 3.12 or 3.13, you will see how much slower it is. Scenes larger than this really simple scene run much slower as they get larger. If you add a simple forest pro preset to this scenes ground plane like grass/flowers you will see how slow it gets, not because of FP. If you do the same in 3.12 or 3.13 you will see how fast the interaction is.JimStar wrote:Thank you.
This is important to know if 3.13 is still OK for you or not.
And it could be good if you give me the scene (the one that does not use Forest Pack and as you say is slow now), and a description of where exactly it is slow (only with Octane viewport running, or just moving the scene inside Max viewport without Octane running)...
- Attachments
-
- GGX Test Octane.rar
- (60.81 KiB) Downloaded 179 times
Win 8.1 64 | AMD Firepro W7000 + Geforce GTX Titan X | i7 3930k | 32GB
Thank you for the scene.
If I understood correctly, you state the slowdown only happens when Octane viewport is active.
It is not clear from your explanations what exactly is slow. So I'm currently playing with your scene, quickly panning and zooming the view when Octane viewport is active. There is no difference for me at all. Both in 3.13 and in 3.14 it moves with the same pace both in 3ds Max viewport and in Octane viewport. I can't even notice a minor slowdown, not to mention "very slow!".
It is even more strange, 'cause the only thing (besides some minor bug-fixes) changed in 3.14 that may affect the interactivity - is the real-time updating procedure for Forest Pack objects. Now it polls the possible FP objects switches every tick. Unfortunately Forest Pack does not provide the SDK where it could be possible to catch the event of switching the objects - so it is only possible to check if it was changed in every tick...
But I've just measured the overhead added by this pooling block in a case there are no FP objects in a scene - it takes less than 1ms. This overhead can't do the noticeable speed drop as you report, even despite the fact it is still called (if the FP plugin is installed) even when there are no FP objects in a scene (to be able to see them after you added them interactively). But if you are curious - you can temporarily uninstall the FP plugin and check if this changes something for you (in this case the 3.14 changed procedure will not be even called during Octane interactive session, so you'll have the plugin almost identical to 3.13)...
Plus it may be something not so obvious as the reason in your case... Are you sure the adapter used for display is not chosen for rendering when you test a scene in 3.14?.. Perhaps you can find some other external factors that may be different in both of your testcases?..
If I understood correctly, you state the slowdown only happens when Octane viewport is active.
It is not clear from your explanations what exactly is slow. So I'm currently playing with your scene, quickly panning and zooming the view when Octane viewport is active. There is no difference for me at all. Both in 3.13 and in 3.14 it moves with the same pace both in 3ds Max viewport and in Octane viewport. I can't even notice a minor slowdown, not to mention "very slow!".
It is even more strange, 'cause the only thing (besides some minor bug-fixes) changed in 3.14 that may affect the interactivity - is the real-time updating procedure for Forest Pack objects. Now it polls the possible FP objects switches every tick. Unfortunately Forest Pack does not provide the SDK where it could be possible to catch the event of switching the objects - so it is only possible to check if it was changed in every tick...
But I've just measured the overhead added by this pooling block in a case there are no FP objects in a scene - it takes less than 1ms. This overhead can't do the noticeable speed drop as you report, even despite the fact it is still called (if the FP plugin is installed) even when there are no FP objects in a scene (to be able to see them after you added them interactively). But if you are curious - you can temporarily uninstall the FP plugin and check if this changes something for you (in this case the 3.14 changed procedure will not be even called during Octane interactive session, so you'll have the plugin almost identical to 3.13)...
Plus it may be something not so obvious as the reason in your case... Are you sure the adapter used for display is not chosen for rendering when you test a scene in 3.14?.. Perhaps you can find some other external factors that may be different in both of your testcases?..
I don't know what to say, I will reinstall 3.14 and do more testing, but from what I tested there was a very large difference. No questions about that. I will see what I can find and report back. Before 3.14 everything ran absolutely great.
Win 8.1 64 | AMD Firepro W7000 + Geforce GTX Titan X | i7 3930k | 32GB
Okay did a lot of testing, Your right it's rendering the same interactive speed for that teapot scene I sent you, I think when I tried it I added a forest pro object and I don't think I completely removed it from the scene. But I can tell you that what ever upgrade you did to solve the forest pro update bug has completely killed the usability of octane with Forest Pro, it is unbelievably slow now with Forest Pro objects in the scene, I use to move around the large scene I'm working on in damn near real-time, now it takes for ever just to move the camera once.
Just try it on your end, Open the same scene in 3.13 and 3.14, put a bunch of grass, trees, rocks, etc. and see the difference.... it's huge!
Just try it on your end, Open the same scene in 3.13 and 3.14, put a bunch of grass, trees, rocks, etc. and see the difference.... it's huge!
Win 8.1 64 | AMD Firepro W7000 + Geforce GTX Titan X | i7 3930k | 32GB