 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
The sub says it all.
What is the next topic, time to get modeling :)
Mike Norton
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Time to get modeling" ought to sink in to my brain sooner than later this
round after delaying so long in getting started on the last one, unless of
course I can't even think of what to make.
I just went to get my entry uploaded and glanced at the clock first.
2:06am (12:06am PDT), six minutes past the deadline.
No use, I have it set to Boulder Colorado's atomic clock.
I didn't really have a chance anyhow, couldn't get out of going to my own
birthday afterall, now could I? (oh-oh... I can just hear it now).
Message <363b18c6.0@news.povray.org>, Mike Norton typed...
>
>The sub says it all.
>
>What is the next topic, time to get modeling :)
>
>Mike Norton
>
>
--
omniVERSE: beyond the universe
http://members.aol.com/inversez/POVring.html
=Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
That's too bad Bob, I was looking forward to seeing you finally enter
something in the IRTC. You'll have to get an early start this round.
I didn't get my own out until 11:59 PDT! I actually started the final render
about 2 days ago, but I built the whole scene around the Superpatch, and
somehow I came up with something that causes a page fault on 5 out of 600
lines. I spent all day today doing partial renders to narrow things down to
those 5 lines, then rendered column-by-column to narrow it down to about 500
pixels.
I finally started commenting things out of the scene and rendering that small
space until it would work. I got all the pixels to render with an hour to go,
then I went about putting the source and text file together. I was staring at
the clock, pulling out hair as I uploaded the text file and the jpeg with 5
minutes to go!
I narrowed things down enough that I think the problem is with a lathe in the
scene. I'm going to do some tests to see if I can get things down to one
object causing the problem, test it in the official version, and post whatever
I come up with to either bug reports or povray.programming, depending on
whether or not it happens in both programs.
I sent the zipfile out after the deadline, so I don't know if that's going to
make it. I had it bounce back at me the first time with a message that it was
over the 3.5 meg limit, which is was, I just didn't know there was a size
limit. I reduced the size of the image_maps and got it down to 450kb and it
went through.
Sorry for the blab-fest, I still have no acceptence letter, so I'm still a
little nervous.
-Mike
=Bob wrote:
> I just went to get my entry uploaded and glanced at the clock first.
> 2:06am (12:06am PDT), six minutes past the deadline.
> No use, I have it set to Boulder Colorado's atomic clock.
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Makes this friendly little "competition" sound like some sort of intense
Olympic Games gymnastics career. Maybe the entrants can refrain from getting
hurt at the IRTC. Frazzled nerves don't count though.
I know about those lathes, they are so prone to error. Surface of revolutions
too, spline trouble. Wonder what exactly is going wrong in them? Doubling over
(getting kinks) is what I always think is happening. Maybe just an out of
range bending? If there were a debugging of the equation along the spline it
would be interesting to see what the faults are.
Message <363C3516.1179F1F9@aol.com>, Mike typed...
>
>That's too bad Bob, I was looking forward to seeing you finally enter
>something in the IRTC. You'll have to get an early start this round.
>
>I didn't get my own out until 11:59 PDT! I actually started the final render
>about 2 days ago, but I built the whole scene around the Superpatch, and
>somehow I came up with something that causes a page fault on 5 out of 600
>lines. I spent all day today doing partial renders to narrow things down to
>those 5 lines, then rendered column-by-column to narrow it down to about 500
>pixels.
>
>I finally started commenting things out of the scene and rendering that small
>space until it would work. I got all the pixels to render with an hour to
go,
>then I went about putting the source and text file together. I was staring
at
>the clock, pulling out hair as I uploaded the text file and the jpeg with 5
>minutes to go!
>
>I narrowed things down enough that I think the problem is with a lathe in the
>scene. I'm going to do some tests to see if I can get things down to one
>object causing the problem, test it in the official version, and post
whatever
>I come up with to either bug reports or povray.programming, depending on
>whether or not it happens in both programs.
>
>I sent the zipfile out after the deadline, so I don't know if that's going to
>make it. I had it bounce back at me the first time with a message that it
was
>over the 3.5 meg limit, which is was, I just didn't know there was a size
>limit. I reduced the size of the image_maps and got it down to 450kb and it
>went through.
>
>Sorry for the blab-fest, I still have no acceptence letter, so I'm still a
>little nervous.
>
>-Mike
>
>=Bob wrote:
>
>> I just went to get my entry uploaded and glanced at the clock first.
>> 2:06am (12:06am PDT), six minutes past the deadline.
>> No use, I have it set to Boulder Colorado's atomic clock.
>>
>
>
>
--
omniVERSE: beyond the universe
http://members.aol.com/inversez/POVring.html
=Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
