POV-Ray : Newsgroups : povray.beta-test : PovRay 3.7.0beta.12a Server Time
31 Oct 2024 23:27:03 EDT (-0400)
  PovRay 3.7.0beta.12a (Message 1 to 4 of 4)  
From: Jonathan
Subject: PovRay 3.7.0beta.12a
Date: 14 Apr 2006 23:37:41
Message: <44406a85@news.povray.org>
I've tried the 12a beta today, most of my renders come out as expected, 
however, scenes imported from Daz via PoseRay regardless of settings or ini 
file just sits after the parse, I checked the processor load and memory 
during several of the tests. Processor load goes back down to 50% and memory 
used down to 300MB immediatly after parse (it will incline close to 900MB on 
most of my more complex scenes) instead of staying high until end of render. 
Theories anyone? BTW 3.6 has no trouble rendering the scenes, just takes 
twice as long (single thread) Once I find my copy of Blender I'll try 
importing an OBJ from it instead to see if there is a difference. I did run 
the scenes that I knew had meshes in them as well as running that grass 
macro (uses a mesh) from the Gilles cloud tutorial with a few million blades 
to see if there was too many triangles.
Thanks in advance,
Jonathan
red### [at] redmasqcom


AMD 64 Dual Core 1GB RAM Windows XP Home
    (Shame I don't have the 64bit version or better
    yet find where I put that Slackware disc, though of course I'd have to 
run two instances of 3.6)
PovRay 3.7.0.beta.12a
PovRay 3.6.1a.icl8.win32
PoseRay 3.8.18.390


Post a reply to this message

From: Lance Birch
Subject: Re: PovRay 3.7.0beta.12a
Date: 15 Apr 2006 08:15:31
Message: <4440e3e3@news.povray.org>
"Jonathan" <red### [at] redmasqcom> wrote in message
news:44406a85@news.povray.org...
> I've tried the 12a beta today, most of my renders come out as expected,
> however, scenes imported from Daz via PoseRay regardless of settings or ini
> file just sits after the parse, I checked the processor load and memory
> during several of the tests. Processor load goes back down to 50% and memory
> used down to 300MB immediatly after parse (it will incline close to 900MB on
> most of my more complex scenes) instead of staying high until end of render.
> Theories anyone? BTW 3.6 has no trouble rendering the scenes, just takes
> twice as long (single thread) Once I find my copy of Blender I'll try
> importing an OBJ from it instead to see if there is a difference. I did run
> the scenes that I knew had meshes in them as well as running that grass
> macro (uses a mesh) from the Gilles cloud tutorial with a few million blades
> to see if there was too many triangles.
> Thanks in advance,
> Jonathan
> red### [at] redmasqcom
>
>
> AMD 64 Dual Core 1GB RAM Windows XP Home
>     (Shame I don't have the 64bit version or better
>     yet find where I put that Slackware disc, though of course I'd have to
> run two instances of 3.6)
> PovRay 3.7.0.beta.12a
> PovRay 3.6.1a.icl8.win32
> PoseRay 3.8.18.390

Are you running with +B2?  If so turn it off and then try.  Also try running it
with /THREADS 1 and see if it renders then.  See if any combinations work and
post back with the results to help narrow it down :)

Lance.

thezone - thezone.firewave.com.au


Post a reply to this message

From: Jonathan
Subject: Re: PovRay 3.7.0beta.12a
Date: 15 Apr 2006 19:41:21
Message: <444184a1@news.povray.org>
> Are you running with +B2?  If so turn it off and then try.  Also try 
> running it
> with /THREADS 1 and see if it renders then.  See if any combinations work 
> and
> post back with the results to help narrow it down :)
>
> Lance.
>
> thezone - thezone.firewave.com.au
>
>

Wasn't running with +B2, tried with /THREADS 1 same result. For the heck of 
it tried it with +B2 same thing.

Thanks,
Jonathan
red### [at] redmasqcom


Post a reply to this message

From: Jonathan
Subject: Re: PovRay 3.7.0beta.12a
Date: 21 Apr 2006 23:04:26
Message: <44499d3a@news.povray.org>
Update:
I managed to get a copy of blender and imported the mesh and reexported the 
mesh back into PoseRay and rendered. Worked fine expect for my losing all my 
groups and UV mappngs. I assume the next course would be to break up the 
groups before exporting and recombine and map in poseray to see if the 
problem repeats itself. Assuming that it would provide ANY valuable data at 
all.

Thanks,
Jonathan
red### [at] redmasqcom


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.