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
···
_________________________________________________________________
Share your photos without swamping your Inbox. Get Hotmail Extra Storage today! http://join.msn.com/?PAGE=features/es
Hi Marcus,
I had similar problems when i created models in desktop radiance, combined the scene files together manually in the method you describe, and tried to investigate the resulting scene files in DAYSIM on Linux. Two options:
1. Replace the '!xform' with '!cat', without the '-n' option. this seems to work most of the time, but not always
2. if all else fails, combine all the scene files into one big scene file using 'xform .... .rad >> combined.rad' on the command line.
Any other advice, from someone who actually understands UNIX, is more than welcome...
Phil.
···
_______________________________
Phillip Greenup
Specialist Engineer
Arup Australasia
Level 10, 201 Kent St
Sydney NSW 2000
Ph (02) 9320 9426
Fax (02) 9320 9321
[email protected] 3/10/2003 11:36:06 am >>>
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
_________________________________________________________________
Share your photos without swamping your Inbox. Get Hotmail Extra Storage
today! http://join.msn.com/?PAGE=features/es
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general
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
Hi Marcus,
I don't use BASH myself, but I think you add the following to your $HOME/.profile or $HOME/.bash_login file:
RAYPATH=.:/usr/local/lib/ray
export RAYPATH
This of course applies only if your Radiance library files are installed in /usr/local/lib/ray. They might be somewhere else on your system. Someone must have set the RAYPATH environment variable somewhere, so you should check that setting and change it there. If it hasn't been set, then I'm puzzled by this error since the default value includes "." as the first entry. Did you recompile from the source files, or install the precompiled binaries? (Maybe we should take this discussion off-list.)
-Greg
···
From: "Marcus Jacobs" <[email protected]>
Date: Fri Oct 3, 2003 10:45:47 AM US/Pacific
Greg
Do you know how to set RAYPATH within BASH shell with these settings?
Thanks
Marcus
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