Victor DiMichina wrote:
Although some users have had a measure of success with Mac & Linux
(more on Linux), the most success we've had with Lightwave is under
Windows. Plugins are more readily available under Windows as well.
If /anyone/ has had success getting command line rendering
of Lightwave working on the mac, please show the command line
you're using.
I've seen two folks who can't get the Mac's LWSN
executable to run at all from the command line;
here's a previous thread from the newsgroup:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-view+1075+1075+1076+1079+1077+1078+1080+1081+1082+1083+1084+1085+1087+1088+1089+1086
Sorry I keep forgetting Mac/LightWave has this problem.
Essentially it comes down to this:
$ cd "/Applications/LightWave [8]/programs"
$ ./lwsn -3 /var/tmp/foo.lws 1 10 1
-bash: ./lwsn: cannot execute binary file
$ ls -la
[..]
-rwxrwxrwx 1 root admin 460643 Oct 4 2005 LWSN <--
-rwxrwxrwx 1 root admin 0 Oct 9 2004 LWSN cmdLine
$ file ./LWSN
./LWSN: header for PowerPC PEF executable
Apparently 'open LWSN' works, and it's possible the intention
of the 'LWSN cmdLine' file is that you put your command line
options into that file, then 'open LWSN', and it goes off and
renders. I haven't tried this, but the above thread seems to
mention something like this. So I'm imagining, I dunno, something like:
$ cd "/Applications/LightWave [8]/programs"
$ echo '-3 /var/tmp/foo.lws 1 10 1' > "LWSN cmdLine"
$ open LWSN
Trouble with this is, that even if it works, the 'open LWSN'
will surely background itself, such that rush won't know
when its done rendering.
Also, such an approach doesn't allow for multiple processor rendering.
(ie. there's only one "LWSN cmdLine" file to work with)
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)(new)
|