Hello,

I always put all the new patches (the .exe) in the same directory 
(.....\povray for ...\bin) and I made a shortcut on my desktop for 
each .exe and all work fine! There are just something annoying:
Suppose I open (for example) the offcial povray, if I close it and 
open after Megapov or Uvpov etc..., the editor show me the "about..."
(exactly as the first time you open povray on your computer).

povray 3.1g for windows
Win98

Fabian.
 

Matthew Bennett wrote:
> 
> Is it possible to use the newest editor version with the (apparently) older
> version supplied with the MegaPatch?  The 3.1g editor fixes numerous display
> glitches for me, that are still present on the MegaPatch version :(
> 
> Thanks
> 
> /\/\/\//

Post a reply to this message

Humm.. thanks for all your help - but when the cmax101.dll file is in the
same directory as the megapov.exe, or even if I simply copy the megapov.exe
into the /bin directory, I still get the older bugs :(

Perhaps it's not the codemax editor part itself that's causing the problem,
but some older code for some other part of the POV win32 GUI.

For example - a fix was made in later versions that meant the timer stopped
when you pause during a render.  When I run the official pvengine.exe, this
is the case - and no graphics glitches too (which I believe where fixed
around the same time as the timer).  However, when I run the megapov.exe (or
indeed the superpatch) the older GUI runs, complete with gfx glitchs and the
timer ~continues~ when a rendering is paused (showing it's an earlier
version).


Any further ideas?  Could some of those who have kindly replied also see if
their timer stops during pausing too, when running patched POVs?


Thanks :)


/\/\/\//

Post a reply to this message

"Fabian Brau" <fab### [at] umhacbe> wrote in message
news:385609C2.B218441A@umh.ac.be...
> There are just something annoying:
> Suppose I open (for example) the offcial povray, if I close it and
> open after Megapov or Uvpov etc..., the editor show me the "about..."
> (exactly as the first time you open povray on your computer).

I know, I've learned to live with it now.  Wonder what is telling it the
executable is different?  Something external to the executables themselves
perhaps?

Bob

Post a reply to this message

I suppose that someone from the team know the solution ;).
But I have learned to live with it too! This is not so terrible :).
I prefer that the team make a good povray 3.5 with a good help file 
instead of find this problem (because when 3.5 will be there, there 
will be only one .exe in my bin directory :)).

Fabian.

omniVERSE wrote:
> 
> "Fabian Brau" <fab### [at] umhacbe> wrote in message
> news:385609C2.B218441A@umh.ac.be...
> > There are just something annoying:
> > Suppose I open (for example) the offcial povray, if I close it and
> > open after Megapov or Uvpov etc..., the editor show me the "about..."
> > (exactly as the first time you open povray on your computer).
> 
> I know, I've learned to live with it now.  Wonder what is telling it the
> executable is different?  Something external to the executables themselves
> perhaps?
> 
> Bob

Post a reply to this message

Matthew Bennett <ben### [at] btinternetcom> wrote...
> Humm.. thanks for all your help - but when the cmax101.dll file is in the
> same directory as the megapov.exe, or even if I simply copy the
megapov.exe
> into the /bin directory, I still get the older bugs :(
>
> Perhaps it's not the codemax editor part itself that's causing the
problem,
> but some older code for some other part of the POV win32 GUI.

True.  The source code to the 3.1g interface is not available.

> For example - a fix was made in later versions that meant the timer
stopped
> when you pause during a render.  When I run the official pvengine.exe,
this
> is the case - and no graphics glitches too (which I believe where fixed
> around the same time as the timer).  However, when I run the megapov.exe
(or
> indeed the superpatch) the older GUI runs, complete with gfx glitchs and
the
> timer ~continues~ when a rendering is paused (showing it's an earlier
> version).

Graphics glitches I think are a problem caused by compiling with VC++
instead of with Watcom.

The timer stopping was fixed in the 3.1g interface, but that source is not
available to the public.

-Nathan

Post a reply to this message

Fabian Brau wrote in message <385609C2.B218441A@umh.ac.be>...
>Hello,
>
>I always put all the new patches (the .exe) in the same directory
>(.....\povray for ...\bin) and I made a shortcut on my desktop for
>each .exe and all work fine! There are just something annoying:
>Suppose I open (for example) the offcial povray, if I close it and
>open after Megapov or Uvpov etc..., the editor show me the "about..."
>(exactly as the first time you open povray on your computer).


The cause of this is that POV-Win is set to show you this dialog box if it
has been more that 24 hours since you last used POV-Ray.  Because of how the
different versions interact, however, the record of when you last used
POV-Ray sometimes gets lost.

Mark

Post a reply to this message

Nathan Kopp <Nat### [at] Koppcom> wrote in message
news:38570d59@news.povray.org...
<snip>
> Graphics glitches I think are a problem caused by compiling with VC++
> instead of with Watcom.
>
> The timer stopping was fixed in the 3.1g interface, but that source is not
> available to the public.

Ahh, that'll be it then.  Thanks for the clarification :)

/\/\/\//

Post a reply to this message

On Tue, 14 Dec 1999 22:40:38 -0500, Nathan Kopp wrote:
>Matthew Bennett <ben### [at] btinternetcom> wrote...
>> Humm.. thanks for all your help - but when the cmax101.dll file is in the
>> same directory as the megapov.exe, or even if I simply copy the
>megapov.exe
>> into the /bin directory, I still get the older bugs :(
>>
>> Perhaps it's not the codemax editor part itself that's causing the
>problem,
>> but some older code for some other part of the POV win32 GUI.
>
>True.  The source code to the 3.1g interface is not available.

3.1g Windows source is available, but I'm not sure it was ever 
announced.

From the FTP site:

ftp> dir
200 PORT command successful.
150 Opening ASCII mode data connection for file list.
[...]
-rw-r--r--   1 povteam  team      5203586 Jul  6 23:54 povwin3.exe
-rw-r--r--   1 povteam  team      1472833 Aug 28 11:41 povwin_s.zip
[...]

Note that the date is after the date of the 3.1g executable.  If you
download it, you should find that it's the 3.1g code (I did, and it is.)

-- 
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html

Post a reply to this message

Ron Parker wrote:

> >True.  The source code to the 3.1g interface is not available.

 
> 3.1g Windows source is available, but I'm not sure it was ever
> announced.
> Note that the date is after the date of the 3.1g executable.  If you
> download it, you should find that it's the 3.1g code (I did, and it is.)

I announced it on Aug, 28, 1999 in the programming group where upon you
informed me that both the SuperPatch and UVPov were both based upon the
source for v3.1g where upon I then said "Arf garble hendershnap @#$?!!!"
and you then replied "Exactly".

-- 
Wishing you Seasons Greetings, A Merry Christmas, and A Happy New Year !
Ken Tyler -  1200+ 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

On Wed, 15 Dec 1999 05:57:50 -0800, Ken wrote:
>
>
>Ron Parker wrote:
>
>> >True.  The source code to the 3.1g interface is not available.
>
> 
>> 3.1g Windows source is available, but I'm not sure it was ever
>> announced.
>> Note that the date is after the date of the 3.1g executable.  If you
>> download it, you should find that it's the 3.1g code (I did, and it is.)
>
>I announced it on Aug, 28, 1999 in the programming group where upon you
>informed me that both the SuperPatch and UVPov were both based upon the
>source for v3.1g where upon I then said "Arf garble hendershnap @#$?!!!"
>and you then replied "Exactly".

Actually, I believe I informed you that they both worked with the 3.1g 
editor, despite being based on 3.1a or 3.1d Windows source, though upon
reading my post now I see that that might not have been clear. The last 
superpatch is still based on 3.1d source, too, though I've had the 3.1g 
public source for a while now.

You can tell an unofficial 3.1g build from any other build because by 
default the icon is cyan instead of white.

-- 
These are my opinions.  I do NOT speak for the POV-Team.
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html

Post a reply to this message