It could be two things that I know of.  First the simple thing.  Make
sure you built the xwindows binary, not just the unix binary (which
doesn't know about X, so it tries to output an ascii approximation of
the image to the console or the xterm you called it from.)

I found I still had this problem, even with the X windows compile.  The
problem only happened when I did a "make newunix" followed by a "make
xwin".  In theory, this shouldn't be a problem but... try doing a "make
clean ; make newxwin" and see if the x-povray binary works properly for
you.  I wonder if this qualifies as a bug in the makefile?

TigerHawk wrote:
> 
> If you have read previous messages, then you know half of my dilema -
> Pov-Ray 3.1g precompile didn't care to work. So, to solve the problem,
> I decided to compile it myself. It worked fine and dandy, no trouble,
> except that when I wanted it to output to the screen, or my
> X-window (using +d), I got ASCII gibberish. The file it created looked
> fine, but I didn't get a correct preview.
> 
> I am running on an AMD K6-II 300 with Slackware 4.0 and a kernel version
> of 2.2.10. It should be noted that I got Pov-Ray 3.1e to work fine on my
> computer....perhaps it's that fast math switch??? <shrug>
> 
> If anyone is having similar problems, I'd apreciate some assisatnce.
> 
> Tim Soderstrom
> TigerHawk

-- 
To reply through email, please remove the number five from my address.
No commercial email please.

Post a reply to this message