Thanks Roeland, useful indeed.roeland wrote:It is a setting to make certain light pass IDs off by default. This is useful if you have a light source which should only cast illumination on a few selected objects. It would be impractical to go to every single object on the scene and switch off that light pass ID.
If you enable one of the passes in "light linking invert", then this pass will not illuminate any objects. Now if you go to an object layer and switch off that light ID, the light source will illuminate only that object.
OctaneRender™ 4 RC 3
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
- enricocerica
- Posts: 1012
- Joined: Wed Nov 25, 2009 7:32 pm
- Contact:
Modeling system : I7 32GB Windows 10 & Fujitsu Celsius H720
GPU : 1x Gigabyte GTX580 3GB + 1x MSI GTX780 3GB + 1x PALIT GTX780 6GB +1x Asus Stix GTX1070 8GB
http://www.myline.be
GPU : 1x Gigabyte GTX580 3GB + 1x MSI GTX780 3GB + 1x PALIT GTX780 6GB +1x Asus Stix GTX1070 8GB
http://www.myline.be
Hi,
Thank for the fixes!
Following my post from the previous release, I've made a small video showing the issue with the transform gizmo.
You will see that with a normal object it works well, but if you scale your object it starts to get difficult to use (and I had worst then that)
I was wondering if I was the only one with this issue.
Just import an object, use the gizmo to move it around. It works fine. Then scale it up and try to use the gizmo again, it's gonna be very clunky.
I hope a fix will come!
Thanks!
Thank for the fixes!
Following my post from the previous release, I've made a small video showing the issue with the transform gizmo.
You will see that with a normal object it works well, but if you scale your object it starts to get difficult to use (and I had worst then that)
I was wondering if I was the only one with this issue.
Just import an object, use the gizmo to move it around. It works fine. Then scale it up and try to use the gizmo again, it's gonna be very clunky.
I hope a fix will come!
Thanks!
- Attachments
-
- Bug_transform.mp4
- (24.6 MiB) Downloaded 3661 times
Hi Enrico,enricocerica wrote:It seems that once a texture is compressed, it cannot be seen anymore in the inline node preview, black result.
Edit : The problem seems to occur in all the cases ...
confirmed, there is an issue with preview in this version, and it has been already fixed for the next release.
ciao Beppe
- mvijfwinkel
- Posts: 11
- Joined: Fri May 06, 2011 9:26 am
Small feature request:
Can you guys add a button that reloads all textures in the scene? Or a way to check if maps have been modified and reload automatically?
We have a pretty iterative workflow and having to manually reload each map is pretty annoying
Great work on this release so far, kudos!
Can you guys add a button that reloads all textures in the scene? Or a way to check if maps have been modified and reload automatically?
We have a pretty iterative workflow and having to manually reload each map is pretty annoying

Great work on this release so far, kudos!
- enricocerica
- Posts: 1012
- Joined: Wed Nov 25, 2009 7:32 pm
- Contact:
I always experimented lag with the standalone UI when using heavy scenes when selecting material, moving camera, ... and this is not specific to this version.
All my video cards are dedicated to the render and I'm using the onboard card for the display (Intel).
I would like to know if someone else also meets this annoying behavior ? Is there a way to speed up ? Should I check some settings on Octane or system ?
Thanks for your feedback
All my video cards are dedicated to the render and I'm using the onboard card for the display (Intel).
I would like to know if someone else also meets this annoying behavior ? Is there a way to speed up ? Should I check some settings on Octane or system ?
Thanks for your feedback
Modeling system : I7 32GB Windows 10 & Fujitsu Celsius H720
GPU : 1x Gigabyte GTX580 3GB + 1x MSI GTX780 3GB + 1x PALIT GTX780 6GB +1x Asus Stix GTX1070 8GB
http://www.myline.be
GPU : 1x Gigabyte GTX580 3GB + 1x MSI GTX780 3GB + 1x PALIT GTX780 6GB +1x Asus Stix GTX1070 8GB
http://www.myline.be
Hi,
I'm getting quite different Results compared to 3.08.
Roughness on Specular (Waterbottle) and Glossy Shaders (KitchenFronts) behaves differently.
Same Settings on both Renders (AI Light and Denoising turned Off)
Octane 4 RC 3 Octane 3.08.3
I'm getting quite different Results compared to 3.08.
Roughness on Specular (Waterbottle) and Glossy Shaders (KitchenFronts) behaves differently.
Same Settings on both Renders (AI Light and Denoising turned Off)
Octane 4 RC 3 Octane 3.08.3
Win7 | Gigabyte G1.Sniper 3 | I7 3770K | 2x Titan (Kepler) | 1x Titan X (Pascal)