POV-Ray : Newsgroups : povray.unofficial.patches : post_process {} broken? Server Time
2 Nov 2024 07:23:19 EDT (-0400)
  post_process {} broken? (Message 1 to 10 of 10)  
From: Bob Hughes
Subject: post_process {} broken?
Date: 31 Jan 2000 04:48:41
Message: <38955a79@news.povray.org>
First thing I'm going to say is thankyou to everyone involved in the existence
of MegaPov 0.4.  I can't begin to show my appreciation, it's fully 10 times more
than POV-Ray has ever been previously... dare I say 100 times.  Yes, I can.
Even 1000 times more a raytracer than ever before.
With that obsequious banter aside, now I must tell of the problem I encountered.
First thing, and only thing, I've tried so far is 'post_process' and the
rendered Png output file seems to be corrupted somehow.  PSP won't open it,
IrfanView will but guess what?  There isn't any final render like what shows in
the display window within POV!  The post processing isn't there, just the
regular unprocessed image.  Another thing that I have to ask about is what the
*tpn file is for.  I can actually open that in PSP without trouble yet it's
still just the unpostprocessed render too.
Another thing I guess I should point out though I'm uncertain it's a defect or
not, the focal_blur is always in focus from the camera to the distance given
apparently and not a range around the focus point like the camera blur in
official POV does.  Unless I'm mistaken.
Footnote: focal_blur and soft_glow were both used at the same time and I used
radiosity also.  Windows 98SE on PC.

I have taken a look through both the Help and Html files and found no mention of
that Tpn file output (some sort of temporary file I presume).

Hope I've described the situation okay; back to the rendering after I get some
shut-eye.  It's such a thrill already I don't know how I can sleep.
Thanks again everyone  8-}}

Bob
--
omniVerse http://users.aol.com/persistenceofv/all.htm


Post a reply to this message

From: Ken
Subject: Re: post_process {} broken?
Date: 31 Jan 2000 06:09:32
Message: <38956D17.57F850CD@pacbell.net>
Bob Hughes wrote:

> Bob
> --
> omniVerse http://users.aol.com/persistenceofv/all.htm

What's with all of these new address changes of yours?

Do I need to make changes or will the existing links stay the same ?

-- 
Ken Tyler -  1300+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/


Post a reply to this message

From: Bob Hughes
Subject: Re: post_process {} broken?
Date: 31 Jan 2000 14:45:39
Message: <3895e663@news.povray.org>
I'm leaving all the old URLs in place.  I checked your *monstrous link web page
(an incredible 3 minute loading time for me) and found four links leading to my
web space and they are okay.  Also those at www.povray.org.
I was actually trying to do two things, get a simpler signature for here and
also make all of my web spaces accessible through the use of very plain entry
web pages.  Hope it works out.

*in this instance it's a friendly monster

Bob

"Ken" <tyl### [at] pacbellnet> wrote in message
news:38956D17.57F850CD@pacbell.net...
| > Bob
| > --
| > omniVerse http://users.aol.com/persistenceofv/all.htm
|
| What's with all of these new address changes of yours?
|
| Do I need to make changes or will the existing links stay the same ?
|
| --
| Ken Tyler -  1300+ Povray, Graphics, 3D Rendering, and Raytracing Links:
| http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/


Post a reply to this message

From: SamuelT 
Subject: Re: post_process {} broken?
Date: 31 Jan 2000 22:55:53
Message: <38965B7F.55236477@aol.com>
It's broken here too, but it won't give me anything. In fact, it crashes pov when I
try to use it.

Bob Hughes wrote:

> <snip>
>
> Bob
> --
> omniVerse http://users.aol.com/persistenceofv/all.htm

--
Samuel Benge

E-Mail: STB### [at] aolcom

Visit the still unfinished isosurface tutorial: http://members.aol.com/stbenge


Post a reply to this message

From: SamuelT 
Subject: Re: post_process {} broken?
Date: 31 Jan 2000 22:57:15
Message: <38965BD3.507E4FEA@aol.com>
Here's the error message:

MEGAPOV4 caused an invalid page fault in
module KERNEL32.DLL at 0137:bff9a07c.
Registers:
EAX=0370e878 CS=0137 EIP=bff9a07c EFLGS=00000246
EBX=bff79883 SS=013f ESP=0370e874 EBP=0370e8c8
ECX=000000ac DS=013f ESI=00000000 FS=415f
EDX=00000000 ES=013f EDI=00000008 GS=0000
Bytes at CS:EIP:
5e 8b e5 5d c2 10 00 64 a1 00 00 00 00 55 8b ec
Stack dump:
0051a400 c0000005 00000000 00000000 bff9a07c 00000000 bff623e8 03707000 bff63d24
bff79883 004b3229 000009d4 00000002 00515051 bff63d24 bff79883

"SamuelT." wrote:

> It's broken here too, but it won't give me anything. In fact, it crashes pov when I
> try to use it.
>
> Bob Hughes wrote:
>
> > <snip>
> >
> > Bob
> > --
> > omniVerse http://users.aol.com/persistenceofv/all.htm
>
> --
> Samuel Benge
>
> E-Mail: STB### [at] aolcom
>
> Visit the still unfinished isosurface tutorial: http://members.aol.com/stbenge

--
Samuel Benge

E-Mail: STB### [at] aolcom

Visit the still unfinished isosurface tutorial: http://members.aol.com/stbenge


Post a reply to this message

From: Bob Hughes
Subject: Re: post_process {} broken?
Date: 1 Feb 2000 00:59:36
Message: <38967648@news.povray.org>
Did you use the #version unofficial MegaPov 0.4; line at the beginning of the
file?  Just in case you missed that being required but I don't think you can
miss it, POV will tell you and I haven't seen that cause anymore than a warning
message and stop parsing.
Other than that I don't see why you get a complete crash and I don't.  Be sure
not to use less than 1 for your focal_blur radius too (third float value), might
not crash the program but it clips off parts of the render.  Same goes for
soft_glow radius amount.  Less than one pixel, in other words, doesn't do too
well.  Interesting, just not what's intended.
The Png writing along with that unknown (thus far) Tpn file seems to be the
relationship with the problem.  So... anyone know what the Tpn file is from?
Just the post process part?  Thanks for any answers you might have.

Bob

"SamuelT." <STB### [at] aolcom> wrote in message news:38965B7F.55236477@aol.com...
| It's broken here too, but it won't give me anything. In fact, it crashes pov
when I
| try to use it.
|
| Bob Hughes wrote:
|
| > <snip>
| >
| > Bob
| > --
| > omniVerse http://users.aol.com/persistenceofv/all.htm
|
| --
| Samuel Benge
|
| E-Mail: STB### [at] aolcom
|
| Visit the still unfinished isosurface tutorial: http://members.aol.com/stbenge
|
|


Post a reply to this message

From: Bob Hughes
Subject: Re: post_process {} broken?
Date: 1 Feb 2000 01:12:36
Message: <38967954@news.povray.org>
Just an after thought.  Maybe the GUI Priority might interfere somewhat if it's
set to Lowest.

Bob


Post a reply to this message

From: Nathan Kopp
Subject: Re: post_process {} broken?
Date: 1 Feb 2000 15:39:05
Message: <38974469@news.povray.org>
Bob Hughes <omn### [at] hotmailcom?subject=PoV-News:> wrote...
> First thing, and only thing, I've tried so far is 'post_process' and the
> rendered Png output file seems to be corrupted somehow.  PSP won't open
it,
> IrfanView will but guess what?  There isn't any final render like what
shows in
> the display window within POV!  The post processing isn't there, just the
> regular unprocessed image.  Another thing that I have to ask about is what
the
> *tpn file is for.  I can actually open that in PSP without trouble yet
it's
> still just the unpostprocessed render too.

As a work-around, use TGA as your output format instead of PNG.  That TPN
file should not be there (should never have been created).  I'll have to
take a closer look at the PNG code to figure out what is going on.

> Another thing I guess I should point out though I'm uncertain it's a
defect or
> not, the focal_blur is always in focus from the camera to the distance
given
> apparently and not a range around the focus point like the camera blur in
> official POV does.  Unless I'm mistaken.

You're mistaken.  :-)

However, everything within the range (start through start+depth) will be
totally in focus.  Sometimes you have to make the range significantly
shorter in order to get good blurring.  I want to add a fourth parameter,
which is the effect strength (a value of 2.0 would double the blurring).

> I have taken a look through both the Help and Html files and found no
mention of
> that Tpn file output (some sort of temporary file I presume).

That tpn file shouldn't exist.  Maybe it's a temporary file created by the
PNG code, but none of my code creates it directly.

-Nathan


Post a reply to this message

From: Bob Hughes
Subject: Re: post_process {} broken?
Date: 1 Feb 2000 22:29:43
Message: <3897a4a7@news.povray.org>
"Nathan Kopp" <Nat### [at] Koppcom> wrote in message
news:38974469@news.povray.org...

| That tpn file shouldn't exist.  Maybe it's a temporary file created by the
| PNG code, but none of my code creates it directly.

Pretty neat anyway since POV-Ray is actually saying to delete the smaller of the
two files in order to continue with another trace.  At least whatever it's doing
seems to be more than just a Png creation process.  Fascinating stuff to someone
like me, although useless.  Hmm, not entirely useless now that I think about it.
Backup copies of renders maybe?  Oh, btw, the Png isn't always corrupted for
some reason.

Bob


Post a reply to this message

From: SamuelT 
Subject: Re: post_process {} broken?
Date: 2 Feb 2000 00:31:24
Message: <3897C367.2555CAA6@aol.com>
Bob Hughes wrote:

> Did you use the #version unofficial MegaPov 0.4; line at the beginning of the
> file?  Just in case you missed that being required but I don't think you can
> miss it, POV will tell you and I haven't seen that cause anymore than a warning
> message and stop parsing.

Yes, I used it.


>
> Other than that I don't see why you get a complete crash and I don't.  Be sure
> not to use less than 1 for your focal_blur radius too (third float value), might
> not crash the program but it clips off parts of the render.  Same goes for
> soft_glow radius amount.  Less than one pixel, in other words, doesn't do too
> well.  Interesting, just not what's intended.

That's not the problem.

I get strange symbols in the message window, like text that has been layered on top
of itself. By that time, I have no choice but to quit the application. I wish there
was something I could do. the GUI priority is on highest, BTW. I guess I might try
downloading it again. Sigh.

--
Samuel Benge

E-Mail: STB### [at] aolcom

Visit the still unfinished isosurface tutorial: http://members.aol.com/stbenge


Post a reply to this message

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