Occasionally, when I translate an object, I get an error in POV-Ray when
raytracing.  Turns out that occasionally, Moray will export (in a position
vector) something like #INF00.  If I move the object somewhere else, then
move it back, the problem is fixed on the next export.

--
This message brought to you by:
-=< Ian (the### [at] hotmailcom >=-

Please visit my site at http://spectere2000.cjb.net! :)

Post a reply to this message

Hi Ian Burgmyer, you recently wrote in moray.win:

> Occasionally, when I translate an object, I get an error in POV-Ray when
> raytracing.  Turns out that occasionally, Moray will export (in a position
> vector) something like #INF00.  If I move the object somewhere else, then
> move it back, the problem is fixed on the next export.
Do you see any pattern to it? Does it occur when you are moving the
object in a specific view? Or very far away? Try to see if there is a
pattern to it.

- Lutz
  email : lut### [at] stmuccom
  Web   : http://www.stmuc.com/moray

Post a reply to this message

i get this occasionally, but also things like

whateveer <35.56,45,345.000000000000000000000000 and on and on>

usually when using a plug when i think abouyt it, but deleting the object or
moving it seems to have fixed the problem everytime so far..

odd

Rick

Ian Burgmyer <the### [at] hotmailcom> wrote in message
news:38167e32@news.povray.org...
> Occasionally, when I translate an object, I get an error in POV-Ray when
> raytracing.  Turns out that occasionally, Moray will export (in a position
> vector) something like #INF00.  If I move the object somewhere else, then
> move it back, the problem is fixed on the next export.
>
> --
> This message brought to you by:
> -=< Ian (the### [at] hotmailcom >=-
>
> Please visit my site at http://spectere2000.cjb.net! :)
>
>
>

Post a reply to this message

Ian Burgmyer <the### [at] hotmailcom> wrote:
: Occasionally, when I translate an object, I get an error in POV-Ray when
: raytracing.  Turns out that occasionally, Moray will export (in a position
: vector) something like #INF00.  If I move the object somewhere else, then
: move it back, the problem is fixed on the next export.

  This sounds like the program is outputting the result of an illegal
operation. This kind of result appears with operations like x/0 (= inf),
-x/0 (= -inf) or 0/0 (= not-a-number). There exists notations for these
three kind of illegal numbers in the floating point format used by the FPU
and when a compiler generates code for printing those illegal numbers, it
generates something like what you are saying above.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Nieminen Juha wrote:

> Ian Burgmyer <the### [at] hotmailcom> wrote:
> : Occasionally, when I translate an object, I get an error in POV-Ray when
> : raytracing.  Turns out that occasionally, Moray will export (in a position
> : vector) something like #INF00.  If I move the object somewhere else, then
> : move it back, the problem is fixed on the next export.
>
>   This sounds like the program is outputting the result of an illegal
> operation. This kind of result appears with operations like x/0 (= inf),
> -x/0 (= -inf) or 0/0 (= not-a-number).

But shouldn't Moray crap out when doing operations like this? I know when I make
programs that divide by zero, they seriously crap out- why doesn't moray?

> There exists notations for these
> three kind of illegal numbers in the floating point format used by the FPU
> and when a compiler generates code for printing those illegal numbers, it
> generates something like what you are saying above.
>
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/



--
Your claims are silly and ridiculous... I'm old, not brain damaged.
-Debate Ballot

Post a reply to this message

Lutz Kretzschmar <lut### [at] stmuccom> wrote in message
news:381### [at] 194174214110...
> Do you see any pattern to it? Does it occur when you are moving the
> object in a specific view? Or very far away? Try to see if there is a
> pattern to it.
>
> - Lutz
>   email : lut### [at] stmuccom
>   Web   : http://www.stmuc.com/moray

Sorry for the long reply time. . .

No, actually I see no pattern in it.  It seems to happen when I change
something in the texture and translate the object at the same update, but
I'm really going to have to do a bit more investigating to really give you
anything isolated.

One thing I do notice, it always happened when I'm already ready to throw
the computer out the window ;)

--
This message brought to you by:
-=< Ian (the### [at] hotmailcom >=-

Please visit my site at http://spectere2000.cjb.net! :)

Post a reply to this message

Alex Magidow <axi### [at] mninternet> wrote in message
news:38183CC1.98AB65C6@mninter.net...
> Nieminen Juha wrote:
> > Ian Burgmyer <the### [at] hotmailcom> wrote:
> > : Occasionally, when I translate an object, I get an error in POV-Ray
when
> > : raytracing.  Turns out that occasionally, Moray will export (in a
position
> > : vector) something like #INF00.  If I move the object somewhere else,
then
> > : move it back, the problem is fixed on the next export.
> >
> >   This sounds like the program is outputting the result of an illegal
> > operation. This kind of result appears with operations like x/0 (= inf),
> > -x/0 (= -inf) or 0/0 (= not-a-number).
>
> But shouldn't Moray crap out when doing operations like this? I know when
I make
> programs that divide by zero, they seriously crap out- why doesn't moray?

Ditto here.  Unless Moray has it's own error handler, which I don't really
think is very logical in a Windows program, and is it even POSSIBLE without
seriously hacking up the code?  And, if there is such an error handler, then
I'd think it would iron out these kind of things.  I dunno.

--
This message brought to you by:
-=< Ian (the### [at] hotmailcom >=-

Please visit my site at http://spectere2000.cjb.net! :)

Post a reply to this message

Ian Burgmyer <the### [at] hotmailcom> wrote in message
news:3825158b@news.povray.org...
[snip]
>
> Ditto here.  Unless Moray has it's own error handler, which I don't really
> think is very logical in a Windows program, and is it even POSSIBLE
without
> seriously hacking up the code?  And, if there is such an error handler,
then
> I'd think it would iron out these kind of things.  I dunno.

It's built in into the output functions of C++ i think.

Try "printf("%d", 10/0);" or "cout << (10/0);" and you should get something
like that (I think).
On the other hand, if you try "int x = 10 / 0"; you will get an exception.

Johannes.

Post a reply to this message