[Radiance-general] OCONV and Radiance 3.5

Fri, 03 Oct 2003 17:45:47 +0000

Greg

Do you know how to set RAYPATH within BASH shell with these settings?

Thanks

Marcus

>From: Greg Ward <[email protected]>
>To: [email protected]
>CC: "Marcus Jacobs" <[email protected]>
>Subject: Re: [Radiance-general] OCONV and Radiance 3.5
>Date: Thu, 2 Oct 2003 23:05:02 -0700
>
>Hi Marcus,
>
>It is good that you bring this up, as one or two others have written to me 
>about this problem, before.
>
>The RAYPATH environment variable if you have set it must include "." in 
>order for xform to find files in or under the working directory without 
>explicitly giving the full path or prefixing the file name with "./".  This 
>is due to an enhancement in xform since 3.1 where it checks the RAYPATH 
>directories for its input files.  This facilitate the use of library 
>objects, allowing you to collect common Radiance scene files in addition to 
>the usual auxiliary files and frozen octrees in your own library 
>location(s).
>
>If you have set RAYPATH without including ".", you should add it.  This is 
>necessary anyway for Radiance to find .cal files and the like in the 
>working directory.  If for some reason you don't wish to do this, then you 
>can change your inline xform commands to:
>
>!xform -n (name1) ./file1.rad
>!xform -n (name2) ./file2.rad
>!xform -n (name3) ./file3.rad
>
>I hope this fixes your problem.
>-Greg
>
>>From: "Marcus Jacobs" <[email protected]>
>>Date: Thu Oct 2, 2003  6:36:06  PM US/Pacific
>>
>>Dear Group
>>
>>I am having an issue with OCONV and Radiance 3.5 (I think that I had the 
>>same issue with V. 3.4 too). Although I am currently using binaries 
>>compiled for Cygwin, I have experienced the same issue with binaries that 
>>I have compiled for Linux. Usually, I use the I use binaries compiled for 
>>Desktop Radiance but in this situation, I would like to use the new 
>>OBJ2MESH utility.
>>
>>It was my understanding that as a method of combining a scene containing 
>>many individual *.rad files, we could use one single file that calls xform 
>>in a manner such as this:
>>
>>!xform -n (name1) file1.rad
>>!xform -n (name2) file2.rad
>>!xform -n (name3) file3.rad
>>
>>I have not encountered any issues with the Desktop Radiance binaries with 
>>this approach but when using Radiance 3.5 (compiled for Windows or Linux), 
>>I contantly get error messages that usually look like this:
>>
>>xform: cannot find file "file1.rad"
>>oconv: warning - (!xform -n name1 file1.rad): empty file
>>
>>Can anyone tell me what's going wrong here?
>>
>>
>>Thanks
>>
>>Marcus D. Jacobs
>

_________________________________________________________________
Instant message during games with MSN Messenger 6.0. Download it now FREE!  
http://msnmessenger-download.com