OTOY Forums

I am using PP2014 game dev, latest SR and NVidia driver 353.30. I have reinstalled the previous version (2.23.1.48) and the delay/freeze is gone. I have then reinstalled 2.23.2.54 on top of it (no reboot) and I no longer get the freeze-ups anymore. Must be an installation glitch.

On the other hand, I have been having another glitch, but I don't remember if it started in the previous version, or before that. The plugin starts with the wrong default settings, and even the figure is loaded with a material I have used in an older scene. I have to call "Load from Default" in every scene I start, which means my default settings are still in there, but the plugin doesn't use them. Even if I re-save as default, it keeps loading those other settings on start-up.

OK, here's what I found.
tested with a scene with 2 V4 and several clothing pieces, selecting nodes and sub-nodes in the material hierarchy, render priority set to low:

2.23.2.48 - no delay in changing between nodes/sub-nodes
2.23.2.54 - a noticeable delay (1 sec or slightly more) in changing between nodes/sub-nodes

specs in sig are up-to-date.

UGH. I am getting the same problem. After I add Redsppec SSS, go to material node to increase bump. I click on bump, and it freezes for about 30 sec. What's going on?

where do I find 2.23.1.48

it's doing it even without redspec

I couldn't reproduce this issue. Would it be possible for someone who is experiencing this problem to create a small sample scene which demonstrates this problem and send it to me pls (telling me which node I need to edit to get the delay)? Ideally just using a Poser Primivite in the scene.

Thanks

Paul

where do I find 2.23.1.48 ????

face_off wrote:I couldn't reproduce this issue. Would it be possible for someone who is experiencing this problem to create a small sample scene which demonstrates this problem and send it to me pls (telling me which node I need to edit to get the delay)? Ideally just using a Poser Primivite in the scene.
Thanks
Paul

Hi Paul,
I don't think this is related to any specific scene. When I tested, I have simply loaded a single V4 with default textures, and I would get the delay/freeze when clicking on ANY numerical parameter in the materials tab. Color swatches were Ok, it was more on the numerical inputs. Clicking on any of them instantly got CPU at 100% and the plugin freezes up for a moment.

I could fix this by simply installing the previous version, and then installing the current version again. I got no more freeze-ups or delays afterwards. I didn't test this much - I just noticed the delays have stopped in a quick test.

As stated above - if someone can pls send me a complete scene which demonstrates this issue, I will take a closer look. Is it happening only when the Viewport is open, or closed too?

Previous builds are below. If someone can tell me exactly which build introduced the issue - that would help.

Thanks

Paul

http://render.otoy.com/customerdownload ... _Win64.exe
http://render.otoy.com/customerdownload ... _Win64.exe
http://render.otoy.com/customerdownload ... _Win64.exe
http://render.otoy.com/customerdownload ... _Win64.exe
http://render.otoy.com/customerdownload ... _Win64.exe
http://render.otoy.com/customerdownload ... _Win64.exe

In my case, the delays would happen with or without the viewport being open. The issue was introduced in the current version. Installing the previous one stops the delays. Curiously, installing the current version afterwards has fixed it for me. But I am still having that start up issue I have mentioned above, where the saved defaults won't stick.

On the other hand, I have been having another glitch, but I don't remember if it started in the previous version, or before that. The plugin starts with the wrong default settings, and even the figure is loaded with a material I have used in an older scene. I have to call "Load from Default" in every scene I start, which means my default settings are still in there, but the plugin doesn't use them. Even if I re-save as default, it keeps loading those other settings on start-up.

Ken, this might be happening because you having saved the Octane settings in your startup scene. If you tick "Launch to factory scene" in the General Preferences->Document that may fix that problem.

Paul