Texture emission changing after array

Rhino 3D (Export script developed by SamPage; Integrated Plugin developed by Paul Kinnane)

Moderator: face_off

Post Reply
xjab
Licensed Customer
Posts: 5
Joined: Sun Jan 19, 2014 1:39 am

Hi All-
I've noticed that when I'm using an image as a texture emission that I can get the power set where I like it and after arraying the object to make multiple copies- each copy is dimmed down including the original and I have to re-adjust the power to get it right. I've also noticed that if I apply an RGB image as a distribution for that emission that the Scale settings will also change after I array the object and my carefully tweaked settings will end up dramatically changed.
Basically I'm creating a diffuse texture, connecting node type as RGB image linking a jpg image then connecting the Texture Emission node selecting the same JPG as my emission and adjusting the power. Then I connect the distribution node linked to a black and white gradient jpg, adjust the scale to fit the surface. This surface is a lighted sign that I polar array to make multiple copies. That's when everything changes.
I've experimented with this many different ways and I'm stumped. I'm hoping that there is something basic that I'm just not catching. Any ideas?
Thanks
-James





MacPro, Quad Core 2.66, Windows 7, GTX 660 x2, Rhino 5-SR8, Octane 1.50.0.17
User avatar
face_off
Octane Plugin Developer
Posts: 15717
Joined: Fri May 25, 2012 10:52 am
Location: Adelaide, Australia

Hi - the actual light power emitted from geometry depends on how many polygons are in the Octane geometry container. So when you array your emitter - the total polygon count for the Octane geometry node is increasing, so the intensity changes. To get around this, you can make the emitter geometry item a block instance, which will force the plugin to allocate it a separate geometry node - so the intensity should be the same. Or tick Live Geometry Update in the Geometry tab for that geometry item (you may need to do this for all the copies too) - which will also force the plugin to allocate the geometry to separate pins on the Octane geometry group.

Hope I have not confused you with this....

Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
xjab
Licensed Customer
Posts: 5
Joined: Sun Jan 19, 2014 1:39 am

Thanks Paul-
Not confusing at all-it makes complete logical sense and I now understand more about how the plug in works with geometry. I gave this a quick try using Block Instances with all my emission and distribution settings and so far so good!
James
Post Reply

Return to “Rhinoceros 3D”