|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 02 Aug 1999 17:12:23 +0300, Margus Ramst wrote:
>Sorry. Should've been more attentive. It happens in the Superpatch, but not in
>official 3.1g
>Ron?
Xenoarch?
No, honestly, I'll have to take a look at it. I haven't a clue, but I suspect
it was broken by one of the lighting changes.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
While your at it :) I just encountered a "malloc" error while attempting
to get a large mesh to parse. Has some sort of memory limitation been
introduced on purpose or by accident?
Or perhaps this error was another problem altogether. Here's the error
as POV-Ray called it:
[a few triangles were shown here]
<----ERROR
C:\3Dmodels\Other\sw_c3p0.inc:19893: error: Attempt to malloc zero size
block (File: C:\incoming\povsrc\super31a\PARSE.C Line: 3796).
The same include parses in the "Official" 3.1g version. Btw, the
triangles were not near zero vectors. Excuse me, I meant to say not
degenerate triangles (else POV-Ray would have said so I'm sure).
Bob
Ron Parker wrote:
>
> On Mon, 02 Aug 1999 17:12:23 +0300, Margus Ramst wrote:
> >Sorry. Should've been more attentive. It happens in the Superpatch, but not in
> >official 3.1g
> >Ron?
>
> Xenoarch?
>
> No, honestly, I'll have to take a look at it. I haven't a clue, but I suspect
> it was broken by one of the lighting changes.
--
omniVERSE: beyond the universe
http://members.aol.com/inversez/homepage.htm
mailto://inversez@aol.com?Subject=PoV-News
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 03 Aug 1999 07:13:55 -0500, Bob Hughes wrote:
>While your at it :) I just encountered a "malloc" error while attempting
>to get a large mesh to parse. Has some sort of memory limitation been
>introduced on purpose or by accident?
It's a known bug. I already have a fix for it around here somewhere...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ron Parker wrote in message <37a6e98e@news.povray.org>...
>On Tue, 03 Aug 1999 07:13:55 -0500, Bob Hughes wrote:
>>While your at it :) I just encountered a "malloc" error while attempting
>>to get a large mesh to parse. Has some sort of memory limitation been
>>introduced on purpose or by accident?
>
>It's a known bug. I already have a fix for it around here somewhere...
>
Do you have a fixed windows compile by any chance. I really need both
isosurfaces and triangle meshes in my irtc entry. (am using Giles's tree
macro)
Gail
*******************************************************************
* gsh### [at] monotixcoza * ERROR: COFFEE.COM not found *
* http://www.rucus.ru.ac.za/~gail/ * Insert cup and press any key *
*******************************************************************
My Software never has bugs, It just develops random features
*******************************************************************
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Bob Hughes <inversez> wrote:
: The same include parses in the "Official" 3.1g version.
By the way: Why do you use quotation marks around the word "Official"?
It's like you were saying "not really official, but kind of" or something.
--
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ahhh, well now, you see it's like this... grammar school did me no good.
I write things the way it seems right to me, and in this case the double
quotes mean simply that the word is what it is.
If I remember my English classes a quoted word or words is only supposed
to be a direct quote (make sense?) and the single quotes are to be used
as second-hand quotes or some such thing. I try, but I am no English
major.
In fact, the most wrong I can get is with titles like movie names,
POV-Ray, books, etc. But I don't feel too alone in this ;)
Bob
Nieminen Mika wrote:
>
> Bob Hughes <inversez> wrote:
> : The same include parses in the "Official" 3.1g version.
>
> By the way: Why do you use quotation marks around the word "Official"?
> It's like you were saying "not really official, but kind of" or something.
>
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
--
omniVERSE: beyond the universe
http://members.aol.com/inversez/homepage.htm
mailto://inversez@aol.com?Subject=PoV-News
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ron Parker wrote:
>
> On Mon, 02 Aug 1999 17:12:23 +0300, Margus Ramst wrote:
> >Sorry. Should've been more attentive. It happens in the Superpatch, but not in
> >official 3.1g
> >Ron?
>
> Xenoarch?
Small_Tolerance maybe?? Or posibbilty of a diffrent patch
setting/testing the shadowless flag and not the Check_No_Shadow_Group
macro?
>
> No, honestly, I'll have to take a look at it. I haven't a clue, but I suspect
> it was broken by one of the lighting changes.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |