Moderator: juanjgon
Thanks, I will check this problem as soon as possible. I am now traveling and I have the Mac in the office to test it. I will check it on windows, and if it doesn't crash here I will test it on my Mac on Monday.3dworks wrote:please test here. open the scene, activate IPR. select all lights. hit 'p', check and uncheck 'unseen by camera' property a few times. it always crashes here after first or second switch.
3dworks wrote:is it normal that when opened IPR and a light is getting unchecked in scene editor, the scene is not changing? only 'reload' fixes this.
Yes, the LW SDK doesn't have a real time event for the enable/disable option in the scene editor and the Octane plugin can't know it's state without reload scene. Sorry.3dworks wrote:is it normal that when opened IPR and a light is getting unchecked in scene editor, the scene is not changing? only 'reload' fixes this.
BorisGoreta wrote:I have this workflow where I need to adjust an image in Photoshop a lot of times and see the result in Octane. When I reload an image in LW nothing happens, I need to reload the scene which is slow, but if I save this image with another name and load it in LW I don't need to reload the scene. It would be great if reload image LW function would reload the image in Octane without scene reload.
EDIT: after I reload the image in LW I have to go to Octane texture node, select some other image and then again the old one and I get the reloaded image in the IPR without scene reload.
juanjgon wrote:Boris, please, can you test this new build? ... you only need to replace the .p file. You should see version 2.2.1 in the "about" window.BorisGoreta wrote:I have finally managed to document this bug. It is present in almost all of my scenes. It is not noticable as soon as you start to work on the scene when the scene is still simple, but very soon the bug kicks in and stays.
So there it is, I hope Juanjo will be able to fix this bug becase all of my arch viz scenes are non interactive in this way.
http://render.otoy.com/customerdownload ... 2.0_11_6.p
The problem is in the update materials functions. Currently the plugin updates all the materials in the object when you change something ... this is slow in objects with a lot of materials, and even worse if the materials have a lot of image maps that Octane needs to read and update.
This new build has a new code to update the materials that should be a lot faster, but it has a lot of deep changes in the plugin update functions, so it could have hidden bugs or problems. Please test it with your complex scenes and let me know how it works, and if you have any kind of problem or side effect.
-Juanjo
