Oconv and IES photometrics

radiance-general
1

Hi all,

I'd like to create a library of packaged luminaire geometry and photometric (.IES) data that I can drop into my scenes. However, it seems as though the photometric data will only last through one oconv command. It's the same behavior if the octree is frozen or not, and all of the files remain in the same directory. The geometry itself works just fine. Should I just stick to xform-ing RAD files (I was under the impression that OCT instances saved memory) or is there something I'm overlooking?

Thanks in advance.

Cheers,
--Dave

Here's an example that (I think) should have two light sources:

#[test.rad]
void plastic mat 0 0 5 .4 .4 .4 0 0
!genbox mat box 250 250 1
void instance lightsource 5 light.oct -t 100 100 100 0 0
!xform -t 200 200 100 light.rad
#[/test.rad]

Commands:
ies2rad -dm/1000 light.ies
oconv -f light.rad > light.oct
objview test.rad

2

[email protected] wrote:

Hi all,

I'd like to create a library of packaged luminaire geometry and photometric (.IES) data that I can drop into my scenes. However, it seems as though the photometric data will only last through one oconv command. It's the same behavior if the octree is frozen or not, and all of the files remain in the same directory. The geometry itself works just fine. Should I just stick to xform-ing RAD files (I was under the impression that OCT instances saved memory) or is there something I'm overlooking?

Hi Dave,

This thread will prove enlightening:
http://www.radiance-online.org/pipermail/radiance-general/2003-August/000946.html

Basically, no, you cannot instance light sources.

···

--------------------------------------------
Rob Guglielmetti

3

Hi Dave,

Lights cannot be included in instances or octrees that are then compiled into a higher level scene. One way to do things is as follows:

   1. compile all non light source fixture geometry (not geometry with
      light, illum or glow materials applied) into an instance object
      (eg a frozen octree)
   2. define your light source elements, such as ies photometry and
      possible glow sources to represent glowing sources (highly
      dependent on what you are trying to accomplish)

Then these two sets of data can be deployed via replmarks or xform (item one then needs to be incorporated into a radiance "instance" definition). Another added step could be to merge these two together as a radiance scene description referencing the instance (1) and sources (2).

Hope this helps.

-Jack

[email protected] wrote:

···

Hi all,

I'd like to create a library of packaged luminaire geometry and photometric (.IES) data that I can drop into my scenes. However, it seems as though the photometric data will only last through one oconv command. It's the same behavior if the octree is frozen or not, and all of the files remain in the same directory. The geometry itself works just fine. Should I just stick to xform-ing RAD files (I was under the impression that OCT instances saved memory) or is there something I'm overlooking?

Thanks in advance.

Cheers,
--Dave

Here's an example that (I think) should have two light sources:

#[test.rad]
void plastic mat 0 0 5 .4 .4 .4 0 0
!genbox mat box 250 250 1
void instance lightsource 5 light.oct -t 100 100 100 0 0
!xform -t 200 200 100 light.rad
#[/test.rad]

Commands:
ies2rad -dm/1000 light.ies
oconv -f light.rad > light.oct
objview test.rad
------------------------------------------------------------------------

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

4

Note: afaik Radzilla supports light sources in instances.

CU Lars.