 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hello all!
I'm back on POV-ray 3.6.1 for windows, trying to render a high res scene of
2 molecules overlaid on top each other. Unbelievably, the .pov file VMD
generated is 1.3GB! I've tried it in both POV-ray and MegaPOV, but no image
file is generated. It just says:
Total Scene Processing Times
Parse Time: 0 hours 0 minutes 0 seconds (0 seconds)
Photon Time: 0 hours 0 minutes 0 seconds (0 seconds)
Cloth Time: 0 hours 0 minutes 0 seconds (0 seconds)
Mechsim Time: 0 hours 0 minutes 0 seconds (0 seconds)
Render Time: 0 hours 9 minutes 44 seconds (584 seconds)
Postpr. Time: 0 hours 0 minutes 0 seconds (0 seconds)
Total Time: 0 hours 9 minutes 44 seconds (584 seconds)
CPU time used: kernel 8.94 seconds, user 275.69 seconds, total 284.63
seconds
POV-Ray finished
I've tested the program with other scenes and it works fine. Does anyone
know what I can do to fix this? I have 1GB RAM and various free GBs of hard
disk space over many partitions.
Thanks in advance!
Uplah
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Wasn't it Uplah who wrote:
>Hello all!
>
>I'm back on POV-ray 3.6.1 for windows, trying to render a high res scene of
>2 molecules overlaid on top each other. Unbelievably, the .pov file VMD
>generated is 1.3GB! I've tried it in both POV-ray and MegaPOV, but no image
>file is generated. It just says:
>
>Total Scene Processing Times
> Parse Time: 0 hours 0 minutes 0 seconds (0 seconds)
> Photon Time: 0 hours 0 minutes 0 seconds (0 seconds)
> Cloth Time: 0 hours 0 minutes 0 seconds (0 seconds)
> Mechsim Time: 0 hours 0 minutes 0 seconds (0 seconds)
> Render Time: 0 hours 9 minutes 44 seconds (584 seconds)
> Postpr. Time: 0 hours 0 minutes 0 seconds (0 seconds)
> Total Time: 0 hours 9 minutes 44 seconds (584 seconds)
>CPU time used: kernel 8.94 seconds, user 275.69 seconds, total 284.63
>seconds
>
>POV-Ray finished
>
>I've tested the program with other scenes and it works fine. Does anyone
>know what I can do to fix this? I have 1GB RAM and various free GBs of hard
>disk space over many partitions.
A parse time of 0 seconds suggests to me that POV isn't parsing 1.3Gb of
data. Even on a pretty fast machine, POV should take quite a while to
perform the parsing of anything that big.
Rather than looking at just the timings, take a look at the "Scene
Statistics" to see how many objects POV thinks there are in the scene.
If it says there are 0 finite objects, then it didn't find your
molecules. If is says there are 0 light sources then your scene appears
may empty because you can't see anything in the dark. Another
possibility (of many) is that VMD might not have pointed the camera
towards the molecules.
--
Mike Williams
Gentleman of Leisure
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hiya,
That's what's strange. I know the lights are in the right position because I
put them in myself (took 2hrs to load the text and then save it...). I also
put the camera in by hand too, although it may either be too close to the
molecule, or even inside it, but I wanted to find out by doing a quick
render of it first...
The statistics you normally see at the end of a render, doesn't appear when
I do it for this huge file...
While I'm here, can anyone recommend a good text editor that can handle huge
files like this?
Hold on, have just tried rendering the file again and I've now got an error
message:
Assertion: line 2190 of file povms.cpp
POVMSObject_Set failed, out of memory
Press Cancel to stop rendering
So this seems to be a memory problem. Is this anything to do with swap
space, or do I have to get more RAM?
Cheers!
Uplah
Mike Williams <nos### [at] econym demoncouk> wrote:
> Wasn't it Uplah who wrote:
> >Hello all!
> >
> >I'm back on POV-ray 3.6.1 for windows, trying to render a high res scene of
> >2 molecules overlaid on top each other. Unbelievably, the .pov file VMD
> >generated is 1.3GB! I've tried it in both POV-ray and MegaPOV, but no image
> >file is generated. It just says:
> >
> >Total Scene Processing Times
> > Parse Time: 0 hours 0 minutes 0 seconds (0 seconds)
> > Photon Time: 0 hours 0 minutes 0 seconds (0 seconds)
> > Cloth Time: 0 hours 0 minutes 0 seconds (0 seconds)
> > Mechsim Time: 0 hours 0 minutes 0 seconds (0 seconds)
> > Render Time: 0 hours 9 minutes 44 seconds (584 seconds)
> > Postpr. Time: 0 hours 0 minutes 0 seconds (0 seconds)
> > Total Time: 0 hours 9 minutes 44 seconds (584 seconds)
> >CPU time used: kernel 8.94 seconds, user 275.69 seconds, total 284.63
> >seconds
> >
> >POV-Ray finished
> >
> >I've tested the program with other scenes and it works fine. Does anyone
> >know what I can do to fix this? I have 1GB RAM and various free GBs of hard
> >disk space over many partitions.
>
> A parse time of 0 seconds suggests to me that POV isn't parsing 1.3Gb of
> data. Even on a pretty fast machine, POV should take quite a while to
> perform the parsing of anything that big.
>
> Rather than looking at just the timings, take a look at the "Scene
> Statistics" to see how many objects POV thinks there are in the scene.
> If it says there are 0 finite objects, then it didn't find your
> molecules. If is says there are 0 light sources then your scene appears
> may empty because you can't see anything in the dark. Another
> possibility (of many) is that VMD might not have pointed the camera
> towards the molecules.
>
> --
> Mike Williams
> Gentleman of Leisure
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Uplah wrote:
> Hiya,
>
> That's what's strange. I know the lights are in the right position because I
> put them in myself (took 2hrs to load the text and then save it...). I also
> put the camera in by hand too, although it may either be too close to the
> molecule, or even inside it, but I wanted to find out by doing a quick
> render of it first...
>
> The statistics you normally see at the end of a render, doesn't appear when
> I do it for this huge file...
>
> While I'm here, can anyone recommend a good text editor that can handle huge
> files like this?
I seems to that seperating the scene and the molecule object would be
much easier that editing the big 1.3G file.
You could write a small scene that contains just
the camera description and light sources and include the
moelcule object from a second file via a #include "molecule.inc"
statement somewhere in the the scene.
This way you could avoid opening the big file.
Sebastian
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Uplah nous apporta ses lumieres ainsi en ce 2004-12-06 07:37... :
>Hello all!
>
>I'm back on POV-ray 3.6.1 for windows, trying to render a high res scene of
>2 molecules overlaid on top each other. Unbelievably, the .pov file VMD
>generated is 1.3GB! I've tried it in both POV-ray and MegaPOV, but no image
>file is generated. It just says:
>
>Total Scene Processing Times
> Parse Time: 0 hours 0 minutes 0 seconds (0 seconds)
> Photon Time: 0 hours 0 minutes 0 seconds (0 seconds)
> Cloth Time: 0 hours 0 minutes 0 seconds (0 seconds)
> Mechsim Time: 0 hours 0 minutes 0 seconds (0 seconds)
> Render Time: 0 hours 9 minutes 44 seconds (584 seconds)
> Postpr. Time: 0 hours 0 minutes 0 seconds (0 seconds)
> Total Time: 0 hours 9 minutes 44 seconds (584 seconds)
>CPU time used: kernel 8.94 seconds, user 275.69 seconds, total 284.63
>seconds
>
>POV-Ray finished
>
>I've tested the program with other scenes and it works fine. Does anyone
>know what I can do to fix this? I have 1GB RAM and various free GBs of hard
>disk space over many partitions.
>
>Thanks in advance!
>
>Uplah
>
>
>
>
It must generate the molecule as a mesh. Try reducing the persision:
less steps = less triangles = smaller file. Can you alter the presision
of the numbers? You probably don't need 6 to 9 digits presision, 4 may
be enough, or even 3.
This may result in some facing/bumpiness, but if it may remain to an
acceptable level.
Alain
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Uplah wrote:
> While I'm here, can anyone recommend a good text editor that can handle huge
> files like this?
For Windows? Check out NoteTab (www.notetab.com).
There are three versions:
Lite Free
Std $9.95
Pro $19.95 (US)
In looking quickly at the docs right now, I can't find it, but I'm sure
I've seen it documented that it can handle up to 2GB files. (Never had
the occasion to find out) ;-) And virtually unlimited number of open
files.
I use the Pro version, and find it to be a really excellent editor.
-=- Larry -=-
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
