I seem to have come across a little problem.  If I export from Rhino an INC
file and then try to parse it, depending on different situations, it will
render or not.

Basically the inc file contains all my smooth_triangles and at a given
point, POV stops reading the inc file and so tries to parse smooth_tria
where it will stop and give me an error message.  The inc file is complete
(I loaded it up and at the bottom it does end correctly) and the problem
occurs quite a way through (eg line 10230).

To note the file is 26mb and I have 256mb RAM (which is def not used up cos
I've tried it with Win2k's Task Manager Open on Performance).  Any ideas?
Is there a limit on how big a file can be?  Should I just give up and export
from rhino with far lower polygon settings?

Peter Cracknell
http://www.petercracknell.com

Post a reply to this message

In article <3b2ccd44@news.povray.org> , "Peter Cracknell" <pc### [at] lineonenet>
wrote:

> give me an error message.

It might help if you include the error message, don't you think so? ;-)


     Thorsten

Post a reply to this message

"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3b2cd3df@news.povray.org...
> In article <3b2ccd44@news.povray.org> , "Peter Cracknell" <pc### [at] lineonenet>
> wrote:

> It might help if you include the error message, don't you think so? ;-)


The error message is based on where it gives up on the inc file, ie if it
stops at smooth_tri it says error object or directive expected but
undeclared identifier 'smooth_tri' found instead.  It's as if it parses to a
certain point then thinks that the inc has finished and so doesn't parse the
remainder of the file.

Peter Cracknell

Post a reply to this message

Peter Cracknell wrote:
> 
> "Thorsten Froehlich" <tho### [at] trfde> wrote in message
> news:3b2cd3df@news.povray.org...
> > In article <3b2ccd44@news.povray.org> , "Peter Cracknell" <pc### [at] lineonenet>
> > wrote:
> 
> > It might help if you include the error message, don't you think so? ;-)
> 
> The error message is based on where it gives up on the inc file, ie if it
> stops at smooth_tri it says error object or directive expected but
> undeclared identifier 'smooth_tri' found instead.  It's as if it parses to a
> certain point then thinks that the inc has finished and so doesn't parse the
> remainder of the file.

Are you running Win95 ? I used to have this problem all the time when
running under Win95. Don't know why but it stopped when I switched
to Win98.

Try splitting the model into 2 or 3 smaller inc's and then recombine them
in a union later. Might help....

Also make sure that there are no errors in the spelling on the line number
indicated by the error message. It is not entirely impossible that Rhino
exports erroneous data.

-- 
Ken Tyler

Post a reply to this message

> Are you running Win95 ? I used to have this problem all the time when
> running under Win95. Don't know why but it stopped when I switched
> to Win98.
I'm running Windows 2000

> Try splitting the model into 2 or 3 smaller inc's and then recombine them
> in a union later. Might help....

That's a good workaround..

> Also make sure that there are no errors in the spelling on the line number
> indicated by the error message. It is not entirely impossible that Rhino
> exports erroneous data.

The errors generally jump around, but its worth checking, thanks

Peter Cracknell

Post a reply to this message

Peter Cracknell wrote:
> 
> I seem to have come across a little problem.  If I export from Rhino an INC
> file and then try to parse it, depending on different situations, it will
> render or not.
> 
> Basically the inc file contains all my smooth_triangles and at a given
> point, POV stops reading the inc file and so tries to parse smooth_tria
> where it will stop and give me an error message.  The inc file is complete
> (I loaded it up and at the bottom it does end correctly) and the problem
> occurs quite a way through (eg line 10230).
> 
> To note the file is 26mb and I have 256mb RAM (which is def not used up cos
> I've tried it with Win2k's Task Manager Open on Performance).  Any ideas?
> Is there a limit on how big a file can be?  Should I just give up and export
> from rhino with far lower polygon settings?
> 
Sounds like some memory error. How big is the Rhino file (.3DM)? If it
is some MB and its contents is not a secret, then if You will, send it
to me (specify export settings as well!) and I try to find out, what is
wrong (I have Rhino, W2K and 256 MB of memory, so almost same setup, as
your's). Given of course, that I have enough time :-)
BTW, does it happen with official version of POV-Ray? Have You tried
MegaPOV?

P.S. If You decide to send mail to me and it bounces back, then try my
work address (vah### [at] aetecee), as I don't know yet, how big mails are
allowed by service provider.

Post a reply to this message