 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I moved to a new system AMD 800 Duron on an Epox 8kta3 MB with the latest
BIOS, 128 Megs PC 100 RAM. Partial renderings with scenes that used to
render fine now crash to a black screen. No error message is reported, no
warning, just "black screen." The scene I have been working with involves
rather large models, so I couldn't post a scene very easily. I will attempt
to find a similar situation, but you can probably see why I might shy away
from too much of it.
The scene that is crashing has an H_F, sky_sphere, cloud layer, water, and
aircraft (of course), with several very 'deep' textures and materials,
motion_blur, etc. I'm not sure as to what exactly I should be concentrating
on to replicate the problem.
If anyone has a suggestion as to what to try I am all ears.
Grim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3b02696f$1@news.povray.org> , "GrimDude" <gri### [at] netzero com>
wrote:
> If anyone has a suggestion as to what to try I am all ears.
Re-install your system and the re-install POV-Ray.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3b026dff$1@news.povray.org...
>
> Re-install your system and the re-install POV-Ray.
Drastic :-)
Is that still the Windows platform? If so, black screen no errors sounds
very fundamentally wrong, like a CPU error perhaps. Could it be that the
Duron has trouble with the MSVC Win32 (Pentium II optimized) build of
POV-Ray? Seems plausible anyway.
What's the video in that? Onboard or card? I ask out of curiosity but maybe
it's related to handling the output to screen somehow instead, which again
would be very low-level since a error message should have been shown
otherwise.
Bob H.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I just realized, and came here, because I failed to post video information.
GeForce 2 MX AGP (card).
I am beginning to wonder if I will have to buy an Intel machine just to
render with. This machine rocks for gaming, and rendering too, but if it's
going to cause problems with Pov I'll need another machine. :(
Grim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
GrimDude <gri### [at] netzerocom> wrote in message
news:3b028c02@news.povray.org...
> I am beginning to wonder if I will have to buy an Intel machine just to
> render with. This machine rocks for gaming, and rendering too, but if it's
> going to cause problems with Pov I'll need another machine. :(
>
How big is the scene? If it zips small enough to email (<5MB), send it to me
and
I'll try it on a pentium2 and an athlon, see if it crashes on either.
Gail
*************************************************************************
* gsh### [at] monotixcoza * Step into the abyss, *
* http://www.rucus.ru.ac.za/~gail/ * and let go. Babylon 5 *
*************************************************************************
* The difficult we do immediately, the impossible takes a little longer *
*************************************************************************
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
GrimDude <gri### [at] netzerocom> wrote:
: I am beginning to wonder if I will have to buy an Intel machine just to
: render with. This machine rocks for gaming, and rendering too, but if it's
: going to cause problems with Pov I'll need another machine. :(
I upgraded my old P-II 350MHz to an Athlon 1.2GHz and I haven't found
any problems whatsoever. I didn't even have to re-install anything.
POV-Ray works like a charm.
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Are you sure that you are not suffering from CPU temperature problems?
This can be sometimes the cause for crashes with CPU-intensive programs
(such as POV-Ray). The CPU gets warmer when it's very busy.
Watch the CPU temperature with a monitoring program such as
http://web.bham.ac.uk/jst829/mbprobe/
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp <war### [at] tagpovrayorg> wrote in message news:3b0291c4@news.povray.org...
> Are you sure that you are not suffering from CPU temperature problems?
> This can be sometimes the cause for crashes with CPU-intensive programs
> (such as POV-Ray). The CPU gets warmer when it's very busy.
> Watch the CPU temperature with a monitoring program such as
> http://web.bham.ac.uk/jst829/mbprobe/
>
Thanks, I was looking for something like that earlier today.
Gail
*************************************************************************
* gsh### [at] monotixcoza * Step into the abyss, *
* http://www.rucus.ru.ac.za/~gail/ * and let go. Babylon 5 *
*************************************************************************
* The difficult we do immediately, the impossible takes a little longer *
*************************************************************************
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3b027cb0$1@news.povray.org> , "Bob H." <omn### [at] msncom>
wrote:
> Is that still the Windows platform? If so, black screen no errors sounds
> very fundamentally wrong, like a CPU error perhaps. Could it be that the
> Duron has trouble with the MSVC Win32 (Pentium II optimized) build of
> POV-Ray? Seems plausible anyway.
> What's the video in that? Onboard or card? I ask out of curiosity but maybe
> it's related to handling the output to screen somehow instead, which again
> would be very low-level since a error message should have been shown
> otherwise.
Sorry, neither of these is a possible reason if there is _no_ defect
elsewhere. Screens don't just randomly black out if you call the operating
system, neither has any optimization for any processor something do with it.
Assuming it is not a hardware problem (if the system runs well under load
for a long time if POV-Ray is not running), the problem is most likely some
damaged software install. The solution to these if running Windows is to
re-install, as well as update all drivers, bios, and add all operating
system bug fixes that are not buggy themselves per se. however, I do not
think the problem can be found without physical access, i.e. it cannot be
found in this newsgroup except someone had the same problem before and found
a solution.
Computer hardware and software are no _magic_ boxes - if there is a problem
there is a specific cause and a (not necessarily obvious) solution.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3b027cb0$1@news.povray.org> , "Bob H." <omn### [at] msncom>
wrote:
>> Re-install your system and the re-install POV-Ray.
>
> Drastic :-)
Windows ;-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
