povray.macintosh message digest

[jr] Re: not saving [63 days and 51 minutes ago]

Mon, 16 Feb 2026 08:50:00 GMT

hi,

"Franz von Dardel" <dar### [at] orangefr> wrote:
> "jr" <cre### [at] gmailcom> wrote:
> > "Franz von Dardel" <dar### [at] orangefr> wrote:
> > > Using POVRay 3.7.0.x
> > > When I use "not saving" (Image Type Don't Save Image), rendering is OK but
> > > (obviously) the image is not saved.  When I use another Image Type (e.g. PNG) I
> > > get the message "Cannot create render state output file."
> > > Where is the mistake?
> >
> > you wrote about having this problem a while ago, one reply to your original post
> > was by the (Apple stuff) maintainer, did you see/read it ?
> > <https://news.povray.org/69613afe%40news.povray.org>
>
> Yes, I wrote about the problem in January, but at that time I did not realise
> that the option "Don't Save Image" would work, while selecting for instance
> "PNG" would produce the message "Cannot create render state output file.". Why
> is ist so, and what can I do to correct the problem?

I have far too little info, so only can speculate.  (and I do not use an UI
version of POV-Ray).  here, on a GNU/Linux machine, there are two files which
control where POV-Ray can read from and write to, both named 'povray.conf'.  one
is global, the other will be in your user's directory (here '~/.povray/3.7/').
I'd start with checking/customising those.


regards, jr.

[Franz von Dardel] Re: not saving [63 days 17 hours and 31 minutes ago]

Sun, 15 Feb 2026 16:10:00 GMT

"jr" <cre### [at] gmailcom> wrote:
> "Franz von Dardel" <dar### [at] orangefr> wrote:
> > Using POVRay 3.7.0.x
> > When I use "not saving" (Image Type Don't Save Image), rendering is OK but
> > (obviously) the image is not saved.  When I use another Image Type (e.g. PNG) I
> > get the message "Cannot create render state output file."
> > Where is the mistake?
>
> you wrote about having this problem a while ago, one reply to your original post
> was by the (Apple stuff) maintainer, did you see/read it ?
> <https://news.povray.org/69613afe%40news.povray.org>
>
>
> regards, jr.

Yes, I wrote about the problem in January, but at that time I did not realise
that the option "Don't Save Image" would work, while selecting for instance
"PNG" would produce the message "Cannot create render state output file.". Why
is ist so, and what can I do to correct the problem?

[jr] Re: not saving [66 days 18 hours and 51 minutes ago]

Thu, 12 Feb 2026 14:50:00 GMT

"Franz von Dardel" <dar### [at] orangefr> wrote:
> Using POVRay 3.7.0.x
> When I use "not saving" (Image Type Don't Save Image), rendering is OK but
> (obviously) the image is not saved.  When I use another Image Type (e.g. PNG) I
> get the message "Cannot create render state output file."
> Where is the mistake?

you wrote about having this problem a while ago, one reply to your original post
was by the (Apple stuff) maintainer, did you see/read it ?
<https://news.povray.org/69613afe%40news.povray.org>

regards, jr.

[Franz von Dardel] not saving [66 days 22 hours and 1 minute ago]

Thu, 12 Feb 2026 11:40:00 GMT

Using POVRay 3.7.0.x
When I use "not saving" (Image Type Don't Save Image), rendering is OK but
(obviously) the image is not saved.  When I use another Image Type (e.g. PNG) I
get the message "Cannot create render state output file."
Where is the mistake?

[Yvo Smellenbergh] Re: POV-Ray 3.8 and 3.7.0.9 update available [82 days 19 hours and 2 minutes ago]

Tue, 27 Jan 2026 14:39:11 GMT

On 2026-01-27 08:54:32 +0000, kurtz le pirate said:

> On 11/01/2026 15:28, yvo (DOT) s (AT) gmx.net wrote:
>> Please visit:
>> 
>> https://povrayunofficial.wordpress.com
>> 
>> 
>> Fixed OpenEXR output, updated Zlib, LibPNG, LibTiff and LibJPEG to the 
>> latest versions.
>> 
>> Fixed some minor bugs in the GUI.
>> 
>> 
>> Both versions are Intel and Apple Silion (universal binaries).
>> 
>> Runs on BigSur (11) and later, older system versions are no longer supported.
>> 
>> 
>> Best regards,
> 
> 
> Good news. Thanks again Yvo.
> 
> A little question : You say â€œApple siliconâ€ only,
but what about the 
> M1, M2, M3, and M4 in terms of code?
> 
> Does XCode automatically optimize and adapt?c

POV-Ray is a universal binary, so it is not limited to â€œApple
Siliconâ€ 
only, but supports both Intel and Apple Silicon.
There are no specific compiler options used per CPU type (such as 
-mcpu=apple-m1 or -mcpu=apple-m2).
Using such options could cause POV-Ray to no longer work on older Apple 
Silicon chips.
Moreover, any performance gain would be minimal.
-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


https://povrayunofficial.wordpress.com
E-mail: yvo(DOT)s(AT)gmx.net

[kurtz le pirate] Re: Tahoe 26.1 [83 days and 42 minutes ago]

Tue, 27 Jan 2026 08:59:30 GMT

On 09/01/2026 18:29, yvo (DOT) s (AT) gmx.net wrote:

> Hi,
> 
> 
> Is your issue solved?
> I had exactly the same issue under Tahoe. It was related to the option 
> in the Preferences panel >> Misc tab, â€œRedirect All Output Images
To 
> This Folderâ€. The path to the folder was incorrect.
> The path was wrong; for some reason my output folder was located 
> somewhere else.
> 
> It is also often related to permissions, so in any case check whether 
> the location where the file needs to be written is available and that 
> you have the correct permissions.
> 
> If you are not using the option in the Misc tab, check where the input 
> file is located; the output will then be written to that same location.
> 
> I also see that you are using version 3.8.0-alpha.9606898.unofficial, 
> which comes from the site http://megapov.inetart.net/ 
> povrayunofficial_mac/ <http://megapov.inetart.net/povrayunofficial_mac/ 
>  >. This is a very old version.
> Only use the newer versions that you can find here: https:// 
> povrayunofficial.wordpress.com <https://povrayunofficial.wordpress.com/>



Try creating a "POV" folder in your home directory and not in 
Application folder.

Put program on it and try to render.
Of course, set correct paths in Preferences -> System Include.





-- 
kurtz le pirate
compagnie de la banquise

[kurtz le pirate] Re: POV-Ray 3.8 and 3.7.0.9 update available [83 days and 46 minutes ago]

Tue, 27 Jan 2026 08:54:32 GMT

On 11/01/2026 15:28, yvo (DOT) s (AT) gmx.net wrote:
> Please visit:
> 
> https://povrayunofficial.wordpress.com
> 
> 
> Fixed OpenEXR output, updated Zlib, LibPNG, LibTiff and LibJPEG to the 
> latest versions.
> 
> Fixed some minor bugs in the GUI.
> 
> 
> Both versions are Intel and Apple Silion (universal binaries).
> 
> Runs on BigSur (11) and later, older system versions are no longer 
> supported.
> 
> 
> Best regards,


Good news. Thanks again Yvo.

A little question : You say â€œApple siliconâ€ only,
but what about the M1, 
M2, M3, and M4 in terms of code?

Does XCode automatically optimize and adapt?





-- 
kurtz le pirate
compagnie de la banquise

[Yvo Smellenbergh] POV-Ray 3.8 and 3.7.0.9 update available [98 days 19 hours and 12 minutes ago]

Sun, 11 Jan 2026 14:28:42 GMT

Please visit:
https://povrayunofficial.wordpress.com

Fixed OpenEXR output, updated Zlib, LibPNG, LibTiff and LibJPEG to the 
latest versions.
Fixed some minor bugs in the GUI.

Both versions are Intel and Apple Silion (universal binaries).
Runs on BigSur (11) and later, older system versions are no longer supported.

Best regards,


-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


https://povrayunofficial.wordpress.com
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Re: Tahoe 26.1 [100 days 16 hours and 11 minutes ago]

Fri, 9 Jan 2026 17:29:34 GMT

On 2026-01-04 10:28:54 +0000, Franz von Dardel said:

> kurtz le pirate <kur### [at] freefr> wrote:
>> On 04/12/2025 14:50, Franz von Dardel wrote:
>>> Since I moved my MacOS to Tahoe, POVRay does not work any more. I am constantly
>>> getting the message: Cannot create render state output file. Does anyone have a
>>> fix for this?
>>> 
>> 
>> 
>> For testing purposes, you can give POV full access to the disk.
>> 
>> 
>> System settings -> Privacy & Security -> Full Disk Access, then add POVRay.
>> 
>> 
>> --
>> kurtz le pirate
>> compagnie de la banquise
> 
> I have tried this, but still no success. I am using
> POV-Ray v3,8,0-alpha.9606898.unofficial

Hi,

Is your issue solved?
I had exactly the same issue under Tahoe. It was related to the option 
in the Preferences panel >> Misc tab, â€œRedirect All Output Images To 
This Folderâ€. The path to the folder was incorrect.
The path was wrong; for some reason my output folder was located 
somewhere else.
It is also often related to permissions, so in any case check whether 
the location where the file needs to be written is available and that 
you have the correct permissions.
If you are not using the option in the Misc tab, check where the input 
file is located; the output will then be written to that same location.
I also see that you are using version 3.8.0-alpha.9606898.unofficial, 
which comes from the site 
http://megapov.inetart.net/povrayunofficial_mac/. This is a very old 
version.
Only use the newer versions that you can find here: 
https://povrayunofficial.wordpress.com

-- 
Yvo

-- 
-------------------------------------------------------------------------------------------

https://povrayunofficial.wordpress.com
E-mail: yvo(DOT)s(AT)gmx.net

[Franz von Dardel] Re: Tahoe 26.1 [105 days 18 hours and 11 minutes ago]

Sun, 4 Jan 2026 15:30:00 GMT

kurtz le pirate <kur### [at] freefr> wrote:
> On 04/12/2025 14:50, Franz von Dardel wrote:
> > Since I moved my MacOS to Tahoe, POVRay does not work any more. I am constantly
> > getting the message: Cannot create render state output file. Does anyone have a
> > fix for this?
> >
>
>
> For testing purposes, you can give POV full access to the disk.
>
>
> System settings -> Privacy & Security -> Full Disk Access, then add POVRay.
>
>
> --
> kurtz le pirate
> compagnie de la banquise

I have tried this, but still no success. I am using
POV-Ray v3,8,0-alpha.9606898.unofficial

[Yvo Smellenbergh] Re: POV-Ray 3.8.0 beta 2, 3.7.0.9 Universal bina... [106 days and 41 minutes ago]

Sun, 4 Jan 2026 09:00:03 GMT

On 2025-12-29 12:12:07 +0000, Cousin Ricky said:

> Yvo Smellenbergh <E-mail: yvo(DOT)s(AT)gmx.net> wrote:
>> Both versions run on system 10.9.5 and later, Intel and Apple Silicon (M1).
>> These are universal binaries.
>> I have compiled these versions for myself but may as well share them
>> with those interested.
> 
> There is a report that your 3.8.0 beta 2 has no EXR capability.  Could you
> please check that?  If this is indeed the case, could you please check that the
> OpenEXR *developer* library is installed on your system?  I know from 
> experience
> that POV-Ray will compile cleanly on GNU/Linux with the EXR and SDL libraries
> missing, and it may be the same on the Mac.
> 
> I suspect your 3.7.0.9 may also have the same omission.

EXR has been implemented; all features of the official version have 
been implemented, and the file format can be selected in the output 
pop-up.
However, due to a small error in the project, EXR does not work as expected.
I will make a new version available in one of the coming days in which 
it works properly, for both the 3.8 version and the 3.7 version.
I just need to make sure that everything works on at least Ventura. 
Moreover, I am no longer actively working on my version of POV-Ray for 
Mac, although I do try to keep the project up to date.
I will post a message as soon as they are available.
Please use only the website https://povrayunofficial.wordpress.com.
The site http://megapov.inetart.net/povrayunofficial_mac/ is outdated, 
but I am unable to remove it. The person who made it available for us 
can no longer be reached, and my password is no longer active :-(.
To avoid any misunderstandings: for my version of POV-Ray, no libraries 
(OpenEXR, Boost, etc.) need to be installed on your Mac. All required 
files are included in the project and in POV-Ray itself.

-- 
Yvo

-- 
-------------------------------------------------------------------------------------------

https://povrayunofficial.wordpress.com
E-mail: yvo(DOT)s(AT)gmx.net

[William F Pokorny] Re: building povray on mac [106 days 13 hours and 18 minutes ago]

Sat, 3 Jan 2026 20:23:04 GMT

On 1/3/26 12:15, kurtz le pirate wrote:
> In which file(s) should this option be added?

Something like:

./configure COMPILED_BY="wfp" CXXFLAGS="-fno-finite-math-only"

should work to add the compiler flag for official POV-Ray source releases.

Bill P.

[kurtz le pirate] Re: building povray on mac [106 days 16 hours and 25 minutes ago]

Sat, 3 Jan 2026 17:15:47 GMT

On 03/01/2026 17:09, William F Pokorny wrote:
> On 1/2/26 10:59, kurtz le pirate wrote:
>> Not everything is perfect, but POV-Ray seems to be working except 
>> that... when I try to render I get a "empty" image with only the 
>> background color and the output file has been successfully created.
> 
> The blank render is one of a few bad results of newer g++ versions 
> changing the fast-math flag behavior. While running the configure script 
> add the additional flag mentioned below:
> 
> "Those using g++ compiler version 13 or later must add the compiler flag 
> -fno-finite-math-only, if using the flag -ffast-math."

* Firstly: Thank you for your reply.



* Secondly: So this problem is known. I feel better.



* Finally: I tried adding the -fno-finite-math-only option in several 
files (where CXXFLAGS=... ), but it is not taken into account. In the 
end, I still have:

povray --V
...
Compiler flags: -pipe -Wno-multichar -Wno-write-strings
                 -Wsuggest-override -O3 -ffast-math
                 -march=native -pthread

no /-fno-finite-math-only/



In which file(s) should this option be added?

./configure does not seem to accept this option,
or I did not know how to do it :(





-- 
kurtz le pirate
compagnie de la banquise

[William F Pokorny] Re: building povray on mac [106 days 17 hours and 32 minutes ago]

Sat, 3 Jan 2026 16:09:04 GMT

On 1/2/26 10:59, kurtz le pirate wrote:
> Not everything is perfect, but POV-Ray seems to be working except 
> that... when I try to render I get a "empty" image with only the 
> background color and the output file has been successfully created.

The blank render is one of a few bad results of newer g++ versions 
changing the fast-math flag behavior. While running the configure script 
add the additional flag mentioned below:

"Those using g++ compiler version 13 or later must add the compiler flag 
-fno-finite-math-only, if using the flag -ffast-math."

Bill P.

[kurtz le pirate] building povray on mac [107 days 17 hours and 42 minutes ago]

Fri, 2 Jan 2026 15:59:05 GMT

Best wishes for this new year, which is off to a funny start for me.


After my tests on Ubuntu, I decided to compile POVRay on MacOS Sequoia 
(15.7.3).


I get sources here : https://github.com/POV-Ray/povray
I installed the libraries with brew.

Some information about the result:

 > povray -version
POV-Ray 3.8.0-alpha.unofficial

This is an unofficial version compiled by:
  kurtz le pirate <kur### [at] freefr>
  The POV-Ray Team is not responsible for supporting this version.

Copyright 1991-2019 Persistence of Vision Raytracer Pty. Ltd.
This is free software; see the source for copying conditions.  There is 
NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
PURPOSE.

Built-in features:
   I/O restrictions:          disabled
   X Window display:          disabled
   Supported image formats:   gif tga iff ppm pgm hdr png jpeg tiff
   Unsupported image formats: openexr

Compilation settings:
   Build architecture:  x86_64-apple-darwin24.6.0
   Built/Optimized for: x86_64-apple-darwin24.6.0 (using -march=native)
   Compiler vendor:     gnu
   Compiler version:    g++ 17.0.0
   Compiler flags:      -pipe -Wno-multichar -Wno-write-strings
                        -Wsuggest-override -O3 -ffast-math
                        -march=native -pthread

Not everything is perfect, but POV-Ray seems to be working except 
that... when I try to render I get a "empty" image with only the 
background color and the output file has been successfully created.

Tested with several standard 3.8 scenes and multiple file formats with 
this command line:

	povray fractal1.pov +W800 +H600 +FN8

No error on output console.

Others info about lib with povray -? command:

Support libraries used by POV-Ray:
   ZLib 1.2.12, Copyright 1995-2012 Jean-loup Gailly and Mark Adler
   LibPNG 1.6.53, Copyright 1998-2012 Glenn Randers-Pehrson
   LibJPEG 8, Copyright 1991-2016 Thomas G. Lane, Guido Vollbeding
   LibTIFF 4.7.1, Copyright 1988-1997 Sam Leffler, 1991-1997 SGI
   Boost 1.90, http://www.boost.org/





Does anyone have any idea what might be happening and
can give me a clue as to how to resolve this issue?

ðŸ¤ª




-- 
kurtz le pirate
compagnie de la banquise

[jr] Re: POV-Ray 3.8.0 beta 2, 3.7.0.9 Universal bina... [110 days 14 hours and 11 minutes ago]

Tue, 30 Dec 2025 19:30:00 GMT

hi,

kurtz le pirate <kur### [at] freefr> wrote:
> to follow up on this story:
>
> On the <http://megapov.inetart.net/povrayunofficial_mac/alphapov.html>
> web page, i downloaded the source for
> "PovRayUnofficial_3.8.0-alpha.10013324-avx" XCode 10 project (XCode is a
> standard IDE).

fwiw, not a useful choice.  as I recall, clipka abandoned ("rolled back" from)
the alphas past 9945627.


regards, jr.

[kurtz le pirate] Re: POV-Ray 3.8.0 beta 2, 3.7.0.9 Universal bina... [110 days 15 hours and 59 minutes ago]

Tue, 30 Dec 2025 17:41:57 GMT

to follow up on this story:

On the <http://megapov.inetart.net/povrayunofficial_mac/alphapov.html> 
web page, i downloaded the source for 
"PovRayUnofficial_3.8.0-alpha.10013324-avx" XCode 10 project (XCode is a 
standard IDE).

The last update to this page was on January 15, 2019, which is quite 
some time ago but the project for POVRay has the same structure.

I have included a screenshot of a project window. It clearly shows the 
libraries used: zlib, tiff,... and openexr. We can therefore assume that 
OpenEXR is supported.

I tried to compile the project as is, but I got miles of errors, and to 
make matters worse, the project is version 10, while we are on version 16.

There are a lot of corrections to be made just to adapt the project, and 
I'm not at all comfortable with all of this.


There are compilation errors in the _stdio.h file, which is part of the 
original SDK. I have a feeling this is going to be complicated.






-- 
kurtz le pirate
compagnie de la banquise

[kurtz le pirate] Re: POV-Ray 3.8.0 beta 2, 3.7.0.9 Universal bina... [110 days 17 hours and 28 minutes ago]

Tue, 30 Dec 2025 16:12:56 GMT

On 29/12/2025 18:12, Cousin Ricky wrote:
> Yvo Smellenbergh <E-mail: yvo(DOT)s(AT)gmx.net> wrote:
>> Both versions run on system 10.9.5 and later, Intel and Apple Silicon (M1).
>> These are universal binaries.
>> I have compiled these versions for myself but may as well share them
>> with those interested.
> 
> There is a report that your 3.8.0 beta 2 has no EXR capability.  Could you
> please check that?  If this is indeed the case, could you please check that the
> OpenEXR *developer* library is installed on your system?  I know from experience
> that POV-Ray will compile cleanly on GNU/Linux with the EXR and SDL libraries
> missing, and it may be the same on the Mac.
> 
> I suspect your 3.7.0.9 may also have the same omission.
> 
> 

No OpenEXR lib installed on my system.

I also think that the â€œunofficialâ€ version compiled
by Yvo does not take 
into account the exr. The Mac version does not accurately reflect the 
official versions of Povray nor is it a "linux version".

And effectively, there is the same issue with version 3.7 (r4 in my case).

Thank you for your help, Richard.

-- 
kurtz le pirate
compagnie de la banquise

[Cousin Ricky] Re: POV-Ray 3.8.0 beta 2, 3.7.0.9 Universal bina... [111 days 16 hours and 26 minutes ago]

Mon, 29 Dec 2025 17:15:00 GMT

Yvo Smellenbergh <E-mail: yvo(DOT)s(AT)gmx.net> wrote:
> Both versions run on system 10.9.5 and later, Intel and Apple Silicon (M1).
> These are universal binaries.
> I have compiled these versions for myself but may as well share them
> with those interested.

There is a report that your 3.8.0 beta 2 has no EXR capability.  Could you
please check that?  If this is indeed the case, could you please check that the
OpenEXR *developer* library is installed on your system?  I know from experience
that POV-Ray will compile cleanly on GNU/Linux with the EXR and SDL libraries
missing, and it may be the same on the Mac.

I suspect your 3.7.0.9 may also have the same omission.

[kurtz le pirate] Re: Tahoe 26.1 [136 days 17 hours and 46 minutes ago]

Thu, 4 Dec 2025 15:55:17 GMT

On 04/12/2025 14:50, Franz von Dardel wrote:
> Since I moved my MacOS to Tahoe, POVRay does not work any more. I am constantly
> getting the message: Cannot create render state output file. Does anyone have a
> fix for this?
> 

For testing purposes, you can give POV full access to the disk.

System settings -> Privacy & Security -> Full Disk Access, then add POVRay.

-- 
kurtz le pirate
compagnie de la banquise

[Maetes] Re: Tahoe 26.1 [136 days 18 hours and 31 minutes ago]

Thu, 4 Dec 2025 15:10:00 GMT

"Franz von Dardel" <dar### [at] orangefr> wrote:
> Since I moved my MacOS to Tahoe, POVRay does not work any more. I am constantly
> getting the message: Cannot create render state output file. Does anyone have a
> fix for this?

The error is also thrown if you have specified a folder in the command line,
that does not exist.

povray +Imypovray.pov +Otest/povray.png +w800 +h600 -GR +A

If the "test" folder does not exist, this error message appears.
Has happened to me 1000 times.

Ma

[William F Pokorny] Re: Tahoe 26.1 [136 days 18 hours and 46 minutes ago]

Thu, 4 Dec 2025 14:54:52 GMT

On 12/4/25 08:50, Franz von Dardel wrote:
> Since I moved my MacOS to Tahoe, POVRay does not work any more. I am constantly
> getting the message: Cannot create render state output file. Does anyone have a
> fix for this?
> 

I'm also not an Apple OS user, but...

1) If you are using a v3.8 based version of POV-Ray, a workaround should 
be the command line flag '-cc' or the ini command 
'create_continue_trace_log=off'.

2) Another thought. Perhaps one or more state files existed prior to 
your OS upgrade due prior aborts for the scene. If so, maybe something 
with ownership or permissions is different enough after the upgrade 
POV-Ray cannot over-write the existing state file for a scene? This a 
wild guess - as probably you've tried multiple scenes.

Bill P.

[jr] Re: Tahoe 26.1 [136 days 19 hours and 26 minutes ago]

Thu, 4 Dec 2025 14:15:00 GMT

hi,

"Franz von Dardel" <dar### [at] orangefr> wrote:
> Since I moved my MacOS to Tahoe, POVRay does not work any more. I am constantly
> getting the message: Cannot create render state output file. Does anyone have a
> fix for this?

(not using Apple, so "sticking my neck out") a permission problem ?  ie is the
directory where POV-Ray would like to output to owned by you (or you have
sufficient rights) ?

regards, jr.

[Franz von Dardel] Tahoe 26.1 [136 days 19 hours and 46 minutes ago]

Thu, 4 Dec 2025 13:55:00 GMT

Since I moved my MacOS to Tahoe, POVRay does not work any more. I am constantly
getting the message: Cannot create render state output file. Does anyone have a
fix for this?

[kurtz le pirate] Re: New to Macintosh - how to install? [166 days 22 hours and 16 minutes ago]

Tue, 4 Nov 2025 11:25:17 GMT

On 02/11/2025 11:26, Paul Bourke wrote:
>>> What you have installed is the "standard" GUI version.
>>> For command line, you have to use another version named "Command line
>>> POV-Ray 3.7.0 final" that you can find here:
>>> <http://megapov.inetart.net/povrayunofficial_mac/finalpov.html>
>> Hmmm unfortunately that seems to be an "INTEL" version only, and the
>> machine I am using is - ARM.
> 
> Install "brew".
>     https://brew.sh/
> Install XCode and Apples command line utilities from App store.
> Type in terminal
>      brew install povray
> This will (at the time of writing) get you the command line version 3.7.0.10_14
> 
> Otherwise current beta 3.8 builds cleanly from source.
> 
> 

Have you tried with the yuqk version of WFP?

-- 
kurtz le pirate
compagnie de la banquise

[Maetes] Re: New to Macintosh - how to install? [168 days 10 hours and 11 minutes ago]

Sun, 2 Nov 2025 23:30:00 GMT

Alessio R Sangalli <ale### [at] manowebcom> wrote:
> OK I did it, thanks for the instructions, I would have never been able
> to figure it out by myself. Under Linux it's so much more... automated
> maybe?

Yes, indeed.

Command-Line:
sudo apt-get install povray povray-doc povray-examples

Thats it.

Not that I want to hold the Linux flag high here... :)

Ma

[Paul Bourke] Re: New to Macintosh - how to install? [168 days 23 hours and 11 minutes ago]

Sun, 2 Nov 2025 10:30:00 GMT

> > What you have installed is the "standard" GUI version.
> > For command line, you have to use another version named "Command line
> > POV-Ray 3.7.0 final" that you can find here:
> > <http://megapov.inetart.net/povrayunofficial_mac/finalpov.html>
> Hmmm unfortunately that seems to be an "INTEL" version only, and the
> machine I am using is - ARM.

Install "brew".
   https://brew.sh/
Install XCode and Apples command line utilities from App store.
Type in terminal
    brew install povray
This will (at the time of writing) get you the command line version 3.7.0.10_14

Otherwise current beta 3.8 builds cleanly from source.

[Yvo Smellenbergh] Re: Apple m4 chip [591 days 17 hours and 13 minutes ago]

Thu, 5 Sep 2024 16:27:42 GMT

On 2024-09-02 16:02:02 +0000, Rick said:

> Does POV-Ray work on the Apple m4 chip?

yes just make sure you downioad from:

https://povrayunofficial.wordpress.com
this is a universal binary, contains naitve builds for Intel and Mx chips.

Best regards,

-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


https://povrayunofficial.wordpress.com
E-mail: yvo(DOT)s(AT)gmx.net

[Rick] Re: Apple m4 chip [594 days 12 hours and 16 minutes ago]

Mon, 2 Sep 2024 21:25:00 GMT

"Bald Eagle" <cre### [at] netscapenet> wrote:
> "Rick" <sto### [at] suddenlinknet> wrote:
> > Does POV-Ray work on the Apple m4 chip?
>
> http://megapov.inetart.net/povrayunofficial_mac/
>
> Try it and see    :)

Besserwisser!

[Bald Eagle] Re: Apple m4 chip [594 days 13 hours and 26 minutes ago]

Mon, 2 Sep 2024 20:15:00 GMT

"Rick" <sto### [at] suddenlinknet> wrote:
> Does POV-Ray work on the Apple m4 chip?

http://megapov.inetart.net/povrayunofficial_mac/

Try it and see    :)

[Rick] Apple m4 chip [594 days 13 hours and 36 minutes ago]

Mon, 2 Sep 2024 20:05:00 GMT

Does POV-Ray work on the Apple m4 chip?

[semafore] Re: POV-Ray 3.8.0 beta 2, 3.7.0.9 Universal bina... [601 days 14 hours and 1 minute ago]

Mon, 26 Aug 2024 19:40:00 GMT

Yvo Smellenbergh <E-mail: yvo(DOT)s(AT)gmx.net> wrote:
> On 2024-08-05 19:47:00 +0000, semafore said:
>
> Have you tried to hold down the control-key while selecting it with the
> right mouse key and then choose open?
> Normaly you should get another dialog to open the app.
> I no longer have a developer ID but it is safe to open if you dowload
> it from the site.
> If it still doesn't work, please e-mail me direct and I'll see what i can do.
>
> yvo
>
> > Hi Yvo,  I downloaded the build for my M2.  It won't run, and the
> > dialog states:
> >
>
> > malicious software."  Then in the second paragraph:
> >
> > "This software needs to be updated.  Contact the developer for more
> > information."
> >
> > I'm on Ventura 13.6.6. Do you have any ideas how to get this to work?
> >
> > Thanks!
> > -ko
> >
> > Yvo Smellenbergh <E-mail: yvo(DOT)s(AT)gmx.net> wrote:
> >> Both versions run on system 10.9.5 and later, Intel and Apple Silicon (M1).
> >> These are universal binaries.
> >> I have compiled these versions for myself but may as well share them
> >> with those interested.
> >>
> >> New site:
> >> https://povrayunofficial.wordpress.com
> >>
> >> The old site is no longer updated, the person who gave our site a place
> >> has disappeared from the face of the earth.
> >> Many years ago, thanks to 'ABX', we got in touch with him but 'ABX' has
> >> also disappeared from the face of the earth...
> >> We can only hope that they have other interests and are still alive and
> >> well somewhere...
> >> Time does not stand still, things change
> >>
> >> --
> >> Yvo
> >>
> >> --
> >>
-------------------------------------------------------------------------------------------
> >>
> >>
> >>
> >> E-mail: yvo(DOT)s(AT)gmx.net
> >
> >
> > <image>
>
>
> --
> Yvo
>
> --
>
-------------------------------------------------------------------------------------------
>
> POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
> UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
> MegaPOV: http://megapov.inetart.net
> E-mail: yvo(DOT)s(AT)gmx.net

Thank you Yvo!  I got it working!  now I'm trying to remember the syntax from 30
years ago... LOL.  Thank you for building this!

-ko

[Yvo Smellenbergh] Re: POV-Ray 3.8.0 beta 2, 3.7.0.9 Universal bina... [620 days 22 hours and 47 minutes ago]

Wed, 7 Aug 2024 10:53:40 GMT

On 2024-08-05 19:47:00 +0000, semafore said:

Have you tried to hold down the control-key while selecting it with the 
right mouse key and then choose open?
Normaly you should get another dialog to open the app.
I no longer have a developer ID but it is safe to open if you dowload 
it from the site.
If it still doesn't work, please e-mail me direct and I'll see what i can do.

yvo

> Hi Yvo,  I downloaded the build for my M2.  It won't run, and the 
> dialog states:
> 
> "“POVRay 3.7.0.x.app” can’t be opened because Apple cannot check it
for
> malicious software."  Then in the second paragraph:
> 
> "This software needs to be updated.  Contact the developer for more
> information."
> 
> I'm on Ventura 13.6.6. Do you have any ideas how to get this to work?
> 
> Thanks!
> -ko
> 
> Yvo Smellenbergh <E-mail: yvo(DOT)s(AT)gmx.net> wrote:
>> Both versions run on system 10.9.5 and later, Intel and Apple Silicon (M1).
>> These are universal binaries.
>> I have compiled these versions for myself but may as well share them
>> with those interested.
>> 
>> New site:
>> https://povrayunofficial.wordpress.com
>> 
>> The old site is no longer updated, the person who gave our site a place
>> has disappeared from the face of the earth.
>> Many years ago, thanks to 'ABX', we got in touch with him but 'ABX' has
>> also disappeared from the face of the earth...
>> We can only hope that they have other interests and are still alive and
>> well somewhere...
>> Time does not stand still, things change
>> 
>> --
>> Yvo
>> 
>> --
>>
-------------------------------------------------------------------------------------------

>> 
>> 
>> 
>> E-mail: yvo(DOT)s(AT)gmx.net
> 
> 
> <image>


-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[semafore] Re: POV-Ray 3.8.0 beta 2, 3.7.0.9 Universal bina... [622 days 9 hours and 51 minutes ago]

Mon, 5 Aug 2024 23:50:00 GMT

Hi Yvo,  I downloaded the build for my M2.  It won't run, and the dialog states:

"“POVRay 3.7.0.x.app” can’t be opened because Apple cannot check it for
malicious software."  Then in the second paragraph:

"This software needs to be updated.  Contact the developer for more
information."

I'm on Ventura 13.6.6. Do you have any ideas how to get this to work?

Thanks!
-ko

Yvo Smellenbergh <E-mail: yvo(DOT)s(AT)gmx.net> wrote:
> Both versions run on system 10.9.5 and later, Intel and Apple Silicon (M1).
> These are universal binaries.
> I have compiled these versions for myself but may as well share them
> with those interested.
>
> New site:
> https://povrayunofficial.wordpress.com
>
> The old site is no longer updated, the person who gave our site a place
> has disappeared from the face of the earth.
> Many years ago, thanks to 'ABX', we got in touch with him but 'ABX' has
> also disappeared from the face of the earth...
> We can only hope that they have other interests and are still alive and
> well somewhere...
> Time does not stand still, things change
>
> --
> Yvo
>
> --
>
-------------------------------------------------------------------------------------------
>
>
> E-mail: yvo(DOT)s(AT)gmx.net

[Francois LE COAT] Re: Ingenuity Flight [922 days 14 hours and 46 minutes ago]

Tue, 10 Oct 2023 18:55:10 GMT

Hi,

Francois LE COAT writes:
>>> I've made a WEB page about 18th flight of Ingenuity over planet Mars:

>>>
>>> It's possible to reconstruct visible relief, and trajectory from the
>>> Ingenuity drone, using a simple video sequence. The monocular dispari
ty
>>> is obtained by matching images with a reference, measuring optical-
>>> flow. The trajectory is obtained using parameters of the perspective
>>> transformation describing successive images...
>>>
>>> <https://hebergement.universite-paris-saclay.fr/lecoat/demoweb/trajec
tory.html> 
>>>
>>>
>>> Since April 19, 2021, the Ingenuity helicopter sent to Mars hasn't
>>> stopped flying over the planet. It was expected taking off only
>>> 5 times, to demonstrate that it was possible. In fact, we are in
>>> February 2022, and a final realization of 19th flight over Mars, was
>>> attempted. The measurements we take correspond to 18th flight over
>>> planet Mars, dated 15 December 2021.
>>>
>>> The localization of the piloting assistance camera which is obtained,

>>> is not perfect. The lens of this camera has a radial distortion, what

>>> is not taken into account by the perspective kinematics model.
>>
>> We are in August 2023, and the Ingenuity helicopter still flies over
>> Mars. There's no GPS satellite system on the planet, and a very little

>> atmosphere compared to Earth, but it is localizing itself with a
>> grey-scale camera that points to the ground, and it works like that...

>>
>> Here is a video <https://www.youtube.com/watch?v=TP_ojUa6XtU>
>>
>> The image processing computations are obtained from interpolation
>> performed at <https://twitter.com/stim3on/status/1419414689998594051>
>> by Simeon Schmauß. That's because video are too sparse when it is
>> transmitted down the JPL/NASA Laboratory at Caltech University...
> 
> Ingenuity made its 55th flight on August 12, 2023, what demonstrates th
e
> robustness of the control GNU/Linux system, including in particularly
> hostile conditions, an unknown environment and minimal supervision,
> because the helicopter is almost autonomous, very very far from
> everything somewhere in space.

*Ingenuity over planet Mars*
In Mastodon by Simeon Schmauß at 2023/10/07
#Ingenuity #Perseverance #Mars2020 #Mars #NASA #Solarocks

<https://www.youtube.com/shorts/gV0iPwSCFBY>

Here is a look back at Ingenuity's 59th flight on Mars, as captured by
the Mastcam-Z on the Perseverance Rover.

In this view, I've heavily enhanced the dust blown away during takeoff.
You can also see dust devils moving in the background!

Best regards,

-- 
François LE COAT
<https://eureka.atari.org/>

[Alessio R Sangalli] Re: New to Macintosh - how to install? [951 days 11 hours and 43 minutes ago]

Mon, 11 Sep 2023 21:58:29 GMT

On 9/9/23 12:04 AM, kurtz le pirate wrote:

> ... not quite.
> What you have installed is the "standard" GUI version.
> 
> For command line, you have to use another version named "Command line
> POV-Ray 3.7.0 final" that you can find here:
> <http://megapov.inetart.net/povrayunofficial_mac/finalpov.html>

Hmmm unfortunately that seems to be an "INTEL" version only, and the 
machine I am using is - ARM. It still works though, and it does not seem 
to be slower than the one I downloaded from 
https://povrayunofficial.wordpress.com

What a mystery. At least with the version from 
http://megapov.inetart.net I do not have to fumble with the zip files, 
copy one inside another, it just works out of the box.

Thank you

[kurtz le pirate] Re: New to Macintosh - how to install? [954 days 2 hours and 37 minutes ago]

Sat, 9 Sep 2023 07:04:21 GMT

On 08/09/2023 18:54, Alessio R Sangalli wrote:

> 
> The next step I wanted to inquire about, I am not sure how to call 
> pov-ray from the command line. I typically build scenes that use a 
> Makefile to render sections according to dependencies, and under Linux I 
> just call the rendering engine that is in the PATH. Do I just have to 
> add the /Applications/PovRay... to the system PATH?
> 

... not quite.
What you have installed is the "standard" GUI version.

For command line, you have to use another version named "Command line
POV-Ray 3.7.0 final" that you can find here:
<http://megapov.inetart.net/povrayunofficial_mac/finalpov.html>


-- 
Kurtz le pirate
Compagnie de la Banquise

[Alessio R Sangalli] Re: New to Macintosh - how to install? [954 days 16 hours and 46 minutes ago]

Fri, 8 Sep 2023 16:54:45 GMT

On 9/8/23 12:15 AM, kurtz le pirate wrote:

> You can now move these folder anywhere on your disk.
> 
> Run "POVRay 3.7.0.x.app" (double-clic), go to "Preferences"
> and adjust "System Include Paths" according to your installation location.

OK I did it, thanks for the instructions, I would have never been able 
to figure it out by myself. Under Linux it's so much more... automated 
maybe? All these manual steps are pretty confusing to me, may I suggest 
the author of this port, whose work I really appreciate, to add some 
installation instructions for the next people? So far in my limited 
experience with MAC, most applications show an icon to drag in order to 
install and that's it.

The next step I wanted to inquire about, I am not sure how to call 
pov-ray from the command line. I typically build scenes that use a 
Makefile to render sections according to dependencies, and under Linux I 
just call the rendering engine that is in the PATH. Do I just have to 
add the /Applications/PovRay... to the system PATH?

Thank you

[kurtz le pirate] Re: New to Macintosh - how to install? [955 days 2 hours and 25 minutes ago]

Fri, 8 Sep 2023 07:15:53 GMT

On 07/09/2023 17:30, Alessio R Sangalli wrote:
> Hello, I am a new APPLE user. I have found, thanks to a link provided in 
> this newsgroup, the website https://povrayunofficial.wordpress.com
> 
> I have a brand new computer and I wanted to install the POV-ray. I got 
> the two zip files, but I have no idea where to unpack them for proper 
> installation. I know how to do it in Linux but for MAC I am very hesitant.
> 
> Thank you for any clarification you might give me.
> 

Hello,

So I think you downloaded these two files :
- PovRay3.7.0.9-universal app.zip
- PovRay3.7.0.9-universal-Scenes-IncludeFiles-Docs.zip

Double-clic this two zip file give you to folders :
- PovRay3.7.0.9-universal app
- PovRay3.7.0.9-universal-Scenes-IncludeFiles-Docs

Folder "PovRay3.7.0.9-universal app" contains the main
application with a few files to read once.

Folder "PovRay3.7.0.9-universal-Scenes-IncludeFiles-Docs" contains
doc, include, ini, scenes... which you can copy into the application
folder (yes, you can ignore duplicates). All utils files/folders in the
same folder.

You can now move these folder anywhere on your disk.

Run "POVRay 3.7.0.x.app" (double-clic), go to "Preferences"
and adjust "System Include Paths" according to your installation location.

Have fun with POV ;)

-- 
Kurtz le pirate
Compagnie de la Banquise

[Alessio R Sangalli] New to Macintosh - how to install? [955 days 18 hours and 10 minutes ago]

Thu, 7 Sep 2023 15:30:48 GMT

Hello, I am a new APPLE user. I have found, thanks to a link provided in 
this newsgroup, the website https://povrayunofficial.wordpress.com

I have a brand new computer and I wanted to install the POV-ray. I got 
the two zip files, but I have no idea where to unpack them for proper 
installation. I know how to do it in Linux but for MAC I am very hesitant.

Thank you for any clarification you might give me.

[Francois LE COAT] Re: Ingenuity Flight [975 days 16 hours and 40 minutes ago]

Fri, 18 Aug 2023 17:00:43 GMT

Hi,

Francois LE COAT writes:
>> I've made a WEB page about 18th flight of Ingenuity over planet Mars:
>>
>> It's possible to reconstruct visible relief, and trajectory from the
>> Ingenuity drone, using a simple video sequence. The monocular disparit
y
>> is obtained by matching images with a reference, measuring optical-
>> flow. The trajectory is obtained using parameters of the perspective
>> transformation describing successive images...
>>
>> <https://hebergement.universite-paris-saclay.fr/lecoat/demoweb/traject
ory.html> 
>>
>>
>> Since April 19, 2021, the Ingenuity helicopter sent to Mars hasn't
>> stopped flying over the planet. It was expected taking off only
>> 5 times, to demonstrate that it was possible. In fact, we are in
>> February 2022, and a final realization of 19th flight over Mars, was
>> attempted. The measurements we take correspond to 18th flight over
>> planet Mars, dated 15 December 2021.
>>
>> The localization of the piloting assistance camera which is obtained,
>> is not perfect. The lens of this camera has a radial distortion, what
>> is not taken into account by the perspective kinematics model.
> 
> We are in August 2023, and the Ingenuity helicopter still flies over
> Mars. There's no GPS satellite system on the planet, and a very little
> atmosphere compared to Earth, but it is localizing itself with a
> grey-scale camera that points to the ground, and it works like that...
> 
> Here is a video <https://www.youtube.com/watch?v=TP_ojUa6XtU>
> 
> The image processing computations are obtained from interpolation
> performed at <https://twitter.com/stim3on/status/1419414689998594051>
> by Simeon Schmauß. That's because video are too sparse when it is
> transmitted down the JPL/NASA Laboratory at Caltech University...

Ingenuity made its 55th flight on August 12, 2023, what demonstrates the
robustness of the control GNU/Linux system, including in particularly
hostile conditions, an unknown environment and minimal supervision,
because the helicopter is almost autonomous, very very far from
everything somewhere in space.

Best regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[Francois LE COAT] Re: Ingenuity Flight (was: [Q] POV-Ray in comman... [992 days 18 hours and 55 minutes ago]

Tue, 1 Aug 2023 14:45:44 GMT

Hi,

Francois LE COAT writes:
> I've made a WEB page about 18th flight of Ingenuity over planet Mars:
> 
> It's possible to reconstruct visible relief, and trajectory from the
> Ingenuity drone, using a simple video sequence. The monocular disparity

> is obtained by matching images with a reference, measuring optical-
> flow. The trajectory is obtained using parameters of the perspective
> transformation describing successive images...
> 
> <https://hebergement.universite-paris-saclay.fr/lecoat/demoweb/trajecto
ry.html> 
> 
> 
> Since April 19, 2021, the Ingenuity helicopter sent to Mars hasn't
> stopped flying over the planet. It was expected taking off only
> 5 times, to demonstrate that it was possible. In fact, we are in
> February 2022, and a final realization of 19th flight over Mars, was
> attempted. The measurements we take correspond to 18th flight over
> planet Mars, dated 15 December 2021.
> 
> The localization of the piloting assistance camera which is obtained,
> is not perfect. The lens of this camera has a radial distortion, what
> is not taken into account by the perspective kinematics model.

We are in August 2023, and the Ingenuity helicopter still flies over
Mars. There's no GPS satellite system on the planet, and a very little
atmosphere compared to Earth, but it is localizing itself with a
grey-scale camera that points to the ground, and it works like that...

Here is a video <https://www.youtube.com/watch?v=TP_ojUa6XtU>

The image processing computations are obtained from interpolation
performed at <https://twitter.com/stim3on/status/1419414689998594051>
by Simeon Schmauß. That's because video are too sparse when it is
transmitted down the JPL/NASA Laboratory at Caltech University...

Best regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[kurtz le pirate] Re: Idea for a new feature [1071 days 19 hours ago]

Sun, 14 May 2023 14:40:44 GMT

On 13/05/2023 10:59, E-mailyvo s gmx.net wrote:
> On 2023-05-07 15:24:37 +0000, kurtz le pirate said:
> 
>> Hello Yvo.
>>
>>
>> In the same way that the editor ribbon displays the list of macros in a
>> menu, would it be possible to add a menu with the list of functions ?
>>
>>
>> Just a suggest ...
> 
> I will try to add it but don't promise anything :-)
> I'm just trying to keep the Mac version running without adding new stuff.
> Like many here, I am nearing retirement after all these years ;-)
> 


If it's too hard, at least add the "function" in the syntax highlighting.



-- 
Kurtz le pirate
Compagnie de la Banquise

[Yvo Smellenbergh] Re: Idea for a new feature [1073 days and 42 minutes ago]

Sat, 13 May 2023 08:59:00 GMT

On 2023-05-07 15:24:37 +0000, kurtz le pirate said:

> Hello Yvo.
> 
> 
> In the same way that the editor ribbon displays the list of macros in a
> menu, would it be possible to add a menu with the list of functions ?
> 
> 
> Just a suggest ...

I will try to add it but don't promise anything :-)
I'm just trying to keep the Mac version running without adding new stuff.
Like many here, I am nearing retirement after all these years ;-)

-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[kurtz le pirate] Idea for a new feature [1078 days 18 hours and 16 minutes ago]

Sun, 7 May 2023 15:24:38 GMT

Hello Yvo.


In the same way that the editor ribbon displays the list of macros in a
menu, would it be possible to add a menu with the list of functions ?


Just a suggest ...


-- 
Kurtz le pirate
Compagnie de la Banquise

[Yvo Smellenbergh] POV-Ray 3.7.0.9 Universal Darkmode Fix update [1093 days 1 hour and 14 minutes ago]

Sun, 23 Apr 2023 08:27:11 GMT

A new version of 3.7.0.9 universal is available.
Fix: editor text in Dark Mode (if the blue color is too dark in Dark 
Mode, please adjust the color settings in the app settings panel)


Both versions (3.8x and 3.7 x)  run on system 10.9.5 and later, Intel 
and Apple Silicon (M1).
These are universal binaries.

New site:
https://povrayunofficial.wordpress.com

-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Re: POV-Ray 3.8.0 beta 2, 3.7.0.9 Universal bina... [1093 days 21 hours and 3 minutes ago]

Sat, 22 Apr 2023 12:38:26 GMT

On 2023-04-19 16:57:17 +0000, Alan Holding said:

There is a little bug in 3.7.x in dark mode. 
The text color is set to black but should be system text color.
3.8 is fine however.

I'll try to upload a new version soon. 

Yvo

> Thank you!
> 
> I'm running v3.7.0.9 Intel 64-bit on macOS Ventura 13.3.1.
> 
> Can I please ask if there is a way to keep the editor's colours in "light mode"
> when the system is in "dark mode"? I find it hard to read code when the editor
> is in dark mode.
> 
> Thanks again!


-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Alan Holding] Re: POV-Ray 3.8.0 beta 2, 3.7.0.9 Universal bina... [1096 days 12 hours and 41 minutes ago]

Wed, 19 Apr 2023 21:00:00 GMT

Thank you!

I'm running v3.7.0.9 Intel 64-bit on macOS Ventura 13.3.1.

Can I please ask if there is a way to keep the editor's colours in "light mode"
when the system is in "dark mode"? I find it hard to read code when the editor
is in dark mode.

Thanks again!

[Francois LE COAT] Re: Mandelbrot and Julia sets [1194 days 18 hours and 50 minutes ago]

Wed, 11 Jan 2023 14:51:20 GMT

Hi,

Francois LE COAT writes:
>> Here is a part of Mandelbrot fractal set in 3D with my software:
>>
>>      <https://www.youtube.com/watch?v=Yf7q2KdAS-4>
>>
>> In Eureka 2.12 the function is julia(x-0.1562+i*(y+1.0323),0)
>> plotted in ±[0.02,0.015]. 3D is obtained with the approximation
>> of distances algorithm. The function julia(z,z') corresponds to
>> the Mandelbrot set when z varies, and Julia when z' varies.
>>
>> Here is a part of Julia fractal subset in 3D with my software:
>>
>>      <https://www.youtube.com/watch?v=NIJSr7CsLR0>
>>
>> In Eureka 2.12 the function is julia(-0.82+i*0.18,y*exp(i*x))
>> plotted in [-PI/2,PI/2][0,PI/2] The 3D is obtained with the
>> approximation of distances algorithm. The function julia(z,z')
>> corresponds to the Mandelbrot set when z varies, and Julia when
>> z' varies.
>>
>> The surfaces were exported from Eureka 2.12 in 3D ".TRI" format and
>> transformed into a POV-Ray script with `tri2pov.ttp`. The same move
>> around the surface is performed, with rotations of one degree. This
>> is an illustration of the export possibilities of Eureka 2.12 =)
>>
>> I wish you will appreciate...
> 
> Here is corresponding Julia and Mandelbrot fractal sets with
> Mathematica software, in the attached "fractal.gif" picture.
> 
> The Mandelbrot set is the same, except the colormap. But for
> the Julia subset, I draw julia(-0.82+i*0.18,y*exp(i*x)) with
> my software, and Mathematica draws julia(-0.82+i*0.18,x+i*y).
> 
> I don't know if there is this kind of transform in Mathematica?
> 
> Maybe someone of you all, can help?...
> 
> Merry Christmas.

Here is a video from Julia subset drawn with my Eureka 2.12 soft:

	<https://www.youtube.com/watch?v=uA20AhHiKc4>

It is using the ARAnyM GNU/GPL ATARI virtual machine under macOS.

Happy New Year.

Best regards,

-- 
François LE COAT
Author of Eureka 2.12 (2D Graph Describer, 3D Modeller)
http://eureka.atari.org/

[Francois LE COAT] Re: Mandelbrot and Julia sets [1214 days 11 hours and 41 minutes ago]

Thu, 22 Dec 2022 22:00:07 GMT

Hi,

Francois LE COAT writes:
> Here is a part of Mandelbrot fractal set in 3D with my software:
> 
>      <https://www.youtube.com/watch?v=Yf7q2KdAS-4>
> 
> In Eureka 2.12 the function is julia(x-0.1562+i*(y+1.0323),0)
> plotted in ±[0.02,0.015]. 3D is obtained with the approximation
> of distances algorithm. The function julia(z,z') corresponds to
> the Mandelbrot set when z varies, and Julia when z' varies.
> 
> Here is a part of Julia fractal subset in 3D with my software:
> 
>      <https://www.youtube.com/watch?v=NIJSr7CsLR0>
> 
> In Eureka 2.12 the function is julia(-0.82+i*0.18,y*exp(i*x))
> plotted in [-PI/2,PI/2][0,PI/2] The 3D is obtained with the
> approximation of distances algorithm. The function julia(z,z')
> corresponds to the Mandelbrot set when z varies, and Julia when
> z' varies.
> 
> The surfaces were exported from Eureka 2.12 in 3D ".TRI" format and
> transformed into a POV-Ray script with `tri2pov.ttp`. The same move
> around the surface is performed, with rotations of one degree. This
> is an illustration of the export possibilities of Eureka 2.12 =)
> 
> I wish you will appreciate...

Here is corresponding Julia and Mandelbrot fractal sets with
Mathematica software, in the attached "fractal.gif" picture.

The Mandelbrot set is the same, except the colormap. But for
the Julia subset, I draw julia(-0.82+i*0.18,y*exp(i*x)) with
my software, and Mathematica draws julia(-0.82+i*0.18,x+i*y).

I don't know if there is this kind of transform in Mathematica?

Maybe someone of you all, can help?...

Merry Christmas.

Best regards,

-- 
François LE COAT
Author of Eureka 2.12 (2D Graph Describer, 3D Modeller)
http://eureka.atari.org/

[Francois LE COAT] Mandelbrot and Julia sets [1237 days 16 hours and 22 minutes ago]

Tue, 29 Nov 2022 17:18:38 GMT

Hi,

Here is a part of Mandelbrot fractal set in 3D with my software:

	<https://www.youtube.com/watch?v=Yf7q2KdAS-4>

In Eureka 2.12 the function is julia(x-0.1562+i*(y+1.0323),0)
plotted in ±[0.02,0.015]. 3D is obtained with the approximation
of distances algorithm. The function julia(z,z') corresponds to
the Mandelbrot set when z varies, and Julia when z' varies.

Here is a part of Julia fractal subset in 3D with my software:

	<https://www.youtube.com/watch?v=NIJSr7CsLR0>

In Eureka 2.12 the function is julia(-0.82+i*0.18,y*exp(i*x))
plotted in [-PI/2,PI/2][0,PI/2] The 3D is obtained with the
approximation of distances algorithm. The function julia(z,z')
corresponds to the Mandelbrot set when z varies, and Julia when
z' varies.

The surfaces were exported from Eureka 2.12 in 3D ".TRI" format and
transformed into a POV-Ray script with `tri2pov.ttp`. The same move
around the surface is performed, with rotations of one degree. This
is an illustration of the export possibilities of Eureka 2.12 =)

I wish you will appreciate...

Best regards,

-- 
François LE COAT
Author of Eureka 2.12 (2D Graph Describer, 3D Modeller)
http://eureka.atari.org/

[kurtz le pirate] Re: Clock settings [1291 days and 55 minutes ago]

Fri, 7 Oct 2022 08:46:03 GMT

On 01/10/2022 15:23, Franz von Dardel wrote:
>  I cannot change the clock settings : all parameters are greyed out.
> POV 3.8
> 

Hello too.

Is the checkbox activated ?




-- 
Kurtz le pirate
Compagnie de la Banquise

[jr] Re: Clock settings [1296 days 19 hours and 41 minutes ago]

Sat, 1 Oct 2022 14:00:00 GMT

hi,

"Franz von Dardel" <nomail@nomail> wrote:
> I cannot change the clock settings : all parameters are greyed out.
> POV 3.8

you use an UI version?  aiui, 'clock' etc is only relevant in conjunction with
other animation settings.  perhaps post a screenshot?
<https://wiki.povray.org/content/Reference:Numeric_Expressions#Built-in_Variables>

regards, jr.

[Franz von Dardel] Clock settings [1296 days 20 hours and 16 minutes ago]

Sat, 1 Oct 2022 13:25:00 GMT

I cannot change the clock settings : all parameters are greyed out.
POV 3.8

[jr] Re: EXR file for HDRI [1318 days 16 hours and 36 minutes ago]

Fri, 9 Sep 2022 17:05:00 GMT

hi,

Yvo Smellenbergh <E-mail: yvo(DOT)s(AT)gmx.net> wrote:
> ...
> Check https://povrayunofficial.wordpress.com

thanks.


regards, jr.

[Yvo Smellenbergh] Re: EXR file for HDRI [1318 days 17 hours and 57 minutes ago]

Fri, 9 Sep 2022 15:43:49 GMT

On 2022-09-06 11:54:58 +0000, jr said:
>> on Unofficial POV-Ray 3.8.x Alpha/Beta for mac
>> <http://megapov.inetart.net/povrayunofficial_mac/alphapov.html>
> 
> no update(s) in three years..

Check https://povrayunofficial.wordpress.com

The old site is no longer updated because I can not contact the owner 
of that domain and I lost access.

-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[jr] Re: EXR file for HDRI [1321 days 17 hours and 41 minutes ago]

Tue, 6 Sep 2022 16:00:00 GMT

hi,

thanks for the link.

kurtz le pirate <kur### [at] gmailcom> wrote:
> ...
> on Unofficial POV-Ray 3.8.x Alpha/Beta for mac
> <http://megapov.inetart.net/povrayunofficial_mac/alphapov.html>

no update(s) in three years..

> 9945627 is dec 2018 release and only 10013324 aviable for download.
>
> I think i remember having this in my /personal archives/. I will look
> for this version and do some tests.

did a quick test with 9945627, works ok.  (proviso: I compile from source, and
get the archive(s) from <https://github.com/POV-Ray/povray/tags/>)

regards, jr.

[kurtz le pirate] Re: EXR file for HDRI [1321 days 18 hours and 34 minutes ago]

Tue, 6 Sep 2022 15:07:22 GMT

On 06/09/2022 10:41, jr wrote:

> anyway, using a different .exr image, your code works on the beta.2, scene code
> below.  fwiw, I think clipka rolled back the alphas to 9945627 to make the
> beta(s).
> 

beta.2...

on Unofficial POV-Ray 3.8.x Alpha/Beta for mac
<http://megapov.inetart.net/povrayunofficial_mac/alphapov.html>

9945627 is dec 2018 release and only 10013324 aviable for download.

I think i remember having this in my /personal archives/. I will look
for this version and do some tests.

thanks jr

-- 
Kurtz le pirate
Compagnie de la Banquise

[kurtz le pirate] Re: EXR file for HDRI [1321 days 18 hours and 43 minutes ago]

Tue, 6 Sep 2022 14:58:05 GMT

On 05/09/2022 18:14, jr wrote:
> and POV-Ray doesn't know that format.  can you post an example image here,
> please?  (want to try with beta.2)

a zip (37Mo) with exr and hdr images here :
<http://louisbel.free.fr/pub/kloppenheim.zip>




-- 
Kurtz le pirate
Compagnie de la Banquise

[jr] Re: EXR file for HDRI [1322 days and 56 minutes ago]

Tue, 6 Sep 2022 08:45:00 GMT

"jr" <cre### [at] gmailcom> wrote:
> kurtz le pirate <kur### [at] gmailcom> wrote:
> > I find **polyhaven.com** site for HRDI images.
> > I try to test this image :
> > ...
> > Possible Parse Error: Cannot initialize semaphore (Function not
> > implemented).
> > Fatal error in parser: Cannot access data in file.
> >
> > Not yet implemented or bug with v3.8.0-alpha.10013324.unoficial ?
>
> I tried to get the image, but ...

anyway, using a different .exr image, your code works on the beta.2, scene code
below.  fwiw, I think clipka rolled back the alphas to 9945627 to make the
beta(s).


regards, jr.



#version 3.8;

global_settings {assumed_gamma 1}

camera {
  location <0,0,-5>
  right x * (4/3)
  up y
  look_at <0,0,0>
}

sky_sphere {
  pigment {
    image_map {
      exr "blurSmall.exr"
      map_type 0
      once
      interpolate 3
      }
    }
  }

[jr] Re: EXR file for HDRI [1322 days 17 hours and 26 minutes ago]

Mon, 5 Sep 2022 16:15:00 GMT

hi,

kurtz le pirate <kur### [at] gmailcom> wrote:
> I find **polyhaven.com** site for HRDI images.
> I try to test this image :
> ...
> Possible Parse Error: Cannot initialize semaphore (Function not
> implemented).
> Fatal error in parser: Cannot access data in file.
>
> Not yet implemented or bug with v3.8.0-alpha.10013324.unoficial ?

I tried to get the image, but it "arrives" as:
  $ file kloppenheim_06.exr
  kloppenheim_06.exr: RIFF (little-endian) data, Web/P image, VP8 encoding,
1560x780, Scaling: [none]x[none], YUV color, decoders should clamp

and POV-Ray doesn't know that format.  can you post an example image here,
please?  (want to try with beta.2)


regards, jr.

[kurtz le pirate] EXR file for HDRI [1322 days 19 hours and 38 minutes ago]

Mon, 5 Sep 2022 14:03:03 GMT

Hello,

I find **polyhaven.com** site for HRDI images.
I try to test this image :
<https://polyhaven.com/a/kloppenheim_06>

SDL code :
...
sky_sphere {
  pigment {
    image_map {
      exr "kloppenheim_06_4k.exr"
      map_type 0
      once
      interpolate 3
      }
    }
  }
...

The "exr" format is well recognized with syntax highlighting.
"Apercu" open the file with no issue, but POVray say :

Possible Parse Error: Cannot initialize semaphore (Function not
implemented).
Fatal error in parser: Cannot access data in file.


Not yet implemented or bug with v3.8.0-alpha.10013324.unoficial ?




-- 
Kurtz le pirate
Compagnie de la Banquise

[Francois LE COAT] Re: Monocular Depth [1396 days 21 hours and 11 minutes ago]

Thu, 23 Jun 2022 12:30:02 GMT

Hi,

Francois LE COAT wrote:
>> To explain what I'm doing I've done a WEB page that is not yet finishe
d:
>>
>> <https://hebergement.universite-paris-saclay.fr/lecoat/demoweb/tempora
l_disparity.html> 
>>
>>
>> POV-Ray is totally appropriate to show what I'm doing, because it can
>> represent the eight parameters I'm obtaining from the camera movement.

>>
>> I obtain the eight:
>>
>> - Tx horizontal translation
>> - Ty vertical translation
>> - Tz depth translation
>> - Rx pitch angle
>> - Ry yaw angle
>> - Rz roll angle
>> - Sx horizontal shear angle
>> - Sy vertical shear angle
>>
>> and POV-Ray can represent those all. This already have been discussed 
in
>> <news://povray.advanced-users> because I'm modelling the 3D motion.
>>
>> The issue here, is just to make POV-Ray quiet when I'm rendering...
> 
> Here is what was done with a sequence at Mont Saint-Michel...
> 
>      <https://www.youtube.com/watch?v=zd_ZXEgX8tw>
> 
> There are three parts to the video, corresponding to three measures
> of the optical-flow: IODP, Farneback and DualTVL1. This gives three
> measures of different monocular depth (Temporal Disparity), quality
> growing. What is shown is that one can as well see the relief of a
> scene, with two eyes in stereo, or with one eye in mono through
> movement.
> 
> Let's experiment... You can either see the relief by closing one eye
> moving, or with both eyes without moving. Movement (as with TV, and
> without glasses) allows you to perceive the relief! There is no need
> to be equipped with a virtual reality headset (VR).

Here is a similar demonstration with a sequence at Notre-Dame...

     <https://www.youtube.com/watch?v=F_J0l_B5A2s>

With these conditions, the drone is flying in a transverse direction.
The monocular depth (temporal disparity) is therefore measured
horizontally. The trajectory is reconstructed in a birdview, at a
constant altitude. There is a yaw rotation (Ry). The four shown
displacement components are <Tx,Ty,Tz,Ry>. All mosaics representing
perspective registration measure have an inter-correlation index
that is not below 60%.

Thanks for your help.

Regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[Francois LE COAT] Re: Monocular Depth (was: [Q] POV-Ray in command... [1431 days 19 hours and 7 minutes ago]

Thu, 19 May 2022 14:33:33 GMT

Hi,

Francois LE COAT writes:
> To explain what I'm doing I've done a WEB page that is not yet finished
:
> 
> <https://hebergement.universite-paris-saclay.fr/lecoat/demoweb/temporal
_disparity.html> 
> 
> 
> POV-Ray is totally appropriate to show what I'm doing, because it can
> represent the eight parameters I'm obtaining from the camera movement.
> 
> I obtain the eight:
> 
> - Tx horizontal translation
> - Ty vertical translation
> - Tz depth translation
> - Rx pitch angle
> - Ry yaw angle
> - Rz roll angle
> - Sx horizontal shear angle
> - Sy vertical shear angle
> 
> and POV-Ray can represent those all. This already have been discussed i
n
> <news://povray.advanced-users> because I'm modelling the 3D motion.
> 
> The issue here, is just to make POV-Ray quiet when I'm rendering...

Here is what was done with a sequence at Mont Saint-Michel...

	<https://www.youtube.com/watch?v=zd_ZXEgX8tw>

There are three parts to the video, corresponding to three measures
of the optical-flow: IODP, Farneback and DualTVL1. This gives three
measures of different monocular depth (Temporal Disparity), quality
growing. What is shown is that one can as well see the relief of a
scene, with two eyes in stereo, or with one eye in mono through
movement.

Let's experiment... You can either see the relief by closing one eye
moving, or with both eyes without moving. Movement (as with TV, and
without glasses) allows you to perceive the relief! There is no need
to be equipped with a virtual reality headset (VR).

Thanks for your help.

Regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[Francois LE COAT] Re: [Q] POV-Ray in command line [1535 days 18 hours and 41 minutes ago]

Fri, 4 Feb 2022 15:00:02 GMT

Hi,

I've made a WEB page about 18th flight of Ingenuity over planet Mars:

It's possible to reconstruct visible relief, and trajectory from the
Ingenuity drone, using a simple video sequence. The monocular disparity
is obtained by matching images with a reference, measuring optical-
flow. The trajectory is obtained using parameters of the perspective
transformation describing successive images...

<https://hebergement.universite-paris-saclay.fr/lecoat/demoweb/trajectory
.html>

Since April 19, 2021, the Ingenuity helicopter sent to Mars hasn't
stopped flying over the planet. It was expected taking off only
5 times, to demonstrate that it was possible. In fact, we are in
February 2022, and a final realization of 19th flight over Mars, was
attempted. The measurements we take correspond to 18th flight over
planet Mars, dated 15 December 2021.

The localization of the piloting assistance camera which is obtained,
is not perfect. The lens of this camera has a radial distortion, what
is not taken into account by the perspective kinematics model.

>> BayashiPascal writes:
>>> Francois LE COAT wrote:
>>>> If you read the comment from the NASA about the 8th flight of Ingenu
ity:
>>>>
>>>> <https://mars.nasa.gov/technology/helicopter/status/308>
>>>>
>>>> you understand that there was no color camera acquisition for the 7t
h
>>>> and the 8th flight on Mars. This was due to the incident on the 6th
>>>> flight, and a conflict between acquisition of the two embedded camer
as.
>>>> Let's hope for subsequent flights of the helicopter, that NASA has f
ixed
>>>> the horodating problem. Let's hope we will have a color video from M
ars.
>>>
>>> Well done ! :-)
>>> I hope too there will be colors for the next videos.
>>
>> Oh, yes! We could only see static colors images for the moment. If it
>> moved, we could better have a representation of Ingenuity's motion.
>>
>>> Your system seems to work quite well. Do you have the data for the ac
tual
>>> trajectory and can you quantify the accuracy of your reconstructed tr
ajectory ?
>>
>> I have no "ground truth" about how the camera moves. NASA has data fro
m
>> various sensors, because there is an IMU that is embedded. The comment

>> is explaining for the sixth flight, that those sensors are drifting...

>> "
>> If the navigation system relied on the IMU alone, it would not be very

>> accurate in the long run: Errors would quickly accumulate, and the
>> helicopter would eventually lose its way. To maintain better accuracy
>> over time, the IMU-based estimates are nominally corrected on a regula
r
>> basis, and this is where Ingenuityâ€™s navigation camera comes i
n. For the
>> majority of time airborne, the downward-looking navcams are taking 30
>> pictures a second of the Martian surface and immediately feeding them
>> into the helicopterâ€™s navigation system.
>> " <https://mars.nasa.gov/technology/helicopter/status/305>
>>
>> Here's my result on 8th flight 
>> <https://www.youtube.com/watch?v=CRUh37xpLT4>
>>
>>> Are you working directly with the Ingenuity team, or just using their
 
>>> public
>>> data ?
>>
>> I'm using public data. And those are extracted from real Mars data
>> acquired with the helicopter. NASA is not transmitting videos with
>> 30 images/second. I have to deal with it. This is fantastic to work
>> on martian images, nevertheless :-)
>>
>>> Bonne continuation :-)
>>
>> Thanks for your interest.
>>
>>> Pascal
> 
> Here is the first color image sequence from 9th flight on planet Mars:
> 
> 
Â Â Â Â <https://www.youtube.com/watch?v=0ug5BgZeNK4
>
> 
> The algorithm driving Ingenuity is pushed to the limits...
> 
> 
Â Â Â Â <https://mars.nasa.gov/technology/helicopter/s
tatus/314>
> 
> I really look forward to look at a real film from this color camera!

Best regards,

-- 
FranÃ§ois LE COAT
<http://eureka.atari.org/>

[aeffects] Re: POV-Ray 3.8.0 beta 2, 3.7.0.9 Universal bina... [1632 days 4 hours and 11 minutes ago]

Sun, 31 Oct 2021 05:30:00 GMT

Yvo Smellenbergh <E-mail: yvo(DOT)s(AT)gmx.net> wrote:
> Both versions run on system 10.9.5 and later, Intel and Apple Silicon (M1).
> These are universal binaries.
> I have compiled these versions for myself but may as well share them
> with those interested.
>
> New site:
> https://povrayunofficial.wordpress.com
>
> The old site is no longer updated, the person who gave our site a place
> has disappeared from the face of the earth.
> Many years ago, thanks to 'ABX', we got in touch with him but 'ABX' has
> also disappeared from the face of the earth...
> We can only hope that they have other interests and are still alive and
> well somewhere...
> Time does not stand still, things change

they do indeed change -- glad you havent, Yvo! Thanks for the OSX compile.

DGHealy
Lake Tahoe-Reno

> --
> Yvo
>
> --
>
-------------------------------------------------------------------------------------------
>
>
> E-mail: yvo(DOT)s(AT)gmx.net

[SafePit] Re: POV-Ray 3.8.0 beta 2, 3.7.0.9 Universal bina... [1678 days 5 hours and 56 minutes ago]

Wed, 15 Sep 2021 03:45:00 GMT

Awesome work, thanks for sharing!

[Yvo Smellenbergh] POV-Ray 3.8.0 beta 2, 3.7.0.9 Universal binaries... [1702 days 17 hours and 33 minutes ago]

Sat, 21 Aug 2021 16:07:38 GMT

Both versions run on system 10.9.5 and later, Intel and Apple Silicon (M1).
These are universal binaries.
I have compiled these versions for myself but may as well share them 
with those interested. 

New site:
https://povrayunofficial.wordpress.com

The old site is no longer updated, the person who gave our site a place 
has disappeared from the face of the earth.
Many years ago, thanks to 'ABX', we got in touch with him but 'ABX' has 
also disappeared from the face of the earth...
We can only hope that they have other interests and are still alive and 
well somewhere...
Time does not stand still, things change

-- 
Yvo

-- 
-------------------------------------------------------------------------------------------



E-mail: yvo(DOT)s(AT)gmx.net

[Francois LE COAT] Re: [Q] POV-Ray in command line [1719 days 20 hours and 56 minutes ago]

Wed, 4 Aug 2021 12:45:08 GMT

Hi,

pkoning writes:
> I've run into the same problem.  The regular Mac release of POVRay is a
 GUI
> tool.  Usually that's nice, but occasionally I want the command line in
terface
> and there isn't any way to get to it.
> For example, FreeCAD has a "render" tool that can feed scene descriptio
ns to
> ray-tracers such as POV-Ray.  It does so by creating the .pov file and 
then
> invoking POVRay as a command line utility.  But on Mac that doesn't wor
k because
> it can't be configured to be told what to do using Unix command line ar
guments
> -- even though Mac OS is a Unix.
> Some graphics applications have a command line switch to say "turn off 
GUI"
> (like "-batch" or the like); it would be useful for POVRay to offer som
ething
> along those lines.

Thanks for reporting your experience with POV-Ray in command line.
Because I use binaries from Macports, I don't know who I should
contact, in order to use POV-Ray port. Is there a mailing-list?

Regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[pkoning] Re: [Q] POV-Ray in command line [1720 days 13 hours and 11 minutes ago]

Tue, 3 Aug 2021 20:30:00 GMT

I've run into the same problem.  The regular Mac release of POVRay is a GUI
tool.  Usually that's nice, but occasionally I want the command line interface
and there isn't any way to get to it.
For example, FreeCAD has a "render" tool that can feed scene descriptions to
ray-tracers such as POV-Ray.  It does so by creating the .pov file and then
invoking POVRay as a command line utility.  But on Mac that doesn't work because
it can't be configured to be told what to do using Unix command line arguments
-- even though Mac OS is a Unix.
Some graphics applications have a command line switch to say "turn off GUI"
(like "-batch" or the like); it would be useful for POVRay to offer something
along those lines.

[Francois LE COAT] Re: [Q] POV-Ray in command line [1746 days 13 hours and 46 minutes ago]

Thu, 8 Jul 2021 19:55:01 GMT

Hi,

> BayashiPascal writes:
>> Francois LE COAT wrote:
>>> If you read the comment from the NASA about the 8th flight of Ingenui
ty:
>>>
>>> <https://mars.nasa.gov/technology/helicopter/status/308>
>>>
>>> you understand that there was no color camera acquisition for the 7th

>>> and the 8th flight on Mars. This was due to the incident on the 6th
>>> flight, and a conflict between acquisition of the two embedded camera
s.
>>> Let's hope for subsequent flights of the helicopter, that NASA has fi
xed
>>> the horodating problem. Let's hope we will have a color video from Ma
rs.
>>
>> Well done ! :-)
>> I hope too there will be colors for the next videos.
> 
> Oh, yes! We could only see static colors images for the moment. If it
> moved, we could better have a representation of Ingenuity's motion.
> 
>> Your system seems to work quite well. Do you have the data for the act
ual
>> trajectory and can you quantify the accuracy of your reconstructed 
>> trajectory ?
> 
> I have no "ground truth" about how the camera moves. NASA has data from

> various sensors, because there is an IMU that is embedded. The comment
> is explaining for the sixth flight, that those sensors are drifting...
> "
> If the navigation system relied on the IMU alone, it would not be very
> accurate in the long run: Errors would quickly accumulate, and the
> helicopter would eventually lose its way. To maintain better accuracy
> over time, the IMU-based estimates are nominally corrected on a regular

> basis, and this is where Ingenuityâ€™s navigation camera comes in
. For the
> majority of time airborne, the downward-looking navcams are taking 30
> pictures a second of the Martian surface and immediately feeding them
> into the helicopterâ€™s navigation system.
> " <https://mars.nasa.gov/technology/helicopter/status/305>
> 
> Here's my result on 8th flight 
> <https://www.youtube.com/watch?v=CRUh37xpLT4>
> 
>> Are you working directly with the Ingenuity team, or just using their 

>> public
>> data ?
> 
> I'm using public data. And those are extracted from real Mars data
> acquired with the helicopter. NASA is not transmitting videos with
> 30 images/second. I have to deal with it. This is fantastic to work
> on martian images, nevertheless :-)
> 
>> Bonne continuation :-)
> 
> Thanks for your interest.
> 
>> Pascal

Here is the first color image sequence from 9th flight on planet Mars:

	<https://www.youtube.com/watch?v=0ug5BgZeNK4>

The algorithm driving Ingenuity is pushed to the limits...

	<https://mars.nasa.gov/technology/helicopter/status/314>

I really look forward to look at a real film from this color camera!

Best regards,

-- 
FranÃ§ois LE COAT
<http://eureka.atari.org/>

[Francois LE COAT] Re: [Q] POV-Ray in command line [1757 days 12 hours and 29 minutes ago]

Sun, 27 Jun 2021 21:11:34 GMT

Hi,

BayashiPascal writes:
> Francois LE COAT wrote:
>> If you read the comment from the NASA about the 8th flight of Ingenuit
y:
>>
>> <https://mars.nasa.gov/technology/helicopter/status/308>
>>
>> you understand that there was no color camera acquisition for the 7th
>> and the 8th flight on Mars. This was due to the incident on the 6th
>> flight, and a conflict between acquisition of the two embedded cameras
.
>> Let's hope for subsequent flights of the helicopter, that NASA has fix
ed
>> the horodating problem. Let's hope we will have a color video from Mar
s.
> 
> Well done ! :-)
> I hope too there will be colors for the next videos.

Oh, yes! We could only see static colors images for the moment. If it
moved, we could better have a representation of Ingenuity's motion.

> Your system seems to work quite well. Do you have the data for the actu
al
> trajectory and can you quantify the accuracy of your reconstructed traj
ectory ?

I have no "ground truth" about how the camera moves. NASA has data from
various sensors, because there is an IMU that is embedded. The comment
is explaining for the sixth flight, that those sensors are drifting...
"
If the navigation system relied on the IMU alone, it would not be very
accurate in the long run: Errors would quickly accumulate, and the
helicopter would eventually lose its way. To maintain better accuracy
over time, the IMU-based estimates are nominally corrected on a regular
basis, and this is where Ingenuityâ€™s navigation camera comes in. 
For the
majority of time airborne, the downward-looking navcams are taking 30
pictures a second of the Martian surface and immediately feeding them
into the helicopterâ€™s navigation system.
" <https://mars.nasa.gov/technology/helicopter/status/305>

Here's my result on 8th flight <https://www.youtube.com/watch?v=CRUh37x
pLT4>

> Are you working directly with the Ingenuity team, or just using their p
ublic
> data ?

I'm using public data. And those are extracted from real Mars data
acquired with the helicopter. NASA is not transmitting videos with
30 images/second. I have to deal with it. This is fantastic to work
on martian images, nevertheless :-)

> Bonne continuation :-)

Thanks for your interest.

> Pascal

Best regards,

-- 
FranÃ§ois LE COAT
<http://eureka.atari.org/>

[BayashiPascal] Re: [Q] POV-Ray in command line [1757 days 23 hours and 1 minute ago]

Sun, 27 Jun 2021 10:40:00 GMT

Francois LE COAT <lec### [at] atariorg> wrote:
> Hi,
>
>
> If you read the comment from the NASA about the 8th flight of Ingenuity:
>
> <https://mars.nasa.gov/technology/helicopter/status/308>
>
> you understand that there was no color camera acquisition for the 7th
> and the 8th flight on Mars. This was due to the incident on the 6th
> flight, and a conflict between acquisition of the two embedded cameras.
> Let's hope for subsequent flights of the helicopter, that NASA has fixed
> the horodating problem. Let's hope we will have a color video from Mars.
>
> Thanks for your help.
>
> Best regards,
>
> --
>
> <http://eureka.atari.org/>

Well done ! :-)
I hope too there will be colors for the next videos.
Your system seems to work quite well. Do you have the data for the actual
trajectory and can you quantify the accuracy of your reconstructed trajectory ?
Are you working directly with the Ingenuity team, or just using their public
data ?

Bonne continuation :-)

Pascal

[Francois LE COAT] Re: [Q] POV-Ray in command line [1758 days 19 hours and 50 minutes ago]

Sat, 26 Jun 2021 13:51:19 GMT

Hi,

>>> Bald Eagle writes:
>>>> Francois LE COAT wrote:
>>>>> I've completed the WEB page I mentioned. This image processing is
>>>>> applied to a drone flying in Vosges a few days ago. I was thinking 

>>>>> about
>>>>> to apply the same computations with the flight of Ingenuity on Mars
...
>>>>>
>>>>> <https://en.wikipedia.org/wiki/Mars_Helicopter_Ingenuity>
>>>>
>>>> Nice.
>>>> I modeled a drone propeller like that ... 7 years ago?
>>>>
>>>> <http://news.povray.org/povray.binaries.images/attachment/%3Cweb.53d
d26749e0d00ba5e7df57c0%40news.povray.org%3E/propeller2_dragonfly.png?ttop
=432863&toff=950> 
>>>>
>>>
>>> Great =)
>>>
>>> The goal is modelling the trajectory and the visible relief with a
>>> simple video, using the images from Ingenuity's camera, like in :
>>>
>>> <https://hebergement.universite-paris-saclay.fr/lecoat/demoweb/tempor
al_disparity.html> 
>>>
>>>
>>> the video is <https://www.youtube.com/watch?v=MzWu7zwdJSk> Do you
>>> remember that we talked about translate <Tx,Ty,Tz>, rotate
>>> <Rx,Ry,Rz> and shear (or skew) angles <Sx,Sy,0> for the camera ?
>>> Then we can deduce the trajectory, and the monocular depth.
>>>
>>> You'll see what it gives on Mars, if you haven't seen it in a
>>> forest, with a drone, in winter ... This is spectacular :-)
>>
>> I recently worked a little further on the trajectory of the drone...
>>
>>      <https://www.youtube.com/watch?v=3PdUvGDCbQc>
>>
>> Instead of using uniquely Ry (yaw) and Tz (translation), I also used
>> Tx (translation) and Rz (roll) to reconstruct the trajectory. I couldn
't
>> use Ty (translation) and Rx (pitch) because it is not looking like a
>> valid camera displacement. I have no real explanation.
>>
>> But the aspect of the drone's trajectory is looking better ...
> 
> I worked on the sixth flight of the "Ingenuity" helicopter on Mars...
> 
>      <https://www.youtube.com/watch?v=pKUAsuXF6EA>
> 
> Unfortunately, there was an incident with the dated flight information
> and the video sources from the NASA aren't so good for processing :-(
> I wish we will have a color video, from the second embedded camera :-)

If you read the comment from the NASA about the 8th flight of Ingenuity:

<https://mars.nasa.gov/technology/helicopter/status/308>

you understand that there was no color camera acquisition for the 7th
and the 8th flight on Mars. This was due to the incident on the 6th
flight, and a conflict between acquisition of the two embedded cameras.
Let's hope for subsequent flights of the helicopter, that NASA has fixed
the horodating problem. Let's hope we will have a color video from Mars.

Thanks for your help.

Best regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[Yvo Smellenbergh] Re: [1772 days 20 hours and 18 minutes ago]

Sat, 12 Jun 2021 13:23:11 GMT

On 2021-05-29 20:23:24 +0000, SafePit said:

> "aeffects" <nomail@nomail> wrote:
>> M1 CPU based Mac's any compatibility issues running POV3.7 or 3.8 (Beta)?
>> 
>> Thanks folks.
>> DGHealy
> 
> No issues running either on my M1. Has anyone had a chance to compile an M1
> version?

Please drop me an e-mail and I will see what I can do.

yvo


-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Mr] Re: POV-Ray v3.8 backing up a bit [1774 days 22 hours and 31 minutes ago]

Thu, 10 Jun 2021 11:10:00 GMT

clipka <ano### [at] anonymousorg> wrote:
> Hi folks,
>
> this is a heads-up for all of you who are faithfully working on
> derivatives of POV-Ray - be it qtpovray, the mac port, or what-have-you.
>
> We're currently preparing to enter the beta phase of POV-Ray v3.8;
> however, in order to do so, we will _not_ continue from the current
> master, but rather back up a bit, to the last commit before we
> integrated the overhauled tokenizer/scanner into the parser. To help you
> more easily find that commit in question (85db57d9), we've tagged it as:
>
>      `nexus-v3.8-v4.0`
>
> Also, v3.8 development will _not_ continue in the `master` branch, but
> rather a dedicated branch, `release/v3.8.0` (which already exists and is
> currently ahead of The Nexus, but will be backed up and branch off soon).
>
> Note that besides reverting to the old parser, this will also revert
> back to the use of the boost-thread and boost-system libraries.
>
>
> We recommend that you _do_ keep all the work you've done since The
> Nexus, as the current state of v3.8 will live on under the moniker v4.0.
>
> There's nothing fundamentally wrong with the changes we introduced since
> The Nexus - we just won't be able to get them to a clean state as fast
> as we'd like to, and we'd probably have to break backward compatibility
> more than we'd be comfortable with in a v3.x release.

That sounds reasonable, thanks !

[clipka] POV-Ray v3.8 backing up a bit [1774 days 23 hours and 54 minutes ago]

Thu, 10 Jun 2021 09:47:02 GMT

Hi folks,

this is a heads-up for all of you who are faithfully working on 
derivatives of POV-Ray - be it qtpovray, the mac port, or what-have-you.

We're currently preparing to enter the beta phase of POV-Ray v3.8; 
however, in order to do so, we will _not_ continue from the current 
master, but rather back up a bit, to the last commit before we 
integrated the overhauled tokenizer/scanner into the parser. To help you 
more easily find that commit in question (85db57d9), we've tagged it as:

     `nexus-v3.8-v4.0`

Also, v3.8 development will _not_ continue in the `master` branch, but 
rather a dedicated branch, `release/v3.8.0` (which already exists and is 
currently ahead of The Nexus, but will be backed up and branch off soon).

Note that besides reverting to the old parser, this will also revert 
back to the use of the boost-thread and boost-system libraries.


We recommend that you _do_ keep all the work you've done since The 
Nexus, as the current state of v3.8 will live on under the moniker v4.0.

There's nothing fundamentally wrong with the changes we introduced since 
The Nexus - we just won't be able to get them to a clean state as fast 
as we'd like to, and we'd probably have to break backward compatibility 
more than we'd be comfortable with in a v3.x release.

[Francois LE COAT] Re: [Q] POV-Ray in command line [1785 days 18 hours and 41 minutes ago]

Sun, 30 May 2021 15:00:01 GMT

Hi,

>> Bald Eagle writes:
>>> Francois LE COAT wrote:
>>>> I've completed the WEB page I mentioned. This image processing is
>>>> applied to a drone flying in Vosges a few days ago. I was thinking 
>>>> about
>>>> to apply the same computations with the flight of Ingenuity on Mars.
..
>>>>
>>>> <https://en.wikipedia.org/wiki/Mars_Helicopter_Ingenuity>
>>>
>>> Nice.
>>> I modeled a drone propeller like that ... 7 years ago?
>>>
>>> <http://news.povray.org/povray.binaries.images/attachment/%3Cweb.53dd
26749e0d00ba5e7df57c0%40news.povray.org%3E/propeller2_dragonfly.png?ttop=
432863&toff=950> 
>>>
>>
>> Great =)
>>
>> The goal is modelling the trajectory and the visible relief with a
>> simple video, using the images from Ingenuity's camera, like in :
>>
>> <https://hebergement.universite-paris-saclay.fr/lecoat/demoweb/tempora
l_disparity.html> 
>>
>>
>> the video is <https://www.youtube.com/watch?v=MzWu7zwdJSk> Do you
>> remember that we talked about translate <Tx,Ty,Tz>, rotate
>> <Rx,Ry,Rz> and shear (or skew) angles <Sx,Sy,0> for the camera ?
>> Then we can deduce the trajectory, and the monocular depth.
>>
>> You'll see what it gives on Mars, if you haven't seen it in a
>> forest, with a drone, in winter ... This is spectacular :-)
> 
> I recently worked a little further on the trajectory of the drone...
> 
>      <https://www.youtube.com/watch?v=3PdUvGDCbQc>
> 
> Instead of using uniquely Ry (yaw) and Tz (translation), I also used
> Tx (translation) and Rz (roll) to reconstruct the trajectory. I couldn'
t
> use Ty (translation) and Rx (pitch) because it is not looking like a
> valid camera displacement. I have no real explanation.
> 
> But the aspect of the drone's trajectory is looking better ...

I worked on the sixth flight of the "Ingenuity" helicopter on Mars...

	<https://www.youtube.com/watch?v=pKUAsuXF6EA>

Unfortunately, there was an incident with the dated flight information
and the video sources from the NASA aren't so good for processing :-(
I wish we will have a color video, from the second embedded camera :-)

Thanks for your help.

Best regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[SafePit] Re: [1786 days 9 hours and 16 minutes ago]

Sun, 30 May 2021 00:25:00 GMT

"aeffects" <nomail@nomail> wrote:
> M1 CPU based Mac's any compatibility issues running POV3.7 or 3.8 (Beta)?
>
> Thanks folks.
> DGHealy

No issues running either on my M1. Has anyone had a chance to compile an M1
version?

[Francois LE COAT] Re: [Q] POV-Ray in command line [1860 days 17 hours and 24 minutes ago]

Tue, 16 Mar 2021 16:17:07 GMT

Hi,

> Bald Eagle writes:
>> Francois LE COAT wrote:
>>> I've completed the WEB page I mentioned. This image processing is
>>> applied to a drone flying in Vosges a few days ago. I was thinking ab
out
>>> to apply the same computations with the flight of Ingenuity on Mars..
.
>>>
>>> <https://en.wikipedia.org/wiki/Mars_Helicopter_Ingenuity>
>>
>> Nice.
>> I modeled a drone propeller like that ... 7 years ago?
>>
>> <http://news.povray.org/povray.binaries.images/attachment/%3Cweb.53dd2
6749e0d00ba5e7df57c0%40news.povray.org%3E/propeller2_dragonfly.png?ttop=
432863&toff=950> 
>>
> 
> Great =)
> 
> The goal is modelling the trajectory and the visible relief with a
> simple video, using the images from Ingenuity's camera, like in :
> 
> <https://hebergement.universite-paris-saclay.fr/lecoat/demoweb/temporal
_disparity.html> 
> 
> 
> the video is <https://www.youtube.com/watch?v=MzWu7zwdJSk> Do you
> remember that we talked about translate <Tx,Ty,Tz>, rotate
> <Rx,Ry,Rz> and shear (or skew) angles <Sx,Sy,0> for the camera ?
> Then we can deduce the trajectory, and the monocular depth.
> 
> You'll see what it gives on Mars, if you haven't seen it in a
> forest, with a drone, in winter ... This is spectacular :-)

I recently worked a little further on the trajectory of the drone...

     <https://www.youtube.com/watch?v=3PdUvGDCbQc>

Instead of using uniquely Ry (yaw) and Tz (translation), I also used
Tx (translation) and Rz (roll) to reconstruct the trajectory. I couldn't
use Ty (translation) and Rx (pitch) because it is not looking like a
valid camera displacement. I have no real explanation.

But the aspect of the drone's trajectory is looking better ...

Thanks for your help.

Best regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[aeffects] [1883 days 9 hours and 36 minutes ago]

Mon, 22 Feb 2021 00:05:01 GMT

M1 CPU based Mac's any compatibility issues running POV3.7 or 3.8 (Beta)?

Thanks folks.
DGHealy

[Francois LE COAT] Re: [Q] POV-Ray in command line [1886 days 14 hours and 52 minutes ago]

Thu, 18 Feb 2021 18:49:31 GMT

Hi,

Bald Eagle writes:
> Francois LE COAT wrote:
>> I've completed the WEB page I mentioned. This image processing is
>> applied to a drone flying in Vosges a few days ago. I was thinking abo
ut
>> to apply the same computations with the flight of Ingenuity on Mars...

>>
>> <https://en.wikipedia.org/wiki/Mars_Helicopter_Ingenuity>
> 
> Nice.
> I modeled a drone propeller like that ... 7 years ago?
> 
> <http://news.povray.org/povray.binaries.images/attachment/%3Cweb.53dd26
749e0d00ba5e7df57c0%40news.povray.org%3E/propeller2_dragonfly.png?ttop=
432863&toff=950>

Great =)

The goal is modelling the trajectory and the visible relief with a
simple video, using the images from Ingenuity's camera, like in :

<https://hebergement.universite-paris-saclay.fr/lecoat/demoweb/temporal_d
isparity.html>

the video is <https://www.youtube.com/watch?v=MzWu7zwdJSk> Do you
remember that we talked about translate <Tx,Ty,Tz>, rotate
<Rx,Ry,Rz> and shear (or skew) angles <Sx,Sy,0> for the camera ?
Then we can deduce the trajectory, and the monocular depth.

You'll see what it gives on Mars, if you haven't seen it in a
forest, with a drone, in winter ... This is spectacular :-)

Thanks for your help.

Best regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[Bald Eagle] Re: [Q] POV-Ray in command line [1886 days 15 hours and 11 minutes ago]

Thu, 18 Feb 2021 18:30:01 GMT

Francois LE COAT <lec### [at] atariorg> wrote:
> Hi,
>
> I've completed the WEB page I mentioned. This image processing is
> applied to a drone flying in Vosges a few days ago. I was thinking about
> to apply the same computations with the flight of Ingenuity on Mars...
>
> <https://en.wikipedia.org/wiki/Mars_Helicopter_Ingenuity>

Nice.
I modeled a drone propeller like that ... 7 years ago?

http://news.povray.org/povray.binaries.images/attachment/%3Cweb.53dd26749e0d00ba5e7df57c0%40news.povray.org%3E/propelle
r2_dragonfly.png?ttop=432863&toff=950

[Francois LE COAT] Re: [Q] POV-Ray in command line [1886 days 16 hours and 56 minutes ago]

Thu, 18 Feb 2021 16:45:17 GMT

Hi,

I've completed the WEB page I mentioned. This image processing is
applied to a drone flying in Vosges a few days ago. I was thinking about
to apply the same computations with the flight of Ingenuity on Mars...

<https://en.wikipedia.org/wiki/Mars_Helicopter_Ingenuity>

The autonomous drone is landing today, and we'll have video sequences =
)

Francois LE COAT writes:
> I had a talk with Bald Eagle, that is present in this newsgroup, about
> the transformations of POV-Ray, in order to render all the eight
> parameters I'm obtaining. I could also use OpenGL, because it may be
> more appropriate for "real-time". But POV-Ray is more realistic, and
> will be more and more convenient for "real-time" photographic rendering
.
> 
> The WEB page that I mentioned will be modified, because it doesn't
> represent all what I wanted to explain about what I'm doing.
> 
> All this is written in C/C++ using POV-Ray and OpenCV, but I also use
> shell scripts, mainly `tcsh`. And I use extensively the macOS Macports
> environment, that allows to use `xv`, ImageMagick, `ffmpeg` etc. And
> of course POV-Ray and OpenCV library, regularly updated.
> 
> All of this would be totally impossible to develop without the Unix
> environment, simply. It also works under GNU/Linux, with the same tools
.
> 
> BayashiPascal writes:
>> Francois LE COAT wrote:
>> Thank you very much for the web page, it looks like a very interesting
 
>> research project.
>>
>>> POV-Ray is totally appropriate to show what I'm doing, because it can

>>> represent the eight parameters I'm obtaining from the camera movement
.
>>
>> Sure, Pov-ray can do that perfectly. What I meant was another renderin
g engine
>> could also do it as well, while avoiding the problem you face with Pov
-ray. For
>> example a graphic library integrated to what you're using to launch th
e Pov-ray
>> instances would avoid creating those 2000 external processes to run Po
v-ray. In
>> a previous comment you were writing "pac%04d.png", maybe you're using 
the C
>> programming language to generate the Pov-ray scripts and launch there 
rendering?
>> In that case, using a graphic library like, for example, OpenGL to ren
der images
>> directly in the C program instead of using Pov-ray would allow you to 
get the
>> same result while avoiding the problem encountered with Pov-ray.
>>
>> But, I still do not understand completely your constraints and I shall
 no go
>> further with hypothesis.
>>
>> Anyway, bonne chance in your research ! :-)
>>
>> Francois LE COAT wrote:
>>> To explain what I'm doing I've done a WEB page that is not yet finish
ed:
>>>
>>> <https://hebergement.universite-paris-saclay.fr/lecoat/demoweb/tempor
al_disparity.html> 
>>>
>>> POV-Ray is totally appropriate to show what I'm doing, because it can

>>> represent the eight parameters I'm obtaining from the camera movement
.
>>>
>>> I obtain the eight:
>>>
>>> - Tx horizontal translation
>>> - Ty vertical translation
>>> - Tz depth translation
>>> - Rx pitch angle
>>> - Ry yaw angle
>>> - Rz roll angle
>>> - Sx horizontal shear angle
>>> - Sy vertical shear angle
>>>
>>> and POV-Ray can represent those all. This already have been discussed
 in
>>> <news://povray.advanced-users> because I'm modelling the 3D motion.
>>>
>>> The issue here, is just to make POV-Ray quiet when I'm rendering...

Thanks for your help.

Regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[Francois LE COAT] Re: [Q] POV-Ray in command line [1904 days 20 hours and 27 minutes ago]

Sun, 31 Jan 2021 13:14:10 GMT

Hi,

I had a talk with Bald Eagle, that is present in this newsgroup, about
the transformations of POV-Ray, in order to render all the eight
parameters I'm obtaining. I could also use OpenGL, because it may be
more appropriate for "real-time". But POV-Ray is more realistic, and
will be more and more convenient for "real-time" photographic rendering.

The WEB page that I mentioned will be modified, because it doesn't
represent all what I wanted to explain about what I'm doing.

All this is written in C/C++ using POV-Ray and OpenCV, but I also use
shell scripts, mainly `tcsh`. And I use extensively the macOS Macports
environment, that allows to use `xv`, ImageMagick, `ffmpeg` etc. And
of course POV-Ray and OpenCV library, regularly updated.

All of this would be totally impossible to develop without the Unix
environment, simply. It also works under GNU/Linux, with the same tools.

BayashiPascal writes:
> Francois LE COAT wrote:
> Thank you very much for the web page, it looks like a very interesting 
research
> project.
> 
>> POV-Ray is totally appropriate to show what I'm doing, because it can
>> represent the eight parameters I'm obtaining from the camera movement.

> 
> Sure, Pov-ray can do that perfectly. What I meant was another rendering
 engine
> could also do it as well, while avoiding the problem you face with Pov-
ray. For
> example a graphic library integrated to what you're using to launch the
 Pov-ray
> instances would avoid creating those 2000 external processes to run Pov
-ray. In
> a previous comment you were writing "pac%04d.png", maybe you're using t
he C
> programming language to generate the Pov-ray scripts and launch there r
endering?
> In that case, using a graphic library like, for example, OpenGL to rend
er images
> directly in the C program instead of using Pov-ray would allow you to g
et the
> same result while avoiding the problem encountered with Pov-ray.
> 
> But, I still do not understand completely your constraints and I shall 
no go
> further with hypothesis.
> 
> Anyway, bonne chance in your research ! :-)
> 
> Francois LE COAT wrote:
>> To explain what I'm doing I've done a WEB page that is not yet finishe
d:
>>
>> <https://hebergement.universite-paris-saclay.fr/lecoat/demoweb/tempora
l_disparity.html>
>>
>> POV-Ray is totally appropriate to show what I'm doing, because it can
>> represent the eight parameters I'm obtaining from the camera movement.

>>
>> I obtain the eight:
>>
>> - Tx horizontal translation
>> - Ty vertical translation
>> - Tz depth translation
>> - Rx pitch angle
>> - Ry yaw angle
>> - Rz roll angle
>> - Sx horizontal shear angle
>> - Sy vertical shear angle
>>
>> and POV-Ray can represent those all. This already have been discussed 
in
>> <news://povray.advanced-users> because I'm modelling the 3D motion.
>>
>> The issue here, is just to make POV-Ray quiet when I'm rendering...
>>
>> BayashiPascal writes:
>>> Trying to guess what you're doing. The execution of the 2000 renderin
gs is
>>> automated in some way but you're getting your data used to create the
 rendering
>>> script in real time, one image after the other, waiting new data to r
ender the
>>> next image, thus don't know in advance the new parameters. Am I right
 ?
>>>
>>> If that's the case, and if the rendering could be delayed, you could 
wait until
>>> you acquired the whole data for the 2000 images and implement a solut
ion as
>>> we've suggested in previous posts to render images at the end of acqu
isition.
>>> But may be you need to render the image as soon as its data are acqui
red and use
>>> the rendered image to acquire the next data ?
>>>
>>> Your video really sparks my curiosity. I'm also working on project us
ing
>>> Pov-ray, real world data and depth images. Would you mind telling us 
a little
>>> more about what you're doing ? Looks like some kind of 3D reconstruct
ion from
>>> data acquired by a drone ?
>>>
>>> I also understand that finding a solution, which I have no idea of, t
o the
>>> finder problem may be more practical to your use case, but, as jr, I 
still
>>> believe there may be a work around. The image you render looks simple
, and given
>>> the real time constraints (either during acquisition, rendering proce
ss or
>>> rendered image post processing) you seem to have, maybe Pov-ray is si
mply not
>>> the appropriate tool to your use case ?
>>>
>>> Hoping to be helpful,
>>> Pascal

Thanks for your help.

Regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[BayashiPascal] Re: [Q] POV-Ray in command line [1905 days 7 hours and 36 minutes ago]

Sun, 31 Jan 2021 02:05:01 GMT

Hi,

Thank you very much for the web page, it looks like a very interesting research
project.

> POV-Ray is totally appropriate to show what I'm doing, because it can
> represent the eight parameters I'm obtaining from the camera movement.

Sure, Pov-ray can do that perfectly. What I meant was another rendering engine
could also do it as well, while avoiding the problem you face with Pov-ray. For
example a graphic library integrated to what you're using to launch the Pov-ray
instances would avoid creating those 2000 external processes to run Pov-ray. In
a previous comment you were writing "pac%04d.png", maybe you're using the C
programming language to generate the Pov-ray scripts and launch there rendering?
In that case, using a graphic library like, for example, OpenGL to render images
directly in the C program instead of using Pov-ray would allow you to get the
same result while avoiding the problem encountered with Pov-ray.

But, I still do not understand completely your constraints and I shall no go
further with hypothesis.

Anyway, bonne chance in your research ! :-)



Francois LE COAT <lec### [at] atariorg> wrote:
> Hi,
>
> To explain what I'm doing I've done a WEB page that is not yet finished:
>
> <https://hebergement.universite-paris-saclay.fr/lecoat/demoweb/temporal_d
> isparity.html>
>
> POV-Ray is totally appropriate to show what I'm doing, because it can
> represent the eight parameters I'm obtaining from the camera movement.
>
> I obtain the eight:
>
> - Tx horizontal translation
> - Ty vertical translation
> - Tz depth translation
> - Rx pitch angle
> - Ry yaw angle
> - Rz roll angle
> - Sx horizontal shear angle
> - Sy vertical shear angle
>
> and POV-Ray can represent those all. This already have been discussed in
> <news://povray.advanced-users> because I'm modelling the 3D motion.
>
> The issue here, is just to make POV-Ray quiet when I'm rendering...
>
> BayashiPascal writes:
> > Trying to guess what you're doing. The execution of the 2000 renderings
>  is
> > automated in some way but you're getting your data used to create the r
> endering
> > script in real time, one image after the other, waiting new data to ren
> der the
> > next image, thus don't know in advance the new parameters. Am I right ?
>
> >
> > If that's the case, and if the rendering could be delayed, you could wa
> it until
> > you acquired the whole data for the 2000 images and implement a solutio
> n as
> > we've suggested in previous posts to render images at the end of acquis
> ition.
> > But may be you need to render the image as soon as its data are acquire
> d and use
> > the rendered image to acquire the next data ?
> >
> > Your video really sparks my curiosity. I'm also working on project usin
> g
> > Pov-ray, real world data and depth images. Would you mind telling us a
> little
> > more about what you're doing ? Looks like some kind of 3D reconstructio
> n from
> > data acquired by a drone ?
> >
> > I also understand that finding a solution, which I have no idea of, to
> the
> > finder problem may be more practical to your use case, but, as jr, I st
> ill
> > believe there may be a work around. The image you render looks simple,
> and given
> > the real time constraints (either during acquisition, rendering process
>  or
> > rendered image post processing) you seem to have, maybe Pov-ray is simp
> ly not
> > the appropriate tool to your use case ?
> >
> > Hoping to be helpful,
> > Pascal
> >
> > Francois LE COAT wrote:
> >> jr writes:
> >>> Francois LE COAT wrote:
> >>>> ...
> >>>> The rendering of POV-Ray synthesis images are done in "real-time". I
> t
> >>>> depends on past data, and future parameters are unknown. I have a
> >>>> POV-Ray script from which I substitute series of float numbers, that
>
> >>>> produces 2000 different scenes, one after the other.
> >>>>
> >>>> I can't launch POV-Ray one time, to produce 2000 images. I must laun
> ch
> >>
> >>>> it 2000 times, to render 2000 images. ...
> >>>> The question is how to configure POV-Ray with the command-line, so t
> ha
> >> t
> >>>> it is quiet ? ...
> >>>
> >>> looking at the ini you posted earlier, am I correct in assuming that
> th
> >> e
> >>> generating "POV-Ray script" produces 2000 scene files named 'pacman_m
> od
> >> .pov'?
> >>
> >> Well, I have a model "pacman.pov" from which I generate "pacman_mod.po
> v"
> >> substituting the parameters at n step. Then I render this script,
> >> producing "pacman.png". And I move "pacman.png" to "pac%04d.png" with
> n.
> >>
> >>> also, since I cannot believe that you'd invoke a(ny) program 2000 tim
> es
> >>
> >>> manually, the script must somehow tell 2nd from 23rd run.  do you run
>  t
> >> he whole
> >>> thing lot from within another script?  (o/wise how do you prevent ove
> rw
> >> riting
> >>> 'pacman.png'?)
> >>
> >> It results 2000 files, from "pac0001.png" to "pac2000.png" with 2000
> >> steps. I have launched POV-Ray 2000 times, knowing parameters from
> >> 1 to n steps. Each step n I have new parameters, but I don't know n+1.
>
> >>
> >>> are you free to modify said POV-Ray script?  then, for instance, you
> co
> >> uld
> >>> change it to generate an array and include that from your scene, usin
> g
> >>> frame_number as index; though there'd likely be other, more efficient
>  w
> >> ays.  (I
> >>> also assume that the newly calculated data only depends on previous)
> >>
> >> I can't generate an array of parameters, because I know those partiall
> y.
> >> I'm drawing a trajectory, steps to steps, and I can't predict future.
> >>
> >>> anyway, I'm fairly certain that the "problem" can be addressed w/out
> re
> >> sorting
> >>> to compiling a new program.  :-)
> >>
> >> It's the simplest solution. If there's no command-line option to make
> >> POV-Ray quiet, I can build a macOS/Macports version, that will be quie
> t.
>
> Thanks for your help.
>
> Regards,
>
> --
> François LE COAT
> <http://eureka.atari.org/>

[Bald Eagle] Re: Alpha channel [1905 days 16 hours and 6 minutes ago]

Sat, 30 Jan 2021 17:35:01 GMT

kurtz le pirate <kur### [at] gmailcom> wrote:

> Looking at your example, I found the guilty !
> The sky_sphere pigment has transmit attribute...
>
> background { color <0,0,0> }
>  => no alpha channel
>
> background { color <0,0,0> transmit 1 }
>  => alpha channel OK !
>
> *transmit* is a key
> I don't remember needing to add this in the old versions.

Right - but if you created an object with transmit 1, then you wouldn't even see
it at all.  So your background with "transmit 1" is invisible - so why even have
it?
Just delete / comment out those lines.

If background and sky_sphere can be overwritten with new values, it might be
useful to pop a little macro into a newbie include file that will be the last
line in the .pov file.  Then background and sky_sphere can be overwritten with
clear textures a s a quick diagnostic / fix, and as a reminder to those who
haven't used it in a long time...

include "newuser.inc"
transparent_background ()

[kurtz le pirate] Re: Alpha channel [1905 days 17 hours and 21 minutes ago]

Sat, 30 Jan 2021 16:19:37 GMT

On 30/01/2021 09:58, E-mailyvo s gmx.net wrote:

> 
> It is still there:
> Turn on "Add Alpha Channel" in the "image & Quality" panel on the 
> preferences panel.
> 
> And use this simple example scene:
> 
> camera {
>  Â Â Â Â perspective
>  Â Â Â Â location < 0.0, 0.0, -5>
>  Â Â Â Â right x * 1
>  Â Â Â Â up y * 3/4
>  Â Â Â Â angle 60
>  Â Â Â Â look_at < 0.0, 0.0, 0.0>
> }
> light_source {
>  Â Â Â Â < 0.0, 100, 100>
>  Â Â Â Â rgb <1.000000, 1.000000, 1.000000>
* 1.0
> }
> 
> sky_sphere {
>  Â Â Â Â pigment {
> 
Â Â Â Â Â Â Â 
rgbt <0.016749, 0.198007, 0.999977, 1.000000>
>  Â Â Â Â }
> }
> sphere {
>  Â Â Â Â <0.0, 0.0, 0.0>, 0.5
> 
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 
pigment {
> 
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 
rgb <0.500000, 1.0, 1.0>
> 
Â Â Â Â Â Â Â Â Â Â Â 
}
> 
> }

Looking at your example, I found the guilty !
The sky_sphere pigment has transmit attribute...

background { color <0,0,0> }
	=> no alpha channel

background { color <0,0,0> transmit 1 }
	=> alpha channel OK !

*transmit* is a key
I don't remember needing to add this in the old versions.




-- 
Kurtz le pirate
Compagnie de la Banquise

[jr] Re: [Q] POV-Ray in command line [1905 days 17 hours and 41 minutes ago]

Sat, 30 Jan 2021 16:00:01 GMT

hi,

Francois LE COAT <lec### [at] atariorg> wrote:
> ...
> >> ...
> >> The rendering of POV-Ray synthesis images are done in "real-time". It
> >> depends on past data, and future parameters are unknown. I have a
> >> POV-Ray script from which I substitute series of float numbers, that
> >> produces 2000 different scenes, one after the other.
> >> ...
> Well, I have a model "pacman.pov" from which I generate "pacman_mod.pov"
> substituting the parameters at n step. Then I render this script,
> producing "pacman.png". And I move "pacman.png" to "pac%04d.png" with n.
> ...

I found the web page helpful, in the video I find it difficult to reconcile
movement of the indicator/pacman with the changes in orientation wrt the images
on the left (cf ~0:25, ~1:14).  concluding thought(s).  in reply to
BayashiPascal you write "The issue here, is just to make POV-Ray quiet when I'm
rendering."  with respect, disagree.  the issue I think, even not knowing the
particulars, is work-flow[*], is to work with POV-Ray, and its animation
provisions, rather than launching thousands of instances.  hope you will find a
satisfactory solution.

regards, jr.

[*] in my head/naively I'd collect the sets of eight values in a text file (CSV
style), have a few lines of 'awk' or such to convert that to an .inc file with
an array, then run an "animation" where the scene simply displays the current
video frame and the indicator gets rendered "on top".

[Francois LE COAT] Re: [Q] POV-Ray in command line [1905 days 23 hours and 45 minutes ago]

Sat, 30 Jan 2021 09:55:45 GMT

Hi,

To explain what I'm doing I've done a WEB page that is not yet finished:

<https://hebergement.universite-paris-saclay.fr/lecoat/demoweb/temporal_d
isparity.html>

POV-Ray is totally appropriate to show what I'm doing, because it can
represent the eight parameters I'm obtaining from the camera movement.

I obtain the eight:

- Tx horizontal translation
- Ty vertical translation
- Tz depth translation
- Rx pitch angle
- Ry yaw angle
- Rz roll angle
- Sx horizontal shear angle
- Sy vertical shear angle

and POV-Ray can represent those all. This already have been discussed in
<news://povray.advanced-users> because I'm modelling the 3D motion.

The issue here, is just to make POV-Ray quiet when I'm rendering...

BayashiPascal writes:
> Trying to guess what you're doing. The execution of the 2000 renderings
 is
> automated in some way but you're getting your data used to create the r
endering
> script in real time, one image after the other, waiting new data to ren
der the
> next image, thus don't know in advance the new parameters. Am I right ?

> 
> If that's the case, and if the rendering could be delayed, you could wa
it until
> you acquired the whole data for the 2000 images and implement a solutio
n as
> we've suggested in previous posts to render images at the end of acquis
ition.
> But may be you need to render the image as soon as its data are acquire
d and use
> the rendered image to acquire the next data ?
> 
> Your video really sparks my curiosity. I'm also working on project usin
g
> Pov-ray, real world data and depth images. Would you mind telling us a 
little
> more about what you're doing ? Looks like some kind of 3D reconstructio
n from
> data acquired by a drone ?
> 
> I also understand that finding a solution, which I have no idea of, to 
the
> finder problem may be more practical to your use case, but, as jr, I st
ill
> believe there may be a work around. The image you render looks simple, 
and given
> the real time constraints (either during acquisition, rendering process
 or
> rendered image post processing) you seem to have, maybe Pov-ray is simp
ly not
> the appropriate tool to your use case ?
> 
> Hoping to be helpful,
> Pascal
> 
> Francois LE COAT wrote:
>> jr writes:
>>> Francois LE COAT wrote:
>>>> ...
>>>> The rendering of POV-Ray synthesis images are done in "real-time". I
t
>>>> depends on past data, and future parameters are unknown. I have a
>>>> POV-Ray script from which I substitute series of float numbers, that

>>>> produces 2000 different scenes, one after the other.
>>>>
>>>> I can't launch POV-Ray one time, to produce 2000 images. I must laun
ch
>>
>>>> it 2000 times, to render 2000 images. ...
>>>> The question is how to configure POV-Ray with the command-line, so t
ha
>> t
>>>> it is quiet ? ...
>>>
>>> looking at the ini you posted earlier, am I correct in assuming that 
th
>> e
>>> generating "POV-Ray script" produces 2000 scene files named 'pacman_m
od
>> .pov'?
>>
>> Well, I have a model "pacman.pov" from which I generate "pacman_mod.po
v"
>> substituting the parameters at n step. Then I render this script,
>> producing "pacman.png". And I move "pacman.png" to "pac%04d.png" with 
n.
>>
>>> also, since I cannot believe that you'd invoke a(ny) program 2000 tim
es
>>
>>> manually, the script must somehow tell 2nd from 23rd run.  do you run
 t
>> he whole
>>> thing lot from within another script?  (o/wise how do you prevent ove
rw
>> riting
>>> 'pacman.png'?)
>>
>> It results 2000 files, from "pac0001.png" to "pac2000.png" with 2000
>> steps. I have launched POV-Ray 2000 times, knowing parameters from
>> 1 to n steps. Each step n I have new parameters, but I don't know n+1.

>>
>>> are you free to modify said POV-Ray script?  then, for instance, you 
co
>> uld
>>> change it to generate an array and include that from your scene, usin
g
>>> frame_number as index; though there'd likely be other, more efficient
 w
>> ays.  (I
>>> also assume that the newly calculated data only depends on previous)
>>
>> I can't generate an array of parameters, because I know those partiall
y.
>> I'm drawing a trajectory, steps to steps, and I can't predict future.
>>
>>> anyway, I'm fairly certain that the "problem" can be addressed w/out 
re
>> sorting
>>> to compiling a new program.  :-)
>>
>> It's the simplest solution. If there's no command-line option to make
>> POV-Ray quiet, I can build a macOS/Macports version, that will be quie
t.

Thanks for your help.

Regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[Yvo Smellenbergh] Re: Alpha channel [1906 days and 42 minutes ago]

Sat, 30 Jan 2021 08:58:49 GMT

On 2021-01-27 18:46:11 +0000, kurtz le pirate said:

> Hi,
> 
> 
> I try to have "transparent" background for one image. In accordance 
> with the documentation, i check the "Add Alpha Channel" in output 
> options. The file type is png. I had already used this option with the 
> previous versions without any problem. It even seems to me that in the 
> image window, a button could raise the transparency (the grey/white 
> checkerboard).
> 
> This feature seems no longer exist.
> Error on my part or forgotten option ?
> 
> 
> My config :
> Povray 3.8.0-alpha.10013324.unofficial
> Mac OS X 10.10.5 (14F2511) - Yosemite.
> 
> 
> Note : work with MacMegaPov v1.2.1 r3 (Universal)
> Display windows is empty, but pgn file is OK.
> 
> 
> 
> Regards

It is still there:
Turn on "Add Alpha Channel" in the "image & Quality" panel on the 
preferences panel.

And use this simple example scene:

camera {
	perspective
	location < 0.0, 0.0, -5>
	right x * 1
	up y * 3/4
	angle 60
	look_at < 0.0, 0.0, 0.0>
}
light_source {
	< 0.0, 100, 100>
	rgb <1.000000, 1.000000, 1.000000> * 1.0
}

sky_sphere {
	pigment {
		rgbt <0.016749, 0.198007, 0.999977, 1.000000>
	}
}
sphere {
	<0.0, 0.0, 0.0>, 0.5
				pigment {
				rgb <0.500000, 1.0, 1.0>
			}
	
}

--
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[BayashiPascal] Re: [Q] POV-Ray in command line [1906 days 6 hours and 21 minutes ago]

Sat, 30 Jan 2021 03:20:00 GMT

Hi,

Trying to guess what you're doing. The execution of the 2000 renderings is
automated in some way but you're getting your data used to create the rendering
script in real time, one image after the other, waiting new data to render the
next image, thus don't know in advance the new parameters. Am I right ?

If that's the case, and if the rendering could be delayed, you could wait until
you acquired the whole data for the 2000 images and implement a solution as
we've suggested in previous posts to render images at the end of acquisition.
But may be you need to render the image as soon as its data are acquired and use
the rendered image to acquire the next data ?

Your video really sparks my curiosity. I'm also working on project using
Pov-ray, real world data and depth images. Would you mind telling us a little
more about what you're doing ? Looks like some kind of 3D reconstruction from
data acquired by a drone ?

I also understand that finding a solution, which I have no idea of, to the
finder problem may be more practical to your use case, but, as jr, I still
believe there may be a work around. The image you render looks simple, and given
the real time constraints (either during acquisition, rendering process or
rendered image post processing) you seem to have, maybe Pov-ray is simply not
the appropriate tool to your use case ?

Hoping to be helpful,
Pascal

Francois LE COAT <lec### [at] atariorg> wrote:
> Hi,
>
> jr writes:
> > Francois LE COAT wrote:
> >> ...
> >> The rendering of POV-Ray synthesis images are done in "real-time". It
> >> depends on past data, and future parameters are unknown. I have a
> >> POV-Ray script from which I substitute series of float numbers, that
> >> produces 2000 different scenes, one after the other.
> >>
> >> I can't launch POV-Ray one time, to produce 2000 images. I must launch
>
> >> it 2000 times, to render 2000 images. ...
> >> The question is how to configure POV-Ray with the command-line, so tha
> t
> >> it is quiet ? ...
> >
> > looking at the ini you posted earlier, am I correct in assuming that th
> e
> > generating "POV-Ray script" produces 2000 scene files named 'pacman_mod
> .pov'?
>
> Well, I have a model "pacman.pov" from which I generate "pacman_mod.pov"
> substituting the parameters at n step. Then I render this script,
> producing "pacman.png". And I move "pacman.png" to "pac%04d.png" with n.
>
> > also, since I cannot believe that you'd invoke a(ny) program 2000 times
>
> > manually, the script must somehow tell 2nd from 23rd run.  do you run t
> he whole
> > thing lot from within another script?  (o/wise how do you prevent overw
> riting
> > 'pacman.png'?)
>
> It results 2000 files, from "pac0001.png" to "pac2000.png" with 2000
> steps. I have launched POV-Ray 2000 times, knowing parameters from
> 1 to n steps. Each step n I have new parameters, but I don't know n+1.
>
> > are you free to modify said POV-Ray script?  then, for instance, you co
> uld
> > change it to generate an array and include that from your scene, using
> > frame_number as index; though there'd likely be other, more efficient w
> ays.  (I
> > also assume that the newly calculated data only depends on previous)
>
> I can't generate an array of parameters, because I know those partially.
> I'm drawing a trajectory, steps to steps, and I can't predict future.
>
> > anyway, I'm fairly certain that the "problem" can be addressed w/out re
> sorting
> > to compiling a new program.  :-)
>
> It's the simplest solution. If there's no command-line option to make
> POV-Ray quiet, I can build a macOS/Macports version, that will be quiet.
>
> Thanks for your help.
>
> Regards,
>
> --
> François LE COAT
> <http://eureka.atari.org/>

[Francois LE COAT] Re: [Q] POV-Ray in command line [1906 days 15 hours and 51 minutes ago]

Fri, 29 Jan 2021 17:50:20 GMT

Hi,

jr writes:
> Francois LE COAT wrote:
>> ...
>> The rendering of POV-Ray synthesis images are done in "real-time". It
>> depends on past data, and future parameters are unknown. I have a
>> POV-Ray script from which I substitute series of float numbers, that
>> produces 2000 different scenes, one after the other.
>>
>> I can't launch POV-Ray one time, to produce 2000 images. I must launch

>> it 2000 times, to render 2000 images. ...
>> The question is how to configure POV-Ray with the command-line, so tha
t
>> it is quiet ? ...
> 
> looking at the ini you posted earlier, am I correct in assuming that th
e
> generating "POV-Ray script" produces 2000 scene files named 'pacman_mod
.pov'?

Well, I have a model "pacman.pov" from which I generate "pacman_mod.pov"
substituting the parameters at n step. Then I render this script,
producing "pacman.png". And I move "pacman.png" to "pac%04d.png" with n.

> also, since I cannot believe that you'd invoke a(ny) program 2000 times

> manually, the script must somehow tell 2nd from 23rd run.  do you run t
he whole
> thing lot from within another script?  (o/wise how do you prevent overw
riting
> 'pacman.png'?)

It results 2000 files, from "pac0001.png" to "pac2000.png" with 2000
steps. I have launched POV-Ray 2000 times, knowing parameters from
1 to n steps. Each step n I have new parameters, but I don't know n+1.

> are you free to modify said POV-Ray script?  then, for instance, you co
uld
> change it to generate an array and include that from your scene, using
> frame_number as index; though there'd likely be other, more efficient w
ays.  (I
> also assume that the newly calculated data only depends on previous)

I can't generate an array of parameters, because I know those partially.
I'm drawing a trajectory, steps to steps, and I can't predict future.

> anyway, I'm fairly certain that the "problem" can be addressed w/out re
sorting
> to compiling a new program.  :-)

It's the simplest solution. If there's no command-line option to make
POV-Ray quiet, I can build a macOS/Macports version, that will be quiet.

Thanks for your help.

Regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[Le Forgeron] Re: Alpha channel [1906 days 16 hours and 13 minutes ago]

Fri, 29 Jan 2021 17:28:03 GMT

Le 27/01/2021 Ã  19:46, kurtz le pirate a Ã©critÂ :
> Hi,
> 
> 
> I try to have "transparent" background for one image. In accordance with
> the documentation, i check the "Add Alpha Channel" in output options.
> The file type is png. I had already used this option with the previous
> versions without any problem. It even seems to me that in the image
> window, a button could raise the transparency (the grey/white
> checkerboard).
> 
> This feature seems no longer exist.
> Error on my part or forgotten option ?

The preview display does not have the checkerboard anymore, and does not
display the alpha channel. But the generated png file should be ok.

From my (old) memory, for png with alpha, +UA on the command line AND
something about "background" in the scene (NO background at all).

Also, that's where sky_sphere might be a problem : it's a background too.

Ok, you will get alpha with background/sky_sphere as long as you have
some transmit or filter part in the colour of background/sky_sphere.
And +UA.

[jr] Re: [Q] POV-Ray in command line [1906 days 19 hours and 56 minutes ago]

Fri, 29 Jan 2021 13:45:07 GMT

hi,

Francois LE COAT <lec### [at] atariorg> wrote:
> ...
> The rendering of POV-Ray synthesis images are done in "real-time". It
> depends on past data, and future parameters are unknown. I have a
> POV-Ray script from which I substitute series of float numbers, that
> produces 2000 different scenes, one after the other.
>
> I can't launch POV-Ray one time, to produce 2000 images. I must launch
> it 2000 times, to render 2000 images. ...
> The question is how to configure POV-Ray with the command-line, so that
> it is quiet ? ...

looking at the ini you posted earlier, am I correct in assuming that the
generating "POV-Ray script" produces 2000 scene files named 'pacman_mod.pov'?

also, since I cannot believe that you'd invoke a(ny) program 2000 times
manually, the script must somehow tell 2nd from 23rd run.  do you run the whole
thing lot from within another script?  (o/wise how do you prevent overwriting
'pacman.png'?)

are you free to modify said POV-Ray script?  then, for instance, you could
change it to generate an array and include that from your scene, using
frame_number as index; though there'd likely be other, more efficient ways.  (I
also assume that the newly calculated data only depends on previous)

anyway, I'm fairly certain that the "problem" can be addressed w/out resorting
to compiling a new program.  :-)

regards, jr.

[Francois LE COAT] Re: [Q] POV-Ray in command line [1906 days 21 hours and 11 minutes ago]

Fri, 29 Jan 2021 12:30:05 GMT

Hi,

jr writes:
> Francois LE COAT wrote:
>> I can't use clock variable, in the case of my rendering. Here it is...

>> ...
>> The rendered image is the yellow camera, in up-right corner. Every
>> 2000 POV-Ray scripts are different. The 2000 POV-Ray scripts are
>> generated reading a data file, containing series of float numbers.
> 
> you don't give (m)any details about how your code is structured, so my 
comments
> are .. a shot in the dark.  :-)
> 
> if your 2000 "scripts" are simply the changing data, and you '#include'
 those
> from a scene, then serially numbered data filenames corresponding to
> 'frame_number' and constructing the file name at runtime would allow yo
u to run
> a single "animation".
> 
> if you have to extract each data set one at a time, using a shell scrip
t in
> conjunction with the '{pre,post}_frame_command's in the ini file might 
do the
> trick, again, you'd only run one animation.  hth.
> 
> regards, jr.

The rendering of POV-Ray synthesis images are done in "real-time". It
depends on past data, and future parameters are unknown. I have a
POV-Ray script from which I substitute series of float numbers, that
produces 2000 different scenes, one after the other.

I can't launch POV-Ray one time, to produce 2000 images. I must launch
it 2000 times, to render 2000 images. The issue is that Macports
POV-Ray binary, changes the menu bar, and displays an icon in the dock.

The question is how to configure POV-Ray with the command-line, so that
it is quiet ? I think I'll have to build POV-Ray binary myself, from
Unix/Linux sources using `./configure; make; make install` it's simple !

Thanks for your help.

Regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[jr] Re: [Q] POV-Ray in command line [1906 days 21 hours and 46 minutes ago]

Fri, 29 Jan 2021 11:55:01 GMT

hi,

Francois LE COAT <lec### [at] atariorg> wrote:
> Hi,
>
> I can't use clock variable, in the case of my rendering. Here it is...
> ...
> The rendered image is the yellow camera, in up-right corner. Every
> 2000 POV-Ray scripts are different. The 2000 POV-Ray scripts are
> generated reading a data file, containing series of float numbers.

you don't give (m)any details about how your code is structured, so my comments
are .. a shot in the dark.  :-)

if your 2000 "scripts" are simply the changing data, and you '#include' those
from a scene, then serially numbered data filenames corresponding to
'frame_number' and constructing the file name at runtime would allow you to run
a single "animation".

if you have to extract each data set one at a time, using a shell script in
conjunction with the '{pre,post}_frame_command's in the ini file might do the
trick, again, you'd only run one animation.  hth.

regards, jr.

[Francois LE COAT] Re: [Q] POV-Ray in command line [1906 days 22 hours and 20 minutes ago]

Fri, 29 Jan 2021 11:21:07 GMT

Hi,

I can't use clock variable, in the case of my rendering. Here it is...

	<https://www.youtube.com/watch?v=vgHOseHTGXs>

The rendered image is the yellow camera, in up-right corner. Every
2000 POV-Ray scripts are different. The 2000 POV-Ray scripts are
generated reading a data file, containing series of float numbers.

I must launch POV-Ray 2000 times, one after the other, to render 2000
different scripts. That's critical, because POV-Ray replaces the menu
bar, and add its icon to the macOS dock, 2000 times successively.
That completely blocks the usage of the Apple Finder's interface.

BayashiPascal writes:
> I don't have a solution to your finder problem but I thought a work aro
und could
> be to render your 2000 images as if it was an animation. Then you would
 launch
> only one instance of Pov-ray (I think, not completely sure actually how
 it works
> on Mac). Yet, I don't know if you could easily change your
> script to render the appropriate image based on the clock variable...
> 
> Pascal
> 
> Francois LE COAT wrote:
>> I use POV-Ray in command line under macOS Catalina and Macports,
>> and run it about 2000 times, in order to render 2000 images. My
>> issue is when you launch `povray` in command line, it opens a
>> menu bar, and displays an icon in the macOS dock ...
>>
>> Is there a command line option, that prevents POV-Ray from displaying
>> a menu bar and an icon in the dock ? Because when you launch it 2000
>> times, for 2000 images, the Apple Finder and the Macintosh become
>> unusable ... The computer keeps displaying the bar and the icon,
>> and you can't do anything else with the Macintosh. You have to wait
>> that the 2000 images are rendered ... You have to wait half an hour,
>> so that POV-Ray stops rendering.
>>
>> There must be a solution. Because you can't do anything else, before
>> POV-Ray has stopped rendering ... This is very painful ...

Thanks for your help.

Regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[jr] Re: [Q] POV-Ray in command line [1906 days 23 hours and 1 minute ago]

Fri, 29 Jan 2021 10:40:01 GMT

hi,

William F Pokorny <ano### [at] anonymousorg> wrote:
> ...
> My last two ideas. First, the sort of advice jr gives me. ...

</grin>  reminds me I meant to post re your comment (in another thread) that
'vim' has become your day-to-day editor.  first, if you want the '#for()' to
indent properly, add it to the list in line 63 of
'/usr/share/vim/vim81/indent/pov.vim'.  second, I recently "discovered" vim's
folding capabilities, great stuff, check it out (I added 'set foldmethod=marker'
in the '~/.vimrc', works equally well with Tcl.  :-))

regards, jr.

[William F Pokorny] Re: [Q] POV-Ray in command line [1907 days and 19 minutes ago]

Fri, 29 Jan 2021 09:22:13 GMT

On 1/28/21 4:10 PM, Francois LE COAT wrote:
> Hi,
> 
...
> 
> If I launch "%povray --preview text pacman.ini" in command line I have :
> "
> povray: cannot open the user configuration file 
> /Users/admin/.povray/3.7/povray.conf: No such file or directory
> 
> Problem with option setting
> povray --preview text pacman.ini
> Failed to parse command-line option
> "
> That doesn't work. Do you have an advice ?
> 

Hi,
My last two ideas. First, the sort of advice jr gives me. Have you tried 
just:

povray --help

at a command line? I don't hold out much hope, but maybe it would kick 
out any extra command line flags that are supported. It's what the 
straight unix/linux compile does.

And second, an idea more complicated. With X11 at least there is a null 
display utility usually used for testing. I can't remember the name... 
Ah, it's xvfb. I've never used it myself only hearing someone else 
mention it long ago. Looks like it can be installed on Ubuntu 20.04, but 
no idea if you have anything similar on macOS?

Aside: I think that configuration file message is another issue and not 
critical.

Bill P.

[BayashiPascal] Re: [Q] POV-Ray in command line [1907 days 5 hours and 11 minutes ago]

Fri, 29 Jan 2021 04:30:01 GMT

Hi,
I don't have a solution to your finder problem but I thought a work around could
be to render your 2000 images as if it was an animation. Then you would launch
only one instance of Pov-ray (I think, not completely sure actually how it works
on Mac). Yet, I don't know if you could easily change your
script to render the appropriate image based on the clock variable...

Pascal



Francois LE COAT <lec### [at] atariorg> wrote:
> Hi,
>
> I use POV-Ray in command line under macOS Catalina and Macports,
> and run it about 2000 times, in order to render 2000 images. My
> issue is when you launch `povray` in command line, it opens a
> menu bar, and displays an icon in the macOS dock ...
>
> Is there a command line option, that prevents POV-Ray from displaying
> a menu bar and an icon in the dock ? Because when you launch it 2000
> times, for 2000 images, the Apple Finder and the Macintosh become
> unusable ... The computer keeps displaying the bar and the icon,
> and you can't do anything else with the Macintosh. You have to wait
> that the 2000 images are rendered ... You have to wait half an hour,
> so that POV-Ray stops rendering.
>
> There must be a solution. Because you can't do anything else, before
> POV-Ray has stopped rendering ... This is very painful ...
>
> Thanks for any help.
>
> Best regards,
>
> --
> François LE COAT
> <http://eureka.atari.org/>

[Francois LE COAT] Re: [Q] POV-Ray in command line [1907 days 12 hours and 30 minutes ago]

Thu, 28 Jan 2021 21:10:39 GMT

Hi,

William F Pokorny writes:
> Thorsten wrote:
>> you need to find out who created that port and figure out what they 
>> did. The regular Unix code does not create any menu bar or icon 
>> because it simply knows nothing about Mac OS X.
>>
>> The other thing is that you should not be starting 2000 instances of 
>> POV-Ray at the same time...
>>
>> Francois LE COAT wrote:
>>> I don't know how I should modify it, so that is doesn't use a menu ba
r,
>>> and show an icon in the macOS dock. "Display=Off" is set, so what s
hould
>>> I do more ? I want POV-Ray to be quiet ... The menu bar and icon are
>>> embarrassing. That prevents from using anything else than POV-Ray :-(

> 
> I agree with Thorsten that finding the author of your particular port 
> and asking them whether one can suppress the menu bar and icon may 
> ultimately be your only option.
> 
> That said, people doing mac ports have posted unix/linux build issues t
o 
> github - so some are using the shipped unix/linux build system. You hav
e 
> the display off - good. Somewhere you are issuing a command line like:
> 
> povray your.ini ...
> 
> It's a shot in the dark, but add '--preview text' to the command line 
> and see if that helps... Try first running a single job with that 
> command line. It's a unix/linux only option and not an ini settable one
. 
> If it isn't supported / doesn't work, it should be immediately obvious 

> from one render.

If I launch "%povray --preview text pacman.ini" in command line I have :
"
povray: cannot open the user configuration file 
/Users/admin/.povray/3.7/povray.conf: No such file or directory

Problem with option setting
povray --preview text pacman.ini
Failed to parse command-line option
"
That doesn't work. Do you have an advice ?

Thanks,

Regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[William F Pokorny] Re: [Q] POV-Ray in command line [1907 days 13 hours ago]

Thu, 28 Jan 2021 20:40:46 GMT

On 1/28/21 1:37 PM, Thorsten wrote:
> Hello,
> 
> you need to find out who created that port and figure out what they did. 
> The regular Unix code does not create any menu bar or icon because it 
> simply knows nothing about Mac OS X.
> 
> The other thing is that you should not be starting 2000 instances of 
> POV-Ray at the same time...
> 
> Thorsten
> 
> On 28.01.2021 17:05, Francois LE COAT wrote:
> 
>> I don't know how I should modify it, so that is doesn't use a menu bar,
>> and show an icon in the macOS dock. "Display=Off" is set, so what should
>> I do more ? I want POV-Ray to be quiet ... The menu bar and icon are
>> embarrassing. That prevents from using anything else than POV-Ray :-(

I agree with Thorsten that finding the author of your particular port 
and asking them whether one can suppress the menu bar and icon may 
ultimately be your only option.

That said, people doing mac ports have posted unix/linux build issues to 
github - so some are using the shipped unix/linux build system. You have 
the display off - good. Somewhere you are issuing a command line like:

povray your.ini ...

It's a shot in the dark, but add '--preview text' to the command line 
and see if that helps... Try first running a single job with that 
command line. It's a unix/linux only option and not an ini settable one. 
If it isn't supported / doesn't work, it should be immediately obvious 
from one render.

Agree too that, if you are submitting 2000 jobs at once, that's likely 
as much the issue with usability as anything. Funneling jobs in over 
time would be better and doing that in a way tied to the availability of 
system resources best. I'd taken what you said to be 2000 jobs one after 
another over 30 minutes (<1s a render).

And a clarification to what Thorsten said about icons and POV-Ray as 
shipped. On unix/linux, if you are running a window manager which looks 
to generate icons from opening X11 windows, you do get them unless you 
override default(s).

Bill P.

[Francois LE COAT] Re: [Q] POV-Ray in command line [1907 days 13 hours and 2 minutes ago]

Thu, 28 Jan 2021 20:38:35 GMT

Hi,

Thorsten writes:
> you need to find out who created that port and figure out what they did
. 
> The regular Unix code does not create any menu bar or icon because it 
> simply knows nothing about Mac OS X.

That's the POV_Ray port available in Macports for macOS Catalina :

	<https://ports.macports.org/port/povray/>

I'd better build POV_Ray myself, what I already done, if there's no
peculiar option to suppress usage of the menu bar, and dock's icon.

> The other thing is that you should not be starting 2000 instances of 
> POV-Ray at the same time...

I launch POV_Ray about 2000 times, one after the other, with the use
of 12 threads (the Macintosh has 9 cores), and I must do something
else in between, because the Mac is completely monopolized. I can't
even read my email, because the Finder's interface becomes a mess ...

It's really curious that no Mac user ever noticed that peculiarity
of the Macports version. There must not be a lot of users like me :-)

> Francois LE COAT wrote:
>> William F Pokorny writes:
>>> Francois LE COAT wrote:
>>>> I use POV-Ray in command line under macOS Catalina and Macports,
>>>> and run it about 2000 times, in order to render 2000 images. My
>>>> issue is when you launch `povray` in command line, it opens a
>>>> menu bar, and displays an icon in the macOS dock ...
>>>>
>>>> Is there a command line option, that prevents POV-Ray from displayin
g
>>>> a menu bar and an icon in the dock ?
>>>
>>> Unsure if true with the macOS version you are running, but with 
>>> Linux/Unix versions (which only display an icon) you can use '-d' to 

>>> not create a preview display and icon or '--preview text' (or '-y 
>>> text) to use the inbuilt text only mode.
>>>
> 
>> I don't know how I should modify it, so that is doesn't use a menu bar
,
>> and show an icon in the macOS dock. "Display=Off" is set, so what sh
ould
>> I do more ? I want POV-Ray to be quiet ... The menu bar and icon are
>> embarrassing. That prevents from using anything else than POV-Ray :-(

Thanks for your help.

Regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[Thorsten] Re: [Q] POV-Ray in command line [1907 days 15 hours and 4 minutes ago]

Thu, 28 Jan 2021 18:37:00 GMT

Hello,

you need to find out who created that port and figure out what they did. 
The regular Unix code does not create any menu bar or icon because it 
simply knows nothing about Mac OS X.

The other thing is that you should not be starting 2000 instances of 
POV-Ray at the same time...

Thorsten

On 28.01.2021 17:05, Francois LE COAT wrote:
> William F Pokorny writes:
>> Francois LE COAT wrote:
>>> I use POV-Ray in command line under macOS Catalina and Macports,
>>> and run it about 2000 times, in order to render 2000 images. My
>>> issue is when you launch `povray` in command line, it opens a
>>> menu bar, and displays an icon in the macOS dock ...
>>>
>>> Is there a command line option, that prevents POV-Ray from displaying
>>> a menu bar and an icon in the dock ?
>>
>> Unsure if true with the macOS version you are running, but with 
>> Linux/Unix versions (which only display an icon) you can use '-d' to 
>> not create a preview display and icon or '--preview text' (or '-y 
>> text) to use the inbuilt text only mode.
>>

> I don't know how I should modify it, so that is doesn't use a menu bar,
> and show an icon in the macOS dock. "Display=Off" is set, so what should
> I do more ? I want POV-Ray to be quiet ... The menu bar and icon are
> embarrassing. That prevents from using anything else than POV-Ray :-(

[Francois LE COAT] Re: [Q] POV-Ray in command line [1907 days 17 hours and 36 minutes ago]

Thu, 28 Jan 2021 16:05:02 GMT

Hi,

William F Pokorny writes:
> Francois LE COAT wrote:
>> I use POV-Ray in command line under macOS Catalina and Macports,
>> and run it about 2000 times, in order to render 2000 images. My
>> issue is when you launch `povray` in command line, it opens a
>> menu bar, and displays an icon in the macOS dock ...
>>
>> Is there a command line option, that prevents POV-Ray from displaying
>> a menu bar and an icon in the dock ?
> 
> Unsure if true with the macOS version you are running, but with 
> Linux/Unix versions (which only display an icon) you can use '-d' to no
t 
> create a preview display and icon or '--preview text' (or '-y text) to 

> use the inbuilt text only mode.
> 
> Bill P.

My .INI file is :
"
All_Console=Off
Antialias=On
Bounding_Threshold=3
Continue_Trace=Off
Display=Off
Draw_Vistas=On
Height=640
Input_File_Name="./pacman_mod.pov"
Library_Path="/usr/share/povray-3.7"
Library_Path="/usr/share/povray-3.7/ini"
Library_Path="/usr/share/povray-3.7/include"
Library_Path="/usr/local/share/povray-3.7"
Library_Path="/usr/local/share/povray-3.7/ini"
Library_Path="/usr/local/share/povray-3.7/include"
Output_File_Name="./pacman.png"
Output_File_Type=N
Output_To_File=On
Split_Unions=On
Test_Abort=Off
Verbose=On
Width=640
Work_Threads=12
"
I don't know how I should modify it, so that is doesn't use a menu bar,
and show an icon in the macOS dock. "Display=Off" is set, so what shoul
d
I do more ? I want POV-Ray to be quiet ... The menu bar and icon are
embarrassing. That prevents from using anything else than POV-Ray :-(

Thanks for your help.

Regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[William F Pokorny] Re: [Q] POV-Ray in command line [1907 days 20 hours and 24 minutes ago]

Thu, 28 Jan 2021 13:16:49 GMT

On 1/27/21 10:30 AM, Francois LE COAT wrote:
> Hi,
> 
> I use POV-Ray in command line under macOS Catalina and Macports,
> and run it about 2000 times, in order to render 2000 images. My
> issue is when you launch `povray` in command line, it opens a
> menu bar, and displays an icon in the macOS dock ...
> 
> Is there a command line option, that prevents POV-Ray from displaying
> a menu bar and an icon in the dock ? 
> 

Unsure if true with the macOS version you are running, but with 
Linux/Unix versions (which only display an icon) you can use '-d' to not 
create a preview display and icon or '--preview text' (or '-y text) to 
use the inbuilt text only mode.

Bill P.

[kurtz le pirate] Alpha channel [1908 days 14 hours and 55 minutes ago]

Wed, 27 Jan 2021 18:46:11 GMT

Hi,


I try to have "transparent" background for one image. In accordance with 
the documentation, i check the "Add Alpha Channel" in output options. 
The file type is png. I had already used this option with the previous 
versions without any problem. It even seems to me that in the image 
window, a button could raise the transparency (the grey/white checkerboard).

This feature seems no longer exist.
Error on my part or forgotten option ?


My config :
Povray 3.8.0-alpha.10013324.unofficial
Mac OS X 10.10.5 (14F2511) - Yosemite.


Note : work with MacMegaPov v1.2.1 r3 (Universal)
Display windows is empty, but pgn file is OK.



Regards
-- 
Kurtz le pirate
Compagnie de la Banquise

[Francois LE COAT] [Q] POV-Ray in command line [1908 days 18 hours and 11 minutes ago]

Wed, 27 Jan 2021 15:30:08 GMT

Hi,

I use POV-Ray in command line under macOS Catalina and Macports,
and run it about 2000 times, in order to render 2000 images. My
issue is when you launch `povray` in command line, it opens a
menu bar, and displays an icon in the macOS dock ...

Is there a command line option, that prevents POV-Ray from displaying
a menu bar and an icon in the dock ? Because when you launch it 2000
times, for 2000 images, the Apple Finder and the Macintosh become
unusable ... The computer keeps displaying the bar and the icon,
and you can't do anything else with the Macintosh. You have to wait
that the 2000 images are rendered ... You have to wait half an hour,
so that POV-Ray stops rendering.

There must be a solution. Because you can't do anything else, before
POV-Ray has stopped rendering ... This is very painful ...

Thanks for any help.

Best regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[kurtz le pirate] Re: Wavefront Import [1936 days 17 hours and 11 minutes ago]

Wed, 30 Dec 2020 16:30:06 GMT

On 28/12/2020 15:47, William F Pokorny wrote:
> During 3.71 development Christoph implemented initial OBJ import support 
> and then disabled it due issues requiring code re-work.

Ok... thanks William.

I started to make a little perl script to convert 'obj' to 
mesh/triangle. For the moment, I'm stuck on the triangularization of 
polygons.

-- 
Kurtz le pirate
Compagnie de la Banquise

[William F Pokorny] Re: Wavefront Import [1938 days 13 hours and 22 minutes ago]

Mon, 28 Dec 2020 20:18:37 GMT

On 12/28/20 9:47 AM, William F Pokorny wrote:
> 
> (1) - Invalid triangles are simply ignored which could lead to confusing 
> messages on "junk" text. The invalid triangles should probably be 
> counted and reported once on exit - as a warning - if the count larger 
> than 0.
> 
> (1+) If there are no valid triangles at the time an unknown token is 
> seen, the token itself should be the error - not that there are no valid 
> triangles.
> 

FWIW. Updated my povr branch to always warn on degenerate triangles and 
degenerate triangles, or not, any invalid identifiers/tokens are always 
flagged as errors by name. Your code as posted now generates:

Parse Error:
Invalid identifier 'obj'
prior to valid triangle or smooth triangle.

Bill P.

Parse Warning:
4 degenerate triangle(s) dropped from mesh with
0 valid triangle(s).
File 'newDegenWarn_wIdentErr.pov' line 18:
Parse Error:
Invalid identifier 'obj'
prior to valid triangle or smooth triangle.

[William F Pokorny] Re: Wavefront Import [1938 days 18 hours and 53 minutes ago]

Mon, 28 Dec 2020 14:47:39 GMT

On 12/27/20 10:22 AM, kurtz le pirate wrote:
> 
> Hello,
> 
> Ref : <http://wiki.povray.org/content/Reference_Talk:Mesh>
> 
> "New to version 3.7.1 support has been added to allow importing 
> Wavefront (OBJ) files." With the given example
> 
...
> and with the latest version of MacPOV, this results in the error :
> "Parse Error: No triangles in triangle mesh".
> 
...
> 
> So, implemented or not ?
> 
For any particular Mac version I cannot be certain of the state.

During 3.71 development Christoph implemented initial OBJ import support 
and then disabled it due issues requiring code re-work.

I occasionally run across disabled remnants of the attempt in the code 
base for v3.8 - which I hope to remove at some point from my povr branch.

The parse message you get, I get, with v3.7 and v3.8 master and it comes 
from the mesh1 parsing code. The parsing done is simple and on the first 
"token" not understood it exits the mesh1 parsing; Checking for a 
triangle count of at least one before returning(1). It must find at 
least one valid 'triangle' or 'smooth_triangle' internal to the first 
block-internal token(1).

(1) - Invalid triangles are simply ignored which could lead to confusing 
messages on "junk" text. The invalid triangles should probably be 
counted and reported once on exit - as a warning - if the count larger 
than 0.

(1+) If there are no valid triangles at the time an unknown token is 
seen, the token itself should be the error - not that there are no valid 
triangles.

Bill P.

[kurtz le pirate] Wavefront Import [1939 days 18 hours and 19 minutes ago]

Sun, 27 Dec 2020 15:22:10 GMT

Hello,

Ref : <http://wiki.povray.org/content/Reference_Talk:Mesh>

"New to version 3.7.1 support has been added to allow importing 
Wavefront (OBJ) files." With the given example

mesh {
   obj "file_name.obj"
   texture_list {
     "Foo" texture { MyTexture }
     "Bar" material { MyMaterial }
     prefix "Tx"
     suffix "_"
   }
   inside_vector y
}

and with the latest version of MacPOV, this results in the error :
"Parse Error: No triangles in triangle mesh".


The "file_name.obj" file contains only geometric vertex list and faces 
elements list. No triangle because it's and OBJ file 
<https://en.wikipedia.org/wiki/Wavefront_.obj_file>.
The file open well with Wings3D and Meshlab.

So, implemented or not ?
Regards





-- 
Kurtz le pirate
Compagnie de la Banquise

[Francois LE COAT] Merry Christmas [1942 days 13 hours and 35 minutes ago]

Thu, 24 Dec 2020 20:05:48 GMT

Hi,

Here is a clip wishing a Merry Christmas, thinking about New Year...

<http://eureka.atari.org/pacman.mov> in QuickTime format
<http://eureka.atari.org/pacman.mp4> in MPEG4 format
<http://eureka.atari.org/pacman.ogg> in OGG Vorbis format

The Pac-Man character that is present, was 40 years old in 2020,
and was built on my ATARI computers long time ago. All the scene
was designed on these machines. But it was rendered with POV-Ray
on Macintosh, and realized with QuickTime. MP4 and OGG formats,
thanks to `ffmpeg` under MacPorts.

I wish that it will remind you about past, and hope for the future =)

Regards,

-- 
François LE COAT
Author of Eureka 2.12 (2D Graph Describer, 3D Modeller)
http://eureka.atari.org/

[Bishopcop3] PovRay 3.7 RC6_r3 Unofficial Macintosh PPC [2322 days 12 hours and 11 minutes ago]

Tue, 10 Dec 2019 21:30:01 GMT

Hate to resurrect an old thread, but it seems these SMP versions supporting PPC
are nowhere to be found on the internet.  Could someone post a working link, or
perhaps someone has a copy to upload?
Cheers,

Bish.

[clipka] Re: Pov-ray 3.8 or 3.7.1 Command Line for Macint... [2613 days 23 hours and 23 minutes ago]

Fri, 22 Feb 2019 10:18:00 GMT

Am 22.02.2019 um 10:37 schrieb clipka:

>> vfe.cpp:612:35: error: declaration of â€˜virtual
>> vfe::VirtualFrontEnd::~VirtualFrontEnd() noexcept (false)â€™ has a 
>> different
>> exception specifier
>> Â  VirtualFrontEnd::~VirtualFrontEnd()
>>
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 
^
>> In file included from vfe.cpp:43:0:
>> vfe.h:222:15: error: from previous declaration â€˜virtual
>> vfe::VirtualFrontEnd::~VirtualFrontEnd() noexcept (true)â€™
>>
Â Â Â Â Â Â Â 
virtual ~VirtualFrontEnd() ;
>>
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 
^
>> make[2]: *** [vfe.o] Error 1
>> make[1]: *** [all-recursive] Error 1
>> make: *** [all] Error 2
> 
> Now this looks like an actual issue in the POV-Ray source code, and I'll 
> look into it.

I'm not exactly sure why this is happening; can you try changing the 
lines in question to

     VirtualFrontEnd::~VirtualFrontEnd() noexcept

and

     virtual ~VirtualFrontEnd() noexcept;

respectively and let me know what that does?


BTW, what version of g++ are you using now?

[clipka] Re: Pov-ray 3.8 or 3.7.1 Command Line for Macint... [2614 days and 3 minutes ago]

Fri, 22 Feb 2019 09:37:51 GMT

Am 22.02.2019 um 06:09 schrieb Jake:
> "Jake" <jak### [at] studentcurtineduau> wrote:
> I've tried your suggestions for upgrading x-code and gcc without any success.

At the moment it may not be about having success, but about making 
progress. There's a huge difference there.

> When I tried using clang I got the following error message:
> 
> Undefined symbols for architecture x86_64:
>    "pov::BoundingTask::BoundingTask(std::__1::shared_ptr<pov::BackendSceneData>,
> unsigned int, unsigned long)", referenced from:
>        pov::Scene::StartParser(POVMS_Object&) in libpovray.a(scene.o)
> ld: symbol(s) not found for architecture x86_64
> clang: error: linker command failed with exit code 1 (use -v to see invocation)
> make[2]: *** [povray] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2

This is a linker error; such errors are typically secondary in nature 
(unless they reference library functions, but this is about a genuine 
POV-Ray function), caused by earlier compiler errors.

> When compiling with gcc I get the error:

Are you still getting those "couldnâ€™t understand kern.osversion" 
warnings? If not, we're definitely getting somewhere:

> 
> vfe.cpp:612:35: error: declaration of â€˜virtual
> vfe::VirtualFrontEnd::~VirtualFrontEnd() noexcept (false)â€™ has a
different
> exception specifier
>   VirtualFrontEnd::~VirtualFrontEnd()
>                                     ^
> In file included from vfe.cpp:43:0:
> vfe.h:222:15: error: from previous declaration â€˜virtual
> vfe::VirtualFrontEnd::~VirtualFrontEnd() noexcept (true)â€™
>         virtual ~VirtualFrontEnd() ;
>                 ^
> make[2]: *** [vfe.o] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2

Now this looks like an actual issue in the POV-Ray source code, and I'll 
look into it.

> I found something for the x86_64 error about switching between libstdc++ and
> libc++ by using -stdlib=libc++ as a flag somewhere in the makefile; however I
> don't want to mess with the makefile unless you think it may help (I'm not even
> sure where to place that line in the makefile).

I don't think the error messages you're seeing with clang are related to 
the standard libs, but it might be worth trying.

Such settings are usually injected into the makefile via the 
`./configure` script, either via `CXXFLAGS=-stdlib=libc++` or 
`LDFLAGS=-stdlib=libc++`; not sure which of the two you'll need, I 
suspect the former. In that case you'd use either:

     export CXXFLAGS="-stdlib=libc++"
     ./configure ...

or:

     ./configure CXXFLAGS="-stdlib=libc++" ...

This will then automatically weave the options into the makefile at the 
proper places.

`LDFLAGS` would work in the same manner, but is for linker flags rather 
than compiler flags.

[Jake] Re: Pov-ray 3.8 or 3.7.1 Command Line for Macint... [2614 days 4 hours and 31 minutes ago]

Fri, 22 Feb 2019 05:10:00 GMT

"Jake" <jak### [at] studentcurtineduau> wrote:
I've tried your suggestions for upgrading x-code and gcc without any success.
When I tried using clang I got the following error message:

Undefined symbols for architecture x86_64:
  "pov::BoundingTask::BoundingTask(std::__1::shared_ptr<pov::BackendSceneData>,
unsigned int, unsigned long)", referenced from:
      pov::Scene::StartParser(POVMS_Object&) in libpovray.a(scene.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [povray] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2


When compiling with gcc I get the error:

vfe.cpp:612:35: error: declaration of ‘virtual
vfe::VirtualFrontEnd::~VirtualFrontEnd() noexcept (false)’ has a different
exception specifier
 VirtualFrontEnd::~VirtualFrontEnd()
                                   ^
In file included from vfe.cpp:43:0:
vfe.h:222:15: error: from previous declaration ‘virtual
vfe::VirtualFrontEnd::~VirtualFrontEnd() noexcept (true)’
       virtual ~VirtualFrontEnd() ;
               ^
make[2]: *** [vfe.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2


I found something for the x86_64 error about switching between libstdc++ and
libc++ by using -stdlib=libc++ as a flag somewhere in the makefile; however I
don't want to mess with the makefile unless you think it may help (I'm not even
sure where to place that line in the makefile).

[Jake] Re: Pov-ray 3.8 or 3.7.1 Command Line for Macint... [2614 days 7 hours and 26 minutes ago]

Fri, 22 Feb 2019 02:15:01 GMT

Hi, this is a little off topic but I've just noticed that I can't see the
message I posted in reply to your first message, nor can I see the reply to my
latest message, when I click on the thread it says there is only 2 messages even
though on the support page the thread has a (4) next to it. Do you know where I
can access the rest of the thread? If necessary please use my email:
jak### [at] studentcurtineduau  Sorry for the inconvenience.

[clipka] Re: Pov-ray 3.8 or 3.7.1 Command Line for Macint... [2615 days 1 hour and 47 minutes ago]

Thu, 21 Feb 2019 07:54:26 GMT

Am 21.02.2019 um 04:59 schrieb Jake:

>> https://github.com/POV-Ray/povray/releases/tag/v3.8.0-alpha.10013324
...
> As for this version, I can run the same configure command as above without the
> freetype flag and the configure program runs with no issues; however, running
> 'make check' produces the following error:
...
> g++: warning: couldnâ€™t understand kern.osversion
â€˜17.7.0
...

> This then loops for too many times for me to count before eventually failing to
> install.

Does it fail to "make install", does it fail to "make check", or does it 
even fail to "make"?

You've only quoted warning messages, but in case of a failure you should 
also get some genuine error messages; can you post those?

> If you have any ideas as to what could fix this I'd greatly appreciate it.

According to the internerds, the warning messages you get seem to 
indicate that your development tools are outdated; people suggest 
updating those, and in that context the followng commands are mentioned 
(either of these may work):

     xcode-select --install

     brew upgrade gcc

     brew upgrade gcc49

(Presumably the `49` in `gcc49` is a version number so you may need to 
adapt this to your case.)

Also, you seem to be using gcc, while we're using clang in our tests 
instead, which to the best of my knowledge is the "native" C/C++ 
compiler on Mac OS X. (IIRC we did have trouble getting gcc to work, too.)

You should be able to set this up by invoking

     export CXX=clang++

before running the `./configure` script. Alternatively, I think it 
should also be possible to pass `CXX=clang++` as a parameter to the 
`./configure` script.

[Jake] Re: Pov-ray 3.8 or 3.7.1 Command Line for Macint... [2615 days 5 hours and 41 minutes ago]

Thu, 21 Feb 2019 04:00:00 GMT

clipka <ano### [at] anonymousorg> wrote:
> Am 19.02.2019 um 07:03 schrieb Jake:
> > I've been trying to install pov-ray from the command line for my Macintosh (High
> > Sierra 10.13.6)
>
> Is that "_install from_ the command line" or "install to _run from_ the
> command line"?

I'm attempting to run from the command line, but it seems to do so I'll also
need to install from the command line.

>
> Tests are currently run with Mac OS X 10.13.3, Apple LLVM version 9.1.0
> (clang-902.0.39.2) amd XCode 9.4.1.

I'm running Mac OS X 10.13.6, Apple LLVM version 10.0.0 and XCode 10.1

> On the test system we do not need to install any extra packages, except
> for homebrew `freetype` for the semi-experimental v3.8.0-x.freetype
> versions.

For the freetype install you suggested I was able to get prebuild.sh to run
fine; I then tried the following compile options which ran through the ./compile
program:

../configure COMPILED_BY=Jake --disable-dependency-tracking --without-libsdl
--without-x --with-libfreetype=/usr/local/Cellar/freetype/2.9.1

This produced the following error:

checking for pkg-config... no
checking for OpenEXR's pkg-config... not found
configure: WARNING: all program features using the OpenEXR library are disabled
checking whether to use the FreeType library... yes
checking for pkg-config... no
checking for FreeType's include path... ./configure: line 11406: pkg-config:
command not found
checking for library containing FT_Init_FreeType... no
configure: error: cannot find a suitable FreeType library

I also tried removing the /2.9.1 and /freetype/2.9.1 parts of the above
../compile line after encountering the above error but I still received the same
error. I'm not sure why this is occuring as 'brew info freetype' gives the
install path as /usr/local/Cellar/freetype/2.9.1 and if I don't specify a path
to freetype I still encounter the above error.

> I recommend you try this version (download the source code package):
>
> https://github.com/POV-Ray/povray/releases/tag/v3.8.0-alpha.10013324
>
> and let us know what (if any) problems you encounter, so that we can
> improve on our build process. The v3.7.0.8 homebrew formula may hold
> some relevant secrets:

As for this version, I can run the same configure command as above without the
freetype flag and the configure program runs with no issues; however, running
'make check' produces the following error:

/Applications/Xcode.app/Contents/Developer/usr/bin/make  all-recursive
Making all in source
g++ -std=gnu++11 -DHAVE_CONFIG_H -I. -I..  -I../unix/povconfig -I..
-I../platform/unix -I../platform/x86 -I../unix -I../vfe -I../vfe/unix -pthread
-I/usr/local/include  -pipe -Wno-multichar -Wno-write-strings
-fno-enforce-eh-specs -Wno-non-template-friend -s -O3 -ffast-math -march=native
-pthread -c -o backend/bounding/boundingtask.o backend/bounding/boundingtask.cpp
g++: warning: couldn’t understand kern.osversion ‘17.7.0
<stdin>:1:11: warning: section "__textcoal_nt" is deprecated
        .section __TEXT,__textcoal_nt,coalesced,pure_instructions
                 ^      ~~~~~~~~~~~~~
<stdin>:1:11: note: change section name to "__text"
        .section __TEXT,__textcoal_nt,coalesced,pure_instructions
                 ^      ~~~~~~~~~~~~~
<stdin>:152:11: warning: section "__textcoal_nt" is deprecated
        .section __TEXT,__textcoal_nt,coalesced,pure_instructions

This is followed by many more similar <stdin> warnings and then:

g++ -std=gnu++11 -DHAVE_CONFIG_H -I. -I..  -I../unix/povconfig -I..
-I../platform/unix -I../platform/x86 -I../unix -I../vfe -I../vfe/unix -pthread
-I/usr/local/include  -pipe -Wno-multichar -Wno-write-strings
-fno-enforce-eh-specs -Wno-non-template-friend -s -O3 -ffast-math -march=native
-pthread -c -o backend/control/benchmark.o backend/control/benchmark.cpp
g++: warning: couldn’t understand kern.osversion ‘17.7.0

This then loops for too many times for me to count before eventually failing to
install.

If you have any ideas as to what could fix this I'd greatly appreciate it.

Thanks again for your help

[clipka] Re: Pov-ray 3.8 or 3.7.1 Command Line for Macint... [2617 days and 15 minutes ago]

Tue, 19 Feb 2019 09:26:31 GMT

Am 19.02.2019 um 07:03 schrieb Jake:
> I've been trying to install pov-ray from the command line for my Macintosh (High
> Sierra 10.13.6)

Is that "_install from_ the command line" or "install to _run from_ the 
command line"?

> and have had little succes with any version other than 3.7 which
> I was able to install through homebrew. I was wondering if there will be a
> command line release of version 3.7.1 or 3.8 for Macintosh in the near future as
> I have a program called Ovito that requires either 3.7.1 or above to produce
> omniÂdirectional stereo projection images.

POV-Ray v3.8.0-alpha for Unix (which is a program designed to run from 
the command line) _should_ build fine on Mac OS X using the official 
Unix build process (which is also run from the command line) - this is 
tested automatically whenever new changes are submitted to the official 
repo.

Tests are currently run with Mac OS X 10.13.3, Apple LLVM version 9.1.0 
(clang-902.0.39.2) amd XCode 9.4.1.

On the test system we do not need to install any extra packages, except 
for homebrew `freetype` for the semi-experimental v3.8.0-x.freetype 
versions.

I recommend you try this version (download the source code package):

https://github.com/POV-Ray/povray/releases/tag/v3.8.0-alpha.10013324

and let us know what (if any) problems you encounter, so that we can 
improve on our build process. The v3.7.0.8 homebrew formula may hold 
some relevant secrets:

https://github.com/Homebrew/homebrew-core/blob/master/Formula/povray.rb


If the problems you encounter are related to linking with the boost 
libraries, there's good news: I just happen to have completed changes 
that do away with this requirement. (We still need boost, but we don't 
need to link to it.)

Unfortunately, the first v3.8.0-alpha development release with these 
properties (v3.8.0-alpha.10064268) fails to build in certain scenarios, 
but a fix for that problem is already included in the latest 
v3.8.0-x.freetype release (just a few minutes old):

https://github.com/POV-Ray/povray/releases/tag/v3.8.0-x.freetype.3

You'll need the `freetype` homebrew package for this.


Alternatively, there is Yvo's semi-official dedicated Mac version, which 
comes with a GUI. But whether it can be installed and/or run from the 
command-line (whatever it is you actually need) is beyond my knowledge.


Last not least, you can of course wait for the Homebrew people to 
support POV-Ray v3.8.0, but I guess is that won't happen until v3.8.0 is 
officially released.

[Jake] Pov-ray 3.8 or 3.7.1 Command Line for Macintosh [2617 days 3 hours and 36 minutes ago]

Tue, 19 Feb 2019 06:05:01 GMT

Hi,

I've been trying to install pov-ray from the command line for my Macintosh (High
Sierra 10.13.6) and have had little succes with any version other than 3.7 which
I was able to install through homebrew. I was wondering if there will be a
command line release of version 3.7.1 or 3.8 for Macintosh in the near future as
I have a program called Ovito that requires either 3.7.1 or above to produce
omnidirectional stereo projection images.

Any help would be greatly appreciated, thank you.

[clipka] Re: Fwd: Stack Size Testers Wanted [2619 days 7 hours and 47 minutes ago]

Sun, 17 Feb 2019 01:53:51 GMT

Am 16.02.2019 um 16:17 schrieb William F Pokorny:

> I've attached an attractors.zip file to a comment to the github issue:
> 
> https://github.com/POV-Ray/povray/issues/239

Thanks - yes, that seems to be the right stuff for testing this.

To reduce parsing and rendering time, I'm testing a slightly modified 
version with 100 instead of 1000 iterations, i.e.:

clifford (1.6,1.9, 0.5,-1.4, -0.4,-0.1, -1.6,1.8, 100, 0.0005, 0.00375, 
cliff_mat, cliff_trans)


On my Windows machine and the x64 Debug version (which should be a bit 
more memory-hungry than the others), I've just compared commit accc779d 
(which did away with the `FixedSimpleVector`, back in 2017-11-10) with 
the commit immediately before, with the following results:

- Before: Required a POV_THREAD_STACK_SIZE of 2 MiB.
- After: Requires a lousy 16 kiB.

I also ran the last test with 1000 iterations just for giggles, with the 
same result: 16 kiB was still sufficient.


I also see no trouble with the Sturmian root solver at 16 kiB (tested 
with `objects/torus1.pov` sample scene, with `sturm` added to torus 
definitions).


So, bottom line: Judging from this first test, even OS X's 512 kiB 
should be enough for everybody now ;)

[clipka] Re: Fwd: Stack Size Testers Wanted [2619 days 12 hours and 2 minutes ago]

Sat, 16 Feb 2019 21:39:11 GMT

Am 16.02.2019 um 16:17 schrieb William F Pokorny:

> This leads to me close with being somewhat worried about the suggested 
> test size of 512KB.

The "target" size of 512 kiB is an invariant - that's the per-thread 
stack size we would get on OS X by default.

> We still have some largish stack allocations - the 
> sturm solver when we increased the max order from 15 to 35(why ?) in 
> v3.7 now causes a 600KB plus (??? don't recall exactly) allocation on 
> the stack - at a considerable performance penalty I'll add(1) - no 
> matter the actual incoming equation order. This alone might cause your 
> suggested size of 512KB to fail. Well, except perhaps on windows where 
> presumably splitting still in place.

Where would those 600 kB be allocated?

The only out-of-the-ordinary local variable I see in all of the 
polynomial solver code is `sseq` in `polysolve()`, which is 36 elements 
of type `polynomial`, which in turn consists of 1 integer and 36 
doubles. That's about 10 kB, not 600.

> (1) - My C++ ish attempts to address this have all been really slow or 
> not worked at all when I try to get fancy/fast with raw memory 
> allocations and pointers.

If the variable is local to a function that is guaranteed to never be 
called recursively, the easiest solution to guarantee speedy allocation 
and not hogging the stack is to change the variable declaration to 
`thread_local`. This is essentially the same as `static`, but with each 
thread having its own copy of the variable.

> C and some C++ compilers (IBM's XLC being one) 
> support the needed dynamic structure array-size allocation mechanism 
> with high performance. This a reason - among others - why I'm toying 
> some with taking the common solver code back to straight C. We will 
> soon, I think? - move to a mixed C++/C mode in picking up FreeType 
> which, as I remember, is actually a C library - so perhaps not so crazy.

Veto to that: All of POV-Ray should be valid C++11 code, so that POV-Ray 
can be compiled with only a single C++ compiler. 3rd party libraries are 
another matter; we expect those to be present in binary form (except on 
Windows, where we expect their source code to be compatible with MSVC's 
dialect of C/C++), and the headers of modern C libs are almost 
invariably designed as hybrid C/C++ headers, in the sense that they use 
pre-processor features to behave as either C or C++ code, depending on 
the compiler used.

There is currently only one genuine C source file ihn POV-Ray proper, 
namely `povms.c`, and even that one is designed as a C/C++ hybrid and 
compiled by including it from a `.cpp` file. (The rationale for this C 
file's existence being that it - in theory - allows 3rd party genuine C 
programs to drive the POV-Ray back-end via POVMS.)

[kurtz le pirate] Re: Some simple testing needed [2619 days 17 hours and 44 minutes ago]

Sat, 16 Feb 2019 15:56:44 GMT

Le 13/02/2019 Ã  20:53, clipka a Ã©critÂ :
> Hi folks,
> 
> can a few of you folks please run the following little program on your 
> computers and report the time it takes to run?
> 
> --------------------------------------------------
> #include <chrono>
> #include <thread>
> #include <iostream>
> 
> inline void Delay(unsigned int msec)
> {
>  Â Â Â 
std::this_thread::sleep_for(std::chrono::milliseconds(msec));
> }
> 
> int main()
> {
>  Â Â Â  int count =Â  1000;
>  Â Â Â  for (int i = 0; i < count; ++i)
>  Â Â Â  {
> 
Â Â Â Â Â Â Â 
Delay(1);
>  Â Â Â  }
>  Â Â Â  std::cout << "Done." << std::endl;
> }
> --------------------------------------------------
> 
> On Windows Subsystem For Linux I see results like the following:
> 
> realÂ Â Â  0m1.782s
> userÂ Â Â  0m0.000s
> sysÂ Â Â Â  0m0.000s
> 
> But as I presume this is using the Windows scheduler, I expect that 
> genuine Linux systems may behave differently, and I'm also interested in 
> other platforms (Mac, maybe BSD if some of you folks are using that, or 
> actually any system you can get your hands on.)
> 
> I have also reason to believe that results may differ between compilers. 
> Using g++ 5.4.0 here.

my little contribution on Mac Intel i5 - 2,7 Ghz.

g++ -v :
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr 
--with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk/usr/include/c++/4.2.1
Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn)
Target: x86_64-apple-darwin13.4.0
Thread model: posix

uname -v :
Darwin Kernel Version 13.4.0: Mon Jan 11 18:17:34 PST 2016; 
root:xnu-2422.115.15~1/RELEASE_X86_64


result :

	real	0m1.239s
	user	0m0.009s
	sys	0m0.019s






-- 
Kurtz le pirate
Compagnie de la Banquise

[William F Pokorny] Re: Fwd: Stack Size Testers Wanted [2619 days 18 hours and 23 minutes ago]

Sat, 16 Feb 2019 15:17:34 GMT

On 2/15/19 7:44 PM, clipka wrote:
> Forgot to cross-post to `povray.beta-test`:
> 
> -------- Weitergeleitete Nachricht --------
> Betreff: Stack Size Testers Wanted
> Datum: Sat, 16 Feb 2019 01:40:46 +0100
> Von: clipka <ano### [at] anonymousorg>
> Newsgruppen: povray.macintosh
> 
> Hi folks,
> 
> I'm looking for guinea pigs for a particular test.
> 
> 
> Here's the background:
> 
> A while ago we (well, some of you) were having issues with crashes due 
> to insufficient thread stack size on Mac OS X, or in one case even on 
> Linux; we solved these issues with a workaround to override the 
> per-thread stack size (or, in the Linux case, increase that override).
> 
...

I've attached an attractors.zip file to a comment to the github issue:

https://github.com/POV-Ray/povray/issues/239

which is a related open issue. One which should be closed if recent 
updates have better addressed the problem.

The zip contains a set of test cases from ThH (Thorsten) at the bottom 
should others want to test in their environment(s). Two or more of which 
failed still after the updates in early 2017. Third down being one of 
these.

These now all run cleanly for me. Ubuntu 18.04 at master (v38) at commit 
054e75c.

And 3rd fails still for me going back to v3.71 release branch at commit 
9808f53 (Jun 24 2017 with updates).

Christoph, Remember we at some point ran across some information 
suggesting windows runs with stack monitoring and splitting/growing the 
stack. Perhaps why windows could always run with a smaller stack and why 
we never saw such fails on windows. Stack splitting as needed due growth 
could be turned on with the gnu compiler - at a performance hit. This 
suggested we might want to turn off such splitting in windows for a 
performance gain. All two year old looks though, and nothing ever tried 
as far as I know, so who knows how things stand today. If just a windows 
compiler setting for you though, might be worth just trying a windows 
compile with splitting off if we are in good shape thread-stack size 
wise.

This leads to me close with being somewhat worried about the suggested 
test size of 512KB. We still have some largish stack allocations - the 
sturm solver when we increased the max order from 15 to 35(why ?) in 
v3.7 now causes a 600KB plus (??? don't recall exactly) allocation on 
the stack - at a considerable performance penalty I'll add(1) - no 
matter the actual incoming equation order. This alone might cause your 
suggested size of 512KB to fail. Well, except perhaps on windows where 
presumably splitting still in place.

I did not run master with 512KB as you suggested or a clang compile with 
the current larger default. I'm focused elsewhere at the moment and 
changes to the more common headers are painfully slow for me to compile 
and try.

Bill P.

(1) - My C++ ish attempts to address this have all been really slow or 
not worked at all when I try to get fancy/fast with raw memory 
allocations and pointers. C and some C++ compilers (IBM's XLC being one) 
support the needed dynamic structure array-size allocation mechanism 
with high performance. This a reason - among others - why I'm toying 
some with taking the common solver code back to straight C. We will 
soon, I think? - move to a mixed C++/C mode in picking up FreeType 
which, as I remember, is actually a C library - so perhaps not so crazy.

[clipka] Stack Size Testers Wanted [2620 days 9 hours ago]

Sat, 16 Feb 2019 00:40:46 GMT

Hi folks,

I'm looking for guinea pigs for a particular test.


Here's the background:

A while ago we (well, some of you) were having issues with crashes due 
to insufficient thread stack size on Mac OS X, or in one case even on 
Linux; we solved these issues with a workaround to override the 
per-thread stack size (or, in the Linux case, increase that override).

In the meantime, some changes have been made to the code which should 
have reduced POV-Ray's stack requirements, so my hope is that the 
workaround is no longer necessary - which would be great news, because 
we could get rid of the entire boost thread library.


Here's where you come in:

If you have ever experienced problems related to the thread stack size, 
and still have a scene available that ran into these issues, then I'd 
like to enlist your help.

@dick balaska:

I'm not sure if you're aware, but I know you were affected; see your 
post on 2017-02-12 in povray.beta-test titled "crash in origin/master" 
(http://news.povray.org/povray.beta-test/thread/%3C58a1e32f%241%40news.povray.org%3E/)


Here's what I'd like you to do:


(1) Reproduce the old problem and workaround [optional]

- Grab the source code of a sufficiently OLD v3.8.0-alpha (BEFORE 
v3.8.0-alpha.9436902; anything built BEFORE December 2017 should do), 
v3.7.1-alpha/beta or even the latest v3.7.0.

- In the file `source/backend/configbackend.h`, place the following 
lines at the end of the file:

     #undef POV_THREAD_STACK_SIZE
     #define POV_THREAD_STACK_SIZE (512 * 1024) // 512 KiB

- Build POV-Ray.

- Run whatever scene you remember crashing on you.

- Verify that the scene does indeed crash. (If not, your scene does not 
seem to be a suitable test candidate.)

- If you want to go the extra mile, increase POV_THREAD_STACK_SIZE to 
see at which size the scene ceases to crash. (I recommend doubling the 
value; you shouldn't have to go any further than 8*1024*1024.)


(2) Test whether the workaround is still required

- Grab the source code of a sufficiently NEW v3.8.0-alpha (AT LEAST 
v3.8.0-alpha.9436902 or newer; anything built in 2018 or 2019 should do; 
I'd recommend the newest tagged alpha though).

- Apply the same changes to `source/backend/configbackend.h` as 
described above.

- Build POV-Ray.

- Run your test scene.

- Observe whether the scene crashes or not.

- If you want to go the extra mile, change POV_THREAD_STACK_SIZE to see 
at which size the behaviour changes: If the scene crashes, increase the 
value until it ceases to; if the scene does not crash, decrease the 
value until it does. (I recommend doubling / halving the value.)


(3) Report your observations.


Your help is very much appreciated!

[clipka] Re: Some simple testing needed [2620 days 16 hours and 59 minutes ago]

Fri, 15 Feb 2019 16:42:12 GMT

Am 15.02.2019 um 08:40 schrieb ingo:
> compiling with the wrong compiler and wrong option creates no errors and
> a program that won't run but you don't notice because the test file test
> is not called but test (check file types and compare values) that is
> already present on the system...

Oh yeah - that's a good one :)

Even better than trying to judge the run-time performance of certain 
code under optimization, and typing `g++ -o3 -ffast-math -o test 
test.cpp` instead of `g++ -O3 -ffast-math -o test test.cpp`...

> But, the proper results are in:
> 
> FreeBSD Clang 6.0
> Delay 1
> 0.000u 0.005s 0:01.07 0.0%      0+0k 2+0io 0pf+0w
> 
> Delay 10
> 0.000u 0.006s 0:10.64 0.0%      0+0k 6+0io 15pf+0w
> 
> Delay 100
> 0.000u 0.005s 1:46.24 0.0%      0+0k 2+0io 0pf+0w

That's 1.07 ms, 10.64 ms and 106.24 ms, respectively, which makes a lot 
more sense :)

> Mingwin g++.exe (Rev1, Built by MSYS2 project) 8.2.1 20181207
> Delay 1
> real    0m15.822s
> user    0m0.000s
> sys     0m0.015s
> 
> Delay 10
> real    0m15.759s
> user    0m0.000s
> sys     0m0.031s
> 
> Delay 100
> real    1m49.566s
> user    0m0.015s
> sys     0m0.031s
> 
> ingo

That, too, makes sense, and indicates that MinGW has a minimum wait of 
ca. 15 ms (on average at any rate). Which is fine, as C++11 allows 
implementations to wait longer than requested (but not less).

[Le Forgeron] Re: Some simple testing needed [2620 days 17 hours and 4 minutes ago]

Fri, 15 Feb 2019 16:36:55 GMT

Le 13/02/2019 Ã  20:53, clipka a Ã©critÂ :
> But as I presume this is using the Windows scheduler, I expect that
> genuine Linux systems may behave differently, and I'm also interested in
> other platforms (Mac, maybe BSD if some of you folks are using that, or
> actually any system you can get your hands on.)
> 
> I have also reason to believe that results may differ between compilers.
> Using g++ 5.4.0 here.

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.10
Release:	18.10
Codename:	cosmic

====

For gcc:

$ time ./a.out
Done.

real	0m1,096s
user	0m0,000s
sys	0m0,015s

$ g++ --version
g++ (Ubuntu 8.2.0-7ubuntu1) 8.2.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


====

For icpc:

$ time ./a.out
Done.

real	0m1,094s
user	0m0,000s
sys	0m0,015s

$ icpc --version
icpc (ICC) 19.0.1.144 20181018
Copyright (C) 1985-2018 Intel Corporation.  All rights reserved.


====

For clang:

$ time ./a.out
Done.

real	0m1,094s
user	0m0,015s
sys	0m0,000s

$ clang++ --version
clang version 7.0.0-3 (tags/RELEASE_700/final)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin

[ingo] Re: Some simple testing needed [2621 days 2 hours ago]

Fri, 15 Feb 2019 07:40:37 GMT

in news:5c65ee33$1@news.povray.org clipka wrote:

> _totally_ bonkers

Take a deep breath.
You have been warned, 
compiling with the wrong compiler and wrong option creates no errors and 
a program that won't run but you don't notice because the test file test 
is not called but test (check file types and compare values) that is 
already present on the system...

But, the proper results are in:

FreeBSD Clang 6.0
Delay 1
0.000u 0.005s 0:01.07 0.0%      0+0k 2+0io 0pf+0w

Delay 10
0.000u 0.006s 0:10.64 0.0%      0+0k 6+0io 15pf+0w

Delay 100
0.000u 0.005s 1:46.24 0.0%      0+0k 2+0io 0pf+0w


Mingwin g++.exe (Rev1, Built by MSYS2 project) 8.2.1 20181207
Delay 1
real    0m15.822s
user    0m0.000s
sys     0m0.015s

Delay 10
real    0m15.759s
user    0m0.000s
sys     0m0.031s

Delay 100
real    1m49.566s
user    0m0.015s
sys     0m0.031s

ingo

[clipka] Re: Some simple testing needed [2621 days 11 hours and 1 minute ago]

Thu, 14 Feb 2019 22:39:47 GMT

Am 14.02.2019 um 08:15 schrieb ingo:
> in news:5c64a63c$1@news.povray.org clipka wrote:
> 
>> "EEeeks!"
> 
...
> delay 1000
> % time test
> 0.000u 0.001s 0:00.00 0.0%      0+0k 2+0io 0pf+0w
...
> delay 100
> real    0m0.064s
> user    0m0.015s
> sys     0m0.015s

Now that seems _totally_ bonkers. Can you add some output to the loop, 
say `cout << i << endl`, to make sure the compiler isn't just optimizing 
away the entire loop?

[ingo] Re: Some simple testing needed [2622 days 2 hours and 26 minutes ago]

Thu, 14 Feb 2019 07:15:17 GMT

in news:5c64a63c$1@news.povray.org clipka wrote:

> "EEeeks!"

FreeBSD

delay 10
% time test
0.000u 0.001s 0:00.00 0.0%      0+0k 2+0io 0pf+0w

delay 100
% time test
0.000u 0.001s 0:00.00 0.0%      0+0k 2+0io 0pf+0w

delay 1000
% time test
0.000u 0.001s 0:00.00 0.0%      0+0k 2+0io 0pf+0w


Mingwin

delay 10
real    0m0.143s   
user    0m0.000s   
sys     0m0.000s   

real    0m0.068s
user    0m0.000s
sys     0m0.046s


delay 100
real    0m0.064s
user    0m0.015s
sys     0m0.015s

[Tor Olav Kristensen] Re: Some simple testing needed [2622 days 10 hours and 1 minute ago]

Wed, 13 Feb 2019 23:40:01 GMT

clipka <ano### [at] anonymousorg> wrote:
> Hi folks,
>
> can a few of you folks please run the following little program on your
> computers and report the time it takes to run?
>...

tok@ava:~$ g++ test.cpp -o test

tok@ava:~$ time ./test
Done.

real 0m1,083s
user 0m0,008s
sys 0m0,015s

tok@ava:~$ g++ --version
g++ (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

tok@ava:~$ grep "model name" /proc/cpuinfo
model name : Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
model name : Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
model name : Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
model name : Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz

tok@ava:~$ lsb_release -d
Description: Ubuntu 18.04.2 LTS

--
Tor Olav
http://subcube.com

[clipka] Re: Some simple testing needed [2622 days 10 hours and 21 minutes ago]

Wed, 13 Feb 2019 23:20:28 GMT

"EEeeks!" for both the FreeBSD and MinGW results (not your fault obviously).

Can you try again with a `Delay(10)` and `Delay(100)` to see what 
happens? And if they behave nicely (i.e. give results of 10s upward and 
100s upward, respectively), can you spare some time and try to figure 
out what the "sweet spot" is?

In case you're curious what I'm doing: I'm testing whether 
`std::this_thread::sleep_for()` is - as advertised by the C++11 standard 
- suitable as a portable way of waiting for _at least_ the specified 
duration. If that is the case, then `Delay(msec)` should wait for at 
least the specified number of millisconds, and thus the entire program 
(doing 1000 such invocations in a loop) should wait for at least the 
specified number of seconds.

But alas! Standards are only as good as the rigorosity by which they are 
implemented.


Am 13.02.2019 um 23:02 schrieb ingo:
> in news:XnsA9F5E84C73117seed7@news.povray.org ingo wrote:
> 
>>
>>
> On Win with Mingwing
> 
> $ gcc --version
> gcc.exe (Rev1, Built by MSYS2 project) 8.2.1 20181207
> Copyright (C) 2018 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> PURPOSE.
> 
> $ time test.exe
> 
> real    0m0.065s
> user    0m0.015s
> sys     0m0.015s
> 
> ingo
>

[dick balaska] Re: Some simple testing needed [2622 days 10 hours and 41 minutes ago]

Wed, 13 Feb 2019 22:59:59 GMT

On 2/13/19 2:53 PM, clipka wrote:

> 
> On Windows Subsystem For Linux I see results like the following:
> 
> realÂ Â Â  0m1.782s
> userÂ Â Â  0m0.000s
> sysÂ Â Â Â  0m0.000s
> 

my i7

dick@cyd:/tmp/x$ g++ foo.c
dick@cyd:/tmp/x$ time ./a.out
Done.

real	0m1.100s
user	0m0.000s
sys	0m0.018s


dick@cyd:/tmp/x$ uname -a
Linux cyd 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux

dick@cyd:/tmp/x$ g++ --version
g++ (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0


One of my i5's

[liza:/tmp/x] g++ foo.c -std=c++11
[liza:/tmp/x] time ./a.out
Done.

real	0m1.074s
user	0m0.000s
sys	0m0.016s
[liza:/tmp/x] uname -a
Linux liza 4.4.0-142-generic #168-Ubuntu SMP Wed Jan 16 21:00:45 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
[liza:/tmp/x] g++ --version
g++ (Ubuntu 5.4.0-6ubuntu1~16.04.11) 5.4.0 20160609

-- 
dik
Rendered 1024 of 921600 pixels (0%)

[ingo] Re: Some simple testing needed [2622 days 11 hours and 38 minutes ago]

Wed, 13 Feb 2019 22:02:36 GMT

in news:XnsA9F5E84C73117seed7@news.povray.org ingo wrote:

> 
> 
On Win with Mingwing

$ gcc --version
gcc.exe (Rev1, Built by MSYS2 project) 8.2.1 20181207
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
PURPOSE.

$ time test.exe

real    0m0.065s
user    0m0.015s
sys     0m0.015s

ingo

[ingo] Re: Some simple testing needed [2622 days 11 hours and 51 minutes ago]

Wed, 13 Feb 2019 21:50:09 GMT

in news:5c6475d2$1@news.povray.org clipka wrote:

Beware, I've no clue but got some data, educate me if wrong,

% cc --version
FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 
6.0.0)
Target: x86_64-unknown-freebsd11.2
Thread model: posix
InstalledDir: /usr/bin

% cc -c -o test test.cc

% time test
0.000u 0.001s 0:00.00 0.0%      0+0k 2+0io 0pf+0w

ingo

[jr] Re: Some simple testing needed [2622 days 13 hours and 1 minute ago]

Wed, 13 Feb 2019 20:40:00 GMT

hi,

clipka <ano### [at] anonymousorg> wrote:
> can a few of you folks please run the following little program on your
> computers and report the time it takes to run?
> --------------------------------------------------
> #include <chrono>
> #include <thread>
> #include <iostream>
>
> inline void Delay(unsigned int msec)
> {
>      std::this_thread::sleep_for(std::chrono::milliseconds(msec));
> }
>
> int main()
> {
>      int count =  1000;
>      for (int i = 0; i < count; ++i)
>      {
>          Delay(1);
>      }
>      std::cout << "Done." << std::endl;
> }
> --------------------------------------------------
> On Windows Subsystem For Linux I see results like the following:
>
> real    0m1.782s
> user    0m0.000s
> sys     0m0.000s
>
> But as I presume this is using the Windows scheduler, I expect that
> genuine Linux systems may behave differently, and I'm also interested in
> other platforms (Mac, maybe BSD if some of you folks are using that, or
> actually any system you can get your hands on.)
>
> I have also reason to believe that results may differ between compilers.
> Using g++ 5.4.0 here.

the laptop (i3 2.3GHz):

jr@goose:46:tmp$ time ./a.out
Done.

real    0m1.109s
user    0m0.004s
sys     0m0.031s

jr@goose:47:tmp$ c++ --version
c++ (GCC) 5.5.0
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

jr@goose:48:tmp$ cat /etc/slackware-version
Slackware 14.2

uses 4.4.157 kernel.


on another i3 (3.1GHz):

jr@crow:10:tmp$ time ./a.out
Done.

real    0m1.084s
user    0m0.002s
sys     0m0.010s

jr@crow:11:tmp$ c++ --version
c++ (GCC) 4.8.2
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

jr@crow:12:tmp$ cat /etc/slackware-version
Slackware 14.1

uses 3.10.17 kernel.



regards, jr.

[clipka] Some simple testing needed [2622 days 13 hours and 47 minutes ago]

Wed, 13 Feb 2019 19:53:54 GMT

Hi folks,

can a few of you folks please run the following little program on your 
computers and report the time it takes to run?

--------------------------------------------------
#include <chrono>
#include <thread>
#include <iostream>

inline void Delay(unsigned int msec)
{
     std::this_thread::sleep_for(std::chrono::milliseconds(msec));
}

int main()
{
     int count =  1000;
     for (int i = 0; i < count; ++i)
     {
         Delay(1);
     }
     std::cout << "Done." << std::endl;
}
--------------------------------------------------

On Windows Subsystem For Linux I see results like the following:

real    0m1.782s
user    0m0.000s
sys     0m0.000s

But as I presume this is using the Windows scheduler, I expect that 
genuine Linux systems may behave differently, and I'm also interested in 
other platforms (Mac, maybe BSD if some of you folks are using that, or 
actually any system you can get your hands on.)

I have also reason to believe that results may differ between compilers. 
Using g++ 5.4.0 here.

[clipka] Broken Mac OS X build - help appreciated [2624 days 14 hours and 14 minutes ago]

Mon, 11 Feb 2019 19:26:47 GMT

Hi folks,

Commit 5219e71c does not compile on Mac OS X, and I'm not really sure why.

The build runs into a compile error in `base/image/jpeg.cpp`, in which 
`TRUE` is passed to a JPEG lib function parameter of type `boolean`.

Now by some quirks of the include hierarchy, a header file 
`mach/boolean.h` is pulled in (apparently _after_ `<jpeglib.h>`), and 
defines `TRUE` as `1`, while JPEGlib apparently wants it to be... well, 
something else apparently, fitting the type `boolean` - whatever that 
might end up being defined as.

I'll be pushing a workaround any moment now, but I'd really like to know 
what's going on there. If someone with better access to a Mac system (or 
maybe just a different pair of Mk1 eyeballs) could have a look into 
this, I'd greatly appreciate it.

[Yvo Smellenbergh] POV-Ray v3.8.0-alpha.10013324 for macintosh avai... [2651 days 17 hours and 20 minutes ago]

Tue, 15 Jan 2019 16:20:58 GMT

http://megapov.inetart.net/povrayunofficial_mac/alphapov.html

Bump to 10013324

--
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] POV-Ray v3.8.0-alpha.10011104 for Macintosh avai... [2653 days 17 hours and 21 minutes ago]

Sun, 13 Jan 2019 16:20:15 GMT

http://megapov.inetart.net/povrayunofficial_mac/alphapov.html

Simply updated to 10011104, userd-defined functions fix included.

--
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] POV-Ray Final 3.7.0.8 for Macintosh available [2695 days 23 hours and 21 minutes ago]

Sun, 2 Dec 2018 10:20:02 GMT

- fixed a bug in the preferences panels (enable/disable options) on Mojave

Note: Runs on Mojave but DarkMode not supported
http://megapov.inetart.net/povrayunofficial_mac/finalpov.html
-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] POV-Ray v3.8.0-alpha.9945627 available for Macin... [2695 days 23 hours and 23 minutes ago]

Sun, 2 Dec 2018 10:17:58 GMT

- updated to the latest Alpha version
- fixed a bug in the preferences panels (enable/disable options) on Mojave

http://megapov.inetart.net/povrayunofficial_mac/alphapov.html

-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Re: POV-Ray v3.8.0-alpha.9893777 [2723 days 15 hours and 51 minutes ago]

Sun, 4 Nov 2018 17:49:53 GMT

On 2018-10-24 01:46:43 +0000, clipka said:

> It's been weeks since the last release, so:
> 
> https://github.com/POV-Ray/povray/releases/tag/v3.8.0-alpha.9893777
> 
> Just bugfixes this time - one for jr (deleting from a dictionary), one 
> for Warren (dithering), and one for our static code analysis tool 
> (memory leak).


I will upload a new version on the website soon but for now here is a 
direct link to the archive (only excecutable):
http://megapov.inetart.net/povrayunofficial_mac/povray_downloads/Pov-Ray 
3.8.x.app.zip
Also fixed a problem with enable/disable controls (checkbox, 
textfields,..) on some dialogs (Mojave specific).


-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Re: Unable to get Insert Menu to function in GUI [2736 days 17 hours and 1 minute ago]

Mon, 22 Oct 2018 16:39:37 GMT

On 2018-10-20 23:48:21 +0000, clipka said:

> Am 17.10.2018 um 22:03 schrieb SergePB:
>> Just unzipped, opened the folder and clicked on PovRay executable.  I see the
>> Templates, but now "Insert Menu".  Am I missing something? Install workaround?

Go to the menu â€œPOVRay ..â€ >>
â€œPreferences..â€
Choose the editor tab
Hit the â€œInsert Folderâ€ button on the bottom of the
panel, now choose 
the â€œInsert Menuâ€ folder  from the expanded archive
in the file 
selector panel.
You can also adjust the size of the images shown in the menuâ€™s with
the 
slider â€œScale insert menu imagesâ€.
Hit â€œApplyâ€ or
â€œOkâ€.
The insert menu will now be populated with the items from the â€œInsert

menuâ€ folder you selected.
Only selectable when an editor window is the front most window of course.

Yvo


>> 
>> Otherwise, thanks for porting this to the Mac.
> 
> You might want to get Yvo's attention on povray.macintosh.

;-)

-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[clipka] Re: Unable to get Insert Menu to function in GUI [2738 days 9 hours and 53 minutes ago]

Sat, 20 Oct 2018 23:48:19 GMT

Am 17.10.2018 um 22:03 schrieb SergePB:
> Just unzipped, opened the folder and clicked on PovRay executable.  I see the
> Templates, but now "Insert Menu".  Am I missing something? Install workaround?
> 
> Otherwise, thanks for porting this to the Mac.

You might want to get Yvo's attention on povray.macintosh.

[Yvo Smellenbergh] POV-Ray v3.8.0-alpha.9844500 for Macintosh avail... [2766 days 1 hour and 8 minutes ago]

Sun, 23 Sep 2018 08:33:31 GMT

http://megapov.inetart.net/povrayunofficial_mac/alphapov.html

- Updated to alpha. 9844500 (mode 3 anti-aliasing options in the 
preferences panel)

-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Re: Thanks... [2772 days 16 hours and 30 minutes ago]

Sun, 16 Sep 2018 17:11:08 GMT

On 2018-09-11 16:05:27 +0000, aeffects said:

> It's been well over 20 years now (for me). Pov-ray has provided hours and hours
> of fun. Many thanks to those that tirelessly work to keep the program updated
> (and ported to the Mac).
> 
> Thanks again for all your time and effort.
> 
> David Healy
> Reno/Lake Tahoe

Yes, well over 20 years for me too!

And I don't know how many versions by now but I just released version 
2689 or something... ;-)



-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] POV-Ray v3.8.0-alpha.9811560 for Macintosh ready [2772 days 16 hours and 41 minutes ago]

Sun, 16 Sep 2018 16:59:57 GMT

http://megapov.inetart.net/povrayunofficial_mac/alphapov.html

- Updated to alpha.9811560
- added basic support for DarkMode. I will continue to update in next versions.


-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[aeffects] Thanks... [2777 days 13 hours and 31 minutes ago]

Tue, 11 Sep 2018 20:10:00 GMT

It's been well over 20 years now (for me). Pov-ray has provided hours and hours
of fun. Many thanks to those that tirelessly work to keep the program updated
(and ported to the Mac).

Thanks again for all your time and effort.

David Healy
Reno/Lake Tahoe

[Yvo Smellenbergh] Re: Run povray from Terminal (Command Line) [2867 days 23 hours and 18 minutes ago]

Wed, 13 Jun 2018 10:22:57 GMT

On 2018-06-12 06:19:21 +0000, Jay said:

> Hi,
> 
> Is there a way to run povray from the command line in Terminal on Mac?
Yes, on my site you can download a compiled version:
http://megapov.inetart.net/povrayunofficial_mac/finalpov.html
"Download 3.7.0 command line".

You can also compile it from source just like any unix version but like 
always you have to
make sure all the libraries and xcode are installed.

Yvo

> 
> i.e. If I ran povray from the command line, passing the .pov file as an 
> argument
> and then it run in Terminal and produces the image file?
> 
> I have a java application that I would like to be able to use povray to 
> generate
> images. I want to be able to programmatically run povray from my java
> application and the only way I can think of doing this is through the command
> line.
> 
> Thanks
> 
> Jay


--
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Jay] Run povray from Terminal (Command Line) [2868 days 23 hours and 21 minutes ago]

Tue, 12 Jun 2018 10:20:01 GMT

Hi,

Is there a way to run povray from the command line in Terminal on Mac?

i.e. If I ran povray from the command line, passing the .pov file as an argument
and then it run in Terminal and produces the image file?

I have a java application that I would like to be able to use povray to generate
images. I want to be able to programmatically run povray from my java
application and the only way I can think of doing this is through the command
line.

Thanks

Jay

[Jay] Re: Help launching povray [2868 days 23 hours and 21 minutes ago]

Tue, 12 Jun 2018 10:20:01 GMT

Thank you, they were very helpful


Yvo Smellenbergh <E-mail: yvo(DOT)s(AT)gmx.net> wrote:
> On 2018-06-09 12:01:49 +0000, Jay said:
>
> Here are some movies a just made to show how to make things work:
> http://megapov.inetart.net/povrayunofficial_mac/mov.html
> No sound, no text,... Never done this before.
>
>
> Yvo
>
>
> > Hi,
> >
> > I've never used povray before so have no idea what I am doing.
> >
> > I've been following the tutorial on creating a simple sphere and have a
> > complete
> > demo.pov file.
> >
> > But I now have no idea how to render this image/scene.
> >
> > I'm not sure where to download the povray software from for Mac, and when I did
> > try and download the software, it had no idea how to run the
> > application or even
> > run it from terminal.
> >
> > Please can someone help me get started with these basic steps for beginning to
> > use povray.
> >
> > Thank you for your time.
> >
> > Jay
>
>
> --
> Yvo
>
> --
>
-------------------------------------------------------------------------------------------
>
> POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
> UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
> MegaPOV: http://megapov.inetart.net
> E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Re: Help launching povray [2870 days 16 hours and 32 minutes ago]

Sun, 10 Jun 2018 17:09:17 GMT

On 2018-06-09 12:01:49 +0000, Jay said:

Here are some movies a just made to show how to make things work:
http://megapov.inetart.net/povrayunofficial_mac/mov.html
No sound, no text,... Never done this before.


Yvo


> Hi,
> 
> I've never used povray before so have no idea what I am doing.
> 
> I've been following the tutorial on creating a simple sphere and have a 
> complete
> demo.pov file.
> 
> But I now have no idea how to render this image/scene.
> 
> I'm not sure where to download the povray software from for Mac, and when I did
> try and download the software, it had no idea how to run the 
> application or even
> run it from terminal.
> 
> Please can someone help me get started with these basic steps for beginning to
> use povray.
> 
> Thank you for your time.
> 
> Jay


--
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Re: Feature request [2870 days 16 hours and 32 minutes ago]

Sun, 10 Jun 2018 17:09:12 GMT

On 2018-06-10 15:41:40 +0000, kurtz le pirate said:

> Hello,
> 
> When generating animations, have a progress window from initial_frame 
> to final_frame (or vice versa).
> 
> Not "must-have" but useful.

Ok, on the list for a future release (if possible).


--
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[kurtz le pirate] Feature request [2870 days 17 hours and 59 minutes ago]

Sun, 10 Jun 2018 15:41:41 GMT

Hello,

When generating animations, have a progress window from initial_frame to 
final_frame (or vice versa).

Not "must-have" but useful.




-- 
Kurtz le pirate
Compagnie de la Banquise

[Bald Eagle] Re: Help launching povray [2871 days 12 hours and 16 minutes ago]

Sat, 9 Jun 2018 21:25:00 GMT

Try  Yvo's site - he's the Mac wizard for POV-Ray

http://megapov.inetart.net/povrayunofficial_mac/finalpov.html

[Jay] Help launching povray [2871 days 17 hours and 36 minutes ago]

Sat, 9 Jun 2018 16:05:01 GMT

Hi,

I've never used povray before so have no idea what I am doing.

I've been following the tutorial on creating a simple sphere and have a complete
demo.pov file.

But I now have no idea how to render this image/scene.

I'm not sure where to download the povray software from for Mac, and when I did
try and download the software, it had no idea how to run the application or even
run it from terminal.

Please can someone help me get started with these basic steps for beginning to
use povray.

Thank you for your time.

Jay

[Yvo Smellenbergh] POV-Ray v3.8.0-Alpha 9606898 optimized noise for... [2884 days 16 hours and 54 minutes ago]

Sun, 27 May 2018 16:47:18 GMT

The CPU-Specific optimizations for Noise generator are now also part of 
this Mac-port.

v3.8.0.x is only for system 10.7.5 or later.

http://megapov.inetart.net/povrayunofficial_mac/alphapov.html


-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Francois LE COAT] Re: POV-Ray 3.7.0.7 for mac available [2889 days 16 hours and 26 minutes ago]

Tue, 22 May 2018 17:15:18 GMT

Hi Yvo,

E-mailyvo s gmx.net writes:
> Francois LE COAT said:
>> E-mailyvo s gmx.net writes:
>>> Fix in the display window and updated to 3.7.0.7 (no new functionalit
y)
>>>
>>> http://megapov.inetart.net/povrayunofficial_mac/finalpov.html
>>> --
>>> Yvo
>>
>> Why isn't it available for Mac OS X 10.6.8 (Snow Leopard) ? This is
>> called "programmed obsolescence" because there's nothing to explain !
>>
>> -- François LE COAT
>> <http://eureka.atari.org/>
>
> 3.7.0.x *is* for 10.6.8 or later, 32 and 64 bit.
> However, the current version crashes on 10.6.8 but not on 10.7.x or lat
er.
> I will fix it.
>
> A simple bug report or email from you would have been nicer ;-)
>
> 3.8.0.x is only for 10.7.6 or later, and only 64bit.
> Current OSx version is 10.13.4, time to move on!
>
> --
> Yvo

I tested final 3.7.0.7 and it runs under 10.6.8 nicely. I could have
sent you a private report, but so many Mac softwares are abandoning
Snow Leopard support, that I was too sad. Thanks for your support.

I can't update my Mac OS X version, because my hardware is old, sorry.

Regards,

-- 
François LE COAT
<http://eureka.atari.org/>

[Yvo Smellenbergh] POV-Ray 3.7.0.7 r3 for Macintosh Available [2889 days 16 hours and 47 minutes ago]

Tue, 22 May 2018 16:53:34 GMT

Fix crash at startup on system 10.6.8.
POV-Ray 3.7.0.7 for macintosh is for system 10.6.8 and later, 32 and 64bit

http://megapov.inetart.net/povrayunofficial_mac/finalpov.html

Please note that 3.8.0.x will not run on systems prior to 10.7.5 and is 
64bit only
--
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net
http://megapov.inetart.net/povrayunofficial_mac/finalpov.html

[Yvo Smellenbergh] Re: POV-Ray 3.7.0.7 for mac available [2889 days 18 hours and 9 minutes ago]

Tue, 22 May 2018 15:31:54 GMT

On 2018-05-21 19:25:07 +0000, Francois LE COAT said:

> Hi,
> 
> E-mailyvo s gmx.net writes:
>> Fix in the display window and updated to 3.7.0.7 (no new functionality)
>> 
>> http://megapov.inetart.net/povrayunofficial_mac/finalpov.html
>> --
>> Yvo
> 
> Why isn't it available for Mac OS X 10.6.8 (Snow Leopard) ? This is
> called "programmed obsolescence" because there's nothing to explain !
> 
> -- François LE COAT
> <http://eureka.atari.org/>

3.7.0.x *is* for 10.6.8 or later, 32 and 64 bit.
However, the current version crashes on 10.6.8 but not on 10.7.x or later.
I will fix it.

A simple bug report or email from you would have been nicer ;-)

3.8.0.x is only for 10.7.6 or later, and only 64bit.
Current OSx version is 10.13.4, time to move on!

--
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Francois LE COAT] Re: POV-Ray 3.7.0.7 for mac available [2890 days 11 hours and 54 minutes ago]

Mon, 21 May 2018 21:47:11 GMT

Hi,

clipka écrit :
> Francois LE COAT wrote:
>> E-mailyvo s gmx.net writes:
>>> Fix in the display window and updated to 3.7.0.7 (no new functionalit
y)
>>>
>>> http://megapov.inetart.net/povrayunofficial_mac/finalpov.html
>>> --
>>> Yvo
>>
>> Why isn't it available for Mac OS X 10.6.8 (Snow Leopard) ? This is
>> called "programmed obsolescence" because there's nothing to explain !
>
> Well, that's the "free" part in "free/libre open source software" for
> you: The author is free to drop support for your platform any time they

> like, for any reason (or even no reason whatsoever) -- you, on the othe
r
> hand, are free to back port their changes to whatever platform you like
.
>
> Unless of course you have entered into a paid service agreement with th
e
> man.
>
> Have you?
>
> I'm not saying "programmed obsolescence" has nothing to do with it, but

> you're definitely barking up the wrong tree. Some small town in Santa
> Clara County would be closer to the mark.

Well ... There's a solution that would be the less painful. Installing
GNU/Linux on my iMac. Because Mac OS X is the worse OS on earth. So
slow and bugged on rather old hardware. Mine is from mid-2010 ... Old !

-- 
François LE COAT
<http://eureka.atari.org/>

[clipka] Re: POV-Ray 3.7.0.7 for mac available [2890 days 12 hours and 35 minutes ago]

Mon, 21 May 2018 21:05:32 GMT

Am 21.05.2018 um 21:25 schrieb Francois LE COAT:
> Hi,
> 
> E-mailyvo s gmx.net writes:
>> Fix in the display window and updated to 3.7.0.7 (no new functionality)
>>
>> http://megapov.inetart.net/povrayunofficial_mac/finalpov.html
>> -- 
>> Yvo
> 
> Why isn't it available for Mac OS X 10.6.8 (Snow Leopard) ? This is
> called "programmed obsolescence" because there's nothing to explain !

Well, that's the "free" part in "free/libre open source software" for
you: The author is free to drop support for your platform any time they
like, for any reason (or even no reason whatsoever) -- you, on the other
hand, are free to back port their changes to whatever platform you like.

Unless of course you have entered into a paid service agreement with the
man.

Have you?

I'm not saying "programmed obsolescence" has nothing to do with it, but
you're definitely barking up the wrong tree. Some small town in Santa
Clara County would be closer to the mark.

[Francois LE COAT] Re: POV-Ray 3.7.0.7 for mac available [2890 days 14 hours and 16 minutes ago]

Mon, 21 May 2018 19:25:08 GMT

Hi,

E-mailyvo s gmx.net writes:
> Fix in the display window and updated to 3.7.0.7 (no new functionality)

>
> http://megapov.inetart.net/povrayunofficial_mac/finalpov.html
> --
> Yvo

Why isn't it available for Mac OS X 10.6.8 (Snow Leopard) ? This is
called "programmed obsolescence" because there's nothing to explain !

-- 
François LE COAT
<http://eureka.atari.org/>

[Yvo Smellenbergh] POV-Ray 3.7.0.7 r2 for mac available [2892 days 1 hour and 3 minutes ago]

Sun, 20 May 2018 08:37:43 GMT

Release 2 fixes a crash for scenes with high trace level:

http://megapov.inetart.net/povrayunofficial_mac/finalpov.html

-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] POV-Ray 3.7.0.7 for mac available [2897 days 18 hours and 14 minutes ago]

Mon, 14 May 2018 15:27:07 GMT

Fix in the display window and updated to 3.7.0.7 (no new functionality)

http://megapov.inetart.net/povrayunofficial_mac/finalpov.html
--
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] POV-Ray v3.8.0-Alpha 9606898 for Macintosh Avail... [2898 days 2 hours and 31 minutes ago]

Mon, 14 May 2018 07:10:00 GMT

Sorry for the delay but it is finally ready for downloading:
http://megapov.inetart.net/povrayunofficial_mac/alphapov.html

Except for the update to the latest alpha version, a little bug in the 
preview window is fixed.

An a big thank you to Christoph L. for modifying the source to work 
around a compiler bug on MacOS!




--
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Release 2 of PovRayUnofficial_3.8.0-alpha.932220... [3108 days 16 hours and 21 minutes ago]

Sun, 15 Oct 2017 17:20:11 GMT

Render times are back to normal.

Reverted back to Xcode 8 for now, sources are identical.
In case you recompile, drop the project file onto Xcode 8 for good 
resultsâ€¦. For now.
To be continued.

http://megapov.inetart.net/povrayunofficial_mac/alphapov.html
-- 
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[kurtz le pirate] Re: PovRayUnofficial_3.8.0-alpha.9322209 for mac... [3109 days 17 hours and 23 minutes ago]

Sat, 14 Oct 2017 16:18:11 GMT

Le 23/09/2017 Ã  11:50, E-mailyvo s gmx.net a Ã©critÂ :
> Copy-pase :-)
> POV-Ray v3.7.1 has been redesignated v3.8.0, and we'll be back at alpha
> stage for now.

Great !


Small note : Preferences from 3.7.1_Beta8 are not resumed.



-- 
Kurtz le pirate
Compagnie de la Banquise

[Yvo Smellenbergh] PovRayUnofficial_3.8.0-alpha.9322209 for macinto... [3130 days 23 hours and 51 minutes ago]

Sat, 23 Sep 2017 09:50:20 GMT

Copy-pase :-)
POV-Ray v3.7.1 has been redesignated v3.8.0, and we'll be back at alpha
stage for now.

http://megapov.inetart.net/povrayunofficial_mac/alphapov.html

--
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Re: POV-Ray 3.7.1-rc1-r2 for Macintosh available [3168 days 13 hours and 10 minutes ago]

Wed, 16 Aug 2017 20:31:13 GMT

On 2017-08-16 15:01:12 +0000, Bald Eagle said:

> Hi Yvo,
> 
> How are you posting to the newsgroups?
> I noticed that you had a "double-post" yesterday, and when I clicked on _one_
> message and then went back to the message digest, BOTH message links 
> were marked
> as visited.
> The same thing happened with your post today - double-posted, and the same link
> behaviour.
> 
> Just something I noticed.

I use Uison, post my message to two groups at once, depending on the version.
Always to povray.macintosh and beta-test for 3.7.1, general for 3.7.0 final.

I donâ€™t use the web interface, can not get used to it :-(.

--
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Bald Eagle] Re: POV-Ray 3.7.1-rc1-r2 for Macintosh available [3168 days 14 hours and 36 minutes ago]

Wed, 16 Aug 2017 19:05:00 GMT

Hi Yvo,

How are you posting to the newsgroups?
I noticed that you had a "double-post" yesterday, and when I clicked on _one_
message and then went back to the message digest, BOTH message links were marked
as visited.
The same thing happened with your post today - double-posted, and the same link
behaviour.

Just something I noticed.

[Yvo Smellenbergh] POV-Ray 3.7.1-rc1-r2 for Macintosh available [3168 days 15 hours and 51 minutes ago]

Wed, 16 Aug 2017 17:49:37 GMT

Same fixes as Povray for Macintosh 3.7 unofficial r9 from yesterday:

Most important fix is the preview window on Retina displays.
This was totally wrong!

Some other minor fixes, see:

http://megapov.inetart.net/povrayunofficial_mac/alphapov.html

To avoid confusion:
This version is the same version as 3.7.1 release candidate 1 with some 
fixes specific for the Macintosh version.

--
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Povray for Macintosh 3.7 unofficial r9 is availa... [3169 days 15 hours and 44 minutes ago]

Tue, 15 Aug 2017 17:56:45 GMT

Most important fix is the preview window on Retina displays.
This was totally wrong!

Some other minor fixes, see:

http://megapov.inetart.net/povrayunofficial_mac/finalpov.html
In case you wonder, r8 was never released to the public ;-)


A new version for 3.7.1 will be ready soon to fix the same issue.


Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] POV-Ray 3.7.1 Release Candidate 1 for Macintosh ... [3221 days 18 hours and 23 minutes ago]

Sat, 24 Jun 2017 15:17:32 GMT

http://megapov.inetart.net/povrayunofficial_mac/alphapov.html

--
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[clipka] Survey: Compilers Used [3225 days 19 hours and 13 minutes ago]

Tue, 20 Jun 2017 14:27:42 GMT

Hi folks,

I'd like to get some feedback on what compilers you are using to build
your own POV-Ray binaries (if applicable).

More specifically, I'd like to know whether anyone is using something
*OTHER* than one of the following:

- Microsoft Visual Studio 2015 or later.
- Gnu Compiler Collection 4.8.1 or later.
- Clang 3.3 or later.

So if you are using an older version of the above compilers, or an
entirely different compiler, please let us know.


The ultimate purpose of this survey is to determine which C++11 features
might be safe to use in the POV-Ray source code.

[clipka] Re: POVRay v3.7.1 beta 8 for Macintosh available [3256 days 19 hours and 13 minutes ago]

Sat, 20 May 2017 14:28:05 GMT

Am 20.05.2017 um 15:52 schrieb E-mailyvo s gmx.net:
> http://megapov.inetart.net/povrayunofficial_mac/alphapov.html

That was fast, even by your standards ;)

[Yvo Smellenbergh] POVRay v3.7.1 beta 8 for Macintosh available [3256 days 19 hours and 49 minutes ago]

Sat, 20 May 2017 13:52:20 GMT

http://megapov.inetart.net/povrayunofficial_mac/alphapov.html


--
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[clipka] Some help needed [3258 days 15 hours and 15 minutes ago]

Thu, 18 May 2017 18:26:00 GMT

Folks,

we could use a bit of help to iron out a kink in the Unix build process:

Currently, our approach at identifying the version of the installed
OpenEXR library is based on the `pkg-config` tool, which does not seem
to be available on all systems (example: Mac OS X darwin 15.6.0).

My guess is that this approach was originally used because older
versions of OpenEXR were pretty taciturn when it came to disclosing
their version number.

However, modern versions of OpenEXR are much more cooperative in this
respect, so getting the version information of those should be well
possible even without `pkg-config`.

So it would be neat if someone with some rudimentary knowledge of
Automake and a bit of Unix know-how could review the current mechanism,
and amend it so that the OpenEXR version information is obtained in a
more portable fashion when possible, and the `pkg-config`-based approach
is only used as a fallback solution.

Any takers?

[Yvo Smellenbergh] POV-Ray v3.7.1 beta 6 for Macintosh available [3263 days 18 hours and 21 minutes ago]

Sat, 13 May 2017 15:20:27 GMT

With a little delay beta 6 for Mac is now available:

http://megapov.inetart.net/povrayunofficial_mac/alphapov.html


--
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[aeffects] Re: POV-Ray v3.7.1-beta 4 for Macintosh released [3277 days 4 hours and 6 minutes ago]

Sun, 30 Apr 2017 05:35:00 GMT

Yvo Smellenbergh <E-mail: yvo(DOT)s(AT)gmx.net> wrote:
> Beta 4 is out, beta 3 was never released for Macintosh :-(
>
> http://megapov.inetart.net/povrayunofficial_mac/alphapov.html
>
>
> Yvo
>
>
> --
>
-------------------------------------------------------------------------------------------
>
> POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
> UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
> MegaPOV: http://megapov.inetart.net
> E-mail: yvo(DOT)s(AT)gmx.net

thank you, Yvo!

[LanuHum] Re: ngPlant - Mac' plugin [3319 days 14 hours and 51 minutes ago]

Sat, 18 Mar 2017 18:50:00 GMT

kurtz le pirate <kur### [at] gmailcom> wrote:
> Hi,
> All in subject.
> Explanations, sample and plugin here :
> <http://louisbel.free.fr/macros/ngplant/ngplant.html>
>
>
> Regards
> --
> Kurtz le pirate
> Compagnie de la Banquise

I do not know Mac, but Povray users will not like it.There is no smooth
transition from the trunk to the branches.This was known when I showed the
Blender plugin.My version of the exporter from Blender to Povray allows you to
get smooth transitions, also it's of no interest to anyone. Povray lives her own
life. He is interested only in the fact that he can himself.Users Povray will
write a macro using SDL. Year, two years, it does not matter. It is important
not to use Blender and ngPlant. :)

[kurtz le pirate] ngPlant - Mac' plugin [3319 days 23 hours and 39 minutes ago]

Sat, 18 Mar 2017 10:02:17 GMT

Hi,
All in subject.
Explanations, sample and plugin here :
<http://louisbel.free.fr/macros/ngplant/ngplant.html>


Regards
-- 
Kurtz le pirate
Compagnie de la Banquise

[Yvo Smellenbergh] POV-Ray v3.7.1-beta 4 for Macintosh released [3332 days 14 hours and 56 minutes ago]

Sun, 5 Mar 2017 18:44:40 GMT

Beta 4 is out, beta 3 was never released for Macintosh :-(

http://megapov.inetart.net/povrayunofficial_mac/alphapov.html


Yvo


-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Public Beta 3.7.1 beta 2 for Macintosh available [3383 days 20 hours and 40 minutes ago]

Fri, 13 Jan 2017 13:01:19 GMT

Please visit:
http://megapov.inetart.net/povrayunofficial_mac/alphapov.html
for download links


Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Re: UberPOV wit MegaPOV glows for mac available [3443 days 15 hours ago]

Mon, 14 Nov 2016 18:40:52 GMT

On 2016-11-14 17:54:04 +0000, clipka said:

> Am 14.11.2016 um 18:46 schrieb E-mailyvo s gmx.net:
>> UberPOV with MegaPOV glows is now available for Macintosh:
> 
> You're quick :)

Yes, I know you.... no guarantee that it will compile tomorrow ;-)

Thanks for adding this patch!

--
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[clipka] Re: UberPOV wit MegaPOV glows for mac available [3443 days 15 hours and 47 minutes ago]

Mon, 14 Nov 2016 17:54:05 GMT

Am 14.11.2016 um 18:46 schrieb E-mailyvo s gmx.net:
> UberPOV with MegaPOV glows is now available for Macintosh:

You're quick :)

[Yvo Smellenbergh] Re: UberPOV wit MegaPOV glows for mac available [3443 days 15 hours and 53 minutes ago]

Mon, 14 Nov 2016 17:48:24 GMT

On 2016-11-14 17:46:23 +0000, Yvo Smellenbergh said:
FYI:
only direct links, not listed on the website until out of beta :-)

Yvo


> UberPOV with MegaPOV glows is now available for Macintosh:
> 
> Executable OSX 10.7.4 and later, 64bit only
>
http://megapov.inetart.net/povrayunofficial_mac/uberpov_downloads/UberPOV-1.37.1.1-alpha.8871946-Glow.zip

> 
> 
> Source:
>
http://megapov.inetart.net/povrayunofficial_mac/uberpov_downloads/UberPOV-1.37.1.1-alpha.8871946-Glow-source.zip

> 
> 
> Discusion:
>
http://news.povray.org/povray.unofficial.patches/thread/%3C5829de00%241%40news.povray.org%3E/

> 
> 
> Yvo
> 
> Simple sample scene:
> 
> // Persistence Of Vision Ray Tracer Scene Description File
> // -------------------------------------------------------
> // File: @(#)glowlits.pov
> // Description: Here the glow effects are coupled with light sources.
> // Features demonstrated: glow
> // Creation Date: $ 27 Sep 2000, 16:08:45 $
> // Last modified: $ 14 Jun 2004, 22:36:41 $
> // Author: Chris Huff
> //
> // -w320 -h240 +a0.3
> 
> #version unofficial patch 3.7;
> 
> global_settings {
> 	assumed_gamma 1.0
> }
> 
> camera {
> 	location <-5, 6,-18>
> 	up y*image_height right x*image_width
> 	look_at < 0, 1.5, 0>
> 	angle 45
> }
> 
> //Types:
> #local Float = 0;
> #local Vector = < 0, 0, 0>;
> #local Color = color rgb < 0, 0, 0>;
> 
> #macro SRand(RS) (rand(RS)*2 - 1) #end
> #macro RRand(RS, Min, Max) (rand(RS)*(Max-Min) + Min) #end
> #macro Clamp(V, Min, Max) (min(Max, max(Min, V))) #end
> #macro Range(V, Rmn, Rmx) (V*(Rmx-Rmn) + Rmn) #end
> #macro RClamp(V, Rmn, Rmx, Min, Max) (Clamp(Range(V, Rmn, Rmx), Min, Max)) #end
> 
> #local RsA = seed(574647);
> 
> #local J = Float;
> #local J = 0;
> #while(J<52)
> 	light_source {
> 		< SRand(RsA)*8, rand(RsA)*4, SRand(RsA)*8>
> 		color rgb 0.045*< rand(RsA), rand(RsA), rand(RsA)>
> 		glow { size rand(RsA)*0.65 type int(rand(RsA))}
> 		fade_distance 4 fade_power 2
> 	}
> 	 #declare  J = J + 1;
> #end
> 
> box {
> 	<-15, 0,-10>, < 15, 0, 10>
> 	pigment {checker color rgb 0.05, color rgb 1}
> 	finish {
> 		reflection {0.5, 0.75 metallic }
> 		diffuse 0.25 ambient 0
> 	}
> }
> 
> sphere {
> 	< 0, 2, 0>, 2
> 	pigment {rgb 1}
> 	finish {
> 		reflection { 0.5, 0.85 metallic }
> 		diffuse 0.15 ambient 0
> 	}
> }
> 
> 
> 
>
-------------------------------------------------------------------------------------------

> 
> POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
> UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
> MegaPOV: http://megapov.inetart.net
> E-mail: yvo(DOT)s(AT)gmx.net


--
Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] UberPOV wit MegaPOV glows for mac available [3443 days 15 hours and 55 minutes ago]

Mon, 14 Nov 2016 17:46:24 GMT

UberPOV with MegaPOV glows is now available for Macintosh:

Executable OSX 10.7.4 and later, 64bit only
http://megapov.inetart.net/povrayunofficial_mac/uberpov_downloads/UberPOV-1.37.1.1-alpha.8871946-Glow.zip



Source:
http://megapov.inetart.net/povrayunofficial_mac/uberpov_downloads/UberPOV-1.37.1.1-alpha.8871946-Glow-source.zip



Discusion:
http://news.povray.org/povray.unofficial.patches/thread/%3C5829de00%241%40news.povray.org%3E/



Yvo

Simple sample scene:

// Persistence Of Vision Ray Tracer Scene Description File
// -------------------------------------------------------
// File: @(#)glowlits.pov
// Description: Here the glow effects are coupled with light sources.
// Features demonstrated: glow
// Creation Date: $ 27 Sep 2000, 16:08:45 $
// Last modified: $ 14 Jun 2004, 22:36:41 $
// Author: Chris Huff
//
// -w320 -h240 +a0.3

#version unofficial patch 3.7;

global_settings {
	assumed_gamma 1.0
}

camera {
	location <-5, 6,-18>
	up y*image_height right x*image_width
	look_at < 0, 1.5, 0>
	angle 45
}

//Types:
#local Float = 0;
#local Vector = < 0, 0, 0>;
#local Color = color rgb < 0, 0, 0>;

#macro SRand(RS) (rand(RS)*2 - 1) #end
#macro RRand(RS, Min, Max) (rand(RS)*(Max-Min) + Min) #end
#macro Clamp(V, Min, Max) (min(Max, max(Min, V))) #end
#macro Range(V, Rmn, Rmx) (V*(Rmx-Rmn) + Rmn) #end
#macro RClamp(V, Rmn, Rmx, Min, Max) (Clamp(Range(V, Rmn, Rmx), Min, Max)) #end

#local RsA = seed(574647);

#local J = Float;
#local J = 0;
#while(J<52)
	light_source {
		< SRand(RsA)*8, rand(RsA)*4, SRand(RsA)*8>
		color rgb 0.045*< rand(RsA), rand(RsA), rand(RsA)>
		glow { size rand(RsA)*0.65 type int(rand(RsA))}
		fade_distance 4 fade_power 2
	}
	 #declare  J = J + 1;
#end

box {
	<-15, 0,-10>, < 15, 0, 10>
	pigment {checker color rgb 0.05, color rgb 1}
	finish {
		reflection {0.5, 0.75 metallic }
		diffuse 0.25 ambient 0
	}
}

sphere {
	< 0, 2, 0>, 2
	pigment {rgb 1}
	finish {
		reflection { 0.5, 0.85 metallic }
		diffuse 0.15 ambient 0
	}
}



-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] UberPOV-Development-Branch-1.37.1.1-alpha.886115... [3450 days 17 hours and 10 minutes ago]

Mon, 7 Nov 2016 16:31:08 GMT

At last, with the help from the great master 'clipka', the most recent 
version of UberPOV is now available for Mac.

Minimum system is 10.7.5, 64-bit (no support for 32-bit)

http://megapov.inetart.net/povrayunofficial_mac/uberpov.html

Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[INVALID ADDRESS] Re: Can I pay someone to add this from MegaPov? [3454 days 17 hours and 10 minutes ago]

Thu, 3 Nov 2016 16:30:37 GMT

Wow no comments huh? Lol... I thought someone would have something to say
at least.

This just motivates me more to personally take out strategic bounties for
stuff that might make Pov more attractive as a 3rd party rendering plugin
at the least...whatever it takes to keep it alive...it looks like our
community is in trouble...not nearly as active as the early 90s...not much
new blood, not much new in the way of IDE/Modelers...

Im going to need to think about what to offer payment for.
I am not rich but I am willing to do my part in thanks to those whose
efforts have given us all, freely, what I feel is one of the most
interesting, useful and beautiful rendering packages out there.

Maybe a gofundme or patreon page for pov would stimulate dev work and
attract new devs, and with certain features maybe attract new users.

I have seen a huge drop off in activity over the decades and want to affect
change. Bounties is the best answer I have come up with so far. For me
Glows are just the start. I am going to invest in this, by damn.

Pov **cannot** be allowed to slowly wither; it is responsible for my entire
23yr career in software engineering (I'm now a VP), my meeting my wife (in
art appreciation class due to death-metal, a presentation on Gilles Tran
Pov work, and a scene I made in Pov) and supporting my family (because Pov
taught me to code)...I *owe* Pov and team...

Who else feels this way?
How has Pov changed your life?
Has it introduced you to programming, helped you visualize your thesis, got
you into a career in 3d art, or what?

I cannot be the only one for whom Pov has opened professional, artistic and
intellectual doors.

Ian

[INVALID ADDRESS] Re: Can I pay someone to add this from MegaPov? [3457 days 1 hour and 3 minutes ago]

Tue, 1 Nov 2016 08:38:04 GMT

For everyones general information, I think bounties like this are a great
way not only to get new features, but most especially to say "thanks" to
the folks who put in work making PovRay what it is.

I am very excited for the opportunities this opens up for everyone.

Once this feature is in I want to look at true displacement, which will be
a ton of work and I won't be able to fund it alone. I think TD would buy a
lot for both the package and the community as a whole.

There was at least one PovRay modification that supported true
displacement, but the way it was accomplished was to make Pov conform to
some degree with the Renderman SL standard, and if I recall correctly it
broke entirely with the way pov handles materials (not the pov term, but
general).

It is dead but the source lives on courtesy of Archive.org:
https://web.archive.org/web/20090103185310/http://www.aetec.ee/fv/vkhomep.nsf/pages/povman2

Povman is based on MP 1.1, and Vahur Krouverk was the author.

Obviously we would want to keep the way pov handles materials in SDL, but
also allow true displacement as seen in Renderman. I don't know what this
would entail specifically but I would feel safe betting it would be
nontrivial work.

I am not advocating full RM spec compliance, only hijacking the
displacement code from PovMan in some form, preferably without having to
use a shader compiler.

I would like to know how many folks would like to see true displacement
ported over because like I said I can't fund that one alone (at least not
in a single shot).

If there isn't much interest (which frankly would shock me) then it
wouldn't even be worth trying to size the work...but conversely if the
interest is great, then there may be some merit at least in investigation
of the idea.

Other things which might be useful:

- OpenCL/GPU. This has been talked to death but because of the complexity
perhaps a large enough bounty would be sufficiently motivating and provide
a good ROI for the team.

- A reasonable alternative to GPU raytracing is "progressive raytracing", a
quick google search even gets you articles stating that this is far less
complex to do than GPU but is much faster than normal RT and is advocated
as either an alternative to GPU RT or an intermediate point between normal
RT and a GPU implementation.

- Ability to "scan" objects into a distance based resolution adaptive mesh
instead of rendering the object as normal, which might speed up render. (I
know marching triangles macros exist, would an internal implementation be
faster?)

- Navier-Stokes flow, compressible and incompressible implemented as a
primitive. So if you place the primitive in a hollow hemisphere it would
naturally fill it, or if you put it in a HF valley with rocks and such it
would fill it to the Y position of the primitive and "flow" around the
rocks, making eddies and ripples and such. Flow direction would be a
vector, fluid would naturally fill whatever was around it as well.

- Enhancements to volumetric rendering, so media behaves
consistently/predictably regardless of container volume and/or scale. Right
now making a good looking variable density fog or cloud can get a bit weird
and it is difficult to predict the outcome of any given input. Having some
kind of distance based resolution may enhance speed as well. Perhaps the
volumetric rendering task can be sent to the GPU alone.

- Implement a plugin based architecture for pov, so new features could be
added without having to rework the whole application each time. I have
solved many problems using plugin based architecture, and am quite a fan of
it. If done correctly this might allow Pov to get more features faster, but
would take a lot of work to do initially.

Ian

[Yvo Smellenbergh] Re: Can I pay someone to add this from MegaPov? [3457 days 17 hours and 49 minutes ago]

Mon, 31 Oct 2016 15:52:14 GMT

On 2016-10-31 10:38:46 +0000, clipka said:

> Am 31.10.2016 um 00:16 schrieb [GDS|Entropy] in povray.advanced-users:
> 
>> I was wondering (hoping) that I could pay someone to add Glows to UberPov,
>> and include enough implementation info via comments or whatever that
>> whoever in the future could easily forward this to the next version when 4
>> comes out. If you are interested Clipka, even better. ;-)
> 
> I've just noticed to my surprise that you're apparently not the guy who
> had requested the very same MegaPOV feature just a few weeks ago on the
> povray.macintosh newsgroup, so I've decided to use this occasion for a
> shameless plug or two:
> 
> 
> While I love working on POV-Ray and UberPOV as a hobby, and will quite
> certainly continue to do so no matter what I get out of it, I'm not
> above taking donations that allow me to spend more time on this hobby --
> nor am I above taking bribes to prioritize my ToDo list.
> 
> So to anyone wishing to back up Ian's (aka GDS|Entropy) motion to get
> the MegaPOV "glow" feature implemented in UberPOV ASAP, feel free to
> place a bounty on the corresponding GitHub issue via Bountysource:
> 
> https://www.bountysource.com/issues/38809617-port-megapov-s-glow-feature-to-uberpov 
> 
> 
> 
> In related news, anyone inclined to send some round tuits my way for
> general POV-Ray and UberPOV development is happily invited to take a
> look at https://salt.bountysource.com/teams/uberpov.

I had a few requests about the glow patch.
It is one of the most wanted patches from MegaPOV, the current patch 
was unfinished if I remember well.
But it seemed to be useful for a lot of users.

Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[clipka] Re: Can I pay someone to add this from MegaPov? [3457 days 23 hours and 2 minutes ago]

Mon, 31 Oct 2016 10:38:45 GMT

Am 31.10.2016 um 00:16 schrieb [GDS|Entropy] in povray.advanced-users:

> I was wondering (hoping) that I could pay someone to add Glows to UberPov,
> and include enough implementation info via comments or whatever that
> whoever in the future could easily forward this to the next version when 4
> comes out. If you are interested Clipka, even better. ;-)

I've just noticed to my surprise that you're apparently not the guy who
had requested the very same MegaPOV feature just a few weeks ago on the
povray.macintosh newsgroup, so I've decided to use this occasion for a
shameless plug or two:


While I love working on POV-Ray and UberPOV as a hobby, and will quite
certainly continue to do so no matter what I get out of it, I'm not
above taking donations that allow me to spend more time on this hobby --
nor am I above taking bribes to prioritize my ToDo list.

So to anyone wishing to back up Ian's (aka GDS|Entropy) motion to get
the MegaPOV "glow" feature implemented in UberPOV ASAP, feel free to
place a bounty on the corresponding GitHub issue via Bountysource:

https://www.bountysource.com/issues/38809617-port-megapov-s-glow-feature-to-uberpov


In related news, anyone inclined to send some round tuits my way for
general POV-Ray and UberPOV development is happily invited to take a
look at https://salt.bountysource.com/teams/uberpov.

[Yvo Smellenbergh] POV-Ray Unofficial 3.7.1 alpha 8826150 available [3466 days 16 hours and 23 minutes ago]

Sat, 22 Oct 2016 17:17:39 GMT

After a few code signing troubles the Mac version of POV-Ray 3.7.1 
alpha 8826150 is available.

http://megapov.inetart.net/povrayunofficial_mac/alphapov.html

- Updated to alpha 8826150;
- Minimum OSX is 10.7.5;
- No support for 32bit (Ask if needed, normally all systems running 
10.7.5 are capable of running 64bit apps;
- Moved to Xcode 8.x;
- Xcode project clean-up;

Have fun!

Yvo
-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[clipka] Re: Glow lights [3480 days 14 hours and 5 minutes ago]

Sat, 8 Oct 2016 19:35:39 GMT

Am 08.10.2016 um 20:53 schrieb Richard Smith:
> Some of my art projects depend upon using the glow light feature. Now that
> MegaPOV is no londer supported, I would like to recommend that the POV-Ray team
> consider adding the glowlight feature to official POV-Ray.

I guess you'll have a better chance suggesting its inclusion into one of
the newer unofficial patch collection projects, such as UberPOV or
HG-Povray. If official POV-Ray ever gets a similar feature, it may be
notably different in the way it operates, not to mention that it will
most certainly use vastly different SDL syntax.

My advice would be to submit a GitHub issue to the UberPOV repo at
https://github.com/UberPOV/UberPOV/issues.

[Richard Smith] Glow lights [3480 days 14 hours and 46 minutes ago]

Sat, 8 Oct 2016 18:55:00 GMT

Some of my art projects depend upon using the glow light feature. Now that
MegaPOV is no londer supported, I would like to recommend that the POV-Ray team
consider adding the glowlight feature to official POV-Ray.

[clipka] Re: "Raw" POV-Ray needs testing on Mac OS X [3482 days and 4 minutes ago]

Fri, 7 Oct 2016 09:36:32 GMT

Am 05.10.2016 um 05:52 schrieb clipka:
> Folks,
> 
> anyone here familiar with building POV-Ray for Mac OS X from the
> official source code (as opposed to Yvo's unofficial port)?
> 
> I need someone to test whether GitHub issue #51
> (https://github.com/POV-Ray/povray/issues/51) is still... um, an
> issue... in this version:
> 
>     https://github.com/POV-Ray/povray/tree/hotfix/stable

Hmm... no takers?

[clipka] "Raw" POV-Ray needs testing on Mac OS X [3484 days 5 hours and 48 minutes ago]

Wed, 5 Oct 2016 03:52:38 GMT

Folks,

anyone here familiar with building POV-Ray for Mac OS X from the
official source code (as opposed to Yvo's unofficial port)?

I need someone to test whether GitHub issue #51
(https://github.com/POV-Ray/povray/issues/51) is still... um, an
issue... in this version:

    https://github.com/POV-Ray/povray/tree/hotfix/stable

[Yvo Smellenbergh] Re: 3.7.x and Yvo! [3506 days 16 hours and 17 minutes ago]

Mon, 12 Sep 2016 17:24:10 GMT

On 2016-09-11 12:26:09 +0000, aeffects said:

> Thank You Yvo, for your 'continued' dedication making PovRay available to mac
> osx users around the world.
> 
> DHealy
> Lake Tahoe/RENO
> USA

Glad to be of help!
Nice to know that it is appreciated !

Yvo
-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[aeffects] 3.7.x and Yvo! [3507 days 17 hours and 11 minutes ago]

Sun, 11 Sep 2016 16:30:00 GMT

Thank You Yvo, for your 'continued' dedication making PovRay available to mac
osx users around the world.

DHealy
Lake Tahoe/RENO
USA

[Mr] Blender Exporter testing needed [3507 days 20 hours and 1 minute ago]

Sun, 11 Sep 2016 13:40:01 GMT

Hello, I tried the exporter from a mac at a friends for the first time and got
stuck on the ini file displayed in some text editor. also the POV console did
appear but no rendered image,  On other platforms, the exporter takes care of
launching the render and closing pov afterwards bringing picture back into
Blender rendered image window.  Could someone else try the basic wiki
instructions (
https://wiki.blender.org/index.php/Extensions:2.6/Py/Scripts/Render/POV-Ray )to
render on Mac and tell me if the  behaviour is the same?  If so, any idea what
the exporter may be doing wrong?

[Yvo Smellenbergh] Povray for Macintosh 3.7 unofficial r7 is availa... [3551 days 2 hours and 24 minutes ago]

Sat, 30 Jul 2016 07:16:56 GMT

Please visit:

http://megapov.inetart.net/povrayunofficial_mac/finalpov.html

-Fixed "redirect Text Streams" option;
-Fixed issues on systems prior to 10.8;
-Added option (see program preferences dialog): always put preview 
window in front on render start;
-More source cleanup;

Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Povray for Macintosh 3.7.1 Alpha 8704732 unoffi... [3551 days 2 hours and 27 minutes ago]

Sat, 30 Jul 2016 07:14:06 GMT

Please visit:

http://megapov.inetart.net/povrayunofficial_mac/alphapov.html

Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[kurtz le pirate] Re: Bug or misconfiguration ? [3558 days 1 hour and 57 minutes ago]

Sat, 23 Jul 2016 07:43:38 GMT

Le 17/07/2016 Ã  20:03, Yvo Smellenbergh a Ã©crit :
> On 2016-07-17 15:27:48 +0000, kurtz le pirate said:
>
>
> Please check out r7-RC1:
>
> http://megapov.inetart.net/beta/POVRay_Unofficial_r7_RC1.zip
>
> - Textstream buffers to file >>  fixed
>
> - option added >> in Application preferences >> misc
>
>  put preview window in front for each render. For animations only for
> the first frame or all frames.
>
>
> Yvo


Cheers



-- 
Kurtz le pirate
Compagnie de la Banquise

[Yvo Smellenbergh] Re: Bug or misconfiguration ? [3563 days 15 hours and 37 minutes ago]

Sun, 17 Jul 2016 18:03:47 GMT

On 2016-07-17 15:27:48 +0000, kurtz le pirate said:

Please check out r7-RC1:
http://megapov.inetart.net/beta/POVRay_Unofficial_r7_RC1.zip
- Textstream buffers to file >>  fixed
- option added >> in Application preferences >> misc 
 put preview window in front for each render. For animations only for 
the first frame or all frames.

Yvo

> Le 17/07/2016 Ã  11:44, Yvo Smellenbergh a Ã©crit :
>> Not allowed anymore to add a full path to the textstream files.
>> Don't know what the reason is, why must they reside in the same directory
>> as the output file?
>> I don't know when this was changed (somewhere in the 3.7 RC I guess)
>> Fix is easy, but uploading a new version for this?
> 
> No... it's not urgent.
> may be in the next release.
> 
> 
>> Do you use this option often?
> 
> Yes, i need for a current project, but I found another way to make this.
> Instead of using #debug concat(...) in code, i use my macro who writes 
> to a file myDebug ( concat(...))  ðŸ˜„
> 
> 
> 
>> You can bypass this bug by using an ini file with the options:
>> Debug_File="biscuit.deb"
>> Fatal_File="biscuit.fat"
>> Render_File="biscuit.ren"
>> Statistic_File="biscuit.sta"
>> Warning_File="biscuit.war"
> 
> I have not thought of these options.
> Thank you recall !


-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[kurtz le pirate] Re: Bug or misconfiguration ? [3563 days 18 hours and 13 minutes ago]

Sun, 17 Jul 2016 15:27:48 GMT

Le 17/07/2016 Ã  11:44, Yvo Smellenbergh a Ã©crit :
> Not allowed anymore to add a full path to the textstream files.
> Don't know what the reason is, why must they reside in the same directory
> as the output file?
> I don't know when this was changed (somewhere in the 3.7 RC I guess)
> Fix is easy, but uploading a new version for this?

No... it's not urgent.
may be in the next release.


> Do you use this option often?

Yes, i need for a current project, but I found another way to make this.
Instead of using #debug concat(...) in code, i use my macro who writes 
to a file myDebug ( concat(...))  ðŸ˜„



> You can bypass this bug by using an ini file with the options:
> Debug_File="biscuit.deb"
> Fatal_File="biscuit.fat"
> Render_File="biscuit.ren"
> Statistic_File="biscuit.sta"
> Warning_File="biscuit.war"

I have not thought of these options.
Thank you recall !


-- 
Kurtz le pirate
Compagnie de la Banquise

[Yvo Smellenbergh] Re: Bug or misconfiguration ? [3563 days 23 hours and 57 minutes ago]

Sun, 17 Jul 2016 09:44:27 GMT

On 2016-07-16 08:54:38 +0000, kurtz le pirate said:

> Hello.
> 
> 
> With 3.7.1 Alpha Unofficial. In "Render preferences", i just select 
> redirect Debug to File an Screen.
> 
> 
> Render the scene give this error :
> 
> 	Stream output files must reside in same
> 	directory as image output file.
> 
> 
> No special configuration. In "Fils & Paths" tab, Scene:Input/Output 
> show correct paths for scene and image.
> 
> 
> What is wrong ?

Not allowed anymore to add a full path to the textstream files.
Don't know what the reason is, why must they reside in the same directory
as the output file?
I don't know when this was changed (somewhere in the 3.7 RC I guess)
Fix is easy, but uploading a new version for this?
Do you use this option often?
You can bypass this bug by using an ini file with the options:
Debug_File="biscuit.deb"
Fatal_File="biscuit.fat"
Render_File="biscuit.ren"
Statistic_File="biscuit.sta"
Warning_File="biscuit.war"

Yvo
-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Re: Bug or misconfiguration ? [3564 days 19 hours and 11 minutes ago]

Sat, 16 Jul 2016 14:29:42 GMT

On 2016-07-16 08:54:38 +0000, kurtz le pirate said:

> Hello.
> 
> 
> With 3.7.1 Alpha Unofficial. In "Render preferences", i just select 
> redirect Debug to File an Screen.
> 
> 
> Render the scene give this error :
> 
> 	Stream output files must reside in same
> 	directory as image output file.
> 
> 
> No special configuration. In "Fils & Paths" tab, Scene:Input/Output 
> show correct paths for scene and image.
> 
> 
> What is wrong ?

No idea, but it the same thing happens in 3.7 final

Will check it out!

Yvo
-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[kurtz le pirate] Bug or misconfiguration ? [3565 days and 46 minutes ago]

Sat, 16 Jul 2016 08:54:38 GMT

Hello.


With 3.7.1 Alpha Unofficial. In "Render preferences", i just select 
redirect Debug to File an Screen.


Render the scene give this error :

	Stream output files must reside in same
	directory as image output file.


No special configuration. In "Fils & Paths" tab, Scene:Input/Output show 
correct paths for scene and image.


What is wrong ?





-- 
Kurtz le pirate
Compagnie de la Banquise

[Yvo Smellenbergh] Povray for Macintosh 3.7.1 Alpha 8615129 unoffic... [3569 days 15 hours and 44 minutes ago]

Mon, 11 Jul 2016 17:56:40 GMT

Please visit the updated web site at:
http://megapov.inetart.net/povrayunofficial_mac/alphapov.html

Yvo
-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Povray for Macintosh 3.7 unofficial r6 is availa... [3569 days 15 hours and 47 minutes ago]

Mon, 11 Jul 2016 17:54:18 GMT

Please visit the updated web site at:
http://megapov.inetart.net/povrayunofficial_mac/index.html

Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Re: Feature request [3570 days 16 hours and 29 minutes ago]

Sun, 10 Jul 2016 17:12:16 GMT

On 2016-07-10 08:45:38 +0000, kurtz le pirate said:

> Hello,
> 
> Simple : on render action, bring the image window in front.

Originally this was the case, the image window was always in front
when a new render or frame started.
It makes you crazy!
That is exactly the reason why I made it like this.
But, the customer is always right!
Maybe I will add an option somewhere to give you the choice.
Howerver, don't come complaining when the men with the white coats
come and get you :-)

Right now I'm redesigning the website for POV-Ray unofficial Macintosh to
release 3.7.0 final r6 and the alpha 3.7.1 version.
After that I will look into it!

Yvo


-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[clipka] Re: Feature request [3570 days 17 hours and 44 minutes ago]

Sun, 10 Jul 2016 15:56:55 GMT

Am 10.07.2016 um 17:06 schrieb kurtz le pirate:
> Le 10/07/2016 Ã  11:19, Le_Forgeron a Ã©crit :
>> Le 10/07/2016 10:45, kurtz le pirate a Ã©crit :
>>>
>>> Hello,
>>>
>>> Simple : on render action, bring the image window in front.
>>>
>>
>> Just a note from other OS: that looks like a good idea... until you
>> start rendering animation with high PPS.
>> As bringing window in front usually also steal the focus, you cannot
>> work anymore on your computer.
>>
>> At least, if you are doing it (bringing the image window in front), do
>> it only at the start of the render, not for each frame.
>> My 0.02â‚¬
>>
> 
> More precisely : bring the image window in front the povray's windows.

That, too, could be a nuisance if it happens for every frame of an
animation, because someone might want to edit the code of a different
scene while waiting for the animation to finish rendering.

[kurtz le pirate] Re: Feature request [3570 days 18 hours and 35 minutes ago]

Sun, 10 Jul 2016 15:06:28 GMT

Le 10/07/2016 Ã  11:19, Le_Forgeron a Ã©crit :
> Le 10/07/2016 10:45, kurtz le pirate a Ã©crit :
>>
>> Hello,
>>
>> Simple : on render action, bring the image window in front.
>>
>
> Just a note from other OS: that looks like a good idea... until you start rendering
animation with high PPS.
> As bringing window in front usually also steal the focus, you cannot work anymore on
your computer.
>
> At least, if you are doing it (bringing the image window in front), do it only at
the start of the render, not for each frame.
> My 0.02â‚¬
>

More precisely : bring the image window in front the povray's windows.



-- 
Kurtz le pirate
Compagnie de la Banquise

[Le Forgeron] Re: Feature request [3571 days and 21 minutes ago]

Sun, 10 Jul 2016 09:19:41 GMT

Le 10/07/2016 10:45, kurtz le pirate a Ã©crit :
> 
> Hello,
> 
> Simple : on render action, bring the image window in front.
> 

Just a note from other OS: that looks like a good idea... until you start rendering
animation with high PPS.
As bringing window in front usually also steal the focus, you cannot work anymore on
your computer.

At least, if you are doing it (bringing the image window in front), do it only at the
start of the render, not for each frame.
My 0.02â‚¬

[kurtz le pirate] Feature request [3571 days and 55 minutes ago]

Sun, 10 Jul 2016 08:45:38 GMT

Hello,

Simple : on render action, bring the image window in front.



-- 
Kurtz le pirate
Compagnie de la Banquise

[Yvo Smellenbergh] Re: 3.7 unofficial Macintosh r6 rc2 available [3586 days 3 hours and 39 minutes ago]

Sat, 25 Jun 2016 06:01:57 GMT

r6, RC 2 is ready

download at:
http://megapov.inetart.net/beta/beta.html



Yvo
-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Re: 3.7 unofficial Macintosh r6 rc1 available [3590 days 15 hours and 47 minutes ago]

Mon, 20 Jun 2016 17:53:36 GMT

On 2016-06-19 06:19:19 +0000, Eriban said:

Hello Erwin,

In one or the other version the option to substitute quotes with fancy ones was
ignored. I had to hardcode it.
That is fixed but older files can cause problems.

BTW: It is a general option in the system preferences panel under
'Language & Region'  bottom of this panel "Keyboard Preferences" >> Text
panel. "Use smart quotes and dashes".
This was always 'forced' off in PovRay, no matter what settings used in 
this panel.

I will have a fix for the inlcude file you send me.
An improved error message when a file can not be read. But files like
Problematic-Basket-Moves.inc are no longer causing problems and load!

Thanks for reporting this!
A new version out in a few days!

Yvo

> Hi Yvo,
> 
> Thanks for making this latest version available. I just downloaded it.
> 
> When trying it out, I encountered one problem. I had been working on this scene
> in an earlier unofficial version of Mac POV (3.7.0.unofficial, Feb 22 2014).
> When starting the latest version of Mac POV it failed to load one of the .inc
> files I had open. In the console I got the following error:
> 
> 19/06/16 11:41:55,573 POVRay_3_7_0_Final_Unofficial[3138]:
> -[NSDocumentController
> reopenDocumentForURL:withContentsOfURL:display:completionHandler:] 
> failed during
> state restoration. Here's the error:
> Error Domain=NSCocoaErrorDomain Code=256 "The autosaved document
> “Basket-Moves.inc” could not be reopened.
> An unknown error has occured." UserInfo={NSUnderlyingError=0x106e83ef0 {Error
> Domain=NSCocoaErrorDomain Code=256 "The file couldn’t be opened."
> UserInfo={NSLocalizedFailureReason=
> An unknown error has occured.}}, NSLocalizedDescription=The autosaved document
> “Basket-Moves.inc” could not be reopened.
> An unknown error has occured., NSLocalizedFailureReason=
> An unknown error has occurred.}
> 
> When subsequently I tried to open the file explicitly this also failed, 
> with the
> following error: The document "Basket-Moves.inc" could not be openend. An
> unknown error occured.
> 
> I did manage to figure out the problem. The file contained the following
> comment:
> 
> // Don't stack Part E.
> 
> I typed the apostrophe using the normal keyboard key, but the editor of the Mac
> POV version I had been using automatically "corrected" it to a fancier one,
> which required a more exotic character encoding (one that showed up as a
> question mark when catting the file in the terminal). After reverting the
> apostrophe back to a normal one, I could open the file also in the latest
> version of Mega POV. Maybe you can improve the error message?
> 
> On a related note, I did notice that in this later version the auto-correction
> that caused these problems is disabled again, so that's good. It already caused
> me problems whenever I typed double quotes (used for strings and include
> statements), whose auto-corrected versions resulted in syntax errors when
> POV-Ray tried to parse them.
> 
> Kind regards,
> Erwin


-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[kurtz le pirate] Re: 3.7 unofficial Macintosh r6 rc1 available [3590 days 23 hours and 27 minutes ago]

Mon, 20 Jun 2016 10:14:01 GMT

Le 13/06/2016 à 12:30, Yvo Smellenbergh a écrit :
> r6, RC 1 is ready, fixed a huge memory leak.
>
>
> download at:
>
> http://megapov.inetart.net/beta/beta.html
>
>
> This is the unofficial Macintosh version  of the last official 3.7
> version, 3.7.1 - alpha will be available soon.


Everything works fine with my few tests.
Great job as usual



-- 
Kurtz le pirate
Compagnie de la Banquise

[Yvo Smellenbergh] Re: 3.7 unofficial Macintosh r6 rc1 available [3591 days 15 hours and 52 minutes ago]

Sun, 19 Jun 2016 17:49:03 GMT

On 2016-06-19 06:19:19 +0000, Eriban said:

Hi Erwin,

Can you e-mail me a file causing this error?

I can not reproduce this.

Yvo

> Hi Yvo,
> 
> Thanks for making this latest version available. I just downloaded it.
> 
> When trying it out, I encountered one problem. I had been working on this scene
> in an earlier unofficial version of Mac POV (3.7.0.unofficial, Feb 22 2014).
> When starting the latest version of Mac POV it failed to load one of the .inc
> files I had open. In the console I got the following error:
> 
> 19/06/16 11:41:55,573 POVRay_3_7_0_Final_Unofficial[3138]:
> -[NSDocumentController
> reopenDocumentForURL:withContentsOfURL:display:completionHandler:] 
> failed during
> state restoration. Here's the error:
> Error Domain=NSCocoaErrorDomain Code=256 "The autosaved document
> “Basket-Moves.inc” could not be reopened.
> An unknown error has occured." UserInfo={NSUnderlyingError=0x106e83ef0 {Error
> Domain=NSCocoaErrorDomain Code=256 "The file couldn’t be opened."
> UserInfo={NSLocalizedFailureReason=
> An unknown error has occured.}}, NSLocalizedDescription=The autosaved document
> “Basket-Moves.inc” could not be reopened.
> An unknown error has occured., NSLocalizedFailureReason=
> An unknown error has occurred.}
> 
> When subsequently I tried to open the file explicitly this also failed, 
> with the
> following error: The document "Basket-Moves.inc" could not be openend. An
> unknown error occured.
> 
> I did manage to figure out the problem. The file contained the following
> comment:
> 
> // Don't stack Part E.
> 
> I typed the apostrophe using the normal keyboard key, but the editor of the Mac
> POV version I had been using automatically "corrected" it to a fancier one,
> which required a more exotic character encoding (one that showed up as a
> question mark when catting the file in the terminal). After reverting the
> apostrophe back to a normal one, I could open the file also in the latest
> version of Mega POV. Maybe you can improve the error message?
> 
> On a related note, I did notice that in this later version the auto-correction
> that caused these problems is disabled again, so that's good. It already caused
> me problems whenever I typed double quotes (used for strings and include
> statements), whose auto-corrected versions resulted in syntax errors when
> POV-Ray tried to parse them.
> 
> Kind regards,
> Erwin


-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Eriban] Re: 3.7 unofficial Macintosh r6 rc1 available [3591 days 23 hours and 21 minutes ago]

Sun, 19 Jun 2016 10:20:00 GMT

Hi Yvo,

Thanks for making this latest version available. I just downloaded it.

When trying it out, I encountered one problem. I had been working on this scene
in an earlier unofficial version of Mac POV (3.7.0.unofficial, Feb 22 2014).
When starting the latest version of Mac POV it failed to load one of the .inc
files I had open. In the console I got the following error:

19/06/16 11:41:55,573 POVRay_3_7_0_Final_Unofficial[3138]:
-[NSDocumentController
reopenDocumentForURL:withContentsOfURL:display:completionHandler:] failed during
state restoration. Here's the error:
Error Domain=NSCocoaErrorDomain Code=256 "The autosaved document
“Basket-Moves.inc” could not be reopened.
An unknown error has occured." UserInfo={NSUnderlyingError=0x106e83ef0 {Error
Domain=NSCocoaErrorDomain Code=256 "The file couldn’t be opened."
UserInfo={NSLocalizedFailureReason=
An unknown error has occured.}}, NSLocalizedDescription=The autosaved document
“Basket-Moves.inc” could not be reopened.
An unknown error has occured., NSLocalizedFailureReason=
An unknown error has occurred.}

When subsequently I tried to open the file explicitly this also failed, with the
following error: The document "Basket-Moves.inc" could not be openend. An
unknown error occured.

I did manage to figure out the problem. The file contained the following
comment:

// Don't stack Part E.

I typed the apostrophe using the normal keyboard key, but the editor of the Mac
POV version I had been using automatically "corrected" it to a fancier one,
which required a more exotic character encoding (one that showed up as a
question mark when catting the file in the terminal). After reverting the
apostrophe back to a normal one, I could open the file also in the latest
version of Mega POV. Maybe you can improve the error message?

On a related note, I did notice that in this later version the auto-correction
that caused these problems is disabled again, so that's good. It already caused
me problems whenever I typed double quotes (used for strings and include
statements), whose auto-corrected versions resulted in syntax errors when
POV-Ray tried to parse them.

Kind regards,
Erwin

[Yvo Smellenbergh] 3.7 unofficial Macintosh r6 rc1 available [3597 days 23 hours and 11 minutes ago]

Mon, 13 Jun 2016 10:30:22 GMT

r6, RC 1 is ready, fixed a huge memory leak.

download at:
http://megapov.inetart.net/beta/beta.html

This is the unofficial Macintosh version  of the last official 3.7 
version, 3.7.1 - alpha will be available soon.

Yvo
-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Re: 3.7 unofficial Macintosh test version availa... [3618 days 4 hours and 15 minutes ago]

Tue, 24 May 2016 05:26:26 GMT

On 2016-05-24 03:47:53 +0000, clipka said:

> Am 23.05.2016 um 19:21 schrieb Yvo Smellenbergh:
>> 
>> http://megapov.inetart.net/beta/POVRay3_7_Unofficial.zip
> 
> Thanks for keeping up the work!
> Just wondering: What version is this based on, exactly? Newest master
> (3.7.1-alpha.8615129)?

Based on 3.7.0 because this is the last official release.
3.7.1-alpha 8600570 is ready but I want to make sure that the last bugs 
are out of the GUI!
So 3.7.1-alpha >8600570 is coming soon.



-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[clipka] Re: 3.7 unofficial Macintosh test version availa... [3618 days 5 hours and 53 minutes ago]

Tue, 24 May 2016 03:47:58 GMT

Am 23.05.2016 um 19:21 schrieb Yvo Smellenbergh:
> 
> http://megapov.inetart.net/beta/POVRay3_7_Unofficial.zip

Thanks for keeping up the work!
Just wondering: What version is this based on, exactly? Newest master
(3.7.1-alpha.8615129)?

[Yvo Smellenbergh] 3.7 unofficial Macintosh test version available ... [3618 days 16 hours and 19 minutes ago]

Mon, 23 May 2016 17:21:40 GMT

http://megapov.inetart.net/beta/POVRay3_7_Unofficial.zip
Only binary

32/64 bit OS X10.6 or later

Changes:

- fixed a few bugs in the preview window resulting in a much, much 
faster update. 
- preferences panel >> "Image & quality' >> "Image Size" section:
  fixed several bugs when adjusting partial image sizes.
- source cleaup

Feedback much appreciated!

Yvo
-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[clipka] Re: POV-Ray 4.0 for Mac [3735 days 13 hours and 53 minutes ago]

Wed, 27 Jan 2016 19:47:39 GMT

Am 27.01.2016 um 20:01 schrieb Asinus Rex:
> Does anyone know whether there is any development going on for version 4.0,
> specifically an official Mac version? If so, any idea when? I feel like I've
> been waiting for ages.

Currently we're not officially working on a version 4.0 of POV-Ray;
however, POV-Ray 3.7 is actually a stepping stone on the way towards
4.0, and current work on what is likely to become POV-Ray 3.7.1 includes
more architectural changes under the hood, which will eventually lead up
to a 4.0 somewhere down the road.

Before version 4.0 there may even be a version 3.x that would be 4.0 in
disguise as far as internal architecture and potential features goes,
except that it would still use the old scene description language, as
the current plan is for 4.0 to not indicate new technology, but a new SDL.

As for Mac versions, there is currently no work on any official one, so
Yvo's unofficial port still is the best you can get and hope for in the
near future.

I'm not sure what Yvo's release schedule is, but at present I would
guess that he is waiting for the next official non-alpha version.

In case a command-line version will do for you, you might want to check
with the folks at the Homebrew or MacPorts projects.

[Asinus Rex] POV-Ray 4.0 for Mac [3735 days 14 hours and 36 minutes ago]

Wed, 27 Jan 2016 19:05:00 GMT

Does anyone know whether there is any development going on for version 4.0,
specifically an official Mac version? If so, any idea when? I feel like I've
been waiting for ages.

[aeffects] Re: macbook air [4037 days 13 hours and 11 minutes ago]

Tue, 31 Mar 2015 20:30:00 GMT

"TreeLimb Jim" <all### [at] yahoocom> wrote:
> > > Are there any known operating/running issues regarding running POV3.7
> > > unofficial
> > > on OSX10.10.x utilizing this laptop? Appreciate all input.
>
> Yes, its going to get warm. I use iStat Menus to monitor system stats and get
> better cooling performance on different surfaces. iStat Menus has
> a function to adjust fan rpm. I recommend copying the default values into their
> own config just in case you want to get back to them.
>
> You'll get better performance putting the app, output and project folders on a
> faster external drive. I have a Mini that file serves as well as being one of
> several Macs to render animations, using the FrameStep > 1 and Continue
> Rendering flag.
>
> I could be out on a limb,
> Jim

belated thanks for the input, Jim...
DHealy

[TreeLimb Jim] Re: macbook air [4118 days 5 hours and 1 minute ago]

Sat, 10 Jan 2015 04:40:00 GMT

> > Are there any known operating/running issues regarding running POV3.7
> > unofficial
> > on OSX10.10.x utilizing this laptop? Appreciate all input.

Yes, its going to get warm. I use iStat Menus to monitor system stats and get
better cooling performance on different surfaces. iStat Menus has
a function to adjust fan rpm. I recommend copying the default values into their
own config just in case you want to get back to them.

You'll get better performance putting the app, output and project folders on a
faster external drive. I have a Mini that file serves as well as being one of
several Macs to render animations, using the FrameStep > 1 and Continue
Rendering flag.

I could be out on a limb,
Jim

[Yvo Smellenbergh] Re: macbook air [4148 days 15 hours and 28 minutes ago]

Wed, 10 Dec 2014 18:12:52 GMT

On 2014-12-09 14:21:47 +0000, aeffects said:

> Are there any known operating/running issues regarding running POV3.7 
> unofficial
> on OSX10.10.x utilizing this laptop? Appreciate all input.
I guess your Macbook Air will produce a bit of heat and fan noise but I 
can't see what other issues there might be.
If it gets too hot, the system will protect your macbook, at least that 
is what I expect.

If you run it on the battery it won't last long so keep it plugged in;-)
> 
> And Yvo, thank you for your continued service bring us this wonderful program
> for the MAC.
You are welcome.

Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[aeffects] macbook air [4149 days 14 hours and 16 minutes ago]

Tue, 9 Dec 2014 19:25:00 GMT

Are there any known operating/running issues regarding running POV3.7 unofficial
on OSX10.10.x utilizing this laptop? Appreciate all input.

And Yvo, thank you for your continued service bring us this wonderful program
for the MAC.

DHealy
Lake Tahoe, Ca.

[Yvo Smellenbergh] Update POV-Ray 3.7 unofficial for Mac GUI(R5) no... [4173 days 18 hours and 55 minutes ago]

Sat, 15 Nov 2014 14:46:28 GMT

An update for POV-Ray 3.7 unofficial GUI version for Mac is available at:
http://megapov.inetart.net/povrayunofficial_mac/index.html#Mac


What is new in POV-Ray 3_7_Unofficial r5 (nov 15 2014):
------------------------------------------------------------------------------

1. fixed preview window for Yosemite;
2. some tweaks for better compatibility under Yosemite

Yvo
-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Re: Yosemite [4179 days 23 hours and 31 minutes ago]

Sun, 9 Nov 2014 10:10:05 GMT

On 2014-11-09 07:59:09 +0000, Anton Sherwood said:

> Oops, looks like I last compiled Pov on my PPC machine (2005â€“2010)
and 
> it was running on emulation until PPC emulation was dropped, sometime 
> between Snow Leopard and Yosemite.
> 
> Any tips for compiling Povray on Yosemite?
> I'm only interested in running it from the Unix shell.
> 
> -- *\\* Anton Sherwood *\\* www.bendwavy.org`

At the bottom of this page:
http://megapov.inetart.net/povrayunofficial_mac/
is a command line version and source-xcode project.

yvo
-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Anton Sherwood] Yosemite [4180 days 1 hour and 42 minutes ago]

Sun, 9 Nov 2014 07:59:09 GMT

Oops, looks like I last compiled Pov on my PPC machine (2005–2010) and 

it was running on emulation until PPC emulation was dropped, sometime 
between Snow Leopard and Yosemite.

Any tips for compiling Povray on Yosemite?
I'm only interested in running it from the Unix shell.

-- 
*\\* Anton Sherwood *\\* www.bendwavy.org`

[Yvo Smellenbergh] POVRay3_7_Unofficial_r5_RC1 for mac ready for te... [4185 days 18 hours and 48 minutes ago]

Mon, 3 Nov 2014 14:52:57 GMT

POVRay3_7_Unofficial_r5_RC1 for Mac ready for testing at:
http://megapov.inetart.net/beta/beta.html
Should run fine in 10.6.8  and later, Yosemite included.
Fixed some issues in the preview window for Yosemite and removed some 
oddities that showed up with the latest compiler.

I would really appreciate it if some of you run some tests on various 
os systems. I can only test on Mavericks and Yosemite.
So those of you who still run Snow Leopard, Lion, and Mountain Lion 
please give it a go and let me know.

Normally it should also run fine on the new Retina iMac, in case anyone 
of you owns one.... need I say more?

Mac users, don't be shy (I can see on my download stats that there are 
many of you) ;-).


Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Paul Bourke] thin lines [4195 days 8 hours and 56 minutes ago]

Sat, 25 Oct 2014 00:45:00 GMT

Updated to Yosemite ... old port install of poverty 3.6 no longer works.
So port installed 3.7, about time I figured.
Seems to render, output saved files look ok but the onscreen display just
consists of thin lines, perhaps every N'th vertical scan line through the model.
Suggestions?

[b2jammer] Povray 3.7 Snow Leopard XFlush Not Found [4254 days 9 hours and 41 minutes ago]

Wed, 27 Aug 2014 00:00:00 GMT

I have installed Povray 3.7 on my Mac, and while everything else works just
fine (I have rendered quite a few test scenes with it, and have performed the
benchmark successfully), I cannot get the X Window display preview support to
compile, as the
configure script cannot find XFlush in the X11 library.

I'm using XQuartz 2.7.7
on Mac OS X 10.6.8, and I have the original install discs in case I need them.
Here's the relevant section of the configuration log:

checking whether -R must be followed by a space... no
checking for dnet_ntoa in -ldnet... no
checking for dnet_ntoa in -ldnet_stub... no
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... no
checking X11/Xlib.h usability... yes
checking X11/Xlib.h presence... yes
checking for X11/Xlib.h... yes
checking for XFlush in -lX11... no
configure: X Window display will be disabled

Language constructs and functions
---------------------------------
checking whether time.h and sys/time.h may both be included... yes
checking time.h usability... yes
checking time.h presence... yes
checking for time.h... yes
checking limits.h usability... yes

Any potential solutions or workarounds? Thanks.

[CAD-Andi] Re: MacPro parallel rendering trouble [4265 days 9 hours and 46 minutes ago]

Fri, 15 Aug 2014 23:55:01 GMT

Thanks to Yvo the problem is solved:

The solution to running multiple render tasks in parallel on a MAC is:

1. Setup multipole users
2. Allow easy user switching for convenience in the OSX settings
3. Use the command line version of povray and .ini file to start your render
tasks.

Don't forget to point povray with the option +Llibrarypath to the standard
includes directory.

Running multiple render tasks of povray can maximize the CPU usage also during
the linear parsing process that can sometimes be as long or even longer than the
render process depending on how much imported mesh data you try to render.
Parsing can only be done on one core at a time.

Thanks Yvo for the MAC (unofficial) port of POVRAY!

Andi

[Yvo Smellenbergh] Re: MacPro parallel rendering trouble [4266 days 15 hours and 31 minutes ago]

Thu, 14 Aug 2014 18:09:49 GMT

On 2014-08-14 08:44:26 +0000, CAD-Andi said:

> Hello!
> 
> I ran into a big problem yesterday night and hope someone can help me.
> 
> Quick description of the problem (if there is such thing):
> Multiple render tasks seem to interfere with each other.
> Resulting images contain blocks and scan lines in areas they should not even
> render in. Every time when two povray instances render together they mess up
> each other.
How do you run 2 instances of the same application?
You can make a copy but they will still use the same prefs file.
This application was not designed to have 2 instances running.
The only thing I can think of is that the same output file is used, I 
just tried this with two instances running and it works ;-)
Maybe you can try to specify the output file in each ini file.

That is  the only thing I can think of, but this does not explain why 
you have the same problems with the command line version.
That version does not use a preference file.

If you have more info, please e-mail it directly to me.

BTW, if you set the number of threads to 24 the full potential is used. 
Running two instances will not speed thing up!
Just watch your activity monitor and you will see that all your cores 
are used 100% all the time.

If you use the GUI version and set number of threads to 'automatic' on 
the "Bounding & Threads" all your cores are used.

Yvo

> 
> More detailed information:
> 
> System:
> MacPro 2.7GHz 12-core with 30MB of L3 cache
> 64GB (4x16GB) of 1866MHz DDR3 ECC
> 1TB PCIe-based flash storage
> Dual AMD FirePro D700 GPUs with 6GB of GDDR5 VRAM each
Nice ;-)

> 
> (Yes! It is the biggest and baddes Mac money can buy!)
> 
> Povray version installed:
> POVRay3_7_Unofficial r4 (jul 6 2014)
> 
> I must utilize the power of this machine rendering multiple jhobs in 
> parallel or
> I will not meet my deadline for my project at the end of this month!
> 
> Background:
> Everything runs fine if I don't run more than one povray task in parallel.
> I successfully ran parallel jobs in regular HD resolution 1920x1080.
> Worked great for a test rendering.
> Then I started the REAL deal and I ran into this:
> 
> My animations are stereoscopic projections using "offset" frustum cameras.
> I achieve this by setting up a regular perspective camera and render only part
> of the image (column and row commands in .ini file). After the render I
> programmed some post-processing to crop and join the stereo frames.
> 
> The problem:
> There seems to be an interference issue between render jobs that run in
> parallel. All the sudden something that looks like fields of offset interlaced
> scan lines appear in areas of the picture that are not even supposed to be
> containing pixels at all. It appears as if rendered pixels from other parallel
> render jobs find their way into other render results where they don't 
> belong. It
> almost looks like as if the different render tasks "share" the same chunk of
> memory and "overwrite" each others result!
> 
> Running only one single render task in parallel is not using the 
> machine to it's
> fullest potential which I must to get done in tome.
> 
> I tried multiple instances of the GUI version and also used the command line
> versions. Both exhibit the same issue.
> 
> Any ideas? I would be eternally grateful!!!
> 
> Two of my .ini files:
> 
> Width=5126
> Height=1550
> Start_Column=190
> Start_Row=441
> End_Column=4030
> End_Row=1521
> Antialias=On
> Antialias_Threshold=0.1
> Antialias_Depth=3
> Input_File_Name="./render_S1_LEFT_EYE_.pov"
> Initial_Frame=1
> Final_Frame=1000
> Subset_Start_Frame=1
> Subset_End_Frame=1000
> Initial_Clock=0
> Final_Clock=1
> Cyclic_Animation=no
> 
> 
> Width=7957
> Height=1529
> Start_Column=4117
> Start_Row=431
> End_Column=7957
> End_Row=1511
> Antialias=On
> Antialias_Threshold=0.1
> Antialias_Depth=3
> Input_File_Name="./render_S3_LEFT_EYE_.pov"
> Initial_Frame=1
> Final_Frame=1000
> Subset_Start_Frame=1
> Subset_End_Frame=1000
> Initial_Clock=0
> Final_Clock=1
> Cyclic_Animation=no


-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[CAD-Andi] MacPro parallel rendering trouble [4266 days 20 hours and 56 minutes ago]

Thu, 14 Aug 2014 12:45:01 GMT

Hello!

I ran into a big problem yesterday night and hope someone can help me.

Quick description of the problem (if there is such thing):
Multiple render tasks seem to interfere with each other.
Resulting images contain blocks and scan lines in areas they should not even
render in. Every time when two povray instances render together they mess up
each other.

More detailed information:

System:
MacPro 2.7GHz 12-core with 30MB of L3 cache
64GB (4x16GB) of 1866MHz DDR3 ECC
1TB PCIe-based flash storage
Dual AMD FirePro D700 GPUs with 6GB of GDDR5 VRAM each

(Yes! It is the biggest and baddes Mac money can buy!)

Povray version installed:
POVRay3_7_Unofficial r4 (jul 6 2014)

I must utilize the power of this machine rendering multiple jhobs in parallel or
I will not meet my deadline for my project at the end of this month!

Background:
Everything runs fine if I don't run more than one povray task in parallel.
I successfully ran parallel jobs in regular HD resolution 1920x1080.
Worked great for a test rendering.
Then I started the REAL deal and I ran into this:

My animations are stereoscopic projections using "offset" frustum cameras.
I achieve this by setting up a regular perspective camera and render only part
of the image (column and row commands in .ini file). After the render I
programmed some post-processing to crop and join the stereo frames.

The problem:
There seems to be an interference issue between render jobs that run in
parallel. All the sudden something that looks like fields of offset interlaced
scan lines appear in areas of the picture that are not even supposed to be
containing pixels at all. It appears as if rendered pixels from other parallel
render jobs find their way into other render results where they don't belong. It
almost looks like as if the different render tasks "share" the same chunk of
memory and "overwrite" each others result!

Running only one single render task in parallel is not using the machine to it's
fullest potential which I must to get done in tome.

I tried multiple instances of the GUI version and also used the command line
versions. Both exhibit the same issue.

Any ideas? I would be eternally grateful!!!

Two of my .ini files:

Width=5126
Height=1550
Start_Column=190
Start_Row=441
End_Column=4030
End_Row=1521
Antialias=On
Antialias_Threshold=0.1
Antialias_Depth=3
Input_File_Name="./render_S1_LEFT_EYE_.pov"
Initial_Frame=1
Final_Frame=1000
Subset_Start_Frame=1
Subset_End_Frame=1000
Initial_Clock=0
Final_Clock=1
Cyclic_Animation=no


Width=7957
Height=1529
Start_Column=4117
Start_Row=431
End_Column=7957
End_Row=1511
Antialias=On
Antialias_Threshold=0.1
Antialias_Depth=3
Input_File_Name="./render_S3_LEFT_EYE_.pov"
Initial_Frame=1
Final_Frame=1000
Subset_Start_Frame=1
Subset_End_Frame=1000
Initial_Clock=0
Final_Clock=1
Cyclic_Animation=no

[Yvo Smellenbergh] Update POV-Ray 3.7 unofficial for Mac GUI (r4) j... [4305 days 20 hours and 23 minutes ago]

Sun, 6 Jul 2014 13:17:52 GMT

An update for POV-Ray 3.7 unofficial GUI version for Mac is available at:
http://megapov.inetart.net/povrayunofficial_mac/index.html#Mac

What is new in POVRay3_7_Unofficial r4 (jul 6 2014):
--------------------------------------------------------
1. fixed bug in sor editor
2. added torus to the objects menu
3. fixed bug msdos line endings in insert menu files;

Yvo
-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Re: Update POV-Ray 3.7 unofficial for Mac GUI (r3) [4307 days 2 hours and 41 minutes ago]

Sat, 5 Jul 2014 06:59:59 GMT

On 2014-07-02 10:34:44 +0000, TStone said:

> Yvo Smellenbergh <yvo### [at] cancel_This_gmxnet> wrote:
> 
>> Little bug, please download a fixed version at (only application):
>> http://megapov.inetart.net/beta/POVRay3_7_Unofficial.zip
>> There are also some minor fixes for syntax highlighting and insert menu
>> files with cr/nl.
>> Thanks for reporting this!
>> 
>> Yvo
> 
> 
> It seems "torus" have vanished from the templates->objects dialogue...

Yes, will fix it!
Thanks for reporting this.

yvo
-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[pjl] Re: Update POV-Ray 3.7 unofficial for Mac GUI (r3) [4327 days 4 hours and 31 minutes ago]

Sun, 15 Jun 2014 05:10:00 GMT

Yvo Smellenbergh <yvo### [at] cancel_This_gmxnet> wrote:
>
> Little bug, please download a fixed version at (only application):
> http://megapov.inetart.net/beta/POVRay3_7_Unofficial.zip
> There are also some minor fixes for syntax highlighting and insert menu
> files with cr/nl.
> Thanks for reporting this!

Yvo,

Fantastic.  You don't get that kind of service anywhere very often.

Once again, I really appreciate your efforts on this.

Many thanks
Peter

[Yvo Smellenbergh] Re: Update POV-Ray 3.7 unofficial for Mac GUI (r3) [4328 days 1 hour and 14 minutes ago]

Sat, 14 Jun 2014 08:27:08 GMT

On 2014-06-14 02:17:28 +0000, pjl said:

> Yvo Smellenbergh <yvo### [at] cancel_This_gmxnet> wrote:
>> An update for POV-Ray 3.7 unofficial GUI version for Mac is available at:
>> http://megapov.inetart.net/povrayunofficial_mac/index.html#Mac
>> 
> 
> Yvo,
> 
> Thanks, I really appreciate the effort you've put into this. However, 
> I'm having
> a problem and I'm wondering if you can suggest what's going wrong.  If 
> I use the
> objects... template to create a new sor and then click the "Edit Spline" button
> the edit window opens but the programme then crashes and vanishes.
> 
> This happens every time on both a Macbook Air running Mavericks and an iMac
> running Mountain Lion.
> 
> Any ideas?
> 
> Peter

Little bug, please download a fixed version at (only application):
http://megapov.inetart.net/beta/POVRay3_7_Unofficial.zip
There are also some minor fixes for syntax highlighting and insert menu 
files with cr/nl.
Thanks for reporting this!

Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[pjl] Re: Update POV-Ray 3.7 unofficial for Mac GUI (r3) [4328 days 3 hours and 21 minutes ago]

Sat, 14 Jun 2014 06:20:01 GMT

Yvo Smellenbergh <yvo### [at] cancel_This_gmxnet> wrote:
> An update for POV-Ray 3.7 unofficial GUI version for Mac is available at:
> http://megapov.inetart.net/povrayunofficial_mac/index.html#Mac
>

Yvo,

Thanks, I really appreciate the effort you've put into this. However, I'm having
a problem and I'm wondering if you can suggest what's going wrong.  If I use the
objects... template to create a new sor and then click the "Edit Spline" button
the edit window opens but the programme then crashes and vanishes.

This happens every time on both a Macbook Air running Mavericks and an iMac
running Mountain Lion.

Any ideas?

Peter

[Yvo Smellenbergh] Re: Update POV-Ray 3.7 unofficial for Mac GUI (r3) [4340 days 20 hours and 2 minutes ago]

Sun, 1 Jun 2014 13:39:08 GMT

On 2014-06-01 09:06:42 +0000, kurtz le pirate said:

> Le 31/05/2014 19:01, Yvo Smellenbergh a écrit :
>> An update for POV-Ray 3.7 unofficial GUI version for Mac is available at:
>> http://megapov.inetart.net/povrayunofficial_mac/index.html#Mac
>> 
>> What is new in POVRay3_7_Unofficial r3:
>> --------------------------------------------------------
>> 1.  turned off "smart quotes" in the editor (bug in Mavericks)
>> 2. insert menu sorts correctly and separator lines are used.
>> 3. insert menu watches every directory for changes and updates accordingly
>> 4. rearranged preview window code to improve speed
>> 5. compiled with Xcode 5.1.1
>> 6. pause/resume fixed
>> 
>> UberPOV beta 5 will follow soon....
>> 
>> Yvo
> 
> 
> thanks again Yvo :)
> 
> 
> just for elegance,(a little bit pernickety, i know), why not remove 
> ".txt" at the end of the items's menus ?
Good idea, will do so.


Yvo

-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[kurtz le pirate] Re: Update POV-Ray 3.7 unofficial for Mac GUI (r3) [4341 days and 34 minutes ago]

Sun, 1 Jun 2014 09:06:43 GMT

Le 31/05/2014 19:01, Yvo Smellenbergh a écrit :
> An update for POV-Ray 3.7 unofficial GUI version for Mac is available at:
> http://megapov.inetart.net/povrayunofficial_mac/index.html#Mac
>
> What is new in POVRay3_7_Unofficial r3:
> --------------------------------------------------------
> 1.  turned off "smart quotes" in the editor (bug in Mavericks)
> 2. insert menu sorts correctly and separator lines are used.
> 3. insert menu watches every directory for changes and updates accordingly
> 4. rearranged preview window code to improve speed
> 5. compiled with Xcode 5.1.1
> 6. pause/resume fixed
>
> UberPOV beta 5 will follow soon....
>
> Yvo


thanks again Yvo :)


just for elegance,(a little bit pernickety, i know), why not remove 
".txt" at the end of the items's menus ?




---
Kurtz le pirate
Compagnie de la Banquise

[Yvo Smellenbergh] Update POV-Ray 3.7 unofficial for Mac GUI (r3) [4341 days 16 hours and 39 minutes ago]

Sat, 31 May 2014 17:01:58 GMT

An update for POV-Ray 3.7 unofficial GUI version for Mac is available at:
http://megapov.inetart.net/povrayunofficial_mac/index.html#Mac

What is new in POVRay3_7_Unofficial r3:
--------------------------------------------------------
1.  turned off "smart quotes" in the editor (bug in Mavericks)
2. insert menu sorts correctly and separator lines are used.
3. insert menu watches every directory for changes and updates accordingly
4. rearranged preview window code to improve speed
5. compiled with Xcode 5.1.1
6. pause/resume fixed

UberPOV beta 5 will follow soon....

Yvo
-- 
-------------------------------------------------------------------------------------------


POV-Ray 3.7 unofficial: http://megapov.inetart.net/povrayunofficial_mac/
UberPOV Mac: http://megapov.inetart.net/uberpov_mac/index.html#Mac
MegaPOV: http://megapov.inetart.net
E-mail: yvo(DOT)s(AT)gmx.net

[kurtz le pirate] Converter utilitie [4376 days 23 hours and 49 minutes ago]

Sat, 26 Apr 2014 09:52:02 GMT

hopeful

http://i3dconverter.com



---
Kurtz le pirate
Compagnie de la Banquise

[kurtz le pirate] Re: New Mac... [4412 days and 47 minutes ago]

Sat, 22 Mar 2014 08:53:55 GMT

Le 18/03/2014 18:54, Yvo Smellenbergh a écrit :
> kurtz le pirate <kur### [at] yahoofr> wrote:
>
>> hello,
>>
>> i ordered my new mac and it will be delivered in a few days
>> it's an 21" iMac (intel core i5) with maveriks.
> Nice machine, congrats with the purchase!
>>
>> so, which version of povray should I use ?
> Do you think you have a choice? ;-)
>>
>> POV-Ray Unofficial 3.7.0  from megapov.inetart.net ?
> Of course, what else? Oh, you can of course also use UberPOV:
> http://megapov.inetart.net/uberpov_mac/index.html#Mac
>
> I hope you will enjoy POV-Ray unofficial on your new machine and if you
> have any questions or need assistance, just drop an e-mail or post here.
>
> Yvo
>

Thanks Yvo.

All works fine...



-- 
Kurtz le pirate
Compagnie de la Banquise

[kurtz le pirate] Re: New Mac... [4412 days and 50 minutes ago]

Sat, 22 Mar 2014 08:51:30 GMT

Le 18/03/2014 18:54, Yvo Smellenbergh a écrit :
> kurtz le pirate <kur### [at] yahoofr> wrote:
>
>> hello,
>>
>> i ordered my new mac and it will be delivered in a few days
>> it's an 21" iMac (intel core i5) with maveriks.
> Nice machine, congrats with the purchase!
>>
>> so, which version of povray should I use ?
> Do you think you have a choice? ;-)
>>
>> POV-Ray Unofficial 3.7.0  from megapov.inetart.net ?
> Of course, what else? Oh, you can of course also use UberPOV:
> http://megapov.inetart.net/uberpov_mac/index.html#Mac
>
> I hope you will enjoy POV-Ray unofficial on your new machine and if you
> have any questions or need assistance, just drop an e-mail or post here.
>
> Yvo
>

Thanks Yvo.

All works fine...



-- 
Kurtz le pirate
Compagnie de la Banquise

[kurtz le pirate] Re: New Mac... [4412 days and 56 minutes ago]

Sat, 22 Mar 2014 08:45:00 GMT

Le 18/03/2014 18:54, Yvo Smellenbergh a écrit :
> kurtz le pirate <kur### [at] yahoofr> wrote:
>
>> hello,
>>
>> i ordered my new mac and it will be delivered in a few days
>> it's an 21" iMac (intel core i5) with maveriks.
> Nice machine, congrats with the purchase!
>>
>> so, which version of povray should I use ?
> Do you think you have a choice? ;-)
>>
>> POV-Ray Unofficial 3.7.0  from megapov.inetart.net ?
> Of course, what else? Oh, you can of course also use UberPOV:
> http://megapov.inetart.net/uberpov_mac/index.html#Mac
>
> I hope you will enjoy POV-Ray unofficial on your new machine and if you
> have any questions or need assistance, just drop an e-mail or post here.
>
> Yvo
>

Thanks Yvo.

All works fine...



-- 
Kurtz le pirate
Compagnie de la Banquise

[Yvo Smellenbergh] Re: New Mac... [4415 days 15 hours and 47 minutes ago]

Tue, 18 Mar 2014 17:54:20 GMT

kurtz le pirate <kur### [at] yahoofr> wrote:

> hello,
> 
> i ordered my new mac and it will be delivered in a few days
> it's an 21" iMac (intel core i5) with maveriks.
Nice machine, congrats with the purchase!
> 
> so, which version of povray should I use ?
Do you think you have a choice? ;-) 
> 
> POV-Ray Unofficial 3.7.0  from megapov.inetart.net ?
Of course, what else? Oh, you can of course also use UberPOV:
http://megapov.inetart.net/uberpov_mac/index.html#Mac

I hope you will enjoy POV-Ray unofficial on your new machine and if you
have any questions or need assistance, just drop an e-mail or post here.

Yvo

-- 
-----------------------------------
MegaPOV at:  http://megapov.inetart.net
MacMegaPOV at:  http://users.skynet.be/smellenbergh
E-mail: yvo(DOT)s(AT)gmx.net

[kurtz le pirate] New Mac... [4416 days 15 hours and 14 minutes ago]

Mon, 17 Mar 2014 18:26:59 GMT

hello,

i ordered my new mac and it will be delivered in a few days
it's an 21" iMac (intel core i5) with maveriks.

so, which version of povray should I use ?

POV-Ray Unofficial 3.7.0  from megapov.inetart.net ?



thnaks

-- 
klp

[Franz von Dardel] Re: Large panoramic images have a completely bla... [4433 days 12 hours and 6 minutes ago]

Fri, 28 Feb 2014 21:35:00 GMT

Last minute: by lowering max_trace_level to 10 instead of 12, the problem
disappears...

[Franz von Dardel] Large panoramic images have a completely black s... [4433 days 15 hours and 21 minutes ago]

Fri, 28 Feb 2014 18:20:00 GMT

I am producing cylindrical and spherical panoramic images, the size being 5000 x
1250 and 4000 x 2000 respectively, PNG format. Using POVRay 3.7 unofficial, with
radiosity. A very small part of the image is very memory-intensive; it contains
bottles of white wine in clear glass bottles.

Rendering takes from 1 to 5 hours depending on the settings: with
max_trace_level 20, it is very slow, so I reduced it to 10 or 12. I also updated
to the Feb 2014 update in the hope that the problem was solved.

The curious thing is that within POVRay, the image is complete, but when I want
to rename it or open it with another software (Photoshop or GraphicConverter), a
large portion of the image is completely black.

I have posted the images here after downsizing them:
http://dardel.info/imagesPOV/Keller_Cyl1.png (2000 x 500, i.e. 40% of the
original)
and
http://dardel.info/imagesPOV/Keller_Sph1.png (1000 x 500, 25% of the original)

Note that the upper left corner of the black polygon is the same in both images;
it starts in the memory-intensive area.

I was able to obtain a workable version of the cylindrical image after reducing
max_trace_level from 20 to 10 (which shortened the rendering time from more than
4 to about 1 hour, but I increased it again to 12 for the spherical image, and
this produced again a black polygon.

Once again, when I see the pict in the rendering window of POVRay, I see nothing
wrong, but I am not able to recover that image.

In smaller sizes, the problem doesn't seem to occur. Also, with other scenes
that don't have the bottles of white wine, there is no problem when rendering at
the same large size.

What may be wrong?

P.S. MacBook Pro, processor 2.2 GHz, memory 4 GB, OS 10.7.5

[Yvo Smellenbergh] Update POV-Ray 3.7 unofficial for Mac GUI [4439 days 15 hours and 33 minutes ago]

Sat, 22 Feb 2014 18:07:40 GMT

There is a little update available for POV-Ray 3.7 unofficial GUI
version for Mac:
http://megapov.inetart.net/povrayunofficial_mac/index.html#Mac
fixes:
- the preview window, it wasn't always updates completely.
- bug fix in the SOR editor (crashed sometimes)

There are no changes for the command line version.

Yvo

-- 
-----------------------------------
MegaPOV at:  http://megapov.inetart.net
MacMegaPOV at:  http://users.skynet.be/smellenbergh
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Update UberPOV for Mac GUI [4439 days 15 hours and 33 minutes ago]

Sat, 22 Feb 2014 18:07:40 GMT

There is a little update available for UberPOV GUI version for Mac:
http://megapov.inetart.net/uberpov_mac/index.html#Mac
This is a fix for the preview window, it wasn't always updates
completely.

There are no changes for the command line version.

Yvo


-- 
-----------------------------------
MegaPOV at:  http://megapov.inetart.net
MacMegaPOV at:  http://users.skynet.be/smellenbergh
E-mail: yvo(DOT)s(AT)gmx.net

[Le Forgeron] Re: Parsing Fails for all the scenes [4468 days 16 hours and 35 minutes ago]

Fri, 24 Jan 2014 17:05:55 GMT

Le 24/01/2014 01:19, Sepideh nous fit lire :
> Hi, I am new to povray and would very much appreciate your help.
> I have installed the povray-3.7 using the MacPorts package manager. Now I am
> trying to render some of the scenes that are already available in the "scenes"
> directory to familiarize myself with povray. I have also placed the right
> library path for the "include" directory.
> 
> Here is the command: povray povray.ini +Istarfield.pov
> and below is the output:
> ******************************************************************************
> Persistence of Vision(tm) Ray Tracer Version 3.7.0.unofficial (clang++ 4.2.1 @
>  x86_64-apple-darwin13)
> This is an unofficial version compiled by:
>  MacPorts <https://www.macports.org/>
>  The POV-Ray Team is not responsible for supporting this version.
> 
> CONTRIBUTORS NAME-DELETED FOR BREVITY
> 
> Support libraries used by POV-Ray:
>   ZLib 1.2.8, Copyright 1995-2012 Jean-loup Gailly and Mark Adler
>   LibPNG 1.6.8, Copyright 1998-2012 Glenn Randers-Pehrson
>   LibJPEG 90, Copyright 1991-2013 Thomas G. Lane, Guido Vollbeding
>   LibTIFF 4.0.3, Copyright 1988-1997 Sam Leffler, 1991-1997 SGI
>   Boost 1.55, http://www.boost.org/
>   OpenEXR, Copyright (c) 2004-2007, Industrial Light & Magic.
> 
> Parser Options
>   Input file: starfield.pov
>   Remove bounds........On
>   Split unions.........Off
>   Library paths:
>     /opt/local/share/povray-3.7/include
>   Clock value:    0.000  (Animation off)
> Image Output Options
>   Image resolution.....800 by 600 (rows 1 to 600, columns 1 to 800).
>   Output file..........starfield.png, 24 bpp PNG
>   Dithering............Off
>   Graphic display......On  (gamma: sRGB)
>   Mosaic preview.......Off
>   Continued trace......Off
> Information Output Options
>   All Streams to console..........On
>   Debug Stream to console.........On
>   Fatal Stream to console.........On
>   Render Stream to console........On
>   Statistics Stream to console....On
>   Warning Stream to console.......On
> ==== [Parsing...] ==========================================================
> Cannot create render state output file.
> Cannot create render state output file.

> ******************************************************************************
> Tried many of the scenes but have got the same result. So I believe this is not
> a scene-specific error but a more general one. Any Suggestions?
> 
> 
Look above ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^

The rendering must be done in a write-ok directory, for the rendering user.

[Sepideh] Parsing Fails for all the scenes [4469 days 9 hours and 21 minutes ago]

Fri, 24 Jan 2014 00:20:01 GMT

Hi, I am new to povray and would very much appreciate your help.
I have installed the povray-3.7 using the MacPorts package manager. Now I am
trying to render some of the scenes that are already available in the "scenes"
directory to familiarize myself with povray. I have also placed the right
library path for the "include" directory.

Here is the command: povray povray.ini +Istarfield.pov
and below is the output:
******************************************************************************
Persistence of Vision(tm) Ray Tracer Version 3.7.0.unofficial (clang++ 4.2.1 @
 x86_64-apple-darwin13)
This is an unofficial version compiled by:
 MacPorts <https://www.macports.org/>
 The POV-Ray Team is not responsible for supporting this version.

CONTRIBUTORS NAME-DELETED FOR BREVITY

Support libraries used by POV-Ray:
  ZLib 1.2.8, Copyright 1995-2012 Jean-loup Gailly and Mark Adler
  LibPNG 1.6.8, Copyright 1998-2012 Glenn Randers-Pehrson
  LibJPEG 90, Copyright 1991-2013 Thomas G. Lane, Guido Vollbeding
  LibTIFF 4.0.3, Copyright 1988-1997 Sam Leffler, 1991-1997 SGI
  Boost 1.55, http://www.boost.org/
  OpenEXR, Copyright (c) 2004-2007, Industrial Light & Magic.

Parser Options
  Input file: starfield.pov
  Remove bounds........On
  Split unions.........Off
  Library paths:
    /opt/local/share/povray-3.7/include
  Clock value:    0.000  (Animation off)
Image Output Options
  Image resolution.....800 by 600 (rows 1 to 600, columns 1 to 800).
  Output file..........starfield.png, 24 bpp PNG
  Dithering............Off
  Graphic display......On  (gamma: sRGB)
  Mosaic preview.......Off
  Continued trace......Off
Information Output Options
  All Streams to console..........On
  Debug Stream to console.........On
  Fatal Stream to console.........On
  Render Stream to console........On
  Statistics Stream to console....On
  Warning Stream to console.......On
==== [Parsing...] ==========================================================
Cannot create render state output file.
Cannot create render state output file.
----------------------------------------------------------------------------
Parser Statistics
----------------------------------------------------------------------------
Finite Objects:            0
Infinite Objects:          1
Light Sources:             1
Total:                     2
----------------------------------------------------------------------------
Parser Time
  Parse Time:       0 hours  0 minutes  0 seconds (0.017 seconds)
              using 1 thread(s) with 0.-01 CPU-seconds total
  Bounding Time:    0 hours  0 minutes  0 seconds (0.000 seconds)
              using 1 thread(s) with 0.-01 CPU-seconds total
Render failed
******************************************************************************
Tried many of the scenes but have got the same result. So I believe this is not
a scene-specific error but a more general one. Any Suggestions?

[SLby] Re: EXC_BAD_ACCESS error for IStream [4479 days 2 hours and 31 minutes ago]

Tue, 14 Jan 2014 07:10:01 GMT

"S-Lim" <byl### [at] hotmailcom> wrote:
> Hi, I'm trying to build an OS X app that has a GUI layout similar to the Windows
> version while running the linux version of povray in the background for
> operations, since it is compilable with modifications i assume it works. I've
> used the povray 3.6.2 source and fixed the outstanding errors accordingly with
> the help of the internet. I'm using precompiled libraries for the image
> libraries and they've been included into my xcode project.
>
> I understand that it might sound really amateurish but I'm just starting with
> the linux and mac systems so please bear with me, thanks!
>
> I'm executing the file by splitting up the original main function into smaller
> subfunctions and passing in "povray /path/to/file/biscuit.pov" where path to
> file is the path to the pov file.
>
> Currently I'm having problems with the IStream portion in fileinputoutput.cpp.
>
> the exact error is:
> "Thread 1: EXC_BAD_ACCESS (code=I386_GPFLT)"
> at this part of the code
> "POV_PLATFORM_BASE.CreateIStream(stype)"
>
> I've googled extensively with regard to that error, apparently it has something
> to do with an invalid pointer, invalid location or permissions. But digging into
> the source it seems to me that this create stream simply creates a class object
> [IStream : IOBase] with the value 'stype' in one of its arguments.
>
> Any ideas what might be causing the problem and how do I address it? Thanks in
> advance for any help!

Not sure if I can actually edit the previous post, so sorry for the double
posting. but i believe the POV_PLATFORM_BASE was the cause of the problem for
me. i stripped it down to its bare function which is essentially new
IStream(type) and it worked. sorry for the trouble! Can I delete this somehow?

[S-Lim] EXC_BAD_ACCESS error for IStream [4479 days 4 hours and 16 minutes ago]

Tue, 14 Jan 2014 05:25:01 GMT

Hi, I'm trying to build an OS X app that has a GUI layout similar to the Windows
version while running the linux version of povray in the background for
operations, since it is compilable with modifications i assume it works. I've
used the povray 3.6.2 source and fixed the outstanding errors accordingly with
the help of the internet. I'm using precompiled libraries for the image
libraries and they've been included into my xcode project.

I understand that it might sound really amateurish but I'm just starting with
the linux and mac systems so please bear with me, thanks!

I'm executing the file by splitting up the original main function into smaller
subfunctions and passing in "povray /path/to/file/biscuit.pov" where path to
file is the path to the pov file.

Currently I'm having problems with the IStream portion in fileinputoutput.cpp.

the exact error is:
"Thread 1: EXC_BAD_ACCESS (code=I386_GPFLT)"
at this part of the code
"POV_PLATFORM_BASE.CreateIStream(stype)"

I've googled extensively with regard to that error, apparently it has something
to do with an invalid pointer, invalid location or permissions. But digging into
the source it seems to me that this create stream simply creates a class object
[IStream : IOBase] with the value 'stype' in one of its arguments.

Any ideas what might be causing the problem and how do I address it? Thanks in
advance for any help!

[Yvo Smellenbergh] UberPOV beta 3 for Mac released [4520 days 15 hours and 17 minutes ago]

Tue, 3 Dec 2013 18:24:12 GMT

Boys and girls,

UberPOV beta 3 is now available for MacOSX v 10.6.8 and later.
GUI and command line version.
The GUI version will not use the same prefs file as Unofficial POV-Ray
for Mac to avoid conflicts. 

Both GUI and Command Line version are first releases, not fully tested.
UberPOV itself is in beta stage so if you use it, you should know what
you are doing or ask info and assistance in this newsgroup
(unofficial.patches).

There are no specific option settings implemented in the preference
panel. If you want to use new options, use an ini file.
Add all the new options, or options you want to overwrite, in that file
and select it in the "files & paths" panel of the prefences panel.
All options set in this file will overwrite all other settings from the
preferences panel.
You can leave the file open and change the settings. Everytime you hit
the render button, the file will be saved.

For example add:
Sampling_Method=3
Antialias_Confidence=n.n
in an ini file and select that one to use the new sampling method 3.

Reed the 'changes.txt' file included in the archives for more info or go
to the UberPOV site, listed on the website.

Ah, you need a link? ;-)
http://megapov.inetart.net/uberpov_mac/

So, mister 'Uber' thinks he is better than 'Mega' ;-)

Nice work 'clipka', good to see that there is a new test bed for new
stuff.

Who is going to implement the mechsim patch from MegaPOV....

Enjoy it and report bugs if you like to see them fixed!

Yvo


-- 
-----------------------------------
MegaPOV at:  http://megapov.inetart.net
MacMegaPOV at:  http://users.skynet.be/smellenbergh
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Unofficial Command line version of POV-Ray 3.7 f... [4526 days 15 hours and 14 minutes ago]

Wed, 27 Nov 2013 18:27:21 GMT

An unofficial version of POV-Ray 3.7 command line for Mac is now
available.
Only text output, no preview window (yet).

Compiled binary and Xcode V5 project available at:
http://megapov.inetart.net/povrayunofficial_mac/
The GUI archive is, just like the compiled command line version, now
code signed. If you already have the GUI version there is no need to
download again. Only difference is that it is code signed for those who
(still) don't trust me :-)

Only Intel-based computers with system 10.6.8 and later (included 10.9)
are supported.

Feedback much appreciated

Yvo


-- 
-----------------------------------
MegaPOV at:  http://megapov.inetart.net
MacMegaPOV at:  http://users.skynet.be/smellenbergh
E-mail: yvo(DOT)s(AT)gmx.net

[Yvo Smellenbergh] Re: POV-Ray 3.7 Unofficial for Mac released [4538 days 15 hours and 35 minutes ago]

Fri, 15 Nov 2013 18:05:49 GMT

Mike W <mik### [at] yahoocom> wrote:

> "Anthony D. Baye" <Sha### [at] spamnomorehotmailcom> wrote:
> > yvo### [at] cancel_This_gmxnet (Yvo Smellenbergh) wrote:
> > > POV-Ray 3.7.0 Unofficial for Mac can be downloaded from:
> > > http://megapov.inetart.net/povrayunofficial_mac/
> > > Only Intel-based computers with system 10.6.8 and later (included 10.9)
> > > are supported.
> > > This is a universal binary with 32 and 64 bit versions.
> > >
> > >
> > > Yvo
> > >
> > >
> > > --
> > > -----------------------------------
> > > MegaPOV at:  http://megapov.inetart.net
> > > MacMegaPOV at:  http://users.skynet.be/smellenbergh
> > > E-mail: yvo(DOT)s(AT)gmx.net
> >
> > Tested in 64-bit 10.8.6 on my AMD Hackintosh
> >
> > CPU: AMD Phenom II X6
> >
> > benchmark.pov @ 640x480 in 6m 26s
> >
> > Regards,
> > A.D.B.
> 
> I downloaded the zip file, but I'm not sure what to do with all those files.
> Is there a dmg in there someplace?
The folder contains everything you need.
The application: PovRAy 3.7 Unofficial
The standard include folder, example scenes,â€¦
You can also use the help menu after you launched the application to get
you started.

yvo



-- 
-----------------------------------
MegaPOV at:  http://megapov.inetart.net
MacMegaPOV at:  http://users.skynet.be/smellenbergh
E-mail: yvo(DOT)s(AT)gmx.net

[Mike W] Re: POV-Ray 3.7 Unofficial for Mac released [4539 days 11 hours and 56 minutes ago]

Thu, 14 Nov 2013 21:45:01 GMT

"Anthony D. Baye" <Sha### [at] spamnomorehotmailcom> wrote:
> yvo### [at] cancel_This_gmxnet (Yvo Smellenbergh) wrote:
> > POV-Ray 3.7.0 Unofficial for Mac can be downloaded from:
> > http://megapov.inetart.net/povrayunofficial_mac/
> > Only Intel-based computers with system 10.6.8 and later (included 10.9)
> > are supported.
> > This is a universal binary with 32 and 64 bit versions.
> >
> >
> > Yvo
> >
> >
> > --
> > -----------------------------------
> > MegaPOV at:  http://megapov.inetart.net
> > MacMegaPOV at:  http://users.skynet.be/smellenbergh
> > E-mail: yvo(DOT)s(AT)gmx.net
>
> Tested in 64-bit 10.8.6 on my AMD Hackintosh
>
> CPU: AMD Phenom II X6
>
> benchmark.pov @ 640x480 in 6m 26s
>
> Regards,
> A.D.B.

I downloaded the zip file, but I'm not sure what to do with all those files.  Is
there a dmg in there someplace?

[Yvo Smellenbergh] POV-Ray 3.7 Unofficial for Mac released [4543 days 15 hours and 20 minutes ago]

Sun, 10 Nov 2013 18:20:41 GMT

POV-Ray 3.7.0 Unofficial for Mac can be downloaded from:
http://megapov.inetart.net/povrayunofficial_mac/
Only Intel-based computers with system 10.6.8 and later (included 10.9)
are supported.
This is a universal binary with 32 and 64 bit versions.


Yvo


-- 
-----------------------------------
MegaPOV at:  http://megapov.inetart.net
MacMegaPOV at:  http://users.skynet.be/smellenbergh
E-mail: yvo(DOT)s(AT)gmx.net

[Warp] Re: Povray 3.7.0.RC7 does not build under Mac OS... [4544 days and 1 minute ago]

Sun, 10 Nov 2013 09:40:12 GMT

BenjaminSeppke <ben### [at] seppkede> wrote:
> The error is due to an ambigous symbol: "shared_ptr"

And then people wonder why you should avoid the 'using' keyword to get
rid of namespaces.

-- 
                                                          - Warp

[BenjaminSeppke] Povray 3.7.0.RC7 does not build under Mac OS X 1... [4546 days 19 hours and 1 minute ago]

Thu, 7 Nov 2013 14:40:01 GMT

Hi all,

under Mavericks, using the new CLang 5.0.0 compile, the povray package (as
described by the macports-portfile:
https://trac.macports.org/browser/trunk/dports/graphics/povray/Portfile) does
not compile.

The error is due to an ambigous symbol: "shared_ptr", which cannot be resolved
uniquely by the compiler. This is due to the c++11 support of Clang, which now
brings with its own "shared_ptr" implementation. In the correspoding header
files, there is a "using boost::shared_ptr", but I think this is not suffient to
resolve the symbol, if it given without namespace inside the source code. Since
this is the case for a lot of declarations, I suggest to replace all
"<tab>shared_ptr" declarations with "<tab>boost::shared_ptr" declaration as it
is done whithin the function calls.

The patch would be quite easy, I succeeded with just executing:

find . -type f -exec gsed 's/\tshared_ptr/\tboost::shared_ptr/g' -i.back '{}' +

in the source directory.

Best wishes
Benjamin

[Alan Holding] Re: Site for the unofficial 3.7 version [4602 days and 1 minute ago]

Fri, 13 Sep 2013 09:40:01 GMT

yvo### [at] cancel_This_gmxnet (Yvo Smellenbergh) wrote:
> The web site for the unofficial version for POV-Ray 3.7 smp is located
> at:
> http://megapov.inetart.net/povrayunofficial_mac/index.html
> Current version is  v 3.7 RC 7.
> The site will be updated as soon as updates are available.
>
> --
> -----------------------------------
> MegaPOV at:  http://megapov.inetart.net
> MacMegaPOV at:  http://users.skynet.be/smellenbergh
> E-mail: yvo(DOT)s(AT)gmx.net

Thanks very very much for making this version!

[Stephen] Re: Site for the unofficial 3.7 version [4603 days 22 hours and 41 minutes ago]

Wed, 11 Sep 2013 11:00:01 GMT

yvo### [at] cancel_This_gmxnet (Yvo Smellenbergh) wrote:

> No problem, after you port Cocoa API to Linux but you better first ask
> Tim Cook's permission ;-)
>
> Yvo

Oh! That Tim Cook. I thought that you meant "our" Tim Cook.

Time to take a wake up pill. :-)

[Paolo Gibellini] Re: Site for the unofficial 3.7 version [4604 days 2 hours and 13 minutes ago]

Wed, 11 Sep 2013 07:27:42 GMT

>Yvo Smellenbergh  on date 10/09/2013 18.53 wrote:
>> ...what about a Linux porting?
> No problem, after you port Cocoa API to Linux but you better first ask
> Tim Cook's permission ;-)
>
> Yvo
>
Today I'm too busy... perhaps tomorrow :D
Paolo

[Yvo Smellenbergh] Re: Site for the unofficial 3.7 version [4604 days 16 hours and 48 minutes ago]

Tue, 10 Sep 2013 16:53:14 GMT

Paolo Gibellini <p.g### [at] gmailcom> wrote:

>  >Yvo Smellenbergh  on date 09/09/2013 22.55 wrote:
> > The web site for the unofficial version for POV-Ray 3.7 smp is located
> > at:
> > http://megapov.inetart.net/povrayunofficial_mac/index.html
> > Current version is  v 3.7 RC 7.
> > The site will be updated as soon as updates are available.
> >
> There are a lot of very interesting tools!
Thanks.

> ...what about a Linux porting?
No problem, after you port Cocoa API to Linux but you better first ask
Tim Cook's permission ;-)

Yvo


-- 
-----------------------------------
MegaPOV at:  http://megapov.inetart.net
MacMegaPOV at:  http://users.skynet.be/smellenbergh
E-mail: yvo(DOT)s(AT)gmx.net

[Paolo Gibellini] Re: Site for the unofficial 3.7 version [4605 days 1 hour and 21 minutes ago]

Tue, 10 Sep 2013 08:20:03 GMT

>Yvo Smellenbergh  on date 09/09/2013 22.55 wrote:
> The web site for the unofficial version for POV-Ray 3.7 smp is located
> at:
> http://megapov.inetart.net/povrayunofficial_mac/index.html
> Current version is  v 3.7 RC 7.
> The site will be updated as soon as updates are available.
>
There are a lot of very interesting tools!
...what about a Linux porting?
;-)
Paolo

[Yvo Smellenbergh] Site for the unofficial 3.7 version [4605 days 12 hours and 46 minutes ago]

Mon, 9 Sep 2013 20:55:22 GMT

The web site for the unofficial version for POV-Ray 3.7 smp is located
at:
http://megapov.inetart.net/povrayunofficial_mac/index.html
Current version is  v 3.7 RC 7.
The site will be updated as soon as updates are available.

-- 
-----------------------------------
MegaPOV at:  http://megapov.inetart.net
MacMegaPOV at:  http://users.skynet.be/smellenbergh
E-mail: yvo(DOT)s(AT)gmx.net

[Martin von Gagern] povray 3.7.0.RC7 does not support Preview_Start_... [4721 days 11 hours and 26 minutes ago]

Thu, 16 May 2013 22:15:00 GMT

It seems that povray 3.7.0.RC7 (compiled from macports) does not support the
`Preview_Start_Size` ini file setting.

== debug.ini: ==
Width=800
Height=600
Output_File_Type=N
Preview_Start_Size=256
Input_File_Name=debug.pov

== debug.pov: ==
#version 3.7;
camera { }

Callig "povray debug.ini" gives the following (or similar) output:

==== [Parsing...] ==========================================================
objc[29333]: Object 0x7ff2b1c65460 of class __NSFontTypefaceInfo autoreleased
with no pool in place - just leaking - break on objc_autoreleaseNoPool() to
debug
objc[29333]: Object 0x7ff2b1c65da0 of class __NSCFDictionary autoreleased with
no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
objc[29333]: Object 0x7ff2b1c65b70 of class NSAffineTransform autoreleased with
no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
objc[29333]: Object 0x7ff2b1c660f0 of class NSFont autoreleased with no pool in
place - just leaking - break on objc_autoreleaseNoPool() to debug
objc[29333]: Object 0x7ff2b1c66720 of class NSFont autoreleased with no pool in
place - just leaking - break on objc_autoreleaseNoPool() to debug
objc[29333]: Object 0x7ff2b1c66940 of class NSFont autoreleased with no pool in
place - just leaking - break on objc_autoreleaseNoPool() to debug
Assertion failed: ((pts >= PRETRACE_FIRST) && (pts <= PRETRACE_MAX)), function
BeforeTile, file lighting/radiosity.cpp, line 383.
Abort trap: 6

I originally reported this at https://trac.macports.org/ticket/39124

[Aaron] Re: povray 3.6 on Snow Leopard / X11 [4805 days 19 hours and 6 minutes ago]

Thu, 21 Feb 2013 14:35:01 GMT

On Mac OS X, you can install povray 3.7.0RC6 quite painlessly with Homebrew (
http://mxcl.github.com/homebrew/ ).  After installing homebrew, just enter the
following from the terminal:

  brew install povray

That will download the source, patch it for the mac, build and install it.  You
can then keep it up to date with the usual brew commands (brew update, brew
upgrade, etc).

Cheers!

[Kevin] Mega POV beta for Mountain Lion [4825 days 15 hours and 11 minutes ago]

Fri, 1 Feb 2013 18:30:01 GMT

Anyone know where I can get a compiled version  - beta or anything...
the advertised beta at http://megapov.inetart.net/beta.html does not seem to
exist

The Display window on MacMegaPov v1.2.1 r3 (if I can find it) seems erratic...

Thanks
Kevin

[pela3247] Povray and libpng on OS X 10.7.5 [4897 days 12 hours and 46 minutes ago]

Wed, 21 Nov 2012 20:55:01 GMT

Hello

I have installed povray on my Macbook Pro using macports:

$port installed |grep povray
povray @3.7.0.RC6_0 (active)

but when I want to render scenes, I get an error message:

Cannot allocate PNG data structures

which indicates that something is wrong with either my version of libpng or
something. The installation of povray changes the libpng version from 1.4.5_0 to
1.5.13_0. I have tried to Google this, but nothing really useful came up.

Any ideas?

Thanks
/Per

[Paul Bourke] White image [4998 days and 56 minutes ago]

Mon, 13 Aug 2012 08:45:00 GMT

I just installed povray using ports ... All went well, fetched
    povray-3.6.1_6.darwin_11.x86_64.tbz2
But every scene I render just results in a white image, on the screen and saved
to file.
Running OSX 10.7.4 on 1 year old MacBook Pro.

[cjaramillo] Re: povray 3.6 on Snow Leopard / X11 [5028 days 13 hours and 11 minutes ago]

Fri, 13 Jul 2012 20:30:01 GMT

"lainal" <dla### [at] yahoocom> wrote:
> "TSGM" <nomail@nomail> wrote:
> > "lainal" <dla### [at] yahoocom> wrote:
> > > Gents,
> > >
> > > For those interested in, I managed to compile povray 3.6 on Mac OS 10.8 since I
> > > didn't found any working version on the Web (PPC distribution is hitting Rosetta
> > > issues). Hereafter the way I went in 7 steps:
> > > 0 - Download the source code for Linux / Generic and unarchive
> > > 1 - hack all 3 "configure.ac" files to add "foreign" in the parameters of the
> > > macro "AM_INIT_AUTOMAKE"  (some GNU distribution mandatory files are missing)
> > > 2 - create the configure script with autoreconf -i
> > > 3 - edit the top "configure" and add at the 1st active line the following:
> > >       ac_cv_prog_egrep=/usr/bin/egrep
> > > 4 - Configure with:
> > >       CFLAGS="-m32" CXXFLAGS="-m32" \
> > >       ./configure COMPILED_BY="<your mail address>" --with-x
> > > 5 - make
> > > 6 - make install (possibly preceded by su)
> > >
> >
> > Dear Dominique,
> >
> > I too am running OSX Lion and I'm trying to install POVRay. Unfortunately, I'm
> > quite clueless about Unix, so I'm hoping you (or someone else) can clarify your
> > instructions. For example, I'm already lost on step 1 (what configure.ac files?)
> >
> > I would most appreciate it if you could guide me through the installation and
> > compilation process, on the assumption that I know little about using make files
> > or unix in general.
> >
> > Thanks!
>
> OK. I was a little too quick I guess. Sorry for that. The distrib to download is
> at this location:
>
http://www.povray.org/redirect/www.povray.org/ftp/pub/povray/Official/Unix/povray-3.6.tar.bz2
>
> I guess it will go in Download. Then you open a terminal, go to this directory.
>
> 1. Unarchive: "tar xjf povray-3.6.tar.bz2" and go to the source directory
> (povray-3.6.1).
>
> 2. There are three "configure.ac" files in the sources tree:
> ......./configure.ac
> ......./libraries/png/configure.ac
> ......./libraries/zlib/configure.ac
> You have to edit them, find the AM_INIT_AUTOMAKE macros. It should look like:
>
> AM_INIT_AUTOMAKE([1.7 ...])
>
> You have to add "foreign". Then it should look like:
>
> AM_INIT_AUTOMAKE([foreign 1.7 ...])
>
> This for all three files.
>
> 3. Then from the top source directory (povray-3.6.1 currently), you type
> "autoreconf -i" and you wait a little bit. After a while, there's a "configure"
> script which has been created. You have to edit it and add the line as
> explained. For me, after adding the line, it looks like:
>
> ...........
> ## --------------------- ##
> ## M4sh Initialization.  ##
> ## --------------------- ##
>
> ac_cv_prog_egrep=/usr/bin/egrep
>
> # Be more Bourne compatible
> ...........
>
> 4. The rest is straightforward. Still from the top source directory, you type:
>
> CFLAGS="-m32" CXXFLAGS="-m32" ./configure COMPILED_BY="email" --with-x
>
> Then you type "make" and you wait for a while.
>
> If no errors occur, then "make install" and that's it.
>
> Happy install !
>
> - Dominique

I got the following error after trying "sudo make install":
make[2]: *** [install-nobase_povlibSCRIPTS] Error 1
make[1]: *** [install-am] Error 2
make: *** [install-recursive] Error 1

Any hints would be appreciated.

Carlos

[KEBman] How do you compile POV-Ray 3.6 for OS X on Intel... [5046 days 13 hours and 36 minutes ago]

Mon, 25 Jun 2012 20:05:01 GMT

Anyone willing to write a "For Dummies" tutorial on how to compile POV-Ray for
Intel Macs? Preferably for OS X versions 10.5 Leopard trough 10.7 Lion.

I've personally have a humble 2 GHz Core 2 Duo / 2 GB RAM MacBook with OS X
10.5.8. It's a work computer, and thus I can't upgrade it. Also I have GCC
4.2.1. Hope it's enough!

Now, what do I do?

[Drakonis] Re: How to Mac-heads compile images into animati... [5137 days 17 hours and 1 minute ago]

Mon, 26 Mar 2012 16:40:00 GMT

"gregjohn" <pte### [at] yahoocom> wrote:
> Patrick Elliott <sel### [at] npgcablecom> wrote:
>
> Okay, the stupid question here is: all I want to do is turn a stack of bitmaps
> into some kind of widely-usable video. Do the bugs you describe impair this
> function?   What is this process called?-- I remember 10-15 years ago trying to
> BUY an off-the-shelf software to do this, and couldn't find one.

Well, 15+ years ago I too couldn't find anything so I wrote my own, and posted
it as $10 USD Shareware (it was an image-to-QuickTime-movie maker called
"MooVer")... but life-and-OS-tectonics have shifted, and I am now relying
completely on the wonderful solid shareware utility "GraphicConverter":
http://www.lemkesoft.com/

I would highly recommend it, for all sorts of wild-file-format open/convert
tasks.  Its user interface is a little bit funky, ala swiss-army-knife, but I've
been a happy customer for 15 years.  It is how all my POV-Ray animated videos
are done these days.  I output PNGs from (Mega) POV-Ray, then post-convert them
to movie sequences using GraphicConverter.  Then I load everything up into Final
Cut to edit, title, and add my music.

I have heard that Final Cut can assemble a sequence of images directly into
movie frames (but haven't done it yet), so if you already have Final Cut, there
are YouTube tutorials that show how to do it.

Looking forward to your movies!
ttfn,
Eduard

--------------------
POV-Ray Mac Developer - Emeritus
www.schwansongs.com

[gregjohn] Re: How to Mac-heads compile images into animati... [5137 days 17 hours and 21 minutes ago]

Mon, 26 Mar 2012 16:20:01 GMT

Patrick Elliott <sel### [at] npgcablecom> wrote:

>
> For "testing" I think it still OK, but.. if you want to do production...
> obviously it just doesn't cut it anymore, and due to the known encoder
> bug, never really did.

Okay, the stupid question here is: all I want to do is turn a stack of bitmaps
into some kind of widely-usable video. Do the bugs you describe impair this
function?   What is this process called?-- I remember 10-15 years ago trying to
BUY an off-the-shelf software to do this, and couldn't find one.

[Patrick Elliott] Re: How to Mac-heads compile images into animati... [5138 days 6 hours and 57 minutes ago]

Mon, 26 Mar 2012 02:44:10 GMT

On 3/24/2012 6:09 PM, gregjohn wrote:
> I looked at TMPGenc, and wasn't sure if it were still free.
>
>

Well, it is, I think. The problem is it is no longer being properly bug 
fixed, since they have the full on editing suite now. This wouldn't be a 
huge deal, except that they admit that one *huge* bug in the free one is 
that the encoder doesn't actually work correctly, and a) you *will* get 
sound desyncs, and b) it doesn't support the sort of resolutions that 
you might actually want to be using it with (for example, trying to 
produce HD video, or even DVD quality.

I discovered both while trying to convert a real video to a different 
format, wondered why the result both looked like crap, and the sound 
would half a second or more out of sync with the video, and then read, 
in the process of trying to figure it out, that it simply couldn't 
manage what I was asking it to do.

For "testing" I think it still OK, but.. if you want to do production... 
obviously it just doesn't cut it anymore, and due to the known encoder 
bug, never really did.

[gregjohn] How to Mac-heads compile images into animations? [5139 days 8 hours and 31 minutes ago]

Sun, 25 Mar 2012 01:10:00 GMT

I looked at TMPGenc, and wasn't sure if it were still free.

[gregjohn] Re: Best path for povving on the mac? [5143 days 9 hours and 1 minute ago]

Wed, 21 Mar 2012 00:40:01 GMT

Warp <war### [at] tagpovrayorg> wrote:
> gregjohn <pte### [at] yahoocom> wrote:
> > I've got a MacBook Pro.  I'm wondering if the best way to use povray is to
> > either use MegaPov or to install a linux VM-- any tips on the latter?
>
>   There's a mac version of POV-Ray, you know...
>

The official version doesn't install-- gives some kind of PPC error

But Yvo was nice enough to provide an RC4 unofficial that worked for me.

[Bill Pragnell] Re: Best path for povving on the mac? [5144 days 21 hours and 26 minutes ago]

Mon, 19 Mar 2012 12:15:00 GMT

"gregjohn" <pte### [at] yahoocom> wrote:
> I've got a MacBook Pro.  I'm wondering if the best way to use povray is to
> either use MegaPov or to install a linux VM-- any tips on the latter?

I've always used Megapov. If you go with this, see also Yvo's extremely helpful
3.7 builds that utilise the Megapov GUI (posted in povray.beta-test).

Bill

[Warp] Re: Best path for povving on the mac? [5147 days 16 hours and 10 minutes ago]

Fri, 16 Mar 2012 17:30:36 GMT

gregjohn <pte### [at] yahoocom> wrote:
> I've got a MacBook Pro.  I'm wondering if the best way to use povray is to
> either use MegaPov or to install a linux VM-- any tips on the latter?

  There's a mac version of POV-Ray, you know...

  Anyways, if you want to use the generic unix version, there's no need
for any "linux VM" (I don't even know what that is, but I take your word
for it). Mac OS X is a unix and thus has all the necessary unix tools that
should be necessary to compile POV-Ray (although you may need to install
the command-line tools of Xcode, which include gcc 4.2 and the newest
clang, among all the other necessary tools).

  If neither solution is feasible, then you could of course install Linux
as a secondary OS. (I actually don't know if Mac OS's multiboot supports
linux out-of-the-box, but I assume it does.)

-- 
                                                          - Warp

[gregjohn] Best path for povving on the mac? [5147 days 16 hours and 26 minutes ago]

Fri, 16 Mar 2012 17:15:01 GMT

I've got a MacBook Pro.  I'm wondering if the best way to use povray is to
either use MegaPov or to install a linux VM-- any tips on the latter?

[eeeeaaii] Re: building povray on the mac [5162 days 12 hours and 56 minutes ago]

Thu, 1 Mar 2012 20:45:00 GMT

"eeeeaaii" <nomail@nomail> wrote:
> I just wanted to drop a quick note to users who might want to use povray 3.6.1
> on Intel Macs, etc.
>
> Yes, it is possible to modify config files and compile directly from the unix
> sources, as posted here, but I've found a better way is to use Homebrew:
>
> http://mxcl.github.com/homebrew/
>
> Homebrew is a package manager for OSX.  Basically you just install homebrew by
> pasting this into a command prompt:
>
> /usr/bin/ruby -e "$(curl -fsSL https://raw.github.com/gist/323731)"
>
> And then at the prompt type
>
> brew install povray
>
> That's it!  No messing about with config files or doing anything funky.
>
> I'm happy to have found this because I was having some serious problems with
> Apple's new LLVM version of GCC -- it wasn't compiling povray correctly and the
> program was behaving bizarrely.  Homebrew fixed the problem.

Looks like I spoke too soon.  Still having problems with the Homebrew version.
I believe the only way around this is to build it with a different version of
GCC.  I have gcc 4.6 now, I'll try that.

[eeeeaaii] building povray on the mac [5162 days 13 hours and 36 minutes ago]

Thu, 1 Mar 2012 20:05:01 GMT

I just wanted to drop a quick note to users who might want to use povray 3.6.1
on Intel Macs, etc.

Yes, it is possible to modify config files and compile directly from the unix
sources, as posted here, but I've found a better way is to use Homebrew:

http://mxcl.github.com/homebrew/

Homebrew is a package manager for OSX.  Basically you just install homebrew by
pasting this into a command prompt:

/usr/bin/ruby -e "$(curl -fsSL https://raw.github.com/gist/323731)"

And then at the prompt type

brew install povray

That's it!  No messing about with config files or doing anything funky.

I'm happy to have found this because I was having some serious problems with
Apple's new LLVM version of GCC -- it wasn't compiling povray correctly and the
program was behaving bizarrely.  Homebrew fixed the problem.

[eeeeaaii] Re: povray 3.6 on Snow Leopard / X11 [5162 days 14 hours and 46 minutes ago]

Thu, 1 Mar 2012 18:55:01 GMT

"lainal" <dla### [at] yahoocom> wrote:
> Gents,
>
> For those interested in, I managed to compile povray 3.6 on Mac OS 10.8 since I
> didn't found any working version on the Web (PPC distribution is hitting Rosetta
> issues). Hereafter the way I went in 7 steps:
> 0 - Download the source code for Linux / Generic and unarchive
> 1 - hack all 3 "configure.ac" files to add "foreign" in the parameters of the
> macro "AM_INIT_AUTOMAKE"  (some GNU distribution mandatory files are missing)
> 2 - create the configure script with autoreconf -i
> 3 - edit the top "configure" and add at the 1st active line the following:
>       ac_cv_prog_egrep=/usr/bin/egrep
> 4 - Configure with:
>       CFLAGS="-m32" CXXFLAGS="-m32" \
>       ./configure COMPILED_BY="<your mail address>" --with-x
> 5 - make
> 6 - make install (possibly preceded by su)
>
> I also compiled with X disabled without noticing performance differences, so
> better keep it :-)
>
> Example of run:
> $ povray ~/Downloads/povray-3.6.1/scenes/advanced/landscape.pov
> Persistence of Vision(tm) Ray Tracer Version 3.6.1 (g++ 4.2.1 @
>  i686-apple-darwin10.8.0)
> This is an unofficial version compiled by:
>  dla### [at] yahoocom
>  The POV-Ray Team(tm) is not responsible for supporting this version.
> [...]
> Peak memory used:           6299545 bytes
> Total Scene Processing Times
>   Parse Time:    0 hours  0 minutes  1 seconds (1 seconds)
>   Photon Time:   0 hours  0 minutes  0 seconds (0 seconds)
>   Render Time:   0 hours  0 minutes 15 seconds (15 seconds)
>   Total Time:    0 hours  0 minutes 16 seconds (16 seconds)
>
> Enjoy!
>
> - Dominique


I'm having a pretty weird problem.  I am able to compile and run the program,
but it performs weirdly: spheres that are clearly there are never intersected
with the rays from the light sources, etc.  I put in some time putting trace
statements in the code and I have actually narrowed it down to a compiler bug in
the llvm compiler.  Works fine on my mac with the older version of XCode but the
LLVM compiler is translating the C code into something wrong, such that memory
gets trashed and variables get scrambled, etc.  Wondering if anyone else had
this problem.

[eeeeaaii] Re: PovRay 3.7 for Macintosh [5162 days 14 hours and 51 minutes ago]

Thu, 1 Mar 2012 18:50:01 GMT

Thorsten Froehlich <tho### [at] trfde> wrote:
> On 08.02.12 19:45, Kmarinelli wrote:
> > Are there any plans to port PovRay 3.7 to MacOS X 10.7?
>
> You can already compile POV-Ray 3.7 on Mac OS X.
>
>  Thorsten


I am unable to compile it.  I currently get an error when trying to run
configure:

configure: error: cannot find a suitable PNG library

[Thorsten Froehlich] Re: PovRay 3.7 for Macintosh [5184 days 14 hours and 48 minutes ago]

Wed, 8 Feb 2012 18:52:53 GMT

On 08.02.12 19:45, Kmarinelli wrote:
> Are there any plans to port PovRay 3.7 to MacOS X 10.7?

You can already compile POV-Ray 3.7 on Mac OS X.

	Thorsten

[Kmarinelli] PovRay 3.7 for Macintosh [5184 days 14 hours and 51 minutes ago]

Wed, 8 Feb 2012 18:50:00 GMT

Are there any plans to port PovRay 3.7 to MacOS X 10.7?

Thanks.

[Warp] Re: povray 3.6 on Snow Leopard / X11 [5232 days 16 hours and 12 minutes ago]

Thu, 22 Dec 2011 17:29:18 GMT

atirtil <nomail@nomail> wrote:
> Making install in unix
> /bin/sh ../config/mkinstalldirs /usr/local/bin
>   /usr/bin/install -c povray /usr/local/bin/povray
> install: /usr/local/bin/povray: Permission denied
> make[2]: *** [install-binPROGRAMS] Error 1
> make[1]: *** [install-am] Error 2
> make: *** [install-recursive] Error 1

  If "make" succeeded, then you don't have to proceed with "make install".
The executable will have been built already (I don't remember if it's in
the same directory as the Makefile or in one of the subdirectories). You
can run it directly, if you want.

  (Note that if you want to define some default settings and the path
to the standard include files, you'll have to manually create a
.povray/3.7/povray.ini file in your home directory.)

-- 
                                                          - Warp

[atirtil] Re: povray 3.6 on Snow Leopard / X11 [5233 days 13 hours and 16 minutes ago]

Wed, 21 Dec 2011 20:25:00 GMT

Dear Dominique,

I tried out your last reply. Everything went well until the " make " process. I
had this error :
""""""""""""""""""""""""""""""""""""""""""""""""""""""""
if [ nodso != nodso ]; then \
     make - nodso; \
 else \
     true; \
 fi
make[2]: Nothing to be done for `all-am'.
Making install in source
Making install in base
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
Making install in frontend
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
Making install in unix
/bin/sh ../config/mkinstalldirs /usr/local/bin
  /usr/bin/install -c povray /usr/local/bin/povray
install: /usr/local/bin/povray: Permission denied
make[2]: *** [install-binPROGRAMS] Error 1
make[1]: *** [install-am] Error 2
make: *** [install-recursive] Error 1
"""""""""""""""""""""""""""""""""""""""""""""""""""""""
I would really appreciate your help,

thank you



"lainal" <dla### [at] yahoocom> wrote:
> "TSGM" <nomail@nomail> wrote:
> > "lainal" <dla### [at] yahoocom> wrote:
> > > Gents,
> > >
> > > For those interested in, I managed to compile povray 3.6 on Mac OS 10.8 since I
> > > didn't found any working version on the Web (PPC distribution is hitting Rosetta
> > > issues). Hereafter the way I went in 7 steps:
> > > 0 - Download the source code for Linux / Generic and unarchive
> > > 1 - hack all 3 "configure.ac" files to add "foreign" in the parameters of the
> > > macro "AM_INIT_AUTOMAKE"  (some GNU distribution mandatory files are missing)
> > > 2 - create the configure script with autoreconf -i
> > > 3 - edit the top "configure" and add at the 1st active line the following:
> > >       ac_cv_prog_egrep=/usr/bin/egrep
> > > 4 - Configure with:
> > >       CFLAGS="-m32" CXXFLAGS="-m32" \
> > >       ./configure COMPILED_BY="<your mail address>" --with-x
> > > 5 - make
> > > 6 - make install (possibly preceded by su)
> > >
> >
> > Dear Dominique,
> >
> > I too am running OSX Lion and I'm trying to install POVRay. Unfortunately, I'm
> > quite clueless about Unix, so I'm hoping you (or someone else) can clarify your
> > instructions. For example, I'm already lost on step 1 (what configure.ac files?)
> >
> > I would most appreciate it if you could guide me through the installation and
> > compilation process, on the assumption that I know little about using make files
> > or unix in general.
> >
> > Thanks!
>
> OK. I was a little too quick I guess. Sorry for that. The distrib to download is
> at this location:
>
http://www.povray.org/redirect/www.povray.org/ftp/pub/povray/Official/Unix/povray-3.6.tar.bz2
>
> I guess it will go in Download. Then you open a terminal, go to this directory.
>
> 1. Unarchive: "tar xjf povray-3.6.tar.bz2" and go to the source directory
> (povray-3.6.1).
>
> 2. There are three "configure.ac" files in the sources tree:
> ......./configure.ac
> ......./libraries/png/configure.ac
> ......./libraries/zlib/configure.ac
> You have to edit them, find the AM_INIT_AUTOMAKE macros. It should look like:
>
> AM_INIT_AUTOMAKE([1.7 ...])
>
> You have to add "foreign". Then it should look like:
>
> AM_INIT_AUTOMAKE([foreign 1.7 ...])
>
> This for all three files.
>
> 3. Then from the top source directory (povray-3.6.1 currently), you type
> "autoreconf -i" and you wait a little bit. After a while, there's a "configure"
> script which has been created. You have to edit it and add the line as
> explained. For me, after adding the line, it looks like:
>
> ...........
> ## --------------------- ##
> ## M4sh Initialization.  ##
> ## --------------------- ##
>
> ac_cv_prog_egrep=/usr/bin/egrep
>
> # Be more Bourne compatible
> ...........
>
> 4. The rest is straightforward. Still from the top source directory, you type:
>
> CFLAGS="-m32" CXXFLAGS="-m32" ./configure COMPILED_BY="email" --with-x
>
> Then you type "make" and you wait for a while.
>
> If no errors occur, then "make install" and that's it.
>
> Happy install !
>
> - Dominique

[lainal] Re: povray 3.6 on Snow Leopard / X11 [5290 days 3 hours and 6 minutes ago]

Wed, 26 Oct 2011 06:35:00 GMT

"TSGM" <nomail@nomail> wrote:
> "lainal" <dla### [at] yahoocom> wrote:
> > Gents,
> >
> > For those interested in, I managed to compile povray 3.6 on Mac OS 10.8 since I
> > didn't found any working version on the Web (PPC distribution is hitting Rosetta
> > issues). Hereafter the way I went in 7 steps:
> > 0 - Download the source code for Linux / Generic and unarchive
> > 1 - hack all 3 "configure.ac" files to add "foreign" in the parameters of the
> > macro "AM_INIT_AUTOMAKE"  (some GNU distribution mandatory files are missing)
> > 2 - create the configure script with autoreconf -i
> > 3 - edit the top "configure" and add at the 1st active line the following:
> >       ac_cv_prog_egrep=/usr/bin/egrep
> > 4 - Configure with:
> >       CFLAGS="-m32" CXXFLAGS="-m32" \
> >       ./configure COMPILED_BY="<your mail address>" --with-x
> > 5 - make
> > 6 - make install (possibly preceded by su)
> >
>
> Dear Dominique,
>
> I too am running OSX Lion and I'm trying to install POVRay. Unfortunately, I'm
> quite clueless about Unix, so I'm hoping you (or someone else) can clarify your
> instructions. For example, I'm already lost on step 1 (what configure.ac files?)
>
> I would most appreciate it if you could guide me through the installation and
> compilation process, on the assumption that I know little about using make files
> or unix in general.
>
> Thanks!

OK. I was a little too quick I guess. Sorry for that. The distrib to download is
at this location:
http://www.povray.org/redirect/www.povray.org/ftp/pub/povray/Official/Unix/povray-3.6.tar.bz2

I guess it will go in Download. Then you open a terminal, go to this directory.

1. Unarchive: "tar xjf povray-3.6.tar.bz2" and go to the source directory
(povray-3.6.1).

2. There are three "configure.ac" files in the sources tree:
......./configure.ac
......./libraries/png/configure.ac
......./libraries/zlib/configure.ac
You have to edit them, find the AM_INIT_AUTOMAKE macros. It should look like:

AM_INIT_AUTOMAKE([1.7 ...])

You have to add "foreign". Then it should look like:

AM_INIT_AUTOMAKE([foreign 1.7 ...])

This for all three files.

3. Then from the top source directory (povray-3.6.1 currently), you type
"autoreconf -i" and you wait a little bit. After a while, there's a "configure"
script which has been created. You have to edit it and add the line as
explained. For me, after adding the line, it looks like:

...........
## --------------------- ##
## M4sh Initialization.  ##
## --------------------- ##

ac_cv_prog_egrep=/usr/bin/egrep

# Be more Bourne compatible
...........

4. The rest is straightforward. Still from the top source directory, you type:

CFLAGS="-m32" CXXFLAGS="-m32" ./configure COMPILED_BY="email" --with-x

Then you type "make" and you wait for a while.

If no errors occur, then "make install" and that's it.

Happy install !

- Dominique

[TSGM] Re: povray 3.6 on Snow Leopard / X11 [5303 days 8 hours and 41 minutes ago]

Thu, 13 Oct 2011 01:00:01 GMT

"lainal" <dla### [at] yahoocom> wrote:
> Gents,
>
> For those interested in, I managed to compile povray 3.6 on Mac OS 10.8 since I
> didn't found any working version on the Web (PPC distribution is hitting Rosetta
> issues). Hereafter the way I went in 7 steps:
> 0 - Download the source code for Linux / Generic and unarchive
> 1 - hack all 3 "configure.ac" files to add "foreign" in the parameters of the
> macro "AM_INIT_AUTOMAKE"  (some GNU distribution mandatory files are missing)
> 2 - create the configure script with autoreconf -i
> 3 - edit the top "configure" and add at the 1st active line the following:
>       ac_cv_prog_egrep=/usr/bin/egrep
> 4 - Configure with:
>       CFLAGS="-m32" CXXFLAGS="-m32" \
>       ./configure COMPILED_BY="<your mail address>" --with-x
> 5 - make
> 6 - make install (possibly preceded by su)
>

Dear Dominique,

I too am running OSX Lion and I'm trying to install POVRay. Unfortunately, I'm
quite clueless about Unix, so I'm hoping you (or someone else) can clarify your
instructions. For example, I'm already lost on step 1 (what configure.ac files?)

I would most appreciate it if you could guide me through the installation and
compilation process, on the assumption that I know little about using make files
or unix in general.

Thanks!

[lainal] povray 3.6 on Snow Leopard / X11 [5362 days 9 hours and 16 minutes ago]

Mon, 15 Aug 2011 00:25:00 GMT

Gents,

For those interested in, I managed to compile povray 3.6 on Mac OS 10.8 since I
didn't found any working version on the Web (PPC distribution is hitting Rosetta
issues). Hereafter the way I went in 7 steps:
0 - Download the source code for Linux / Generic and unarchive
1 - hack all 3 "configure.ac" files to add "foreign" in the parameters of the
macro "AM_INIT_AUTOMAKE"  (some GNU distribution mandatory files are missing)
2 - create the configure script with autoreconf -i
3 - edit the top "configure" and add at the 1st active line the following:
      ac_cv_prog_egrep=/usr/bin/egrep
4 - Configure with:
      CFLAGS="-m32" CXXFLAGS="-m32" \
      ./configure COMPILED_BY="<your mail address>" --with-x
5 - make
6 - make install (possibly preceded by su)

I also compiled with X disabled without noticing performance differences, so
better keep it :-)

Example of run:
$ povray ~/Downloads/povray-3.6.1/scenes/advanced/landscape.pov
Persistence of Vision(tm) Ray Tracer Version 3.6.1 (g++ 4.2.1 @
 i686-apple-darwin10.8.0)
This is an unofficial version compiled by:
 dla### [at] yahoocom
 The POV-Ray Team(tm) is not responsible for supporting this version.
[...]
Peak memory used:           6299545 bytes
Total Scene Processing Times
  Parse Time:    0 hours  0 minutes  1 seconds (1 seconds)
  Photon Time:   0 hours  0 minutes  0 seconds (0 seconds)
  Render Time:   0 hours  0 minutes 15 seconds (15 seconds)
  Total Time:    0 hours  0 minutes 16 seconds (16 seconds)

Enjoy!

- Dominique

[Yvo Smellenbergh] Re: Mega-Pov on OSX 10.7 Lion [5370 days and 32 minutes ago]

Sun, 7 Aug 2011 09:08:54 GMT

"CAD-Andi" <nomail@nomail> wrote:

> Did anyone try out Mega-Pov by Yvo Smellenbergh on OSX Lion?
> I can't risk to ruin my running povray (Megapov) on my iMac by 
> installing Lion.
> Anyone with good news?

MegaPOV 1.2.1 r3 universal runs fine on Lion.

Yvo

-- 
-----------------------------------
MegaPOV at:  http://megapov.inetart.net
MacMegaPOV at:  http://users.skynet.be/smellenbergh
E-mail: yvo(DOT)s(AT)gmx.net

[CAD-Andi] Mega-Pov on OSX 10.7 Lion [5370 days 15 hours and 36 minutes ago]

Sat, 6 Aug 2011 18:05:01 GMT

Did anyone try out Mega-Pov by Yvo Smellenbergh on OSX Lion?
I can't risk to ruin my running povray (Megapov) on my iMac by installing Lion.
Anyone with good news?

[erfurt2809] Re: Configuring POVray for use with Eagle 3D [5597 days and 56 minutes ago]

Thu, 23 Dec 2010 08:45:01 GMT

"erfurt2809" <ste### [at] webde> wrote:
> "societyofrobots" <nomail@nomail> wrote:
> > Probably a year too late for you, but this is a tutorial I wrote up:
> > http://www.societyofrobots.com/electronics_Eagle3D_tutorial.shtml
> >
> > Tiger <nos### [at] nospam> wrote:
> > > I'm a complete newbie when it comes to POVray and need some help
> > > configuring and using it.
> > > I'm on a Powerbook G4 (1.67GHz) running MacOS 10.4.10.
> > > I've installed POVray 3.6.
> > >
> > > I barely know what POVray is (excuse my ignorance), but have an interest
> > > in it because of "Eagle 3D" which is a script that produces a .POV file
> > > out of an electronic circuit board design.
> > > The POV file is then (as far as I know) run through POVray to create a
> > > 3-dimensional drawing of the actual circuit board.
> > > Check out this website for more info about Eagle 3D as well as pictures:
> > > http://www.matwei.de/doku.php?id=en:eagle3d:eagle3d
> > >
> > > What I've done so far is download the installation files from the above
> > > site, the direct file-link being:
> > >
http://www.matwei.de/lib/exe/fetch.php?id=en%3Aeagle3d%3Aeagle3d&cache=cache&media=files:eagle3d:eagle3d_1_05_271
12
> 00
> > 6.zip
> > >
> > > And then I placed the ULP (script file) where my electronic design
> > > application; Eagle (http://www.cadsoft.de/) can find it.
> > >
> > > However, when it comes to POVray and how to treat the Eagle-generated
> > > .POV file I'm totally lost.
> > > I've so far double-clicked the POV file which loaded it into POVray, and
> > > following that I assumed that I should just go to the "Render" menu and
> > > choose to render this file. Well, I seemed to have gotten several error
> > > messages.
> > > Upon contacting the author of Eagle 3D I was told that I need to tell
> > > POVray the location of a specific folder which came with Eagle 3D.
> > > However, I don't see any way of configuring this in POVray.
> > >
> > > A folder named "POVray" comes with Eagle 3D which contains the following
> > > files:
> > >
> > > total 1712
> > > -rwx------   1   21456 Nov 27  2006 alphalcd.ttf
> > > -rw-r--r--   1   39231 Nov 27  2006 cap.inc
> > > -rw-r--r--   1   13141 Nov 27  2006 capwima.inc
> > > -rw-r--r--   1      78 Nov 27  2006 col.inc
> > > -rw-r--r--   1  210961 Nov 27  2006 connector.inc
> > > -rw-r--r--   1   65218 Nov 27  2006 diode.inc
> > > -rwx------   1   54344 Nov 27  2006 eagle3d.ttf
> > > -rw-r--r--   1   59350 Nov 27  2006 ic.inc
> > > -rw-r--r--   1   14237 Nov 27  2006 qfp.inc
> > > -rw-r--r--   1   81236 Nov 27  2006 resistor.inc
> > > -rw-r--r--   1   16955 Nov 27  2006 socket.inc
> > > -rw-r--r--   1   95898 Nov 27  2006 special.inc
> > > -rw-r--r--   1   48831 Nov 27  2006 switch.inc
> > > -rwx------   1     223 Nov 27  2006 tex_elko.png
> > > -rwx------   1    3039 Nov 27  2006 tex_elko_axial.png
> > > -rw-r--r--   1   46472 Nov 27  2006 tools.inc
> > > -rw-r--r--   1   33623 Nov 27  2006 trafo.inc
> > > -rw-r--r--   1   31581 Nov 27  2006 transistor.inc
> > > -rw-r--r--   1       0 Nov 27  2006 user.inc
> > >
> > >
> > > I tried placing all those files in POVray's "include" folder, but I'm
> > > still getting error messages when I try to render the POV file, so I
> > > assume I have to place them somewhere else or I'm not understanding how
> > > to use POVray properly.
> > > Here are those error messages:
> > >
> > >
> > > POV-Ray 3.6 for Mac OS Frontend Build 197
> > > Copyright © 1991-2003 Persistence of Vision Team™
> > > Copyright © 2003-2004 Persistence of Vision Raytracer Pty. Ltd.
> > > Persistence of Vision(tm) Ray Tracer Version 3.6.1 (Mac CodeWarrior)
> > > This is an official version prepared by the POV-Ray Team. See the
> > >   documentation on how to contact the authors or visit us on the
> > >   internet at http://www.povray.org/.
> > > POV-Ray is based on DKBTrace 2.12 by David K. Buck & Aaron A. Collins
> > > Copyright 1991-2003 Persistence of Vision Team
> > > Copyright 2003-2004 Persistence of Vision Raytracer Pty. Ltd.
> > > Parsing Options
> > >    Input file: Internal_drive:Users:Tiger:Desktop:test.pov (compatible
> > > to version 3.60)
> > >    Remove bounds........On   Split unions.........On
> > >    Library paths:
> > > Output Options
> > >    Image resolution 160 by 120 (rows 0 to 120, columns 0 to 160).
> > >    Output file: test.pict, 24 bpp (system format)
> > >    Graphic display.....On  (gamma:  1.8)
> > >    Mosaic preview.......Off
> > >    CPU usage histogram.Off
> > >    Continued trace......Off
> > > Tracing Options
> > >    Quality:  9
> > >    Bounding boxes......On  Bounding threshold: 1
> > >    Light Buffer.........On   Vista Buffer.........On   Draw Vista
> > > Buffer....Off
> > >    Antialiasing........Off
> > >    Radiosity............Off
> > > Animation Options
> > >    Clock value....   0.000  (Animation off)
> > > Possible Parse Error: Could not find file 'tools.inc'
> > >
> > > File test.pov line 117
> > > Parse Error: Cannot open include file tools.inc.
> > >
> > > File test.pov line 117
> > > Parse Warning: Check that the file is in a directory specifed with a +L
> > > switch or 'Library_Path='
> > > .INI item. Standard include files are in the include directory or
> > > folder. Please read your
> > > documentation carefully.
> > >
> > > File test.pov line 117
> > > Total Scene Processing Times
> > >    Parse Time:    0 hours  0 minutes  0 seconds (0 seconds)
> > >    Photon Time:   0 hours  0 minutes  0 seconds (0 seconds)
> > >    Render Time:   0 hours  0 minutes  0 seconds (0 seconds)
> > >    Total Time:    0 hours  0 minutes  0 seconds (0 seconds)
>
> Hallo
>
> unfortunately also with my Setup:
>
> Intel Xeon 2.66 Quad Core (2009 Model) 8GB Ram MacOs 10.6.5,
>
> there are some Problems as follow:
>
> "Possible Parse Error: Cannot find file 'tools.inc', even after trying to append
> file type extension.
>
> line 117: Parse Error: Cannot open include file tools.inc."
>
>
> with the Macintosh Version of PovRay 3.7 unofficial beta39;
>
> ...pov file was created with Eagle 3D v.1.0.5 and Eagle 5.11.0
>
> no change still no rendering with Eagle 3D(of the Mac Platform)
>
> Id would be great, if somebody has any Idea what i do wrong.
>
> Thank`s
>
> Steffen

..........ok now i puted all .inc - Files on the right place and sayed this
the Programm in the Files & Path Preferences and it going on, but
now i get this:

"POV-Ray 3.7 64bit Unofficial/include/glass_old.inc" line 79: Parse Error:
Expected '=', ,  found instead

Render failed"

by the way in both Versions MegPov and the PovRay 3.7 Unofficial the same
Effect.

what should i do? The = was already there.

Steffen

[erfurt2809] Re: Configuring POVray for use with Eagle 3D [5597 days 21 hours and 26 minutes ago]

Wed, 22 Dec 2010 12:15:01 GMT

"societyofrobots" <nomail@nomail> wrote:
> Probably a year too late for you, but this is a tutorial I wrote up:
> http://www.societyofrobots.com/electronics_Eagle3D_tutorial.shtml
>
> Tiger <nos### [at] nospam> wrote:
> > I'm a complete newbie when it comes to POVray and need some help
> > configuring and using it.
> > I'm on a Powerbook G4 (1.67GHz) running MacOS 10.4.10.
> > I've installed POVray 3.6.
> >
> > I barely know what POVray is (excuse my ignorance), but have an interest
> > in it because of "Eagle 3D" which is a script that produces a .POV file
> > out of an electronic circuit board design.
> > The POV file is then (as far as I know) run through POVray to create a
> > 3-dimensional drawing of the actual circuit board.
> > Check out this website for more info about Eagle 3D as well as pictures:
> > http://www.matwei.de/doku.php?id=en:eagle3d:eagle3d
> >
> > What I've done so far is download the installation files from the above
> > site, the direct file-link being:
> >
http://www.matwei.de/lib/exe/fetch.php?id=en%3Aeagle3d%3Aeagle3d&cache=cache&media=files:eagle3d:eagle3d_1_05_27112
00
> 6.zip
> >
> > And then I placed the ULP (script file) where my electronic design
> > application; Eagle (http://www.cadsoft.de/) can find it.
> >
> > However, when it comes to POVray and how to treat the Eagle-generated
> > .POV file I'm totally lost.
> > I've so far double-clicked the POV file which loaded it into POVray, and
> > following that I assumed that I should just go to the "Render" menu and
> > choose to render this file. Well, I seemed to have gotten several error
> > messages.
> > Upon contacting the author of Eagle 3D I was told that I need to tell
> > POVray the location of a specific folder which came with Eagle 3D.
> > However, I don't see any way of configuring this in POVray.
> >
> > A folder named "POVray" comes with Eagle 3D which contains the following
> > files:
> >
> > total 1712
> > -rwx------   1   21456 Nov 27  2006 alphalcd.ttf
> > -rw-r--r--   1   39231 Nov 27  2006 cap.inc
> > -rw-r--r--   1   13141 Nov 27  2006 capwima.inc
> > -rw-r--r--   1      78 Nov 27  2006 col.inc
> > -rw-r--r--   1  210961 Nov 27  2006 connector.inc
> > -rw-r--r--   1   65218 Nov 27  2006 diode.inc
> > -rwx------   1   54344 Nov 27  2006 eagle3d.ttf
> > -rw-r--r--   1   59350 Nov 27  2006 ic.inc
> > -rw-r--r--   1   14237 Nov 27  2006 qfp.inc
> > -rw-r--r--   1   81236 Nov 27  2006 resistor.inc
> > -rw-r--r--   1   16955 Nov 27  2006 socket.inc
> > -rw-r--r--   1   95898 Nov 27  2006 special.inc
> > -rw-r--r--   1   48831 Nov 27  2006 switch.inc
> > -rwx------   1     223 Nov 27  2006 tex_elko.png
> > -rwx------   1    3039 Nov 27  2006 tex_elko_axial.png
> > -rw-r--r--   1   46472 Nov 27  2006 tools.inc
> > -rw-r--r--   1   33623 Nov 27  2006 trafo.inc
> > -rw-r--r--   1   31581 Nov 27  2006 transistor.inc
> > -rw-r--r--   1       0 Nov 27  2006 user.inc
> >
> >
> > I tried placing all those files in POVray's "include" folder, but I'm
> > still getting error messages when I try to render the POV file, so I
> > assume I have to place them somewhere else or I'm not understanding how
> > to use POVray properly.
> > Here are those error messages:
> >
> >
> > POV-Ray 3.6 for Mac OS Frontend Build 197
> > Copyright © 1991-2003 Persistence of Vision Team™
> > Copyright © 2003-2004 Persistence of Vision Raytracer Pty. Ltd.
> > Persistence of Vision(tm) Ray Tracer Version 3.6.1 (Mac CodeWarrior)
> > This is an official version prepared by the POV-Ray Team. See the
> >   documentation on how to contact the authors or visit us on the
> >   internet at http://www.povray.org/.
> > POV-Ray is based on DKBTrace 2.12 by David K. Buck & Aaron A. Collins
> > Copyright 1991-2003 Persistence of Vision Team
> > Copyright 2003-2004 Persistence of Vision Raytracer Pty. Ltd.
> > Parsing Options
> >    Input file: Internal_drive:Users:Tiger:Desktop:test.pov (compatible
> > to version 3.60)
> >    Remove bounds........On   Split unions.........On
> >    Library paths:
> > Output Options
> >    Image resolution 160 by 120 (rows 0 to 120, columns 0 to 160).
> >    Output file: test.pict, 24 bpp (system format)
> >    Graphic display.....On  (gamma:  1.8)
> >    Mosaic preview.......Off
> >    CPU usage histogram.Off
> >    Continued trace......Off
> > Tracing Options
> >    Quality:  9
> >    Bounding boxes......On  Bounding threshold: 1
> >    Light Buffer.........On   Vista Buffer.........On   Draw Vista
> > Buffer....Off
> >    Antialiasing........Off
> >    Radiosity............Off
> > Animation Options
> >    Clock value....   0.000  (Animation off)
> > Possible Parse Error: Could not find file 'tools.inc'
> >
> > File test.pov line 117
> > Parse Error: Cannot open include file tools.inc.
> >
> > File test.pov line 117
> > Parse Warning: Check that the file is in a directory specifed with a +L
> > switch or 'Library_Path='
> > .INI item. Standard include files are in the include directory or
> > folder. Please read your
> > documentation carefully.
> >
> > File test.pov line 117
> > Total Scene Processing Times
> >    Parse Time:    0 hours  0 minutes  0 seconds (0 seconds)
> >    Photon Time:   0 hours  0 minutes  0 seconds (0 seconds)
> >    Render Time:   0 hours  0 minutes  0 seconds (0 seconds)
> >    Total Time:    0 hours  0 minutes  0 seconds (0 seconds)

Hallo

unfortunately also with my Setup:

Intel Xeon 2.66 Quad Core (2009 Model) 8GB Ram MacOs 10.6.5,

there are some Problems as follow:

"Possible Parse Error: Cannot find file 'tools.inc', even after trying to append
file type extension.

line 117: Parse Error: Cannot open include file tools.inc."


with the Macintosh Version of PovRay 3.7 unofficial beta39;

...pov file was created with Eagle 3D v.1.0.5 and Eagle 5.11.0

no change still no rendering with Eagle 3D(of the Mac Platform)

Id would be great, if somebody has any Idea what i do wrong.

Thank`s

Steffen

[scirender] Re: Multiple POV-Ray instances possible on Mac? [5631 days 6 hours and 6 minutes ago]

Fri, 19 Nov 2010 03:35:01 GMT

I've been pondering the same question myself, and have just found this thread-
the suggested solution does the job nicely!
 Most grateful for the advice, as it looks as though it'll cut the rendering
time for a 3D project quite significantly.
 Just doing some timing tests now- looking forward to seeing what the results
will be.

[Mayoneez] Re: mac multicore rendering/distributed rendering [5867 days 23 hours and 41 minutes ago]

Sat, 27 Mar 2010 10:00:00 GMT

I'm also interested in hearing any news on this.

[Oren] mac multicore rendering/distributed rendering [5869 days 20 hours and 26 minutes ago]

Thu, 25 Mar 2010 13:15:01 GMT

Hello,

anyone had success with Mac Megapov or povray multicore rendering or with
distributed rendering of a scene file across many Macs? Any tips to share

Thanks in advance... Oren

[rroddy] Re: installing on mac [5876 days 5 hours and 1 minute ago]

Fri, 19 Mar 2010 04:40:01 GMT

I have a vanilla command line Unix build of POV-Ray 3.6.1 running on a MacBook
Pro v. 10.5.8.  I should add that I have a fairly complete GNU gcc 4.4.3
compiler with GNU make running under $HOME which I used to build it.  I also
have the Apple developer tools installed, which I assume would build it also but
can't guarantee since I didn't go that route.  I had to tweak the
$HOME/.povray/3.6/povray.conf and $HOME/.povray/3.6/povray.ini files, but
allscene.sh and allanim.sh ran clean.

That's as far as I've gotten so far.  As usual, caveat lector and YMMV.

[rere-911] Re: Find and Replace [5886 days 21 hours and 31 minutes ago]

Mon, 8 Mar 2010 12:10:00 GMT

"Greg Williams" <gre### [at] comcastnet> wrote:
> What are the limits of the Search/Replace command on the Mac platform?
>
> I have a file that contains several thousand instances of: rgbt <number, number,
> number, 1.000000>  I need to replace all of those 1.000000  t-values with  0.
> (The source of the 1.000000 values is the modeling program, DS Visualizer, and
> I can't fix it. It's a known bug in Visualizer.)
>
> I can replace a small set of them, say on the order of 25 or so with
> Search/Replace All, Selection only.
>
> However, if I select all of the entire file, or even more than a couple of
> hundred cases, and do the same Search/Replace All, Selection only, I get the
> Mac spinning color wheel of the death, and the program locks up. I have to
> Force Quit POV Ray.
>
> This isn't a problem on the Windows version.
>
> Is this a known problem for Mac 3.6.0 build197?
>
> Thanks,
>
> Greg









There are no limits, it will just take really long if you have a very huge
file. POV-Ray does not lock up, it is just taking very long to perform the
find and replace, especially if the file is several megabytes in size.

[Anthony D Baye] Re: installing on mac [5909 days 13 hours and 16 minutes ago]

Sat, 13 Feb 2010 20:25:00 GMT

Are you running 3.7 beta?  I don't think earlier versions work on Intel
machines...  (I could be wrong)  try downloading the mac megapov compile
of the betas, they should be linked from p.general

news://news.povray.org:119/1jc9std.4nvzs31prylpyN%yvo.s@cancel_This_gmx.net

Or you could try compiling the Unix binaries yourself... I've not had
much luck with that, personally, but it must be possible.

A.D.B.

gsc_1 wrote:
> Hi,
> I have a MacBook and am running Mac OS X 10.6.1.  I downloaded povray, and when
> I try to open it, it says it quit unexpectedly and I get the information below.
> Does anyone know how to fix this?
> Thanks!
> 
> 
> 
> Process:         translate [659]
> Path:            /POV-Ray 3.6/POV-Ray Mac 3.6 Folder/POV-Ray Mac 3.6
> Identifier:      translate
> Version:         ??? (56721408)
> Code Type:       PPC (Translated)
> Parent Process:  launchd [83]
> 
> Date/Time:       2010-02-12 14:44:14.031 -0800
> OS Version:      Mac OS X 10.6.1 (10A2047)
> Report Version:  6
> 
> Interval Since Last Report:          287586 sec
> Crashes Since Last Report:           11
> Per-App Crashes Since Last Report:   7
> Anonymous UUID:                      E22E83E7-1D9F-4CF8-A1F0-60FB781D7665
> 
> Exception Type:  EXC_BAD_ACCESS (SIGBUS)
> Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000004
> Crashed Thread:  0  Dispatch queue: com.apple.main-thread
> 
> Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
> 0   LaunchCFMApp                   0xb80c5e94 0xb8000000 + 810644
> 1   LaunchCFMApp                   0xb80c01bb 0xb8000000 + 786875
> 2   LaunchCFMApp                   0xb80dda6c 0xb8000000 + 907884
> 3   LaunchCFMApp                   0xb8145da1 spin_lock_wrapper + 3973
> 4   LaunchCFMApp                   0xb801d03b 0xb8000000 + 118843
> 
> Thread 1:
> 0   libSystem.B.dylib              0x800c57da mach_msg_trap + 10
> 1   libSystem.B.dylib              0x800c5f47 mach_msg + 68
> 2   LaunchCFMApp                   0xb819448f CallPPCFunctionAtAddressInt +
> 206155
> 3   libSystem.B.dylib              0x800f2f39 _pthread_start + 345
> 4   libSystem.B.dylib              0x800f2dbe thread_start + 34
> 
> Thread 2:
> 0   LaunchCFMApp                   0xb815ae44 spin_lock_wrapper + 90152
> 1   LaunchCFMApp                   0xb8179d27 CallPPCFunctionAtAddressInt +
> 97763
> 2   LaunchCFMApp                   0xb80c6c97 0xb8000000 + 814231
> 3   LaunchCFMApp                   0xb80c01bb 0xb8000000 + 786875
> 4   LaunchCFMApp                   0xb80dda6c 0xb8000000 + 907884
> 5   LaunchCFMApp                   0xb814551b spin_lock_wrapper + 1791
> 6   LaunchCFMApp                   0xb801d03b 0xb8000000 + 118843
> 
> Thread 3:
> 0   LaunchCFMApp                   0xb815aa83 spin_lock_wrapper + 89191
> 1   LaunchCFMApp                   0xb8176f29 CallPPCFunctionAtAddressInt +
> 85989
> 2   LaunchCFMApp                   0xb80c6c97 0xb8000000 + 814231
> 3   LaunchCFMApp                   0xb80c01bb 0xb8000000 + 786875
> 4   LaunchCFMApp                   0xb80dda6c 0xb8000000 + 907884
> 5   LaunchCFMApp                   0xb814551b spin_lock_wrapper + 1791
> 6   LaunchCFMApp                   0xb801d03b 0xb8000000 + 118843
> 
> Thread 4:
> 0   LaunchCFMApp                   0xb815aa83 spin_lock_wrapper + 89191
> 1   LaunchCFMApp                   0xb8176f29 CallPPCFunctionAtAddressInt +
> 85989
> 2   LaunchCFMApp                   0xb80c6c97 0xb8000000 + 814231
> 3   LaunchCFMApp                   0xb80c01bb 0xb8000000 + 786875
> 4   LaunchCFMApp                   0xb80dda6c 0xb8000000 + 907884
> 5   LaunchCFMApp                   0xb814551b spin_lock_wrapper + 1791
> 6   LaunchCFMApp                   0xb801d03b 0xb8000000 + 118843
> 
> Thread 5:
> 0   LaunchCFMApp                   0xb815ad54 spin_lock_wrapper + 89912
> 1   LaunchCFMApp                   0xb817040c CallPPCFunctionAtAddressInt +
> 58568
> 2   LaunchCFMApp                   0xb80c6c97 0xb8000000 + 814231
> 3   LaunchCFMApp                   0xb80c01bb 0xb8000000 + 786875
> 4   LaunchCFMApp                   0xb80dda6c 0xb8000000 + 907884
> 5   LaunchCFMApp                   0xb8145da1 spin_lock_wrapper + 3973
> 6   LaunchCFMApp                   0xb801d03b 0xb8000000 + 118843
> 
> Thread 6:
> 0   LaunchCFMApp                   0xb815ae87 spin_lock_wrapper + 90219
> 1   LaunchCFMApp                   0xb8174ac7 CallPPCFunctionAtAddressInt +
> 76675
> 2   LaunchCFMApp                   0xb80c6c97 0xb8000000 + 814231
> 3   LaunchCFMApp                   0xb80c01bb 0xb8000000 + 786875
> 4   LaunchCFMApp                   0xb80dda6c 0xb8000000 + 907884
> 5   LaunchCFMApp                   0xb8145da1 spin_lock_wrapper + 3973
> 6   LaunchCFMApp                   0xb801d03b 0xb8000000 + 118843
> 
> Thread 7:
> 0   LaunchCFMApp                   0xb815ac0f spin_lock_wrapper + 89587
> 1   LaunchCFMApp                   0xb818c47b CallPPCFunctionAtAddressInt +
> 173367
> 2   LaunchCFMApp                   0xb818ef7c CallPPCFunctionAtAddressInt +
> 184376
> 3   LaunchCFMApp                   0xb80e8a4f 0xb8000000 + 952911
> 4   ???                            0x816c4302 0 + 2171355906
> 
> Thread 8:
> 0   ???                            0x816e839a 0 + 2171503514
> 
> Thread 0 crashed with X86 Thread State (32-bit):
>   eax: 0x00000004  ebx: 0xb80c5e6c  ecx: 0x00000000  edx: 0x00000003
>   edi: 0x00000004  esi: 0x804037f0  ebp: 0xb7fffa08  esp: 0xb7fff9d0
>    ss: 0x0000001f  efl: 0x00010206  eip: 0xb80c5e94   cs: 0x00000017
>    ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
>   cr2: 0x00000004
> 
> Binary Images:
> 0x80000000 - 0x8006afe7  libstdc++.6.dylib ??? (???)
> <411D87F4-B7E1-44EB-F201-F8B4F9227213> /usr/lib/libstdc++.6.dylib
> 0x800c5000 - 0x80269feb  libSystem.B.dylib ??? (???)
> <37A346CE-CBBD-8317-B4D7-7ECF3A010974> /usr/lib/libSystem.B.dylib
> 0x802e9000 - 0x802ecfe7  libmathCommon.A.dylib ??? (???)
> <1622A54F-1A98-2CBE-B6A4-2122981A500E> /usr/lib/system/libmathCommon.A.dylib
> 0x8fe00000 - 0x8fe4162b  dyld 132.1 (???) <226BF7A0-94E0-2F4C-6D6B-9189C952331C>
> /usr/lib/dyld
> 0xb8000000 - 0xb81defff  LaunchCFMApp ??? (???)
> <3E4E06B8-E1FC-B232-1371-643DC0FBE8C9>
> /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp
> 0xffff0000 - 0xffff1fff  libSystem.B.dylib ??? (???)
> <37A346CE-CBBD-8317-B4D7-7ECF3A010974> /usr/lib/libSystem.B.dylib
> 
> Translated Code Information:
> Rosetta Version:  22.23
> Args:
> /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp
> /POV-Ray 3.6/POV-Ray Mac 3.6 Folder/POV-Ray Mac 3.6
> Exception: EXC_BAD_ACCESS (0x0001)
> 
> Thread 0: (0xb009ad38, 0xb815ae44)
> 0x904f6588: /usr/lib/libSystem.B.dylib : __dispatch_mgr_invoke + 228
> 0x904f60c0: /usr/lib/libSystem.B.dylib : __dispatch_queue_invoke + 320
> 0x904f6244: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread2 + 364
> 0x904f6380: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 76
> 0x90416da8: /usr/lib/libSystem.B.dylib : __pthread_body + 40
> 0x00000000:
> /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
> + 0
> 
> PPC Thread State
> srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
> cr:  0xXXXXXXXX  xer: 0x20000000   lr: 0x904f6550  ctr: 0x903ba2d4
> r00: 0x0000016b  r01: 0xf0080bb0  r02: 0x00000000  r03: 0x00000004
> r04: 0x00000000  r05: 0x00000000  r06: 0xf0080d0c  r07: 0x00000001
> r08: 0xf0080d28  r09: 0x00000000  r10: 0x00000037  r11: 0xa008b524
> r12: 0x903ba2d4  r13: 0x10624dd3  r14: 0x90545b2c  r15: 0xf0080c0c
> r16: 0xf0080c8c  r17: 0xa00a64ac  r18: 0xf0080d28  r19: 0xa00a04f8
> r20: 0xa00a14f8  r21: 0xf0080d0c  r22: 0xa00a0478  r23: 0xa00a03f8
> r24: 0xa00a64ac  r25: 0x00000000  r26: 0x00000000  r27: 0xa00925c8
> r28: 0xa0092300  r29: 0xa00925c8  r30: 0xf0080d28  r31: 0x904f64ac
> 
> Thread 1: (0xb03a6efc, 0x816e81d6)
> 0x82b8e3a0: No symbol
> 0x82b91968: No symbol
> 0x82b8d4b4: No symbol
> 0x82b91a40: No symbol
> 0x98259628:
>
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
> : _PrivateMPEntryPoint + 100
> 0x98259628:
>
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
> : _PrivateMPEntryPoint + 100
> 0x90416da8: /usr/lib/libSystem.B.dylib : __pthread_body + 40
> 0x00000000:
> /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
> + 0
> 
> PPC Thread State
> srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
> cr:  0xXXXXXXXX  xer: 0x20000000   lr: 0x82b91968  ctr: 0x90376770
> r00: 0xffffffc5  r01: 0xf0432cd0  r02: 0x982586b4  r03: 0x00000000
> r04: 0x000e5a00  r05: 0x0190ec00  r06: 0x00000006  r07: 0x000da000
> r08: 0x000e5a14  r09: 0x007f8000  r10: 0x0190f800  r11: 0xa008c1f0
> r12: 0x90376770  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
> r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00000000
> r20: 0x00000000  r21: 0x00000000  r22: 0x00000000  r23: 0x00000000
> r24: 0x00000000  r25: 0x00000000  r26: 0x00000000  r27: 0x00000000
> r28: 0x00000000  r29: 0x005a4e90  r30: 0x17224b08  r31: 0xf0432d60
> 
> Thread 2: (0xb011cd74, 0xb815aa83)
> 0x904f80b4: /usr/lib/libSystem.B.dylib : __dispatch_semaphore_wait_slow + 248
> 0x904f63a8: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 116
> 0x90416da8: /usr/lib/libSystem.B.dylib : __pthread_body + 40
> 0x00000000:
> /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
> + 0
> 
> PPC Thread State
> srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
> cr:  0xXXXXXXXX  xer: 0x20000000   lr: 0x904f80cc  ctr: 0x903766c0
> r00: 0xffffffda  r01: 0xf0101dc0  r02: 0x00000000  r03: 0x00002403
> r04: 0x0000003b  r05: 0x10dceb32  r06: 0x0000001d  r07: 0x00000000
> r08: 0x4c77b532  r09: 0x00000000  r10: 0x10dceb32  r11: 0xa008c670
> r12: 0x903766c0  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
> r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00000000
> r20: 0x00000000  r21: 0xa0092790  r22: 0xa0092784  r23: 0xa009278c
> r24: 0x000001ff  r25: 0x822c43b8  r26: 0xa00924d0  r27: 0x0000003b
> r28: 0x0000000d  r29: 0xcd897932  r30: 0xa0092764  r31: 0x904f7fc4
> 
> Thread 3: (0xb02a2d44, 0xb815ae87)
> 0x90413544: /usr/lib/libSystem.B.dylib : __pthread_cond_wait + 880
> 0x0077bdf0:
> /System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport
> : _CarbonOperationThreadFunc + 172
> 0x90416da8: /usr/lib/libSystem.B.dylib : __pthread_body + 40
> 0x00000000:
> /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
> + 0
> 
> PPC Thread State
> srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
> cr:  0xXXXXXXXX  xer: 0x00000000   lr: 0x904136b0  ctr: 0x90460514
> r00: 0x0000014e  r01: 0xf0284aa0  r02: 0xf0284aec  r03: 0x00004703
> r04: 0x00004803  r05: 0x00000000  r06: 0x00000000  r07: 0x00000000
> r08: 0x00000000  r09: 0x00000000  r10: 0x00000050  r11: 0xa008c19c
> r12: 0x90460514  r13: 0xf0284bb4  r14: 0xf0284bb0  r15: 0xf0284bac
> r16: 0xf0284ba8  r17: 0xf0284ba4  r18: 0xf0284ba0  r19: 0xf0284d08
> r20: 0xf0284b8c  r21: 0x007950c0  r22: 0x00000000  r23: 0x00000000
> r24: 0x00000000  r25: 0x00000000  r26: 0xa00936e4  r27: 0x00000000
> r28: 0x00515e80  r29: 0x01841a00  r30: 0x00515e28  r31: 0x904131e0
> 
> Thread 4: (0xb019ed74, 0xb815aa83)
> 0x904f80b4: /usr/lib/libSystem.B.dylib : __dispatch_semaphore_wait_slow + 248
> 0x904f63a8: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 116
> 0x90416da8: /usr/lib/libSystem.B.dylib : __pthread_body + 40
> 0x00000000:
> /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
> + 0
> 
> PPC Thread State
> srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
> cr:  0xXXXXXXXX  xer: 0x20000000   lr: 0x904f80cc  ctr: 0x903766c0
> r00: 0xffffffda  r01: 0xf0182dc0  r02: 0x00000000  r03: 0x00002403
> r04: 0x00000040  r05: 0x3b9aad74  r06: 0x00000020  r07: 0x00000000
> r08: 0x3b9aad74  r09: 0x00000000  r10: 0x3b9aad74  r11: 0xa008c670
> r12: 0x903766c0  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
> r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00000000
> r20: 0x00000000  r21: 0xa0092790  r22: 0xa0092784  r23: 0xa009278c
> r24: 0x00000200  r25: 0xe66edee2  r26: 0xa00924d0  r27: 0x00000040
> r28: 0x0000000f  r29: 0x224d2d74  r30: 0xa0092764  r31: 0x904f7fc4
> 
> Thread 5: Crashed (0xb7fff9d0, 0xb80c5e94)
> 0x8556b3cc: No symbol
> 0x854d8a9c: No symbol
> 0x854d7830: No symbol
> 0x855d0d14: No symbol
> 
> PPC Thread State
> srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
> cr:  0xXXXXXXXX  xer: 0x00000000   lr: 0x8557480c  ctr: 0x9039a7e0
> r00: 0x854d8a9c  r01: 0xbfffed30  r02: 0x01821400  r03: 0x00000000
> r04: 0x00000000  r05: 0xa0ec7c0c  r06: 0x00000007  r07: 0x00000001
> r08: 0x00002a18  r09: 0x000fc080  r10: 0x000001f2  r11: 0xa0ebe094
> r12: 0x9039a7e0  r13: 0x00000000  r14: 0x00000000  r15: 0x00000016
> r16: 0x00000000  r17: 0x00000000  r18: 0x0182cb30  r19: 0x0182d800
> r20: 0x0182e120  r21: 0x0182d8d0  r22: 0x0182f110  r23: 0x01907ee0
> r24: 0x00000000  r25: 0x0182a6f0  r26: 0xbffff724  r27: 0x0181ff7c
> r28: 0x00000000  r29: 0x00000000  r30: 0x00000009  r31: 0x00000000
> 
> Thread 6: (0xb0220d78, 0xb815ad54)
> 0x0077a0cc:
> /System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport
> : _BSD_watchevent + 44
> 0x0077f788:
> /System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport
> : _CarbonSelectThreadFunc + 228
> 0x90416da8: /usr/lib/libSystem.B.dylib : __pthread_body + 40
> 0x00000000:
> /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
> + 0
> 
> PPC Thread State
> srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
> cr:  0xXXXXXXXX  xer: 0x00000000   lr: 0x0077a060  ctr: 0x903b8304
> r00: 0x00000000  r01: 0xf0203d50  r02: 0x00790f18  r03: 0x000000e8
> r04: 0xf0203e08  r05: 0x00000000  r06: 0x00000000  r07: 0x01000000
> r08: 0x00791b08  r09: 0x434f4e44  r10: 0xffffffff  r11: 0x007941a0
> r12: 0x903b8304  r13: 0x0078f6b4  r14: 0xf0203e24  r15: 0xf0203e5f
> r16: 0xf0203e50  r17: 0xf0203e4c  r18: 0xf0203e54  r19: 0x70636c73
> r20: 0xf0203e08  r21: 0x0fffffff  r22: 0x00000000  r23: 0x007950c0
> r24: 0x00000000  r25: 0x0079f6b4  r26: 0x00000000  r27: 0xf0203e58
> r28: 0xf0203e08  r29: 0x00000000  r30: 0x00000000  r31: 0x0077f6b4
> 
> Thread 7: (0xb032484c, 0xb815ac0f)
> 0x00000000:
> /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
> + 0
> 0x9829a174:
>
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
> : _YieldToThread + 524
> 0x9829a214:
>
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
> : _YieldToAnyThread + 20
> 0x854d20c4: No symbol
> 0x9829aad8:
>
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
> : _CooperativeThread + 348
> 0x90416da8: /usr/lib/libSystem.B.dylib : __pthread_body + 40
> 
> PPC Thread State
> srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
> cr:  0xXXXXXXXX  xer: 0x00000000   lr: 0x90376d84  ctr: 0x90376650
> r00: 0xffffffe1  r01: 0xf0305c90  r02: 0x00000013  r03: 0xf0305d4c
> r04: 0x00000003  r05: 0x00000018  r06: 0x00000020  r07: 0x00007c07
> r08: 0x00000000  r09: 0x00000000  r10: 0xa00a4b28  r11: 0xa008c180
> r12: 0x90376650  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
> r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00000000
> r20: 0x00000000  r21: 0x00000000  r22: 0xf0305d4c  r23: 0x00000018
> r24: 0x00000020  r25: 0x00007c07  r26: 0x00000000  r27: 0x00000000
> r28: 0x00000003  r29: 0x00000003  r30: 0x00000000  r31: 0x98299f70
> 
> 
> Model: MacBook6,1, BootROM MB61.00C8.B00, 2 processors, Intel Core 2 Duo, 2.26
> GHz, 2 GB, SMC 1.51f53
> Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB
> Memory Module: global_name
> AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom
> BCM43xx 1.0 (5.10.131.1 )
> Bluetooth: Version 2.2.2f7, 2 service, 0 devices, 1 incoming serial ports
> Network Service: Ethernet, Ethernet, en0
> Serial ATA Device: Hitachi HTS545025B9SA02, 232.89 GB
> Serial ATA Device: MATSHITADVD-R   UJ-898
> USB Device: Built-in iSight, 0x05ac  (Apple Inc.), 0x8507, 0x24400000
> USB Device: BRCM2070 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x06100000
> USB Device: Bluetooth Module, 0x05ac  (Apple Inc.), 0x8218, 0x06130000
> USB Device: Apple Internal Keyboard / Trackpad, 0x05ac  (Apple Inc.), 0x0236,
> 0x04600000
> 
> 
>

[gsc 1] installing on mac [5910 days 10 hours and 51 minutes ago]

Fri, 12 Feb 2010 22:50:00 GMT

Hi,
I have a MacBook and am running Mac OS X 10.6.1.  I downloaded povray, and when
I try to open it, it says it quit unexpectedly and I get the information below.
Does anyone know how to fix this?
Thanks!



Process:         translate [659]
Path:            /POV-Ray 3.6/POV-Ray Mac 3.6 Folder/POV-Ray Mac 3.6
Identifier:      translate
Version:         ??? (56721408)
Code Type:       PPC (Translated)
Parent Process:  launchd [83]

Date/Time:       2010-02-12 14:44:14.031 -0800
OS Version:      Mac OS X 10.6.1 (10A2047)
Report Version:  6

Interval Since Last Report:          287586 sec
Crashes Since Last Report:           11
Per-App Crashes Since Last Report:   7
Anonymous UUID:                      E22E83E7-1D9F-4CF8-A1F0-60FB781D7665

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000004
Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
0   LaunchCFMApp                   0xb80c5e94 0xb8000000 + 810644
1   LaunchCFMApp                   0xb80c01bb 0xb8000000 + 786875
2   LaunchCFMApp                   0xb80dda6c 0xb8000000 + 907884
3   LaunchCFMApp                   0xb8145da1 spin_lock_wrapper + 3973
4   LaunchCFMApp                   0xb801d03b 0xb8000000 + 118843

Thread 1:
0   libSystem.B.dylib              0x800c57da mach_msg_trap + 10
1   libSystem.B.dylib              0x800c5f47 mach_msg + 68
2   LaunchCFMApp                   0xb819448f CallPPCFunctionAtAddressInt +
206155
3   libSystem.B.dylib              0x800f2f39 _pthread_start + 345
4   libSystem.B.dylib              0x800f2dbe thread_start + 34

Thread 2:
0   LaunchCFMApp                   0xb815ae44 spin_lock_wrapper + 90152
1   LaunchCFMApp                   0xb8179d27 CallPPCFunctionAtAddressInt +
97763
2   LaunchCFMApp                   0xb80c6c97 0xb8000000 + 814231
3   LaunchCFMApp                   0xb80c01bb 0xb8000000 + 786875
4   LaunchCFMApp                   0xb80dda6c 0xb8000000 + 907884
5   LaunchCFMApp                   0xb814551b spin_lock_wrapper + 1791
6   LaunchCFMApp                   0xb801d03b 0xb8000000 + 118843

Thread 3:
0   LaunchCFMApp                   0xb815aa83 spin_lock_wrapper + 89191
1   LaunchCFMApp                   0xb8176f29 CallPPCFunctionAtAddressInt +
85989
2   LaunchCFMApp                   0xb80c6c97 0xb8000000 + 814231
3   LaunchCFMApp                   0xb80c01bb 0xb8000000 + 786875
4   LaunchCFMApp                   0xb80dda6c 0xb8000000 + 907884
5   LaunchCFMApp                   0xb814551b spin_lock_wrapper + 1791
6   LaunchCFMApp                   0xb801d03b 0xb8000000 + 118843

Thread 4:
0   LaunchCFMApp                   0xb815aa83 spin_lock_wrapper + 89191
1   LaunchCFMApp                   0xb8176f29 CallPPCFunctionAtAddressInt +
85989
2   LaunchCFMApp                   0xb80c6c97 0xb8000000 + 814231
3   LaunchCFMApp                   0xb80c01bb 0xb8000000 + 786875
4   LaunchCFMApp                   0xb80dda6c 0xb8000000 + 907884
5   LaunchCFMApp                   0xb814551b spin_lock_wrapper + 1791
6   LaunchCFMApp                   0xb801d03b 0xb8000000 + 118843

Thread 5:
0   LaunchCFMApp                   0xb815ad54 spin_lock_wrapper + 89912
1   LaunchCFMApp                   0xb817040c CallPPCFunctionAtAddressInt +
58568
2   LaunchCFMApp                   0xb80c6c97 0xb8000000 + 814231
3   LaunchCFMApp                   0xb80c01bb 0xb8000000 + 786875
4   LaunchCFMApp                   0xb80dda6c 0xb8000000 + 907884
5   LaunchCFMApp                   0xb8145da1 spin_lock_wrapper + 3973
6   LaunchCFMApp                   0xb801d03b 0xb8000000 + 118843

Thread 6:
0   LaunchCFMApp                   0xb815ae87 spin_lock_wrapper + 90219
1   LaunchCFMApp                   0xb8174ac7 CallPPCFunctionAtAddressInt +
76675
2   LaunchCFMApp                   0xb80c6c97 0xb8000000 + 814231
3   LaunchCFMApp                   0xb80c01bb 0xb8000000 + 786875
4   LaunchCFMApp                   0xb80dda6c 0xb8000000 + 907884
5   LaunchCFMApp                   0xb8145da1 spin_lock_wrapper + 3973
6   LaunchCFMApp                   0xb801d03b 0xb8000000 + 118843

Thread 7:
0   LaunchCFMApp                   0xb815ac0f spin_lock_wrapper + 89587
1   LaunchCFMApp                   0xb818c47b CallPPCFunctionAtAddressInt +
173367
2   LaunchCFMApp                   0xb818ef7c CallPPCFunctionAtAddressInt +
184376
3   LaunchCFMApp                   0xb80e8a4f 0xb8000000 + 952911
4   ???                            0x816c4302 0 + 2171355906

Thread 8:
0   ???                            0x816e839a 0 + 2171503514

Thread 0 crashed with X86 Thread State (32-bit):
  eax: 0x00000004  ebx: 0xb80c5e6c  ecx: 0x00000000  edx: 0x00000003
  edi: 0x00000004  esi: 0x804037f0  ebp: 0xb7fffa08  esp: 0xb7fff9d0
   ss: 0x0000001f  efl: 0x00010206  eip: 0xb80c5e94   cs: 0x00000017
   ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
  cr2: 0x00000004

Binary Images:
0x80000000 - 0x8006afe7  libstdc++.6.dylib ??? (???)
<411D87F4-B7E1-44EB-F201-F8B4F9227213> /usr/lib/libstdc++.6.dylib
0x800c5000 - 0x80269feb  libSystem.B.dylib ??? (???)
<37A346CE-CBBD-8317-B4D7-7ECF3A010974> /usr/lib/libSystem.B.dylib
0x802e9000 - 0x802ecfe7  libmathCommon.A.dylib ??? (???)
<1622A54F-1A98-2CBE-B6A4-2122981A500E> /usr/lib/system/libmathCommon.A.dylib
0x8fe00000 - 0x8fe4162b  dyld 132.1 (???) <226BF7A0-94E0-2F4C-6D6B-9189C952331C>
/usr/lib/dyld
0xb8000000 - 0xb81defff  LaunchCFMApp ??? (???)
<3E4E06B8-E1FC-B232-1371-643DC0FBE8C9>
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp
0xffff0000 - 0xffff1fff  libSystem.B.dylib ??? (???)
<37A346CE-CBBD-8317-B4D7-7ECF3A010974> /usr/lib/libSystem.B.dylib

Translated Code Information:
Rosetta Version:  22.23
Args:
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp
/POV-Ray 3.6/POV-Ray Mac 3.6 Folder/POV-Ray Mac 3.6
Exception: EXC_BAD_ACCESS (0x0001)

Thread 0: (0xb009ad38, 0xb815ae44)
0x904f6588: /usr/lib/libSystem.B.dylib : __dispatch_mgr_invoke + 228
0x904f60c0: /usr/lib/libSystem.B.dylib : __dispatch_queue_invoke + 320
0x904f6244: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread2 + 364
0x904f6380: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 76
0x90416da8: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000:
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
+ 0

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
cr:  0xXXXXXXXX  xer: 0x20000000   lr: 0x904f6550  ctr: 0x903ba2d4
r00: 0x0000016b  r01: 0xf0080bb0  r02: 0x00000000  r03: 0x00000004
r04: 0x00000000  r05: 0x00000000  r06: 0xf0080d0c  r07: 0x00000001
r08: 0xf0080d28  r09: 0x00000000  r10: 0x00000037  r11: 0xa008b524
r12: 0x903ba2d4  r13: 0x10624dd3  r14: 0x90545b2c  r15: 0xf0080c0c
r16: 0xf0080c8c  r17: 0xa00a64ac  r18: 0xf0080d28  r19: 0xa00a04f8
r20: 0xa00a14f8  r21: 0xf0080d0c  r22: 0xa00a0478  r23: 0xa00a03f8
r24: 0xa00a64ac  r25: 0x00000000  r26: 0x00000000  r27: 0xa00925c8
r28: 0xa0092300  r29: 0xa00925c8  r30: 0xf0080d28  r31: 0x904f64ac

Thread 1: (0xb03a6efc, 0x816e81d6)
0x82b8e3a0: No symbol
0x82b91968: No symbol
0x82b8d4b4: No symbol
0x82b91a40: No symbol
0x98259628:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
: _PrivateMPEntryPoint + 100
0x98259628:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
: _PrivateMPEntryPoint + 100
0x90416da8: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000:
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
+ 0

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
cr:  0xXXXXXXXX  xer: 0x20000000   lr: 0x82b91968  ctr: 0x90376770
r00: 0xffffffc5  r01: 0xf0432cd0  r02: 0x982586b4  r03: 0x00000000
r04: 0x000e5a00  r05: 0x0190ec00  r06: 0x00000006  r07: 0x000da000
r08: 0x000e5a14  r09: 0x007f8000  r10: 0x0190f800  r11: 0xa008c1f0
r12: 0x90376770  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00000000
r20: 0x00000000  r21: 0x00000000  r22: 0x00000000  r23: 0x00000000
r24: 0x00000000  r25: 0x00000000  r26: 0x00000000  r27: 0x00000000
r28: 0x00000000  r29: 0x005a4e90  r30: 0x17224b08  r31: 0xf0432d60

Thread 2: (0xb011cd74, 0xb815aa83)
0x904f80b4: /usr/lib/libSystem.B.dylib : __dispatch_semaphore_wait_slow + 248
0x904f63a8: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 116
0x90416da8: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000:
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
+ 0

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
cr:  0xXXXXXXXX  xer: 0x20000000   lr: 0x904f80cc  ctr: 0x903766c0
r00: 0xffffffda  r01: 0xf0101dc0  r02: 0x00000000  r03: 0x00002403
r04: 0x0000003b  r05: 0x10dceb32  r06: 0x0000001d  r07: 0x00000000
r08: 0x4c77b532  r09: 0x00000000  r10: 0x10dceb32  r11: 0xa008c670
r12: 0x903766c0  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00000000
r20: 0x00000000  r21: 0xa0092790  r22: 0xa0092784  r23: 0xa009278c
r24: 0x000001ff  r25: 0x822c43b8  r26: 0xa00924d0  r27: 0x0000003b
r28: 0x0000000d  r29: 0xcd897932  r30: 0xa0092764  r31: 0x904f7fc4

Thread 3: (0xb02a2d44, 0xb815ae87)
0x90413544: /usr/lib/libSystem.B.dylib : __pthread_cond_wait + 880
0x0077bdf0:
/System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport
: _CarbonOperationThreadFunc + 172
0x90416da8: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000:
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
+ 0

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
cr:  0xXXXXXXXX  xer: 0x00000000   lr: 0x904136b0  ctr: 0x90460514
r00: 0x0000014e  r01: 0xf0284aa0  r02: 0xf0284aec  r03: 0x00004703
r04: 0x00004803  r05: 0x00000000  r06: 0x00000000  r07: 0x00000000
r08: 0x00000000  r09: 0x00000000  r10: 0x00000050  r11: 0xa008c19c
r12: 0x90460514  r13: 0xf0284bb4  r14: 0xf0284bb0  r15: 0xf0284bac
r16: 0xf0284ba8  r17: 0xf0284ba4  r18: 0xf0284ba0  r19: 0xf0284d08
r20: 0xf0284b8c  r21: 0x007950c0  r22: 0x00000000  r23: 0x00000000
r24: 0x00000000  r25: 0x00000000  r26: 0xa00936e4  r27: 0x00000000
r28: 0x00515e80  r29: 0x01841a00  r30: 0x00515e28  r31: 0x904131e0

Thread 4: (0xb019ed74, 0xb815aa83)
0x904f80b4: /usr/lib/libSystem.B.dylib : __dispatch_semaphore_wait_slow + 248
0x904f63a8: /usr/lib/libSystem.B.dylib : __dispatch_worker_thread + 116
0x90416da8: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000:
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
+ 0

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
cr:  0xXXXXXXXX  xer: 0x20000000   lr: 0x904f80cc  ctr: 0x903766c0
r00: 0xffffffda  r01: 0xf0182dc0  r02: 0x00000000  r03: 0x00002403
r04: 0x00000040  r05: 0x3b9aad74  r06: 0x00000020  r07: 0x00000000
r08: 0x3b9aad74  r09: 0x00000000  r10: 0x3b9aad74  r11: 0xa008c670
r12: 0x903766c0  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00000000
r20: 0x00000000  r21: 0xa0092790  r22: 0xa0092784  r23: 0xa009278c
r24: 0x00000200  r25: 0xe66edee2  r26: 0xa00924d0  r27: 0x00000040
r28: 0x0000000f  r29: 0x224d2d74  r30: 0xa0092764  r31: 0x904f7fc4

Thread 5: Crashed (0xb7fff9d0, 0xb80c5e94)
0x8556b3cc: No symbol
0x854d8a9c: No symbol
0x854d7830: No symbol
0x855d0d14: No symbol

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
cr:  0xXXXXXXXX  xer: 0x00000000   lr: 0x8557480c  ctr: 0x9039a7e0
r00: 0x854d8a9c  r01: 0xbfffed30  r02: 0x01821400  r03: 0x00000000
r04: 0x00000000  r05: 0xa0ec7c0c  r06: 0x00000007  r07: 0x00000001
r08: 0x00002a18  r09: 0x000fc080  r10: 0x000001f2  r11: 0xa0ebe094
r12: 0x9039a7e0  r13: 0x00000000  r14: 0x00000000  r15: 0x00000016
r16: 0x00000000  r17: 0x00000000  r18: 0x0182cb30  r19: 0x0182d800
r20: 0x0182e120  r21: 0x0182d8d0  r22: 0x0182f110  r23: 0x01907ee0
r24: 0x00000000  r25: 0x0182a6f0  r26: 0xbffff724  r27: 0x0181ff7c
r28: 0x00000000  r29: 0x00000000  r30: 0x00000009  r31: 0x00000000

Thread 6: (0xb0220d78, 0xb815ad54)
0x0077a0cc:
/System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport
: _BSD_watchevent + 44
0x0077f788:
/System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport
: _CarbonSelectThreadFunc + 228
0x90416da8: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000:
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
+ 0

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
cr:  0xXXXXXXXX  xer: 0x00000000   lr: 0x0077a060  ctr: 0x903b8304
r00: 0x00000000  r01: 0xf0203d50  r02: 0x00790f18  r03: 0x000000e8
r04: 0xf0203e08  r05: 0x00000000  r06: 0x00000000  r07: 0x01000000
r08: 0x00791b08  r09: 0x434f4e44  r10: 0xffffffff  r11: 0x007941a0
r12: 0x903b8304  r13: 0x0078f6b4  r14: 0xf0203e24  r15: 0xf0203e5f
r16: 0xf0203e50  r17: 0xf0203e4c  r18: 0xf0203e54  r19: 0x70636c73
r20: 0xf0203e08  r21: 0x0fffffff  r22: 0x00000000  r23: 0x007950c0
r24: 0x00000000  r25: 0x0079f6b4  r26: 0x00000000  r27: 0xf0203e58
r28: 0xf0203e08  r29: 0x00000000  r30: 0x00000000  r31: 0x0077f6b4

Thread 7: (0xb032484c, 0xb815ac0f)
0x00000000:
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
+ 0
0x9829a174:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
: _YieldToThread + 524
0x9829a214:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
: _YieldToAnyThread + 20
0x854d20c4: No symbol
0x9829aad8:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
: _CooperativeThread + 348
0x90416da8: /usr/lib/libSystem.B.dylib : __pthread_body + 40

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
cr:  0xXXXXXXXX  xer: 0x00000000   lr: 0x90376d84  ctr: 0x90376650
r00: 0xffffffe1  r01: 0xf0305c90  r02: 0x00000013  r03: 0xf0305d4c
r04: 0x00000003  r05: 0x00000018  r06: 0x00000020  r07: 0x00007c07
r08: 0x00000000  r09: 0x00000000  r10: 0xa00a4b28  r11: 0xa008c180
r12: 0x90376650  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00000000
r20: 0x00000000  r21: 0x00000000  r22: 0xf0305d4c  r23: 0x00000018
r24: 0x00000020  r25: 0x00007c07  r26: 0x00000000  r27: 0x00000000
r28: 0x00000003  r29: 0x00000003  r30: 0x00000000  r31: 0x98299f70


Model: MacBook6,1, BootROM MB61.00C8.B00, 2 processors, Intel Core 2 Duo, 2.26
GHz, 2 GB, SMC 1.51f53
Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom
BCM43xx 1.0 (5.10.131.1 )
Bluetooth: Version 2.2.2f7, 2 service, 0 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: Hitachi HTS545025B9SA02, 232.89 GB
Serial ATA Device: MATSHITADVD-R   UJ-898
USB Device: Built-in iSight, 0x05ac  (Apple Inc.), 0x8507, 0x24400000
USB Device: BRCM2070 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x06100000
USB Device: Bluetooth Module, 0x05ac  (Apple Inc.), 0x8218, 0x06130000
USB Device: Apple Internal Keyboard / Trackpad, 0x05ac  (Apple Inc.), 0x0236,
0x04600000

[Kappy] Re: Help with Pov-Ray Tutorial use with MegaPov [5931 days 23 hours and 26 minutes ago]

Fri, 22 Jan 2010 10:15:01 GMT

"Laser" <Par### [at] shawca> wrote:
> Can someone help me translate this tutorial for Pov-Ray so I can use it with
> MegaPov?
>
> It is a 3D Block Letter tutorial found at this site:
>
> http://www.scrapbookgraphics.com/wordpress/?p=2202
>
> As I am using a Mac 10.5.7 I cannot run Pov-Ray without it crashing so have
> installed MegaPov. I am not a programmer (just a Mac user LOL) and can't figure
> out how to make the tutorial work using MegaPov.
>
> Any help would be most appreciated.
>
> THanks so much

Hi

Here is the code I made some adjustments to it.

What you need to remember is to place the True Type Font in the same folder as
the scene file.
So MegaPov can find it this is the simplest way.

This is how we use to set up documents for print, you always had to remember to
include the font you were using in the folder that you would give the printer.

You can do a search using spotlight for True Type fonts just type in .ttf in
Spotlight (Note remember the period symbol before the ttf)

The Font I used was Brush Script.ttf and I used the word "help" (Note it could
be any word or letter)

Just copy and paste this code into MegaPOV  scene file.

You can do this by selecting file new then pasting this code into it then
saving that file into a folder (I suggest an empty folder) with your True Type
Font within this folder.

Then select Render every thing should work fine.

Note Type selection and word selection could affect how the final rendered image
looks. I suggest that you use Brush Script.ttf to start  off with and the word I
used "Help" just to get you started.
-------------------------------------------------------------------------------
camera {
  location  <-1.2, -9.0, 1.5>
  up z
  sky z
  look_at   <0.0, 0.0, 0.7>
  right x*(image_width/image_height)
  angle 19
}

light_source {
  <-1000, -5500, 6000>*0.5
  color rgb 2
  area_light 100*x 100*y  6, 6
}

text { ttf "Brush Script.ttf", "Help", .5, 0
       pigment  { color rgb <1,0,0> }
       translate <-.9,.2,0>
       rotate <85,0,3>
       scale 1.5
     }
-------------------------------------------------------------------------------

I hope this helps

[Thorsten Froehlich] Re: I want a working POV-Ray for Intel Macs [5970 days 4 hours and 49 minutes ago]

Tue, 15 Dec 2009 04:52:25 GMT

Sterling Garwood wrote:
> "KEBman" <nomail@nomail> wrote:
>> Yes, that's what I want. I think it's lame to blame it on malfunctioning PowerPC
>> emulator when you should have made the binary work on both PowerPC and Intel
> etc .... <snip>
> 
> I filed a bug report with Apple and they actually sent me the needed fixes in
> PovRay code ... its a PovRay issue -- who can get the source code fixed???

I know, I finally received them a few weeks ago, too. And to clarify, they 
send you workarounds for the bugs in the PowerPC emulator, not for any bugs 
in POV-Ray. The claim the responsible Apple engineer makes is this:

"The root cause of the problem is NOT a bug in Rosetta. The translator is 
behaving exactly as it was designed. The problem is that the translator was 
never intended to completely emulate a PowerPC processor. There are some 
behaviors that simply can't be translated properly."

So their PowerPC emulator is no PowerPC emulator after all. His workaround 
is actually inserting a few calls to the Carbon multithreading API that are 
trapped by Rosetta and which allow the Rosetta PowerPC emulator to pick up a 
thread state change. This call is not needed on a real PowerPC system, which 
is in turn what POV-Ray was designed for. Hence, his excuse is rather funny 
... and to shorten it he is saying "The Rosetta PowerPC emulator is not 
designed to emulate a PowerPC processor."

	Thorsten, POV-Team

PS: The issue of there being no POV-Ray update yet simply has to do with the 
fact that I will only have time during my Christmas vacation for this.

[Sterling Garwood] Re: I want a working POV-Ray for Intel Macs [5970 days 12 hours and 21 minutes ago]

Mon, 14 Dec 2009 21:20:01 GMT

"KEBman" <nomail@nomail> wrote:
> Yes, that's what I want. I think it's lame to blame it on malfunctioning PowerPC
> emulator when you should have made the binary work on both PowerPC and Intel
etc .... <snip>

I filed a bug report with Apple and they actually sent me the needed fixes in
PovRay code ... its a PovRay issue -- who can get the source code fixed???

[Marriott] Re: I want a working POV-Ray for Intel Macs [5981 days 7 hours and 1 minute ago]

Fri, 4 Dec 2009 02:40:00 GMT

Thorsten Froehlich <tho### [at] trfde> wrote:
> KEBman wrote:
> > Yes, that's what I want. I think it's lame to blame it on malfunctioning PowerPC
> > emulator when you should have made the binary work on both PowerPC and Intel
> > Macs in the first place.
>
> You do realize that Apple shifted from one day to the other from PowerPC to
> x86 with no advance warning except for their largest software vendors, Adobe
> and Microsoft?

Apple announced that they would be switching to Intel in June 2005, and the
first Intel Macs were sold in January 2006.  In a few weeks it will be 2010!
With or without the advance warning, there has been plenty of time for a
universal binary of POV-Ray.

> To ask a software released before that move to support
> something that was not known at the time is a joke, and a bad one!

We are not asking for an Intel version to have been released in 2005.

I do not intend to be critical of the POV-Ray team, here-- as others have
mentioned, this is free software, there are workarounds to this, and so on.  But
the above response is invalid.  As KEBman said, blaming an obscure PowerPC
emulation bug is lame.  Likewise, blaming a years-old architecture switch is
lame.  Here are some non-lame responses:

1. This will be fixed in our next major release.
2. Use MegaPOV or the command-line version instead.  We not longer issue a
working Mac POV-Ray frontend program.

[protein-renderer] Re: fatal error upon launch, -199 error code [6031 days 2 hours and 41 minutes ago]

Thu, 15 Oct 2009 07:00:01 GMT

I recently installed PovRay 3.6 for Mac from this website, and get a similar
problem. But for me, PovRay just crashes upon launch without returning an error
code. Also, I don't find any related files in the ~/Library/Preferences/ folder.

I use MacBook with OS X 10.5.8, 2.4 GHz Intel Core 2 Duo.

Is there any progress related to this problem?

[aeffects] Re: Mega-Pov and Snow Leopard... [6068 days 17 hours and 56 minutes ago]

Mon, 7 Sep 2009 15:45:01 GMT

yvo### [at] cancel_This_gmxnet (Yvo Smellenbergh) wrote:
> "aeffects" <nomail@nomail> wrote:
>
> MegaPOV runs fine on SL, no problem at all.
>
>
> > Anyone running Mega-POV on Snow Leopard?
> >
> > Thanks,
> > DHealy
>
>
> --
> -----------------------------------
> MegaPOV at:  http://megapov.inetart.net
> MacMegaPOV at:  http://users.skynet.be/smellenbergh
> E-mail: yvo(DOT)s(AT)gmx.net

Yvo..... thanks much, and thanks for all the years you and others have put into
the excellent patch Mega-POV.

David H.
LasVegas - Reno- Lake Tahoe

[Yvo Smellenbergh] Re: Mega-Pov and Snow Leopard... [6070 days 4 hours and 32 minutes ago]

Sun, 6 Sep 2009 05:09:06 GMT

"aeffects" <nomail@nomail> wrote:

MegaPOV runs fine on SL, no problem at all.


> Anyone running Mega-POV on Snow Leopard?
> 
> Thanks,
> DHealy


-- 
-----------------------------------
MegaPOV at:  http://megapov.inetart.net
MacMegaPOV at:  http://users.skynet.be/smellenbergh
E-mail: yvo(DOT)s(AT)gmx.net

[aeffects] Mega-Pov and Snow Leopard... [6070 days 12 hours and 26 minutes ago]

Sat, 5 Sep 2009 21:15:00 GMT

Anyone running Mega-POV on Snow Leopard?

Thanks,
DHealy

[Thorsten Froehlich] Re: building povray on Snow Leopard [6071 days 17 hours and 1 minute ago]

Fri, 4 Sep 2009 16:40:30 GMT

Phil wrote:
> On Leopard this worked beautifully for me:
> 
> ../configure COMPILED_BY="Phil"
> make
> sudo make install

> Help!

As you are using the Unix version, you should ask in that group, not here.

	Thorsten

[Phil] building povray on Snow Leopard [6071 days 19 hours and 31 minutes ago]

Fri, 4 Sep 2009 14:10:01 GMT

On Leopard this worked beautifully for me:

../configure COMPILED_BY="Phil"
make
sudo make install

On Snow Leopard, the configuration script complains with several file-not-found
errors; I was able to work around this by manually setting the ac_cv_prog_egrep
variable in the configure script.

But then "make" poops out early:

gcc -DHAVE_CONFIG_H -I. -I. -I.     -pipe -O3 -march=i686 -mtune=i686
-malign-double -minline-all-stringops  -c `test -f 'png.c' || echo './'`png.c
png.c:1: error: CPU you selected does not support x86-64 instruction set
png.c:1: error: -malign-double makes no sense in the 64bit mode

Help!

[Thorsten Froehlich] Re: Any solution on failure of POV-RAY 3.6 on in... [6086 days 2 hours and 31 minutes ago]

Fri, 21 Aug 2009 07:09:38 GMT

Sterling Garwood wrote:
> "hauskurz" <kur### [at] biochemwustledu> wrote:
>> I really miss being able to render my figures in POV-RAY. This problem has been
>> reported mutliple times and the home page even states it is not a bug but an
>> apple problem but siggests it is some kind of configuration problem.  Any idea
>> of how to fix???   What is probably needed is a universal binary.  Has anyone
>> solved this problem? Apple is not going to rewrite the emulator.
>> I am getting the Pov-Ray unexpectedly quit message that everyone else is
>> getting.
> 
> I may have a fix from Apple .... and I have delta sources ... who do I send them
> to?

tho### [at] povrayorg please.

Thanks,

	Thorsten, POV-Team

[Sterling Garwood] Re: Any solution on failure of POV-RAY 3.6 on in... [6086 days 7 hours and 36 minutes ago]

Fri, 21 Aug 2009 02:05:01 GMT

"triple_r" <nomail@nomail> wrote:
> "jasonkrupert" <jas### [at] yahoocom> wrote:
>
> > Triple R - Thank you for your follow-up.  What are you suggesting?
> >
> > Are you suggesting to try to recompile POVRay on the OS 10.5 Intel machine and
> > see if it works?
> >
> > Has this been tried successfully before?
>
> Oops.  Sorry for such a delay.  I didn't notice the reply.  My advice though, is
> that if you take the "Unix / Linux / Generic Source Code" from the download page
> and compile it through the OS X terminal, you should have no problems.  I also
> thought it would be interesting to compare something likePOV-Ray natively
> compiled and run through Rosetta, just to see the difference in performance,
> except the old version doesn't seem to run on all computers.
>
>  - Ricky

I got a fix from Apple ... with delta source ... to whom do I send it?

[Sterling Garwood] Re: Any solution on failure of POV-RAY 3.6 on in... [6086 days 7 hours and 36 minutes ago]

Fri, 21 Aug 2009 02:05:00 GMT

"hauskurz" <kur### [at] biochemwustledu> wrote:
> I really miss being able to render my figures in POV-RAY. This problem has been
> reported mutliple times and the home page even states it is not a bug but an
> apple problem but siggests it is some kind of configuration problem.  Any idea
> of how to fix???   What is probably needed is a universal binary.  Has anyone
> solved this problem? Apple is not going to rewrite the emulator.
> I am getting the Pov-Ray unexpectedly quit message that everyone else is
> getting.

I may have a fix from Apple .... and I have delta sources ... who do I send them
to?

[Rune] Re: Problems with external volumes [6105 days and 56 minutes ago]

Sun, 2 Aug 2009 08:45:00 GMT

Thorsten Froehlich <tho### [at] trfde> wrote:
> Rune wrote:
> > guess I am just out of luck?
>
> No, not really...
>
> it depends on how much convenience you need, or basically how often you
> mount/unmount the disk. Given Mac OS X mounting is Unix-style, you can
> control it much better than on Windows. Essentially, you should be able to
> use either symlinks or renaming of the volume to get it fixed every time it
> is mounted. This task can then be automated if you know enough about Unix
> (sorry, I don't know more than that it can be done this way).

Thanks. I know practically nothing about Unix, but it's good to know it can be
done. Maybe I'll be able to find someone to help me at some point.

Rune

[Thorsten Froehlich] Re: Problems with external volumes [6107 days and 59 minutes ago]

Fri, 31 Jul 2009 08:42:13 GMT

Rune wrote:
> Thorsten Froehlich <tho### [at] trfde> wrote:
>> What type of format does the drive use? This happens only if it has no
>> proper name under Mac OS X because it is formatted as something else (like
>> FAT32).
> 
> Indeed these are formattet as NTFS (Get Info says "NTFS-3g (MacFUSE)"
> specifically). I need this as I am using the drives for both Mac and Windows. I
> guess I am just out of luck?

No, not really...

it depends on how much convenience you need, or basically how often you 
mount/unmount the disk. Given Mac OS X mounting is Unix-style, you can 
control it much better than on Windows. Essentially, you should be able to 
use either symlinks or renaming of the volume to get it fixed every time it 
is mounted. This task can then be automated if you know enough about Unix 
(sorry, I don't know more than that it can be done this way).

	Thorsten

[Rune] Re: Problems with external volumes [6109 days 12 hours and 16 minutes ago]

Tue, 28 Jul 2009 21:25:00 GMT

Thorsten Froehlich <tho### [at] trfde> wrote:
> What type of format does the drive use? This happens only if it has no
> proper name under Mac OS X because it is formatted as something else (like
> FAT32).

Indeed these are formattet as NTFS (Get Info says "NTFS-3g (MacFUSE)"
specifically). I need this as I am using the drives for both Mac and Windows. I
guess I am just out of luck?

Rune

[Thorsten Froehlich] Re: Problems with external volumes [6110 days 4 hours and 43 minutes ago]

Tue, 28 Jul 2009 04:57:37 GMT

Rune wrote:
> Anyway, I'm having problems because my scene and include files are located on an
> external hard drive with multiple partitions. All scene and include files are
> located on a partition called "Data" but when storing references to the include
> file folder the hard drive shows up as "Volumes/Untitled 1" instead of "Data".
> The problem is that it shows up inconsistently as "Untitled", "Untitled 1", or
> "Untitled 2" depending on which order OS X happens to mount the drives in on
> that particular day. This basically seems to mean that I have to reconfigure
> the include file path every day (and all the other configured paths), which is a
> pain.
> 
> I know this is more of a general Mac OS X problem than a POV-Ray problem, but I
> have searched the net for an answer and couldn't find anything. What can be
> done about this?

What type of format does the drive use? This happens only if it has no 
proper name under Mac OS X because it is formatted as something else (like 
FAT32). If it is formatted as Mac only, it should work just fine. I have two 
external drives formatted for Mac and both mount correctly, but I have seen 
strange issues with a few USB sticks formatted as FAT32...

	Thorsten

[Rune] Problems with external volumes [6110 days 13 hours and 41 minutes ago]

Mon, 27 Jul 2009 20:00:01 GMT

Hi,

I'm finally able to use POV-Ray again. (After I switched from Windows to Mac
about a year ago I haven't been able to run POV-Ray because it crashed on
startup, but I recently found out that MegaPOV for Mac works just fine - thanks
MegaPOV team!)

Anyway, I'm having problems because my scene and include files are located on an
external hard drive with multiple partitions. All scene and include files are
located on a partition called "Data" but when storing references to the include
file folder the hard drive shows up as "Volumes/Untitled 1" instead of "Data".
The problem is that it shows up inconsistently as "Untitled", "Untitled 1", or
"Untitled 2" depending on which order OS X happens to mount the drives in on
that particular day. This basically seems to mean that I have to reconfigure
the include file path every day (and all the other configured paths), which is a
pain.

I know this is more of a general Mac OS X problem than a POV-Ray problem, but I
have searched the net for an answer and couldn't find anything. What can be
done about this?

Thanks,

Rune

[L5n25] Re: Cannot run Benchmark (a NEW USER) [6145 days 3 hours and 46 minutes ago]

Tue, 23 Jun 2009 05:55:00 GMT

"alanbell" <bel### [at] yahoocom> wrote:
> I've tried running the benchmark but without success. I am using a powerbook G4
> with Mac OS X 10.5.6.
>
> Here is the message I receive, any helpm would be MUCH appreciated
>
> POV-Ray 3.6 for Mac OS Frontend Build 197
> Persistence of Vision(tm) Ray Tracer Version 3.6.1 for G4 (Mac CodeWarrior)

> Possible Parse Error: Could not find file 'functions.inc'
>
> File benchmark.pov line 3
> Parse Error: Cannot open include file functions.inc.
>

The clue is the snippet from the post above.  So it cannot find the include
file.  I too had this problem.  It was solved by navigating to
Edit>Preferences, selecting the Scenes tab or button in the POV-Ray Application
Preferences, clicking "Add..." and navigating to where you installed POV-Ray,
selecting the "include" folder and click open.

At this point you may wish to also un-check the checkbox on the "Files" tab of
that same dialog that reads "Allow rendering of ".pov" files only" as this
trips up folk who don't save to files with explicit .pov extensions.

Close the dialog and restart POV-Ray.

Now the Benchmark will run after you restart.  Note that on my G4 PowerBook the
benchmark took over 70 minutes to run.  It does not render an image... just
spits out stats.

Try entering into a new file the very simple example in the help file and saving
it.  Now you should be able to render it and see it display in the POV-Ray
preview.  When you successfully render, the program save the image in the same
folder as the source .pov file you just save as a "pict" image file.

[KEBman] Re: I want a working POV-Ray for Intel Macs [6145 days 9 hours and 6 minutes ago]

Tue, 23 Jun 2009 00:35:01 GMT

I checked what a compiler is on Wikipedia, and it seemed a bit beyond my int...
in... capacity for being smart.

Seeing as Intel Macs are now the standard, and since people are buying Intel
Macs in droves, will the next release of fantastic POV-Ray be for Intel Macs?

I sure hope so! =) 'Cause I LOVE POV-Ray! If you do that, imagine a little
puppy-dog running around you in circles. That would be me.

I don't know about this Mega-POW program, though... What's the catch? I like the
real thing. You can't beat the feeling.

[Laser] Help with Pov-Ray Tutorial use with MegaPov [6157 days 19 hours and 41 minutes ago]

Wed, 10 Jun 2009 14:00:00 GMT

Can someone help me translate this tutorial for Pov-Ray so I can use it with
MegaPov?

It is a 3D Block Letter tutorial found at this site:

http://www.scrapbookgraphics.com/wordpress/?p=2202

As I am using a Mac 10.5.7 I cannot run Pov-Ray without it crashing so have
installed MegaPov. I am not a programmer (just a Mac user LOL) and can't figure
out how to make the tutorial work using MegaPov.

Any help would be most appreciated.

THanks so much

[alanbell] Cannot run Benchmark (a NEW USER) [6169 days 7 hours and 16 minutes ago]

Sat, 30 May 2009 02:25:00 GMT

I've tried running the benchmark but without success. I am using a powerbook G4
with Mac OS X 10.5.6.

Here is the message I receive, any helpm would be MUCH appreciated

POV-Ray 3.6 for Mac OS Frontend Build 197
Persistence of Vision(tm) Ray Tracer Version 3.6.1 for G4 (Mac CodeWarrior)
This is an official version prepared by the POV-Ray Team. See the
 documentation on how to contact the authors or visit us on the
 internet at http://www.povray.org/.

Parsing Options
  Input file:
:private:var:folders:D5:D5b7NXdaGASQcUmEXdjcr++++TI:TemporaryItems:benchmark.pov
(compatible to version 3.50)
  Remove bounds........On   Split unions.........Off
  Library paths:
     :Applications:POV-Ray 3.6:scenes:
Output Options
  Image resolution 384 by 384 (rows 0 to 384, columns 0 to 384).
  Graphic display.....Off
  Mosaic preview.......Off
  CPU usage histogram.Off
  Continued trace......Off
Tracing Options
  Quality:  9
  Bounding boxes......On  Bounding threshold: 3
  Light Buffer.........On   Vista Buffer.........On   Draw Vista Buffer....Off
  Antialiasing........On  (Method 1, Threshold 0.300, Depth 3, Jitter 1.00)
  Radiosity............Off
Animation Options
  Clock value....   0.000  (Animation off)
Possible Parse Error: Could not find file 'functions.inc'

File benchmark.pov line 3
Parse Error: Cannot open include file functions.inc.

File benchmark.pov line 3
Parse Warning: Check that the file is in a directory specifed with a +L switch
or 'Library_Path='
..INI item. Standard include files are in the include directory or folder. Please
read your
documentation carefully.

File benchmark.pov line 3
Total Scene Processing Times
  Parse Time:    0 hours  0 minutes  0 seconds (0 seconds)
  Photon Time:   0 hours  0 minutes  0 seconds (0 seconds)
  Render Time:   0 hours  0 minutes  0 seconds (0 seconds)
  Total Time:    0 hours  0 minutes  0 seconds (0 seconds)

[PTV] Re: Pov-Ray 3.6 and Mac OS 10.5 Leopard [6186 days 16 hours and 16 minutes ago]

Tue, 12 May 2009 17:25:00 GMT

I just installed POV-Ray 3.6 with MegaPOV 1.2.1r3 (Universal) on Intel MacBook
running 10.5.6

No problems so far.

"Nicolás Miari" <typ### [at] yahoocojp> wrote:
> I have a similar problem. I'm running OS X 10.4.11 (Tiger, latest update as of
> Apr 2009), on a (possibly) first-gen intel iMac (White acryillic).
>
> POV-Ray 3.6 will crash soon after the splash screen.
>
> Megapov will start up, but crash on File > Open...
>
> I followed the MegaPOV installation instructions up to the "include" settings,
> but without being able to open files that's as far as I can go.
>
> The curious thing is, I used to have no problems on another iMac I used before
> (Aluminium intel iMac), at my former job.
>
> Very frustrating...
>
>
>
>
> "MacGuyver" <nomail@nomail> wrote:
> > Anyone out there trying to use Pov-Ray and Mac OS 10.5? Pov-Ray tries to open,
> > and seems to get most of the way, but then it unexpectedly quits on me. Has
> > anyone else had this problem? Better yet, has anyone found a solution?
> >
> > Thanks in advance,
> > MacGuyver

[] Re: Pov-Ray 3.6 and Mac OS 10.5 Leopard [6215 days 6 hours and 21 minutes ago]

Tue, 14 Apr 2009 03:20:00 GMT

I have a similar problem. I'm running OS X 10.4.11 (Tiger, latest update as of
Apr 2009), on a (possibly) first-gen intel iMac (White acryillic).

POV-Ray 3.6 will crash soon after the splash screen.

Megapov will start up, but crash on File > Open...

I followed the MegaPOV installation instructions up to the "include" settings,
but without being able to open files that's as far as I can go.

The curious thing is, I used to have no problems on another iMac I used before
(Aluminium intel iMac), at my former job.

Very frustrating...

"MacGuyver" <nomail@nomail> wrote:
> Anyone out there trying to use Pov-Ray and Mac OS 10.5? Pov-Ray tries to open,
> and seems to get most of the way, but then it unexpectedly quits on me. Has
> anyone else had this problem? Better yet, has anyone found a solution?
>
> Thanks in advance,
> MacGuyver

[eefKnot] Re: fatal error upon launch, -199 error code [6215 days 17 hours and 46 minutes ago]

Mon, 13 Apr 2009 15:55:00 GMT

"Renderdog" <slo### [at] hiwaaynet> wrote:
> I believe there are some POV-Ray files in ~/Library/Preferences

I deleted the POV-ray files (pov-ray preferences and pov-ray mac 3.6.plist) in
the Library/preferences.  This took care of the -199 error code and POV-ray
seems to start, but then it "unexpectedly quits".  I tried putting the plist
file back and the same thing happens.

So, it seems that these files are effecting things and I am now closer to
getting it to work, thanks Renderdog.

[Renderdog] Re: fatal error upon launch, -199 error code [6219 days 16 hours and 6 minutes ago]

Thu, 9 Apr 2009 17:35:01 GMT

I believe there are some POV-Ray files in ~/Library/Preferences

[Renderdog] Re: fatal error upon launch, -199 error code [6219 days 16 hours and 11 minutes ago]

Thu, 9 Apr 2009 17:30:01 GMT

It also runs fine on my G5 PowerPC Mac OS X 10.5.6.  I'll be installing
a bunch of updates over the next day or two, I'll report if anything
changes.  Have you tried deleting the POV-Ray related files in your
Library directory?  Another possible solution would be to run Mega
POV-Ray.

Mark

[eefKnot] Re: fatal error upon launch, -199 error code [6223 days 7 hours and 1 minute ago]

Mon, 6 Apr 2009 02:40:01 GMT

"eefKnot" <nomail@nomail> wrote:
> This problem was posted orginally by jmcfizix on the bugreports page and it was
> suggested that it be posted here as well.
>
> Both jmcfizix and I have had the same experience.  POV RAY had been working fine
> on my Macbook (Mac OS 10.5.6, 2.16 GHZ Intel Duo,1 Gb 667 MHz DDR2 SDRAM).  Now when
I launch, I get a fatal  error m
essage and a -199 error
> code.  The launching stalls out on the "Reading Preferences", then shows the
> error message.
>
> I am using POV-Ray Mac 3.6 dated Aug 1, 2004 7:23 pm and downloaded directly
> from the povray site.
>
> Restarting the computer and downloading a new copy of POV-ray both failed to fix
> the problem.
>
> I cannot think of any changes I made to the system to cause this.  POV-ray last
> worked on 15 March 2009 and a week later it no longer worked.  \
>
> Any suggestions would be appreciated.
>
> Thanks.

POV-Ray 3.6.0 Build 0197 still works fine on my PowerBook G4 using Mac OS
10.4.11.

[eefKnot] fatal error upon launch, -199 error code [6223 days 7 hours and 36 minutes ago]

Mon, 6 Apr 2009 02:05:01 GMT

This problem was posted orginally by jmcfizix on the bugreports page and it was
suggested that it be posted here as well.

Both jmcfizix and I have had the same experience.  POV RAY had been working fine
on my Macbook (Mac OS 10.5.6, 2.16 GHZ Intel Duo,1 Gb 667 MHz DDR2 SDRAM) for
over a year.  Now when I launch, I get a fatal  error message and a -199 error
code.  The launching stalls out on the "Reading Preferences", then shows the
error message.

I am using POV-Ray Mac 3.6 dated Aug 1, 2004 7:23 pm and downloaded directly
from the povray site.

Restarting the computer and downloading a new copy of POV-ray both failed to fix
the problem.

I cannot think of any changes I made to the system to cause this.  POV-ray last
worked on 15 March 2009 and a week later it no longer worked.  \

Any suggestions would be appreciated.

Thanks.

[Yvo Smellenbergh] Re: I don't see the problem, am I missing someth... [6232 days and 47 minutes ago]

Sat, 28 Mar 2009 08:54:12 GMT

Claes Nygren <cla### [at] allwidgetscom> wrote:

> I've seen a lot of posts about problems with POV-Ray on MAC i386.
> I pulled the Linux source and did:
> ../configure
> make
> make install
> 
> and it just works!
Of course it works.
 
> What am I missing ?
Maybe Mac users want a Mac version and not a linux version? ;-)
In other words, they want a version with complete GUI (editor,
preferences,...)
A command line version is not the same.

Yvo


-- 
-----------------------------------
MegaPOV at:  http://megapov.inetart.net
MacMegaPOV at:  http://users.skynet.be/smellenbergh
E-mail: yvo(DOT)s(AT)gmx.net

[Claes Nygren] I don't see the problem, am I missing something ? [6232 days 3 hours and 46 minutes ago]

Sat, 28 Mar 2009 05:55:00 GMT

I've seen a lot of posts about problems with POV-Ray on MAC i386.
I pulled the Linux source and did:
../configure
make
make install

and it just works!

What am I missing ?

[Bill Pragnell] Re: I want a working POV-Ray for Intel Macs [6255 days and 31 minutes ago]

Thu, 5 Mar 2009 09:10:00 GMT

"triple_r" <nomail@nomail> wrote:
> "Bill Pragnell" <bil### [at] hotmailcom> wrote:
> > Maybe not the ideal solution, but better than switching computers all the time,
> > or (perish the thought) giving up on POV-Ray entirely... :-)
> >
> > http://megapov.inetart.net/
>
> Blast!  Beaten to the punch.

Maybe, but look at the timestamps on our posts... ;-)

[phendric] Re: megaPov #include files can't be found [6255 days 13 hours and 1 minute ago]

Wed, 4 Mar 2009 20:40:01 GMT

Score, problem solved!  Thanks so much!

[triple r] Re: I want a working POV-Ray for Intel Macs [6255 days 15 hours and 36 minutes ago]

Wed, 4 Mar 2009 18:05:01 GMT

"clipka" <nomail@nomail> wrote:
> So why not join the POV team as a volunteer to officially bringing POV to Intel
> Mac users? Even if it's just that you'd be the one to compile the official
> binary ready to install. Or just write a how-to. Anything that gets other
> Intel-Mac users closer to fulfilment of their dreams will probably be
> appreciated.

Insufficient time/knowledge.  It doesn't seem it has been ported over from
CodeWarrior to something more current, and I wouldn't know where to start.  The
command-line approach seems to turn many people off and indicate a
non-user-friendly program.  If MegaPOV works, then it's probably the best
option currently available.  It might make sense to note on the download page
that it's a valid option, rather than just turn people away with an apology.

 - Ricky

[clipka] Re: I want a working POV-Ray for Intel Macs [6255 days 16 hours and 16 minutes ago]

Wed, 4 Mar 2009 17:25:01 GMT

"triple_r" <nomail@nomail> wrote:
> First of all, be assured that in no way do I speak for the POV-Team, and that
> I'm certainly no computer scientist either.  In fact they may be getting sick
> of me saying this, but if you're desperate enough to run it on an old slow
> computer, it's probably worth the trouble just to download XCode from Apple,
> compile POV-Ray yourself from the Unix/Linux source, and be on your way.  It's
> very easy.  This approach works the same for POV-Ray, MegaPOV, and MCPov.
> There are also good text editors (vi, for example) that, although there may be
> a learning curve, do excellent POV-Ray formatting.  I really, genuinely, hope
> this doesn't sound rude, but sometimes it's true that when you want something
> done right, you need to do it yourself.

Isn't that the very basis for most open source projects?

If you want something done right and nobody else seems to be doing it, just go
ahead, do it yourself - then go the extra mile to let others participate...

So why not join the POV team as a volunteer to officially bringing POV to Intel
Mac users? Even if it's just that you'd be the one to compile the official
binary ready to install. Or just write a how-to. Anything that gets other
Intel-Mac users closer to fulfilment of their dreams will probably be
appreciated.

Unless of course you're afraid that the users you'd be helping would complain
that you weren't helping them enough or that you were doing it wrong.

[triple r] Re: I want a working POV-Ray for Intel Macs [6255 days 17 hours and 6 minutes ago]

Wed, 4 Mar 2009 16:35:01 GMT

"Bill Pragnell" <bil### [at] hotmailcom> wrote:
> Maybe not the ideal solution, but better than switching computers all the time,
> or (perish the thought) giving up on POV-Ray entirely... :-)
>
> http://megapov.inetart.net/

Blast!  Beaten to the punch.

 - Ricky

[triple r] Re: I want a working POV-Ray for Intel Macs [6255 days 17 hours and 21 minutes ago]

Wed, 4 Mar 2009 16:20:01 GMT

"KEBman" <nomail@nomail> wrote:
> So PLLLLLEEEEASE make an update for Intel Mac's! =)

I have not tried this, but it sounds like MegaPOV might also be a solution for
Intel macs:

http://megapov.inetart.net/

 - Ricky

[Bill Pragnell] Re: I want a working POV-Ray for Intel Macs [6255 days 17 hours and 21 minutes ago]

Wed, 4 Mar 2009 16:20:01 GMT

"KEBman" <nomail@nomail> wrote:
> I have an Intel Mac, a PowerBook Pro in fact, and I think it's such a shame to
> have to use a moldy old PC laptop to render my pic's (in general I hate
> touching PC's, but when you gotta, you gotta) - a thing that takes for ever
> too. I also love the POV-Ray program interface and ease of use, thus I see no
> point in even using the Mac for editing POV-files...

I say this every time someone posts this problem: use MegaPOV until the
situation is resolved one way or another. That's what I do. It's based on POV
3.6.1, uses all the same includes etc, and is a universal binary, equally happy
on either architecture. True, the editor is a little different, but you get used
to it.

Maybe not the ideal solution, but better than switching computers all the time,
or (perish the thought) giving up on POV-Ray entirely... :-)

http://megapov.inetart.net/

[triple r] Re: I want a working POV-Ray for Intel Macs [6255 days 17 hours and 21 minutes ago]

Wed, 4 Mar 2009 16:20:00 GMT

"KEBman" <nomail@nomail> wrote:
> Yes, that's what I want. I think it's lame to blame it on malfunctioning PowerPC
> emulator when you should have made the binary work on both PowerPC and Intel
> Macs in the first place. I really hope you'll fix this, because even though I
> can write a POV-file, I'm not a computer scientist.

First of all, be assured that in no way do I speak for the POV-Team, and that
I'm certainly no computer scientist either.  In fact they may be getting sick
of me saying this, but if you're desperate enough to run it on an old slow
computer, it's probably worth the trouble just to download XCode from Apple,
compile POV-Ray yourself from the Unix/Linux source, and be on your way.  It's
very easy.  This approach works the same for POV-Ray, MegaPOV, and MCPov.
There are also good text editors (vi, for example) that, although there may be
a learning curve, do excellent POV-Ray formatting.  I really, genuinely, hope
this doesn't sound rude, but sometimes it's true that when you want something
done right, you need to do it yourself.  If I had a binary of the GUI program,
I'd send it to you, but unfortunately this is the only advice I can really
offer.  Let me know if you'd like any more details or help.

 - Ricky

[Thorsten Froehlich] Re: I want a working POV-Ray for Intel Macs [6255 days 17 hours and 37 minutes ago]

Wed, 4 Mar 2009 16:03:57 GMT

KEBman wrote:
> Yes, that's what I want. I think it's lame to blame it on malfunctioning PowerPC
> emulator when you should have made the binary work on both PowerPC and Intel
> Macs in the first place.

You do realize that Apple shifted from one day to the other from PowerPC to 
x86 with no advance warning except for their largest software vendors, Adobe 
and Microsoft? To ask a software released before that move to support 
something that was not known at the time is a joke, and a bad one!

 > The Design of Everyday Things by Donald Norman

Which is a really nice book discussing issues that have absolutely nothing 
to do with POV-Ray - but maybe you could recommend it to people at Apple 
that change directions at light speed without regard for backward 
compatibility...

	Thorsten, POV-Team

[KEBman] I want a working POV-Ray for Intel Macs [6255 days 18 hours and 11 minutes ago]

Wed, 4 Mar 2009 15:30:00 GMT

Yes, that's what I want. I think it's lame to blame it on malfunctioning PowerPC
emulator when you should have made the binary work on both PowerPC and Intel
Macs in the first place. I really hope you'll fix this, because even though I
can write a POV-file, I'm not a computer scientist.

Now, of course I know this is freeware, and I'm really thankful for the effort,
but if I hear more excuses, please read the book The Design of Everyday Things
by Donald Norman.

I have an Intel Mac, a PowerBook Pro in fact, and I think it's such a shame to
have to use a moldy old PC laptop to render my pic's (in general I hate
touching PC's, but when you gotta, you gotta) - a thing that takes for ever
too. I also love the POV-Ray program interface and ease of use, thus I see no
point in even using the Mac for editing POV-files...

So PLLLLLEEEEASE make an update for Intel Mac's! =)

[Yvo Smellenbergh] Re: megaPov #include files can't be found [6255 days 18 hours and 23 minutes ago]

Wed, 4 Mar 2009 15:17:38 GMT

"phendric" <nomail@nomail> wrote:

[...]
> my file hierarchy is as follows:
> my scene is: MegaPOV_C_UB/scenes/demo.pov
> and in the Megapov GUI under 'set search paths for additional include files' I
> have: MegaPOV_C_UB/Insert Menu/20-Include files   which is where colors.inc is
> located (or I guess it's actually colors.inc.txt)

You selected the wrong include folder.
Just go to "MegaPOV" >> "Preferences.."
Now select the "System Includes" tab.
Press the 'Add' button and select the 'include' folder from the official
POV-Ray release.
Press 'Apply' or 'Ok' and now you will be able to run the standard
scenes.
If you also want to render  some of the MegaPOV specific scenes, also
add the 'include' file that comes with the MegaPOV archive.
You can also set some include files in 'set search paths for additional
include files' like you did but the 'Insert menu' is not an include
folder.
You can select this folder in:
"MegaPOV" >> "Preferences.."
Now select the "Editor"  tab and add the folder by pressing the "Insert
Folder" button at the bottom of the panel.
When you do this and you have an editor window on top, you can go to the
"Templates" menu and at the bottom you will find the insert menu now. 

I hope you will succeed now.

Yvo

-- 
-----------------------------------
MegaPOV at:  http://megapov.inetart.net
MacMegaPOV at:  http://users.skynet.be/smellenbergh
E-mail: yvo(DOT)s(AT)gmx.net

[phendric] Re: megaPov #include files can't be found [6256 days 10 hours and 26 minutes ago]

Tue, 3 Mar 2009 23:15:01 GMT

Thanks for your reply but I don't see a "master POVRAY.INI" in any of my files.
I do have povray 3.6, however I'm not sure how I'm supposed to incorporate the
two so I can get the #include statements working.

oh and sorry about the confusion, I'm on an intel Mac.

[clipka] Re: megaPov #include files can't be found [6256 days 10 hours and 56 minutes ago]

Tue, 3 Mar 2009 22:45:01 GMT

"clipka" <nomail@nomail> wrote:
> Um... I've never seen this option in MegaPOV 1.2.1... hum... maybe you should
> add some info what OS you're actually using - I was assuming Windows, but
> currently only you really know...

Argh! Stupid me! (*slaps head*)

I'm reading the messages through the "digest" - I really should occasionally
have a look at what group they're actually posted in... >_<

[phendric] Re: megaPov #include files can't be found [6256 days 11 hours and 6 minutes ago]

Tue, 3 Mar 2009 22:35:01 GMT

sorry but I should add that the example files included in the scene directory
such as bear.pov have trouble with their #include statements as well.

[clipka] Re: megaPov #include files can't be found [6256 days 11 hours and 6 minutes ago]

Tue, 3 Mar 2009 22:35:00 GMT

"phendric" <nomail@nomail> wrote:
> I apologize if this seems a silly question, but my concern is when I run
> megapov, include files such as #include "colors.inc" etc cannot be found when
> the scene is rendered.  I have made no changes to the file hierarchy after
> megapov was downloaded (I have downloaded povray was well) but I get this error

You may need to edit your "master POVRAY.INI" file (see the "tools" menu); make
sure it includes a "Library_Path=" line to point to the original POV 3.6
include directory, e.g.:

Library_Path="C:\Program Files\POV-Ray for Windows v3.6\INCLUDE"

(You do have POV 3.6 (e.g. 3.6.1c) installed, don't you?)


> and in the Megapov GUI under 'set search paths for additional include files' I
> have: MegaPOV_C_UB/Insert Menu/20-Include files   which is where colors.inc is
> located (or I guess it's actually colors.inc.txt)

Um... I've never seen this option in MegaPOV 1.2.1... hum... maybe you should
add some info what OS you're actually using - I was assuming Windows, but
currently only you really know...

[phendric] megaPov #include files can't be found [6256 days 12 hours and 56 minutes ago]

Tue, 3 Mar 2009 20:45:00 GMT

I apologize if this seems a silly question, but my concern is when I run
megapov, include files such as #include "colors.inc" etc cannot be found when
the scene is rendered.  I have made no changes to the file hierarchy after
megapov was downloaded (I have downloaded povray was well) but I get this error

Parse Error: Cannot open include file colors.inc.

'Library_Path=' .INI item. Standard
 include files are in the include directory or folder. Please read your
documentation carefully.

my file hierarchy is as follows:
my scene is: MegaPOV_C_UB/scenes/demo.pov
and in the Megapov GUI under 'set search paths for additional include files' I
have: MegaPOV_C_UB/Insert Menu/20-Include files   which is where colors.inc is
located (or I guess it's actually colors.inc.txt)

Does anyone know why megapov cannot fine the include files?
Cheers,
Pat

[Thorsten Froehlich] Re: How to make POV-Ray run [6264 days 20 hours and 46 minutes ago]

Mon, 23 Feb 2009 12:54:56 GMT

maria wrote:
> Hello,
> Could you help me to make the POV-Ray working.
> 
> System Version: Mac OS X 10.4.11
> Installed the software POV-Ray
> 
> Run the application:
> Finder>Applications>POV-Ray 3.6>POV-Ray Mac 3.6 Folder>POV-Ray Mac 3.6
> 
> With editor:TextEdit
> create file and named it demo.pov, and saved in a folder: username/pov/demo.pov
> 
> content on file is as per PDF(5.0MB) Documentation on this website:
> 
>   #include "colors.inc"    // The include files contain
> //  #include "stones.inc"    // pre-defined scene elements
> background { color Cyan }
>   camera {
>     location <0, 2, -3>
>     look_at  <0, 1,  2>
>   }
>   sphere {
>     <0, 1, 2>, 2
>     texture {
>       pigment { color Yellow }
>     }
>   }
> // color red 1.0 green 0.8 blue 0.8  // nice shade of pink can be specified
> // color rgb <1.0, 0.8, 0.8>   // The following produces the same shade of pink
> // rgb <1.0, 0.8, 0.8>  // shortest way to specify the pink color is
> light_source { <2, 4, -3> color White}
> 
> Saved with name demo.pov
> and tried to render it, but how?
> tried from Terminal, Applications>Utilities>Terminal:
> 
> Macintosh:~ mari$ povray +Idemo.pov
> -bash: povray: command not found
> Macintosh:~ mari$
> 
> Nothing happens, tried:
> 
> Macintosh:~ mari$ povray +Idemo.pov +Odemo.png +D +P +W800 +H800 +A
> -bash: povray: command not found
> Macintosh:~ mari$

All this is the wrong way to go. You apparently followed the Unix tutorial 
in the documentation...

> Tried from POV-Ray:
> File>New
> copy the file here
> and in POV-Ray: File>Save as: demo1.pov
> but cannot render on the option:
> Render>Start Render is grey not able to select it.

Make sure you did actually assign the extension. If you are unsure, in the 
POV-Ray preferences disables rendering of ".pov" files only so it will 
render with files of any extension.

	Thorsten, POV-Team

[Bill Pragnell] Re: How to make POV-Ray run [6264 days 23 hours and 6 minutes ago]

Mon, 23 Feb 2009 10:35:01 GMT

If I understood correctly, you tried to run POV-Ray from the Applications
directory via Finder? This the right way to do it; however, there may be a
problem. If you have an Intel Mac, POV-Ray 3.6 will not work. You'll see the
splash screen and (briefly) its main gui, but then it exits.

If this is the case, then Ricky's solution is the only way to use POV3.6.
Otherwise, use MegaPOV - this will run properly.

Bill

[triple r] Re: How to make POV-Ray run [6265 days 2 hours and 36 minutes ago]

Mon, 23 Feb 2009 07:05:01 GMT

"maria" <mar### [at] gmailcom> wrote:
> Macintosh:~ mari$ povray +Idemo.pov
> -bash: povray: command not found

To use this approach, you will have to actually install the command line
version.  It is not enough to install the Mac version.  If you wish to do this,
an approach I have had good luck with, you will first need the developer tools
(XCode) from the apple website, http://developer.apple.com .  After this you
must download the unix/linux/generic source code for POV-Ray.  Go to the
uncompressed directory and type './configure', followed by 'make', and finally
'sudo make install'.  If this completes successfully, POV-Ray should be
installed so that you can call it from the command line.  Sorry if this is too
much or not enough detail, but just let me know if you need clarification.

> Tried from POV-Ray:
> File>New
> copy the file here
> and in POV-Ray: File>Save as: demo1.pov
> but cannot render on the option:
> Render>Start Render is grey not able to select it.

My only guess is that you may have to set some render preferences or check all
of the menus for something that would make rendering unavailable.  Usually when
the file is saved, you should be able to render.  Unfortunately since I have Mac
OS 10.5.6, I can't test this since the GUI version will not open for me.

If you don't mind the terminal, I recommend that approach overall since I find
it more dependable, but many people prefer the GUI version.  Of course I am
unable to help you with that, but perhaps someone else around can give better
advice.  Good luck.

 - Ricky

[maria] How to make POV-Ray run [6265 days 9 hours and 41 minutes ago]

Mon, 23 Feb 2009 00:00:00 GMT

Hello,
Could you help me to make the POV-Ray working.

System Version: Mac OS X 10.4.11
Installed the software POV-Ray

Run the application:
Finder>Applications>POV-Ray 3.6>POV-Ray Mac 3.6 Folder>POV-Ray Mac 3.6

With editor:TextEdit
create file and named it demo.pov, and saved in a folder: username/pov/demo.pov

content on file is as per PDF(5.0MB) Documentation on this website:

  #include "colors.inc"    // The include files contain
//  #include "stones.inc"    // pre-defined scene elements
background { color Cyan }
  camera {
    location <0, 2, -3>
    look_at  <0, 1,  2>
  }
  sphere {
    <0, 1, 2>, 2
    texture {
      pigment { color Yellow }
    }
  }
// color red 1.0 green 0.8 blue 0.8  // nice shade of pink can be specified
// color rgb <1.0, 0.8, 0.8>   // The following produces the same shade of pink
// rgb <1.0, 0.8, 0.8>  // shortest way to specify the pink color is
light_source { <2, 4, -3> color White}

Saved with name demo.pov
and tried to render it, but how?
tried from Terminal, Applications>Utilities>Terminal:

Macintosh:~ mari$ povray +Idemo.pov
-bash: povray: command not found
Macintosh:~ mari$

Nothing happens, tried:

Macintosh:~ mari$ povray +Idemo.pov +Odemo.png +D +P +W800 +H800 +A
-bash: povray: command not found
Macintosh:~ mari$


Tried from POV-Ray:
File>New
copy the file here
and in POV-Ray: File>Save as: demo1.pov
but cannot render on the option:
Render>Start Render is grey not able to select it.

Well, could you advice, how it works?
I am not able to find the option to render it and see the picture.

Thank you,
Mari

[societyofrobots] Re: Configuring POVray for use with Eagle 3D [6287 days and 56 minutes ago]

Sun, 1 Feb 2009 08:45:00 GMT

Probably a year too late for you, but this is a tutorial I wrote up:
http://www.societyofrobots.com/electronics_Eagle3D_tutorial.shtml

Tiger <nos### [at] nospam> wrote:
> I'm a complete newbie when it comes to POVray and need some help
> configuring and using it.
> I'm on a Powerbook G4 (1.67GHz) running MacOS 10.4.10.
> I've installed POVray 3.6.
>
> I barely know what POVray is (excuse my ignorance), but have an interest
> in it because of "Eagle 3D" which is a script that produces a .POV file
> out of an electronic circuit board design.
> The POV file is then (as far as I know) run through POVray to create a
> 3-dimensional drawing of the actual circuit board.
> Check out this website for more info about Eagle 3D as well as pictures:
> http://www.matwei.de/doku.php?id=en:eagle3d:eagle3d
>
> What I've done so far is download the installation files from the above
> site, the direct file-link being:
>
http://www.matwei.de/lib/exe/fetch.php?id=en%3Aeagle3d%3Aeagle3d&cache=cache&media=files:eagle3d:eagle3d_1_05_2711200
6.zip
>
> And then I placed the ULP (script file) where my electronic design
> application; Eagle (http://www.cadsoft.de/) can find it.
>
> However, when it comes to POVray and how to treat the Eagle-generated
> .POV file I'm totally lost.
> I've so far double-clicked the POV file which loaded it into POVray, and
> following that I assumed that I should just go to the "Render" menu and
> choose to render this file. Well, I seemed to have gotten several error
> messages.
> Upon contacting the author of Eagle 3D I was told that I need to tell
> POVray the location of a specific folder which came with Eagle 3D.
> However, I don't see any way of configuring this in POVray.
>
> A folder named "POVray" comes with Eagle 3D which contains the following
> files:
>
> total 1712
> -rwx------   1   21456 Nov 27  2006 alphalcd.ttf
> -rw-r--r--   1   39231 Nov 27  2006 cap.inc
> -rw-r--r--   1   13141 Nov 27  2006 capwima.inc
> -rw-r--r--   1      78 Nov 27  2006 col.inc
> -rw-r--r--   1  210961 Nov 27  2006 connector.inc
> -rw-r--r--   1   65218 Nov 27  2006 diode.inc
> -rwx------   1   54344 Nov 27  2006 eagle3d.ttf
> -rw-r--r--   1   59350 Nov 27  2006 ic.inc
> -rw-r--r--   1   14237 Nov 27  2006 qfp.inc
> -rw-r--r--   1   81236 Nov 27  2006 resistor.inc
> -rw-r--r--   1   16955 Nov 27  2006 socket.inc
> -rw-r--r--   1   95898 Nov 27  2006 special.inc
> -rw-r--r--   1   48831 Nov 27  2006 switch.inc
> -rwx------   1     223 Nov 27  2006 tex_elko.png
> -rwx------   1    3039 Nov 27  2006 tex_elko_axial.png
> -rw-r--r--   1   46472 Nov 27  2006 tools.inc
> -rw-r--r--   1   33623 Nov 27  2006 trafo.inc
> -rw-r--r--   1   31581 Nov 27  2006 transistor.inc
> -rw-r--r--   1       0 Nov 27  2006 user.inc
>
>
> I tried placing all those files in POVray's "include" folder, but I'm
> still getting error messages when I try to render the POV file, so I
> assume I have to place them somewhere else or I'm not understanding how
> to use POVray properly.
> Here are those error messages:
>
>
> POV-Ray 3.6 for Mac OS Frontend Build 197
> Copyright © 1991-2003 Persistence of Vision Team™
> Copyright © 2003-2004 Persistence of Vision Raytracer Pty. Ltd.
> Persistence of Vision(tm) Ray Tracer Version 3.6.1 (Mac CodeWarrior)
> This is an official version prepared by the POV-Ray Team. See the
>   documentation on how to contact the authors or visit us on the
>   internet at http://www.povray.org/.
> POV-Ray is based on DKBTrace 2.12 by David K. Buck & Aaron A. Collins
> Copyright 1991-2003 Persistence of Vision Team
> Copyright 2003-2004 Persistence of Vision Raytracer Pty. Ltd.
> Parsing Options
>    Input file: Internal_drive:Users:Tiger:Desktop:test.pov (compatible
> to version 3.60)
>    Remove bounds........On   Split unions.........On
>    Library paths:
> Output Options
>    Image resolution 160 by 120 (rows 0 to 120, columns 0 to 160).
>    Output file: test.pict, 24 bpp (system format)
>    Graphic display.....On  (gamma:  1.8)
>    Mosaic preview.......Off
>    CPU usage histogram.Off
>    Continued trace......Off
> Tracing Options
>    Quality:  9
>    Bounding boxes......On  Bounding threshold: 1
>    Light Buffer.........On   Vista Buffer.........On   Draw Vista
> Buffer....Off
>    Antialiasing........Off
>    Radiosity............Off
> Animation Options
>    Clock value....   0.000  (Animation off)
> Possible Parse Error: Could not find file 'tools.inc'
>
> File test.pov line 117
> Parse Error: Cannot open include file tools.inc.
>
> File test.pov line 117
> Parse Warning: Check that the file is in a directory specifed with a +L
> switch or 'Library_Path='
> .INI item. Standard include files are in the include directory or
> folder. Please read your
> documentation carefully.
>
> File test.pov line 117
> Total Scene Processing Times
>    Parse Time:    0 hours  0 minutes  0 seconds (0 seconds)
>    Photon Time:   0 hours  0 minutes  0 seconds (0 seconds)
>    Render Time:   0 hours  0 minutes  0 seconds (0 seconds)
>    Total Time:    0 hours  0 minutes  0 seconds (0 seconds)

[triple r] Re: Any solution on failure of POV-RAY 3.6 on in... [6292 days 15 hours and 16 minutes ago]

Mon, 26 Jan 2009 18:25:00 GMT

"jasonkrupert" <jas### [at] yahoocom> wrote:

> Triple R - Thank you for your follow-up.  What are you suggesting?
>
> Are you suggesting to try to recompile POVRay on the OS 10.5 Intel machine and
> see if it works?
>
> Has this been tried successfully before?

Oops.  Sorry for such a delay.  I didn't notice the reply.  My advice though, is
that if you take the "Unix / Linux / Generic Source Code" from the download page
and compile it through the OS X terminal, you should have no problems.  I also
thought it would be interesting to compare something likePOV-Ray natively
compiled and run through Rosetta, just to see the difference in performance,
except the old version doesn't seem to run on all computers.

 - Ricky

[Bill Pragnell] Re: POVRay Mac versuses PC [6299 days 22 hours and 41 minutes ago]

Mon, 19 Jan 2009 11:00:00 GMT

"jasonkrupert" <jas### [at] yahoocom> wrote:
> "Woody" <nomail@nomail> wrote:
> > Hi, Im quickly becoming discusted with MY PC laptop and an seriously considering
> > getting a MacBook.
> >
> > Are there any users out there who have used POVRay on both a Mac and PC?
> >
> > Any advanatages of one over the other?
> >
> > How do they compare/Contrast?
> >
> > Any Help would be greatly appreciated?
>
> Sadly recommend sticking with the Windows version.   Seem to be problems with
> POVRay on OS 10.5 on Intel Mac machines.   I am experiencing a problem right
> now where POVRay won't even launch correctly.

Somebody else suggested it too, but it's worth reiterating:

MegaPOV works perfectly on the Intel Macs! It does everything the current
official version does (and more). As long as you're happy with this version,
it's the way to go for the time being.

http://megapov.inetart.net/

[jasonkrupert] Re: Any solution on failure of POV-RAY 3.6 on in... [6300 days 12 hours and 41 minutes ago]

Sun, 18 Jan 2009 21:00:01 GMT

"triple_r" <nomail@nomail> wrote:
> "jasonkrupert" <jas### [at] yahoocom> wrote:
>
> > Identifier:      POV-Ray Mac 3.6
> > Version:         ??? (56721408)
> > Code Type:       PPC (Translated)
> > Parent Process:  launchd [63]
>
> > Translated Code Information:
> > Rosetta Version:  21.03
>
> Sorry in advance that I can't offer a solution.  Also, I suppose you can't
> benchmark something that won't run, but it might be better (if you care about
> speed) to run it natively by compiling the unix version yourself.  I found this
> very simple to do, and it looks like Rosetta performance is about 50% that of
> native performance.  I'm no expert on this, but only took a quick look at the
> following:
>
> http://www.geekpatrol.ca/2006/02/rosetta-performance/
>
> I could be completely wrong about performance, but this seems reasonable, even
> pretty good.
>
>  - Ricky

Triple R - Thank you for your follow-up.  What are you suggesting?

Are you suggesting to try to recompile POVRay on the OS 10.5 Intel machine and
see if it works?

Has this been tried successfully before?

Thanks.

[jasonkrupert] Re: POVRay Mac versuses PC [6300 days 12 hours and 46 minutes ago]

Sun, 18 Jan 2009 20:55:00 GMT

"Woody" <nomail@nomail> wrote:
> Hi, Im quickly becoming discusted with MY PC laptop and an seriously considering
> getting a MacBook.
>
> Are there any users out there who have used POVRay on both a Mac and PC?
>
> Any advanatages of one over the other?
>
> How do they compare/Contrast?
>
> Any Help would be greatly appreciated?

Sadly recommend sticking with the Windows version.   Seem to be problems with
POVRay on OS 10.5 on Intel Mac machines.   I am experiencing a problem right
now where POVRay won't even launch correctly.

[triple r] Re: Any solution on failure of POV-RAY 3.6 on in... [6301 days 4 hours and 41 minutes ago]

Sun, 18 Jan 2009 05:00:00 GMT

"jasonkrupert" <jas### [at] yahoocom> wrote:

> Identifier:      POV-Ray Mac 3.6
> Version:         ??? (56721408)
> Code Type:       PPC (Translated)
> Parent Process:  launchd [63]

> Translated Code Information:
> Rosetta Version:  21.03

Sorry in advance that I can't offer a solution.  Also, I suppose you can't
benchmark something that won't run, but it might be better (if you care about
speed) to run it natively by compiling the unix version yourself.  I found this
very simple to do, and it looks like Rosetta performance is about 50% that of
native performance.  I'm no expert on this, but only took a quick look at the
following:

http://www.geekpatrol.ca/2006/02/rosetta-performance/

I could be completely wrong about performance, but this seems reasonable, even
pretty good.

 - Ricky

[triple r] Re: POVRay Mac versuses PC [6301 days 4 hours and 56 minutes ago]

Sun, 18 Jan 2009 04:45:00 GMT

"jasonkrupert" <jas### [at] yahoocom> wrote:

> Be aware that POVRay appears to crash on MacBookPro with OS 10.5.6.  I have a
> new machine and discovered this software and tried to use it and it crashes.
> Apparently others with OS 10 are also seeing this behavior.  Thus, my naive
> recommendation is "if it ain't broke don't" switch. (Hurts me to say this since
> I love my Mac).

To be fair, that doesn't prevent you from using POV-Ray altogether.  I also have
OS 10.5.6 on a MacBook Pro and didn't notice any problems, although I prefer the
command-line versions of POV-Ray, MegaPOV, and MC-POV.  If that fails, you can
also install Ubuntu and Windows XP for a triple-boot system.  I don't use them
very often, but have had good luck with POV-Ray under both of those.

 - Ricky

[jasonkrupert] Re: POVRay Mac versuses PC [6301 days 5 hours and 26 minutes ago]

Sun, 18 Jan 2009 04:15:01 GMT

"Woody" <nomail@nomail> wrote:
> Hi, Im quickly becoming discusted with MY PC laptop and an seriously considering
> getting a MacBook.
>
> Are there any users out there who have used POVRay on both a Mac and PC?
>
> Any advanatages of one over the other?
>
> How do they compare/Contrast?
>
> Any Help would be greatly appreciated?

Be aware that POVRay appears to crash on MacBookPro with OS 10.5.6.  I have a
new machine and discovered this software and tried to use it and it crashes.
Apparently others with OS 10 are also seeing this behavior.  Thus, my naive
recommendation is "if it ain't broke don't" switch. (Hurts me to say this since
I love my Mac).

[jasonkrupert] Re: Any solution on failure of POV-RAY 3.6 on in... [6301 days 5 hours and 31 minutes ago]

Sun, 18 Jan 2009 04:10:00 GMT

I believe I also received the same problem.  I do not believe I have an abnormal
configuration of my MacBook Pro.  Not exactly sure what that would be?

Any how, here is a copy of the report that was generated (hope this helps as I
just tried to open the application and it crashed):


Process:         POV-Ray Mac 3.6 [394]
Path:            /Applications/POV-Ray 3.6/POV-Ray Mac 3.6 Folder/POV-Ray Mac
3.6
Identifier:      POV-Ray Mac 3.6
Version:         ??? (56721408)
Code Type:       PPC (Translated)
Parent Process:  launchd [63]

Date/Time:       2009-01-17 22:06:05.866 -0600
OS Version:      Mac OS X 10.5.6 (9G55)
Report Version:  6

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000004
Crashed Thread:  0

Thread 0 Crashed:
0   translate                      0xb80bcd58 0xb8000000 + 773464
1   translate                      0xb80b7007 0xb8000000 + 749575
2   translate                      0xb80d49c0 0xb8000000 + 870848
3   translate                      0xb813ce79 spin_lock_wrapper + 1981

Thread 1:
0   ???                            0x800bc1c6 0 + 2148254150
1   ???                            0x800c39bc 0 + 2148284860
2   translate                      0xb818b6ea CallPPCFunctionAtAddressInt +
202886
3   ???                            0x800ed095 0 + 2148454549
4   ???                            0x800ecf52 0 + 2148454226

Thread 2:
0   translate                      0xb8152b34 spin_lock_wrapper + 91256
1   translate                      0xb8167dce CallPPCFunctionAtAddressInt +
57194
2   translate                      0xb80bdb8b 0xb8000000 + 777099
3   translate                      0xb80b7007 0xb8000000 + 749575
4   translate                      0xb80d49c0 0xb8000000 + 870848
5   translate                      0xb813d75f spin_lock_wrapper + 4259

Thread 3:
0   translate                      0xb8152c24 spin_lock_wrapper + 91496
1   translate                      0xb816c825 CallPPCFunctionAtAddressInt +
76225
2   translate                      0xb80bdb8b 0xb8000000 + 777099
3   translate                      0xb80b7007 0xb8000000 + 749575
4   translate                      0xb80d49c0 0xb8000000 + 870848
5   translate                      0xb813d75f spin_lock_wrapper + 4259

Thread 4:
0   translate                      0xb81529ef spin_lock_wrapper + 90931
1   translate                      0xb8183633 CallPPCFunctionAtAddressInt +
169935
2   translate                      0xb81861e2 CallPPCFunctionAtAddressInt +
181118
3   translate                      0xb80bdb8b 0xb8000000 + 777099
4   translate                      0xb80b7007 0xb8000000 + 749575
5   translate                      0xb80d49c0 0xb8000000 + 870848
6   translate                      0xb813d75f spin_lock_wrapper + 4259

Thread 5:
0   translate                      0xb80a101b 0xb8000000 + 659483
1   translate                      0xb815d27b CallPPCFunctionAtAddressInt +
13335
2   translate                      0xb816f06c CallPPCFunctionAtAddressInt +
86536
3   translate                      0xb80dfb0b 0xb8000000 + 916235

Thread 0 crashed with X86 Thread State (32-bit):
  eax: 0x00000004  ebx: 0xb80bcd30  ecx: 0x00000000  edx: 0x00000003
  edi: 0x00000004  esi: 0x80303820  ebp: 0xb7fffa08  esp: 0xb7fff9d0
   ss: 0x0000001f  efl: 0x00010206  eip: 0xb80bcd58   cs: 0x00000017
   ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
  cr2: 0x00000004

Binary Images:
0xb8000000 - 0xb81d7fe7  translate ??? (???) /usr/libexec/oah/translate

Translated Code Information:
Rosetta Version:  21.03
Args:
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp
/Applications/POV-Ray 3.6/POV-Ray Mac 3.6 Folder/POV-Ray Mac 3.6
Exception: EXC_BAD_ACCESS (0x0001)

Thread 0: (0xb0220ea8, 0xb816effd)
0x7ff43868: No symbol
0x7ff4744c: No symbol
0x7ff429ec: No symbol
0x7ff47394: No symbol
0x9545247c:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
: _PrivateMPEntryPoint + 80
0x9545247c:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
: _PrivateMPEntryPoint + 80
0x910c317c: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000:
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
+ 0

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
cr:  0xXXXXXXXX  xer: 0x00000000   lr: 0x7ff4744c  ctr: 0x91032280
r00: 0xffffffc5  r01: 0xf02afcd0  r02: 0x9546681c  r03: 0x00000000
r04: 0x00005000  r05: 0x00005000  r06: 0x00000000  r07: 0x0085fe00
r08: 0x0085fe00  r09: 0x000000ff  r10: 0x000000ff  r11: 0xa0269cc4
r12: 0x91032280  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00000000
r20: 0x00000000  r21: 0x00000000  r22: 0x00000000  r23: 0x00000000
r24: 0x00000000  r25: 0x00000000  r26: 0x00000000  r27: 0x00000000
r28: 0x00000000  r29: 0x00879000  r30: 0x15f90d88  r31: 0xf02afd60

Thread 1: (0xb019e77c, 0xb81529ef)
0x00000000:
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
+ 0
0x95481bc8:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
: _YieldToThread + 532
0x954819a4:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
: _YieldToAnyThread + 20
0x852d10c4: No symbol
0x95486df4:
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
: _CooperativeThread + 348
0x910c317c: /usr/lib/libSystem.B.dylib : __pthread_body + 40

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
cr:  0xXXXXXXXX  xer: 0x00000000   lr: 0x91039080  ctr: 0x91032150
r00: 0xffffffe1  r01: 0xf0182c90  r02: 0x00000013  r03: 0xf0182d3c
r04: 0x00000003  r05: 0x00000018  r06: 0x00000020  r07: 0x00006607
r08: 0x00000000  r09: 0x00000000  r10: 0x00000000  r11: 0xa0269694
r12: 0x91032150  r13: 0x00000000  r14: 0x00000000  r15: 0x00000000
r16: 0x00000000  r17: 0x00000000  r18: 0x00000000  r19: 0x00000000
r20: 0x00000000  r21: 0x00000000  r22: 0x00000000  r23: 0x00000018
r24: 0xf0182d3c  r25: 0x00000020  r26: 0x00006607  r27: 0x00000000
r28: 0x00000000  r29: 0x00000003  r30: 0x00000003  r31: 0x954819bc

Thread 2: (0xb011cd38, 0xb8152c24)
0x9107528c: /usr/lib/libSystem.B.dylib : __pthread_cond_wait + 1260
0x0044804c:
/System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport
: _CarbonOperationThreadFunc + 136
0x910c317c: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000:
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
+ 0

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
cr:  0xXXXXXXXX  xer: 0x00000000   lr: 0x910753d0  ctr: 0x9103d45c
r00: 0x0000014e  r01: 0xf0101a50  r02: 0xf0101a90  r03: 0x00003603
r04: 0x00003703  r05: 0x00000000  r06: 0x00000000  r07: 0x00000000
r08: 0x00000000  r09: 0x00000001  r10: 0xfffffff1  r11: 0xa026993c
r12: 0x9103d45c  r13: 0xf0101b28  r14: 0xf0101b24  r15: 0xf0101b20
r16: 0xf0101b1c  r17: 0xf0101b18  r18: 0xf0101ce8  r19: 0x00000000
r20: 0x00000000  r21: 0x00000000  r22: 0x00000000  r23: 0x00000000
r24: 0x00000000  r25: 0x00000000  r26: 0x00000000  r27: 0xa0264db4
r28: 0x0011b130  r29: 0x00819200  r30: 0x0011b0d8  r31: 0x91074db4

Thread 3: Crashed (0xb7fff9d0, 0xb80bcd58)
0x8536a3cc: No symbol
0x852d7a9c: No symbol
0x852d6830: No symbol
0x853cfd14: No symbol

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
cr:  0xXXXXXXXX  xer: 0x20000000   lr: 0x8537380c  ctr: 0x9106d000
r00: 0x852d7a9c  r01: 0xbfffed30  r02: 0x003f1000  r03: 0x00000000
r04: 0x00000000  r05: 0x00000447  r06: 0x00000000  r07: 0x00000000
r08: 0x00000000  r09: 0xa029e830  r10: 0x000005b9  r11: 0xa091dbe8
r12: 0x9106d000  r13: 0x00000000  r14: 0x00000000  r15: 0x00000016
r16: 0x00000000  r17: 0x00000000  r18: 0x003fc530  r19: 0x003fd200
r20: 0x003fdb20  r21: 0x003fd2d0  r22: 0x003feb10  r23: 0x15daa5a0
r24: 0x00108920  r25: 0x003fa0f0  r26: 0xbffff6f4  r27: 0x003efb7c
r28: 0x00000000  r29: 0x00000000  r30: 0x00000009  r31: 0x00000000

Thread 4: (0xb009ad68, 0xb8152b34)
0x00446e34:
/System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport
: _BSD_watchevent + 44
0x0044bfb8:
/System/Library/PrivateFrameworks/OpenTransport.framework/Versions/A/OpenTransport
: _CarbonSelectThreadFunc + 204
0x910c317c: /usr/lib/libSystem.B.dylib : __pthread_body + 40
0x00000000:
/System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp :
+ 0

PPC Thread State
srr0: 0x00000000 srr1: 0x00000000               vrsave: 0x00000000
cr:  0xXXXXXXXX  xer: 0x00000000   lr: 0x00446ea0  ctr: 0x910876c0
r00: 0x00000000  r01: 0xf0080d60  r02: 0x00464010  r03: 0x000000e8
r04: 0xf0080e34  r05: 0x00000000  r06: 0x00000000  r07: 0x01000000
r08: 0x00000000  r09: 0x01000000  r10: 0x00000000  r11: 0x0046442c
r12: 0x910876c0  r13: 0x00464010  r14: 0x00000000  r15: 0x00464010
r16: 0x00464008  r17: 0xf0080e18  r18: 0x0046befc  r19: 0xf0080e0c
r20: 0xf0080dfc  r21: 0xf0080e08  r22: 0xf0080e34  r23: 0x00000000
r24: 0x0046befc  r25: 0x00464010  r26: 0x00000000  r27: 0xf0080e04
r28: 0xf0080e34  r29: 0x00000000  r30: 0x00464010  r31: 0x0044befc

[Thorsten Froehlich] Re: Any solution on failure of POV-RAY 3.6 on in... [6327 days and 35 minutes ago]

Tue, 23 Dec 2008 09:05:42 GMT

QKRS WEB wrote:
> "hauskurz" <kur### [at] biochemwustledu> wrote:
> 
>> What is probably needed is a universal binary.  Has anyone
>> solved this problem?
> 
> In theory, the application just needs to be tweaked with
> a tool such as "Resorcerer" http://www.mathemaesthetics.com
> to set the "Application (Universal)" flag.
> 
> Looking at it from "Resorcerer," the PowerPC native "cfrg" Code Fragment
> resource looks right but the "carb" Carbon Direct Launch resource is set to
> "0."
> 
> My hunch is that something has to be set to invoke Rosetta (the PowerPC
> Emulator) when Carbon Direct Launch is called.
> 
> I'm hunting around for a working Universal Application ported from PowerPC to
> open under "Resorcerer" to confirm the hunch.

POV-Ray 3.6 is not a universal application. Please see the note on the 
website. The problem is within Apple's PowerPC emulator and only occurs on 
some systems x86 systems running Mac OS X 10.4 as well as on Mac OS X 10.5.

	Thorsten, POV-Team

[QKRS WEB] Re: Any solution on failure of POV-RAY 3.6 on in... [6327 days 7 hours and 46 minutes ago]

Tue, 23 Dec 2008 01:55:00 GMT

"hauskurz" <kur### [at] biochemwustledu> wrote:

> What is probably needed is a universal binary.  Has anyone
> solved this problem?

In theory, the application just needs to be tweaked with
a tool such as "Resorcerer" http://www.mathemaesthetics.com
to set the "Application (Universal)" flag.

Looking at it from "Resorcerer," the PowerPC native "cfrg" Code Fragment
resource looks right but the "carb" Carbon Direct Launch resource is set to
"0."

My hunch is that something has to be set to invoke Rosetta (the PowerPC
Emulator) when Carbon Direct Launch is called.

I'm hunting around for a working Universal Application ported from PowerPC to
open under "Resorcerer" to confirm the hunch.

All the best ... /qkrs

[John Smith] Xgrid Agent Security in Windows [6332 days 17 hours and 56 minutes ago]

Wed, 17 Dec 2008 15:45:00 GMT

hi,

I am recently playing around the Xgrid technology.
In my setup, an iMac is acting as a controller, coordinating a bunch of Mac,
Linux and Windows machines. I managed to hook the non-Mac os platforms into the
Xgrid network by using the XgirdAgent-Java, which can be found on:
http://sourceforge.net/projects/xgridagent-java/

My intention of this post is to ask if anyone is aware of the security for using
xgridagent on Windows. In Linux, we would be able to create a sandbox easily for
the xgrid agent process.

However, if I run the xgridagent in windows, it exposed my entire file structure
to the Xgrid network. I could submit a java programme to read, write delete
files in C:\ drive.

In addition, if I submit DOS commands such as "dir, cd, copy, del, etc", they
don't work as they are not "recognized as a command".

Any suggestions?

[hauskurz] Any solution on failure of POV-RAY 3.6 on intel ... [6337 days 18 hours and 56 minutes ago]

Fri, 12 Dec 2008 14:45:01 GMT

I really miss being able to render my figures in POV-RAY. This problem has been
reported mutliple times and the home page even states it is not a bug but an
apple problem but siggests it is some kind of configuration problem.  Any idea
of how to fix???   What is probably needed is a universal binary.  Has anyone
solved this problem? Apple is not going to rewrite the emulator.
I am getting the Pov-Ray unexpectedly quit message that everyone else is
getting.

[Bill Pragnell] Re: Newbie+old posting:Pov-Ray 3.6 and Mac OS 10... [6356 days and 6 minutes ago]

Mon, 24 Nov 2008 09:35:00 GMT

"Peter" <nomail@nomail> wrote:
> "Peter" <nomail@nomail> wrote:
> > Hello,
> > I solved my question about Stuffit. But!!
> > I have the same experience as in the old posting: Pov-Ray 3.6 and Mac OS 10.5
> > Leopard
> > It has (15) but as far as I can see: no solution to this problem.
> > My problem is the same: pov-ray quits unexpectedly (a message window and a
> > template window).
> > Any suggestion?
> > with friendly greetings,
> > Peter
>
> Ok. I understood the text in the Mac Os download. Maybe the formulation could be
> shorter: that POV-Ray does not work for the Mac Intel.
> with friendly greetings,

POV-Ray 3.6 does not work, but MegaPov does:
http://megapov.inetart.net/

You can treat megapov just like a normal version of POV-Ray, and there are
additional features too.

Bill

[Peter] Re: Newbie+old posting:Pov-Ray 3.6 and Mac OS 10... [6356 days 11 hours and 16 minutes ago]

Sun, 23 Nov 2008 22:25:01 GMT

"Peter" <nomail@nomail> wrote:
> Hello,
> I solved my question about Stuffit. But!!
> I have the same experience as in the old posting: Pov-Ray 3.6 and Mac OS 10.5
> Leopard
> It has (15) but as far as I can see: no solution to this problem.
> My problem is the same: pov-ray quits unexpectedly (a message window and a
> template window).
> Any suggestion?
> with friendly greetings,
> Peter

Ok. I understood the text in the Mac Os download. Maybe the formulation could be
shorter: that POV-Ray does not work for the Mac Intel.
with friendly greetings,
Peter

[Peter] Newbie+old posting:Pov-Ray 3.6 and Mac OS 10.5 L... [6356 days 11 hours and 36 minutes ago]

Sun, 23 Nov 2008 22:05:00 GMT

Hello,
I solved my question about Stuffit. But!!
I have the same experience as in the old posting: Pov-Ray 3.6 and Mac OS 10.5
Leopard
It has (15) but as far as I can see: no solution to this problem.
My problem is the same: pov-ray quits unexpectedly (a message window and a
template window).
Any suggestion?
with friendly greetings,
Peter

[Peter] Newbie+Stuffit refuses to open povpmac.sit under... [6356 days 12 hours and 21 minutes ago]

Sun, 23 Nov 2008 21:20:01 GMT

Hello,
I downloaded for the the MacBookPro pov-ray under MacOs 10.4.11
Stuffit refused to open povpmac.sit.
Any suggestions? If I go for a free version of Stuffit, I get the impression I
still must buy some item before I get the download.
Can anyone help me here?
Peter

[HelveticaFanatic] Spline editor [6463 days 15 hours and 21 minutes ago]

Fri, 8 Aug 2008 18:20:01 GMT

What can I use as a spline editor on a Mac? I have MegaPOV which has a spline
editor with coordinates up to 1 that I could use possibly (if I scale it up),
but does something else work better? I need coordinates up to about 1,000.
Thanks.

[Tim Nikias] POV-Ray on Intel Mac AND two versions at once? [6517 days 22 hours and 2 minutes ago]

Sun, 15 Jun 2008 11:38:38 GMT

Hello all!

I'm fairly new to the Mac (half a year now, roughly) and just yesterday 
compiled POV-Ray 3.6.1 on it, tinkered around and figured where stuff is 
supposed to go and to get set in order to work the way I'm used to from 
my WinXP PC.

Now, the 3.6 version has a little (known) bug in relation to macros and 
passing on arguments. Sometimes it won't return/update the parameters 
and instead leave them at the old value when the macro is finished. 
AFAIK (haven't been POV-active for some time now) there was/is no 
"official" fix, because the problem seems to be related to the 
compilers, not the source-code.

So, two questions: IF there is a working fix, can someone point me to 
it? I could modify the source accordingly (given that the fix is easy to 
understand, I'm not that experienced with coding and compiling) and 
compile my own version of 3.6.1.t (t for Tim ;-).

Or, the other solution (which worked fine for me on the PC) is to 
install/compile POV-Ray 3.5, which didn't have the macro-parameter-bug.

However, I have no clue how to set that up properly, because I figure 
both compilations would end up with a console-command "povray". Any 
pointers to a Mac-Newbie on how to solve that "properly", e.g. would 
renaming the 3.5 povray to povray35 hurt? And some files just install to 
a folder named povray, with no 3.6 subfolder or such, so I'd be 
overwriting files, wouldn't I?

I'll probably be tinkering with it all at work today, but even though I 
MIGHT find a solution, I'd rather not spend days recompiling the sources 
a couple of times a day to repair what I damaged. ;-)

Regards,
Tim

-- 
aka "Tim Nikias"
Homepage: <http://www.nolights.de>

[Yvo Smellenbergh] Re: Quicktime direct from MegaPOV [6566 days 14 hours and 58 minutes ago]

Sun, 27 Apr 2008 18:43:20 GMT

Kevin <Kev### [at] Karneycom> wrote:

Kevin,

The current version of MegaPOV doesn't support direct output to
QuickTime movie. The next release will support it again. You can use
QuickTime Pro or GraphicConverter to create a movie from the images
created by MegaPOV. This is also much safer to do and is much more
flexible. You can not continue a render when you save directly to a
movie, you can not render only a few frames and in case your computer
crashes in the middle of a long render you loose all your work instead
of only one image.

Yvo

> Having just acquired a brand new Intel based IMac, I found the that the
> official POV does not work, as has been reported before.
> 
> I was delighted to find MegaPov - which works just fine and is a MAJOR
> improvement on the official version.  But I do not seem to be able to
> animate directly into Quicktime, as I could do with the official POV.
> 
> Am I missing a trick? I really do not want to have to find a utility that
> will sting a bunch of images into a movie.... Can anyone help....
> 
> Best regards Kevin Karney

-- ----------------------------------- MegaPOV at:
http://megapov.inetart.net MacMegaPOV at:
http://users.skynet.be/smellenbergh E-mail: yvo### [at] gmxnet

[Kevin] Quicktime direct from MegaPOV [6566 days 18 hours and 26 minutes ago]

Sun, 27 Apr 2008 15:15:01 GMT

Having just acquired a brand new Intel based IMac, I found the that the official
POV does not work, as has been reported before.

I was delighted to find MegaPov - which works just fine and is a MAJOR
improvement on the official version.  But I do not seem to be able to animate
directly into Quicktime, as I could do with the official POV.

Am I missing a trick? I really do not want to have to find a utility that will
sting a bunch of images into a movie.... Can anyone help....

Best regards
Kevin Karney

[newbie] Re: Start Render is disabled. Why? [6582 days 23 hours and 11 minutes ago]

Fri, 11 Apr 2008 10:30:00 GMT

Thorsten Froehlich <tho### [at] trfde> wrote:
> newbie wrote:
> > "newbie" <nomail@nomail> wrote:
> >
> > I just found out what the issue is with POV. The text file it loads must have an
> > extention of ".pov" or the render command is disabled.
>
> Yes, because this option is enabled/disabled in the preferences...
>
>  Thorsten

Yes, I see that. IMHO the default should be that this option is disabled.

[Thorsten Froehlich] Re: Start Render is disabled. Why? [6583 days 21 hours and 7 minutes ago]

Thu, 10 Apr 2008 12:34:19 GMT

newbie wrote:
> "newbie" <nomail@nomail> wrote:
> 
> I just found out what the issue is with POV. The text file it loads must have an
> extention of ".pov" or the render command is disabled. 

Yes, because this option is enabled/disabled in the preferences...

	Thorsten

[newbie] Re: Start Render is disabled. Why? [6584 days 23 hours and 31 minutes ago]

Wed, 9 Apr 2008 10:10:00 GMT

"newbie" <nomail@nomail> wrote:

I just found out what the issue is with POV. The text file it loads must have an
extention of ".pov" or the render command is disabled. MegaPOV does not have
that requirement.

[newbie] Re: Start Render is disabled. Why? [6584 days 23 hours and 41 minutes ago]

Wed, 9 Apr 2008 10:00:00 GMT

"newbie" <nomail@nomail> wrote:

I've dug into other threads and discovered MegaPOV. Having downloaded
and installed it, I find that it renders just fine. I wonder what is wrong
with POV? I assume that the problem is with the GUI; it is as if the
framework does not realize that a file is open and active. Anyway, on to
MegaPOV.

[newbie] Start Render is disabled. Why? [6585 days 22 hours and 21 minutes ago]

Tue, 8 Apr 2008 11:20:00 GMT

I just downloaded POV 3.6 on my iBook G4 running OX X 10.5.2

After starting up POV, I created a new file and pasted a sample file
from a tutorial into it:

#include "colors.inc"
camera {
  location <-2, 3, -10>
  look_at <0, 5, 0>
}
plane { // the floor
  y, 0  // along the x-z plane (y is the normal vector)
  pigment { checker color Black color White } // checkered pattern
}
sphere {
  <0, 5, 0>, 2
  pigment { color White }
  finish {
    reflection 0.9
    phong 1
  }
}
light_source { <10, 10, -10> color White }
light_source { <-10, 5, -15> color White }

I put the focus on the file, but when I go to the Render menu,
the Start Render command is grayed out. I can't figure out why.
What am I missing here?

[Thorsten Froehlich] Re: Pov-Ray 3.6 and Mac OS 10.5 Leopard [6630 days 17 hours and 13 minutes ago]

Sat, 23 Feb 2008 16:28:04 GMT

Dennis Miller wrote:
>> it is Apple's problem...
> 
> (And you figure they are going to fix it?)

LOL - in the old days when Apple wasn't all about marketing and Jobs, yes, 
nowadays, no :-(

> What do you think the problem is? A shame not to work under the newest OS.

The problem is somewhere in the PowerPC emulator because that is were the 
crash is. It isn't in any POV-Ray code.

	Thorsten

[Dennis Miller] Re: Pov-Ray 3.6 and Mac OS 10.5 Leopard [6630 days 19 hours and 18 minutes ago]

Sat, 23 Feb 2008 14:23:05 GMT

>it is Apple's problem...

(And you figure they are going to fix it?)
What do you think the problem is? A shame not to work under the newest OS.

Best,
D.
"Thorsten Froehlich" <tho### [at] trfde> wrote in message 
news:47be63df@news.povray.org...
> Dennis Miller wrote:
>> Same problem on an Intel 8-core with 10.5.2.
>> Anyone looking into this?
>
> As I said, it is Apple's problem and outside the scope of POV-Ray to fix 
> as there is nothing to be fixed in POV-Ray.
>
> Thorsten

[Thorsten Froehlich] Re: Pov-Ray 3.6 and Mac OS 10.5 Leopard [6632 days 3 hours and 45 minutes ago]

Fri, 22 Feb 2008 05:55:43 GMT

Dennis Miller wrote:
> Same problem on an Intel 8-core with 10.5.2.
> Anyone looking into this?

As I said, it is Apple's problem and outside the scope of POV-Ray to fix as 
there is nothing to be fixed in POV-Ray.

	Thorsten

[Dennis Miller] Re: Pov-Ray 3.6 and Mac OS 10.5 Leopard [6632 days 4 hours and 32 minutes ago]

Fri, 22 Feb 2008 05:09:00 GMT

Same problem on an Intel 8-core with 10.5.2.
Anyone looking into this?
best.
d

"Thorsten Froehlich" <tho### [at] trfde> wrote in message 
news:472ad15e@news.povray.org...
> MacGuyver wrote:
>> Anyone out there trying to use Pov-Ray and Mac OS 10.5? Pov-Ray tries to 
>> open,
>> and seems to get most of the way, but then it unexpectedly quits on me. 
>> Has
>> anyone else had this problem? Better yet, has anyone found a solution?
>
> On a PowerPC or an Intel Mac?
>
> Thorsten

[Dennis Miller] Re: Pov-Ray 3.6 and Mac OS 10.5 Leopard [6636 days 7 hours and 31 minutes ago]

Mon, 18 Feb 2008 02:10:07 GMT

I have the exact problem with 10.5.2 on a new MacPro. unexpectedly quits 
after the splash screen.
I am running MegaPov on the same machine with no problem, FYI.

Best.
D.

"MacGuyver" <nomail@nomail> wrote in message 
news:web.472aa92c4eebd24716ada8f90@news.povray.org...
> Anyone out there trying to use Pov-Ray and Mac OS 10.5? Pov-Ray tries to 
> open,
> and seems to get most of the way, but then it unexpectedly quits on me. 
> Has
> anyone else had this problem? Better yet, has anyone found a solution?
>
> Thanks in advance,
> MacGuyver
>
>

[Anton Sherwood] Re: Leopard CLI [6646 days 15 hours and 39 minutes ago]

Thu, 7 Feb 2008 18:02:21 GMT

> Anton Sherwood wrote:
>> Eek! Since I installed Leopard, when I try to render from the shell I 
>> get: "Init Error:  The display '/tmp/launch-uGIbWC/:0' is not a valid 
>> display, or you do not have permission to open a window there."

Thorsten Froehlich wrote:
> Did you try to recompile?

Yes, without success at first, probably because "make" won't do anything 
if there exists an object file newer than the source file.

Then I deleted the source directory and recreated it, recompiled again; 
problem solved.

-- 
Anton Sherwood, http://www.ogre.nu/
"How'd ya like to climb this high *without* no mountain?" --Porky Pine

[Thorsten Froehlich] Re: Leopard CLI [6648 days 14 hours and 46 minutes ago]

Tue, 5 Feb 2008 18:54:33 GMT

Anton Sherwood wrote:
> Eek! Since I installed Leopard, when I try to render from the shell I 
> get: "Init Error:  The display '/tmp/launch-uGIbWC/:0' is not a valid 
> display, or you do not have permission to open a window there."

Did you try to recompile?

	Thorsten

[Anton Sherwood] Leopard CLI [6649 days 10 hours and 1 minute ago]

Mon, 4 Feb 2008 23:40:18 GMT

Eek! Since I installed Leopard, when I try to render from the shell I 
get: "Init Error:  The display '/tmp/launch-uGIbWC/:0' is not a valid 
display, or you do not have permission to open a window there."

-- 
Anton Sherwood, http://www.ogre.nu/
"How'd ya like to climb this high *without* no mountain?" --Porky Pine

[Günther Dietrich] Re: font conversion? [6650 days 22 hours and 36 minutes ago]

Sun, 3 Feb 2008 11:05:08 GMT

Anton Sherwood <bro### [at] poboxcom> wrote:

>> I have managed to convert several of my fonts using two old
>> utlility programs for Mac Classic: one is TTConverter. . . .
>
>Sigh, I wish you'd said that before I moved to Leopard,
>which abandoned Classic ...

SheepShaver works fine, also -- or let's say especially -- on intel Macs 
with Leopard.



Best regards,

GÃ¼nther

[Anton Sherwood] Re: font conversion? [6651 days 5 hours and 14 minutes ago]

Sun, 3 Feb 2008 04:26:52 GMT

François de Dardel wrote:
> I have managed to convert several of my fonts using two old
> utlility programs for Mac Classic: one is TTConverter. . . .

Sigh, I wish you'd said that before I moved to Leopard,
which abandoned Classic ...

-- 
Anton Sherwood, http://www.ogre.nu/
"How'd ya like to climb this high *without* no mountain?" --Porky Pine

[Thorsten Froehlich] Re: font conversion? [6651 days 20 hours and 12 minutes ago]

Sat, 2 Feb 2008 13:28:46 GMT

François de Dardel wrote:
> I think our friend Thorsten Froehlich is overly optimistic...

Well, the thing is that Apple delivers more and more fonts in other formats 
with each version of Mac OS X (which is a good thing, as plain TrueType font 
files are not perfect). And what POV-Ray needs is indeed a "real" TrueType 
font file. One way to get lots of TrueType font files (that still work on 
Mac OS X) is from a Mac OS 9 Install CD. Or from any Windows install, in 
particular if various Adobe tools have been installed before, because they 
tend to come with additional TrueType fonts.

> My experience (of today and earlier):
> Of the many fonts available on my Mac, only very few seem to qualify for POV.
> Those are mainly Windows fonts with names like "myfont.ttf".

They are not Windows fonts, they are regular TrueType font files.

> These fonts must be single fonts, not font suitcases. Most dfil fonts or other
> fonts described as TrueType by Apple FontBook do not work.

Font Book calls almost everything TrueType that isn't a PostScript font. In 
particular, as you note, the new font suitcase files won't work - 
internally they contain multiple TrueType font versions, but that is of no 
use for POV-Ray because they don't match a ".ttf" file format...

	Thorsten

[] Re: font conversion? [6651 days 21 hours and 1 minute ago]

Sat, 2 Feb 2008 12:40:01 GMT

Anton Sherwood <bro### [at] poboxcom> wrote:
> >>> Anton Sherwood wrote:
> >>>> Short of buying Fontographer or its successor, what tools are
> >>>> available to convert fonts to .ttf so Povray can use them?
>
> >> Thorsten Froehlich wrote:
> >>> Since 3.5 you don't need any tools. Just supply the font name
> >>> and all that are supported will be used automatically.
>
> So I open the "Text Fonts" scene template and replace "crystal.ttf"
> with "Baskerville Bold" (having first used Font Book to choose an
> existing font name), and am not utterly astonished to see
>
>  Parse Error: Cannot open font file.
>
> Then it occurs to me that "no syntax" could mean the keyword "ttf"
> shouldn't be there, so I delete it and am even less amazed to see
>
>  Parse Error: Expected 'ttf', string literal found instead
>
I think our friend Thorsten Froehlich is overly optimistic...
My experience (of today and earlier):
Of the many fonts available on my Mac, only very few seem to qualify for POV.
Those are mainly Windows fonts with names like "myfont.ttf".
These fonts must be single fonts, not font suitcases. Most dfil fonts or other
fonts described as TrueType by Apple FontBook do not work.
I have managed to convert several of my fonts using two old utlility programs
for Mac Classic: one is TTConverter. Once you have done that, you must put the
new converted fonts in POV's "include" folder or in the same folder as your
..pov file.

[Anton Sherwood] Re: font conversion? [6652 days 4 hours and 8 minutes ago]

Sat, 2 Feb 2008 05:33:14 GMT

>>> Anton Sherwood wrote:
>>>> Short of buying Fontographer or its successor, what tools are 
>>>> available to convert fonts to .ttf so Povray can use them?

>> Thorsten Froehlich wrote:
>>> Since 3.5 you don't need any tools. Just supply the font name
>>> and all that are supported will be used automatically.

> Anton Sherwood wrote:
>> I made a wild guess at the syntax, but no luck ..

Thorsten Froehlich wrote:
> There is no "syntax" to guess. You just supply the _name_ of the font.

So I open the "Text Fonts" scene template and replace "crystal.ttf"
with "Baskerville Bold" (having first used Font Book to choose an 
existing font name), and am not utterly astonished to see

	Parse Error: Cannot open font file.

Then it occurs to me that "no syntax" could mean the keyword "ttf" 
shouldn't be there, so I delete it and am even less amazed to see

	Parse Error: Expected 'ttf', string literal found instead

So far so good.

-- 
Anton Sherwood, http://www.ogre.nu/
"How'd ya like to climb this high *without* no mountain?" --Porky Pine

[Thorsten Froehlich] Re: font conversion? [6658 days 1 hour and 23 minutes ago]

Sun, 27 Jan 2008 08:18:13 GMT

Anton Sherwood wrote:
>> Anton Sherwood wrote:
>>> Short of buying Fontographer or its successor, what tools are 
>>> available to convert fonts to .ttf so Povray can use them?
> 
> Thorsten Froehlich wrote:
>> Since 3.5 you don't need any tools. Just supply the font name
>> and all that are supported will be used automatically.
> 
> I made a wild guess at the syntax, but no luck ..

There is no "syntax" to guess. You just supply the _name_ of the font.

	Thorsten

[Anton Sherwood] Re: font conversion? [6658 days 2 hours and 16 minutes ago]

Sun, 27 Jan 2008 07:25:19 GMT

> Anton Sherwood wrote:
>> Short of buying Fontographer or its successor, what tools are 
>> available to convert fonts to .ttf so Povray can use them?

Thorsten Froehlich wrote:
> Since 3.5 you don't need any tools. Just supply the font name
> and all that are supported will be used automatically.

I made a wild guess at the syntax, but no luck ..

-- 
Anton Sherwood, http://www.ogre.nu/
"How'd ya like to climb this high *without* no mountain?" --Porky Pine

[Thorsten Froehlich] Re: font conversion? [6676 days 12 hours and 36 minutes ago]

Tue, 8 Jan 2008 21:05:05 GMT

Anton Sherwood wrote:
> Short of buying Fontographer or its successor, what tools are available 
> to convert fonts to .ttf so Povray can use them?

Since 3.5 you don't need any tools. Just supply the font name and all that 
are supported will be used automatically.

	Thorsten

[Anton Sherwood] font conversion? [6676 days 12 hours and 54 minutes ago]

Tue, 8 Jan 2008 20:47:16 GMT

Short of buying Fontographer or its successor, what tools are available 
to convert fonts to .ttf so Povray can use them?

-- 
Anton Sherwood, http://www.ogre.nu/
"How'd ya like to climb this high *without* no mountain?" --Porky Pine

[Woody] Moray For Mac [6694 days 20 hours and 46 minutes ago]

Fri, 21 Dec 2007 12:55:00 GMT

Anybody know if there are plans to release a Mac version of Moray once it goes
to open source (after POVRay 4.0)

[Woody] POVRay Mac versuses PC [6694 days 20 hours and 51 minutes ago]

Fri, 21 Dec 2007 12:50:00 GMT

Hi, Im quickly becoming discusted with MY PC laptop and an seriously considering
getting a MacBook.

Are there any users out there who have used POVRay on both a Mac and PC?

Any advanatages of one over the other?

How do they compare/Contrast?

Any Help would be greatly appreciated?

[jhu] Re: Distributed Rendering on Mac clusters? [6695 days 7 hours and 21 minutes ago]

Fri, 21 Dec 2007 02:20:01 GMT

"StephenPope" <stp### [at] createucsbedu> wrote:
> Hello there!
>
> I've been using MegaPOV on a Macintosh, and would like to be able to use both
> cores on an SMP machine, as well as clusters.
>
> I've used both MPI and XLMRPC (for digital audio processing), but the various
> extensions to POV-Ray and MegaPOV don't appear to support MacOSX SMP machines
> or clusters thereof. Is there some patch or new version I'm missing?
>
> I know about the new SMP POV-Ray and Megapov-XRS, but can't find Mac ports.
>
> .....any reply appreciated...
>
> Stephen Pope
> U C Santa Barbara

If you're any good at scripting, you can achieve the same effect that smpov
does. I'd help but I'm only mediocre at scripting and I don't have a multi-core
processor.

[Tom York] Re: What to buy? [6698 days 15 hours and 16 minutes ago]

Mon, 17 Dec 2007 18:25:01 GMT

"Sky Shields" <sky {u} wlym {tochka} com> wrote:

> Also, I don't know what to expect from the new POVray 4.0 in 2008.

Will it even be started in 2008? It's a complete rewrite, I thought, that's got
to take time.

Tom

[Tom York] Re: What to buy? [6698 days 15 hours and 16 minutes ago]

Mon, 17 Dec 2007 18:25:01 GMT

"Sky Shields" <sky {u} wlym {tochka} com> wrote:
> I would very much like to be able to use a multicore processor.  There seem to
> be a number of complaints about that here.

I'm using POVRay on a Q6600 (quad core processor), after a long time using a
Pentium 4 processor of the same speed (2.4GHz). The following is based on
personal experience only - it contains no facts of significance:

Highs:
* (3.7 beta only) When you're dealing with a scene where rendering time
dominates over parsing time, POV tends to start eating scenes like popcorn. I
don't know whether the speedup is as good as 400% over a P4 of the same speed,
but it's enough that I don't really care.

Lows:
* (3.7 beta only) Because many scenes render so rapidly on multicore processors,
the morally improving aspect of raytracing is initially lost. Not much time left
to sit in a comfy chair contemplating The Great Questions while you wait for a
render to complete.

* (3.6 and variants only) The realization that when using POVRay 3.6 or variants
to render a still, rendering is leaving almost three-quarters of the available
CPU idle. While rendering on a single core of intel's quad or dual core chips
is likely faster than rendering on a P4 of equivalent clock speed, I haven't
been bothered enough to find out the precise figure.

On the upside, switching back to 3.6 (when you've got a scene using radiosity,
or you're tired of living on the edge) brings back the morally improving
aspect.

Intel seem to be releasing a new line of processors, including a few
mobile/laptop processors, in the not too distant future (first half of next
year?), I don't know how that changes things compared to the current generation
of chips.

Tom

[jhu] Re: What to buy? [6699 days 12 hours and 21 minutes ago]

Sun, 16 Dec 2007 21:20:00 GMT

"Sky Shields" <sky {u} wlym {tochka} com> wrote:
> Addition:
>
> I would very much like to be able to use a multicore processor.  There seem to
> be a number of complaints about that here.
>
> Thanks!
>
> --Sky

If all you're worried about is rendering speed, the best bang-for-buck is
something other than a Mac since you can get equal or better processor
performance for less money. Or, hey, get two or three and run them as a
cluster...

[Sky Shields] Re: What to buy? [6700 days 6 hours and 51 minutes ago]

Sun, 16 Dec 2007 02:50:01 GMT

Addition:

I would very much like to be able to use a multicore processor.  There seem to
be a number of complaints about that here.

Thanks!

--Sky

[Sky Shields] Re: Error running POV-Ray on OS X 10.3 [6700 days 7 hours and 31 minutes ago]

Sun, 16 Dec 2007 02:10:00 GMT

Hello!

I found the solution to the problem posted on this site here:
http://www.somewhereville.com/?cat=29

It worked for me.  Here's the text from the site:

"The error,

"The Error number is -199. (For internal reference only!)

"appears upon startup and exits from the program proper, such that POV-Ray
becomes useless (not pleasant when you need that last minute image 30 seconds
before lecturing).

"The only mention online (if you search by the message text) can be found at

"
http://news.povray.org/povray.macintosh/thread/%3Cweb.431de75539863b47bd78a280@news.povray.org%3E/

"The error itself is not diagnosed, only noting that a corrupted file is not
being accessed upon startup and that running a Disk Utility verification/fixing
and reinstalling POV-Ray solves the problem. If this has happened to you, you
may have noted that verification/fixing and re-installation does not do the
trick.

"The origin of the problem on my machine could be traced to a crashed POV-Ray
rendering run of a number of images and the retention of the file POV-Ray Mac
3.6.plist in my /[USER]/Library/Preferences/ directory, which typically only
contains the file POV-Ray Preferences 3.5 (why an installation of POV-Ray 3.6
would still leave a 3.5 Preference file is beyond the scope of this post).

"Deleting the POV-Ray Mac 3.6.plist file fixes the problem.

" www.apple.com
" www.povray.org
"
news.povray.org/povray.macintosh/thread/%3Cweb.431de75539863b47bd78a280@news.povray.org%3E
"

[Sky Shields] What to buy? [6700 days 7 hours and 46 minutes ago]

Sun, 16 Dec 2007 01:55:01 GMT

Hello!

I'm new to this group.  This is my first post, but I've been using POVray for a
little while now, quite happily, on an iBook G4 with 256MB of RAM.  I'm now,
finally, in a position to purchase a much faster laptop, but I was wondering
what would be best to buy (in the opinion of the people here).  My primary
consideration is speed of rendering and, though I like the Mac, purchasing a
Linux machine is also an option.

(The place where I work is currently in the process of migrating entirely to
Linux, and my next desktop will probably run Linux.)

I've browsed this site reading discussions on the render speeds of various
operating systems, but I'm still unsure as to which way to go.  Also, I don't
know what to expect from the new POVray 4.0 in 2008.

Any help is appreciated!

Thanks!

--Sky

[Thorsten Froehlich] Re: Find and Replace [6705 days 1 hour and 54 minutes ago]

Tue, 11 Dec 2007 07:47:20 GMT

Greg Williams wrote:
> What are the limits of the Search/Replace command on the Mac platform?
<snip>
> However, if I select all of the entire file, or even more than a couple of
> hundred cases, and do the same Search/Replace All, Selection only, I get the
> Mac spinning color wheel of the death, and the program locks up. I have to
> Force Quit POV Ray.

There are no limits, it will just take really long if you have a very huge
file. POV-Ray does not lock up, it is just taking very long to perform the
find and replace, especially if the file is several megabytes in size.

	Thorsten

[Greg Williams] Find and Replace [6705 days 7 hours and 11 minutes ago]

Tue, 11 Dec 2007 02:30:01 GMT

What are the limits of the Search/Replace command on the Mac platform?

I have a file that contains several thousand instances of: rgbt <number, number,
number, 1.000000>  I need to replace all of those 1.000000  t-values with  0.
(The source of the 1.000000 values is the modeling program, DS Visualizer, and
I can't fix it. It's a known bug in Visualizer.)

I can replace a small set of them, say on the order of 25 or so with
Search/Replace All, Selection only.

However, if I select all of the entire file, or even more than a couple of
hundred cases, and do the same Search/Replace All, Selection only, I get the
Mac spinning color wheel of the death, and the program locks up. I have to
Force Quit POV Ray.

This isn't a problem on the Windows version.

Is this a known problem for Mac 3.6.0 build197?

Thanks,

Greg

[Thorsten Froehlich] Re: Error running POV-Ray on OS X 10.3 [6709 days 14 hours and 28 minutes ago]

Thu, 6 Dec 2007 19:13:01 GMT

Sky Shields wrote:
> Is there a better disk repair program?

Yes, but they are all commercial.

	Thorsten

[Sky Shields] Re: Error running POV-Ray on OS X 10.3 [6709 days 15 hours and 26 minutes ago]

Thu, 6 Dec 2007 18:15:00 GMT

>
> A file that POV-Ray tries to access is corrupted on your harddisk. Run Disk
> Utility to check your harddisk for errors, tell Disk Utility to fix them and
> then reinstall POV-Ray.
>
>  Thorsten

Hello!

I had the same problem.  I've run Disk Utility three times now, but I'm getting
the same error message.  Disk Utility also makes the exact same repairs every
time, which has never happened before.  I'm assuming this isn't a POVray
problem . . .

Is there a better disk repair program?

--Sky

[Keith] Re: Render Settings [6716 days 13 hours and 1 minute ago]

Thu, 29 Nov 2007 20:40:00 GMT

Very good. Problem solved now. Thanks! Feel silly I hadn't realized as much
myself, but I was so convinced the solution would be more complex that I pretty
much ignored such a simple, obvious cause.


Keith

[Thorsten Froehlich] Re: Pov-Ray 3.6 and Mac OS 10.5 Leopard [6716 days 13 hours and 41 minutes ago]

Thu, 29 Nov 2007 20:00:16 GMT

Drakonis wrote:
> Thorsten Froehlich <tho### [at] trfde> wrote:
>> MacGuyver wrote:
>>> Anyone out there trying to use Pov-Ray and Mac OS 10.5? Pov-Ray tries to open,
>>> and seems to get most of the way, but then it unexpectedly quits on me. Has
>>> anyone else had this problem? Better yet, has anyone found a solution?
>> On a PowerPC or an Intel Mac?
>>
>>  Thorsten
> 
> I too just recently upgraded (CLEAN install) my Quicksilver dual G4 (PowerPC),
> and my brand new Dual-core (Intel) Mac to Leopard (10.5, and now 10.5.1), and I
> can confirm that POV-Ray 3.6.0 crashes on both hardware platforms, wit the
> following stack crawl (snippet):
> 
> Exception Type:  EXC_BAD_ACCESS (SIGBUS)
> Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000004
> Crashed Thread:  0

Is this a PPC or x86 stack trace???

	Thorsten

[Drakonis] Re: Pov-Ray 3.6 and Mac OS 10.5 Leopard [6716 days 14 hours and 31 minutes ago]

Thu, 29 Nov 2007 19:10:00 GMT

Thorsten Froehlich <tho### [at] trfde> wrote:
> MacGuyver wrote:
> > Anyone out there trying to use Pov-Ray and Mac OS 10.5? Pov-Ray tries to open,
> > and seems to get most of the way, but then it unexpectedly quits on me. Has
> > anyone else had this problem? Better yet, has anyone found a solution?
>
> On a PowerPC or an Intel Mac?
>
>  Thorsten

I too just recently upgraded (CLEAN install) my Quicksilver dual G4 (PowerPC),
and my brand new Dual-core (Intel) Mac to Leopard (10.5, and now 10.5.1), and I
can confirm that POV-Ray 3.6.0 crashes on both hardware platforms, wit the
following stack crawl (snippet):

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000004
Crashed Thread:  0

Thread 0 Crashed:
0   translate                      0xb80bc8c8 0xb8000000 + 772296
1   translate                      0xb80b6b77 0xb8000000 + 748407
2   translate                      0xb80d4530 0xb8000000 + 869680
3   translate                      0xb813c9e9 spin_lock_wrapper + 1981

Thread 1:
0   ???                            0x800bb8e6 0 + 2148251878
1   ???                            0x800c30dc 0 + 2148282588
2   translate                      0xb818b69a CallPPCFunctionAtAddressInt +
202826
3   ???                            0x800ec075 0 + 2148450421
4   ???                            0x800ebf32 0 + 2148450098

Thread 2:
0   translate                      0xb8152ad4 spin_lock_wrapper + 92328
1   translate                      0xb8167d9e CallPPCFunctionAtAddressInt +
57166
2   translate                      0xb80bd6fb 0xb8000000 + 775931
3   translate                      0xb80b6b77 0xb8000000 + 748407
4   translate                      0xb80d4530 0xb8000000 + 869680
5   translate                      0xb813d2cf spin_lock_wrapper + 4259
:::

As more and more people start using Leopard, this will become more important to
look into, for the Mac-POV-Ray users out there (including me, in the middle of
a POV-Ray animation project :-).  Yvo's MegaPOV seems to be a good alternative
for now.

ttfn,
Eduard

[Thorsten Froehlich] Re: Render Settings [6717 days 1 hour and 53 minutes ago]

Thu, 29 Nov 2007 07:48:03 GMT

Keith wrote:
> I have managed to set everything up fine and POV-Ray works well on the Mac, with
> one major exception. Scenes render well and everything seems to be set up fine,
> but rendering only produces a wee little image. I have used the Windows version
> for a fairly long time, but am totally new to using the program on Mac. So,
> after a brief search through all the relevent documentation I could lay my
> hands on, I found it firmly established that the solution of my problem lies in
> the Render Settings dialogue accessed through the Edit menu. Trouble is, I click
> on the Edit menu and Render Settings is greyed out and not selectable. No matter
> what steps I take to try to get it to be accessible, it remains unselectable. I
> spent the better part of the past few days searching in vain for some way to
> access it, but to no avail. I have yet to find a single issue where Render
> Settings in the Edit menu is not accessible. I'd greatly appreciate it if
> someone could explain possibilities as to why this may be the case and what I
> could do to correct it, keeping in mind that I seem to have set up the program
> fine and have no problem rendering images.

Your files are missing a ".pov" extension and you have
<http://www.povray.org/documentation/view/3.6.1/750/> enabled. I would
recommend you add ".pov" extensions to your POV-Ray files.

	Thorsten, POV-Team

[Keith] Render Settings [6717 days 8 hours and 11 minutes ago]

Thu, 29 Nov 2007 01:30:00 GMT

I have managed to set everything up fine and POV-Ray works well on the Mac, with
one major exception. Scenes render well and everything seems to be set up fine,
but rendering only produces a wee little image. I have used the Windows version
for a fairly long time, but am totally new to using the program on Mac. So,
after a brief search through all the relevent documentation I could lay my
hands on, I found it firmly established that the solution of my problem lies in
the Render Settings dialogue accessed through the Edit menu. Trouble is, I click
on the Edit menu and Render Settings is greyed out and not selectable. No matter
what steps I take to try to get it to be accessible, it remains unselectable. I
spent the better part of the past few days searching in vain for some way to
access it, but to no avail. I have yet to find a single issue where Render
Settings in the Edit menu is not accessible. I'd greatly appreciate it if
someone could explain possibilities as to why this may be the case and what I
could do to correct it, keeping in mind that I seem to have set up the program
fine and have no problem rendering images.

Keith

[plagarri] Re: Pov-Ray 3.6 and Mac OS 10.5 Leopard [6722 days 18 hours and 16 minutes ago]

Fri, 23 Nov 2007 15:25:01 GMT

"Renderdog" <slo### [at] hiwaaynet> wrote:
> Has anyone run POV-Ray 3.6 on a PowerPC under Leapard?
>
> Thanks,
> Mark

I get the following error msg when Pov-ray is starting: "The application POV-Ray
Mac 3.6 quit unexpectedly".
I use OS X 10.4.11 on a 2.16 GHz Intel core duo with 2 GB mem

[Renderdog] Re: Pov-Ray 3.6 and Mac OS 10.5 Leopard [6724 days 14 hours and 56 minutes ago]

Wed, 21 Nov 2007 18:45:00 GMT

Has anyone run POV-Ray 3.6 on a PowerPC under Leapard?

Thanks,
Mark

[StephenPope] Distributed Rendering on Mac clusters? [6726 days 5 hours and 16 minutes ago]

Tue, 20 Nov 2007 04:25:00 GMT

Hello there!

I've been using MegaPOV on a Macintosh, and would like to be able to use both
cores on an SMP machine, as well as clusters.

I've used both MPI and XLMRPC (for digital audio processing), but the various
extensions to POV-Ray and MegaPOV don't appear to support MacOSX SMP machines
or clusters thereof. Is there some patch or new version I'm missing?

I know about the new SMP POV-Ray and Megapov-XRS, but can't find Mac ports.

.....any reply appreciated...

Stephen Pope
U C Santa Barbara

[Dennis Lazowski] Re: Pov-Ray 3.6 and Mac OS 10.5 Leopard [6738 days 10 hours and 16 minutes ago]

Wed, 7 Nov 2007 23:25:00 GMT

"MacGuyver" <nomail@nomail> wrote:
> Thorsten Froehlich <tho### [at] trfde> wrote:
> > MacGuyver wrote:
> > > Anyone out there trying to use Pov-Ray and Mac OS 10.5? Pov-Ray tries to open,
> > > and seems to get most of the way, but then it unexpectedly quits on me. Has
> > > anyone else had this problem? Better yet, has anyone found a solution?
> >
> > On a PowerPC or an Intel Mac?
> >
> >  Thorsten
>
> This is an Intel Mac. I wish I'd tried using Pov-Ray on it with 10.4, just so I
> could eliminate that factor. Oh, well, hindsight's always 20/20.
>
> MacGuyver


I have an Intel Mac and it does the same thing on OS 10.4 as it does on OS 10.5.
It unexpectedly  quits.

Lazowski

[StephenPope] Re: Pov-Ray 3.6 and Mac OS 10.5 Leopard [6741 days 18 hours and 51 minutes ago]

Sun, 4 Nov 2007 14:50:01 GMT

"MacGuyver" <nomail@nomail> wrote:
> Thorsten Froehlich <tho### [at] trfde> wrote:
> > MacGuyver wrote:
> > > Anyone out there trying to use Pov-Ray and Mac OS 10.5? Pov-Ray tries to open,
> > > and seems to get most of the way, but then it unexpectedly quits on me. Has
> > > anyone else had this problem? Better yet, has anyone found a solution?
> >
> > On a PowerPC or an Intel Mac?
> >
> >  Thorsten
>
> This is an Intel Mac. I wish I'd tried using Pov-Ray on it with 10.4, just so I
> could eliminate that factor. Oh, well, hindsight's always 20/20.
>
> MacGuyver

I use POVray on an Intel-iMac with 10.4.10 and it runs just fine.
I generally use the MEGAPOV front-end.

stp

[MacGuyver] Re: Pov-Ray 3.6 and Mac OS 10.5 Leopard [6743 days 18 hours and 51 minutes ago]

Fri, 2 Nov 2007 14:50:00 GMT

Thorsten Froehlich <tho### [at] trfde> wrote:
> MacGuyver wrote:
> > Anyone out there trying to use Pov-Ray and Mac OS 10.5? Pov-Ray tries to open,
> > and seems to get most of the way, but then it unexpectedly quits on me. Has
> > anyone else had this problem? Better yet, has anyone found a solution?
>
> On a PowerPC or an Intel Mac?
>
>  Thorsten

This is an Intel Mac. I wish I'd tried using Pov-Ray on it with 10.4, just so I
could eliminate that factor. Oh, well, hindsight's always 20/20.

MacGuyver

[Thorsten Froehlich] Re: Pov-Ray 3.6 and Mac OS 10.5 Leopard [6744 days 3 hours and 14 minutes ago]

Fri, 2 Nov 2007 06:27:26 GMT

MacGuyver wrote:
> Anyone out there trying to use Pov-Ray and Mac OS 10.5? Pov-Ray tries to open,
> and seems to get most of the way, but then it unexpectedly quits on me. Has
> anyone else had this problem? Better yet, has anyone found a solution?

On a PowerPC or an Intel Mac?

	Thorsten

[Günther Dietrich] Re: Pov-Ray 3.6 and Mac OS 10.5 Leopard [6744 days 3 hours and 16 minutes ago]

Fri, 2 Nov 2007 06:25:15 GMT

"MacGuyver" <nomail@nomail> wrote:


>Better yet, has anyone found a solution?

Take some MacGyver-tape and fix it?

SCNR



Best regards,

Günther

[MacGuyver] Pov-Ray 3.6 and Mac OS 10.5 Leopard [6744 days 6 hours and 1 minute ago]

Fri, 2 Nov 2007 03:40:00 GMT

Anyone out there trying to use Pov-Ray and Mac OS 10.5? Pov-Ray tries to open,
and seems to get most of the way, but then it unexpectedly quits on me. Has
anyone else had this problem? Better yet, has anyone found a solution?

Thanks in advance,
MacGuyver

[Tiger] Re: Configuring POVray for use with Eagle 3D [6746 days 15 hours and 31 minutes ago]

Tue, 30 Oct 2007 18:09:39 GMT

On 16-10-07 03:28, Jim wrote:
> Tiger <nos### [at] nospam> wrote:
>> [...]
>> Parse Error: Illegal character in input file, value is 02.
>> Total Scene Processing Times
>> [...]
>>
>> What does that mean, and what can I do in order to fix it?
> 
> What it means is that there is an error in the input, and the rendering
> can't continue until it is fixed.
> 
> Unfortunately you have not included the portion of the error message which
> immediately precedes what you posted.

I've been in touch with the author and sent him the complete error 
messages. I believe he's got it under control, but will have to wait for 
the next version of Eagle 3D before I can actually test it.

[Jim] Re: Configuring POVray for use with Eagle 3D [6761 days 8 hours and 11 minutes ago]

Tue, 16 Oct 2007 01:30:01 GMT

Tiger <nos### [at] nospam> wrote:
> [...]
> Parse Error: Illegal character in input file, value is 02.
> Total Scene Processing Times
> [...]
>
> What does that mean, and what can I do in order to fix it?

What it means is that there is an error in the input, and the rendering
can't continue until it is fixed.

Unfortunately you have not included the portion of the error message which
immediately precedes what you posted. You need to get the information which
will tell you the "File:" and provide (5 lines) of "File Context." From
there, you can figure out what file is causing the problem - and possibly
correct it.

From what is displayed, I'd guess that an ASCII "02" character has somehow
gotten into the file you're using, and that is causing problems. I have
seen similar bad problems (including crashing MegaPOV) when ^C and other
non-printable made it into some SDL files I was using.

Hopefully this helps you out at least some.

[Tiger] Re: [solved] Eagle 3D File will not render [6791 days 18 hours and 17 minutes ago]

Sat, 15 Sep 2007 15:23:50 GMT

On 13-09-07 19:06, Yvo Smellenbergh wrote:
> Tiger <nos### [at] nospam> wrote:
> 
> [...]
>> * MegaPOV (Mac)       : error message shows up when trying to render:
>> -----------------------------------------------------
>> File: /Users/Tiger/Desktop/From Mac/Eagle 3D (Mac) 
>> created/mac_eagle3d.pov  Line: 42
>> File Context (5 lines):
>> #declare col_preset = 2;
>> #declare pin_short = on;
>> #declare environment
>> Parse Error: Expected 'undeclared identifier', environment found instead

> 'environment' is a reserved keyword in MegaPOV. It is used for the
> mechsim patch.
> This patch doesn't exist in the official POV-Ray version and that is the
> only reason why POV-Ray for Windows is rendering it.
> You will see that WinMegaPOV will not render it either.

Thanks. I've forwarded your reply to the author of Eagle 3D. Hopefully 
he'll fix it soon.

[Yvo Smellenbergh] Re:[solved] Eagle 3D File will not render [6793 days 16 hours and 34 minutes ago]

Thu, 13 Sep 2007 17:07:00 GMT

Tiger <nos### [at] nospam> wrote:

[...]
> * MegaPOV (Mac)       : error message shows up when trying to render:
> -----------------------------------------------------
> File: /Users/Tiger/Desktop/From Mac/Eagle 3D (Mac) 
> created/mac_eagle3d.pov  Line: 42
> File Context (5 lines):
> #declare col_preset = 2;
> #declare pin_short = on;
> #declare environment
> Parse Error: Expected 'undeclared identifier', environment found instead
'environment' is a reserved keyword in MegaPOV. It is used for the
mechsim patch.
This patch doesn't exist in the official POV-Ray version and that is the
only reason why POV-Ray for Windows is rendering it.
You will see that WinMegaPOV will not render it either.

So, this is actually an error in Eagle 3D, they should use 'Environment'
instead, starting the word with an uppercase character.

User defined variables and/or declares should never start with a lower
case character!

Regards,

Yvo
-- 
-----------------------------------
MegaPOV at:  http://megapov.inetart.net
MacMegaPOV at:  http://users.skynet.be/smellenbergh
E-mail: yvo### [at] cancel_This_first_gmxnet

[Yvo Smellenbergh] Re: Eagle 3D File will not render [6794 days 18 hours and 28 minutes ago]

Wed, 12 Sep 2007 15:13:20 GMT

Tiger <nos### [at] nospam> wrote:

[...]
> * MegaPOV (Mac)       : error message shows up when trying to render:
> -----------------------------------------------------
> File: /Users/Tiger/Desktop/From Mac/Eagle 3D (Mac) 
> created/mac_eagle3d.pov  Line: 42
> File Context (5 lines):
> #declare col_preset = 2;
> #declare pin_short = on;
> #declare environment
> Parse Error: Expected 'undeclared identifier', environment found instead
> -----------------------------------------------------

> I suspect Eagle 3D saving the POV files in a specific format which 
> Mac-POVray can't use. We really should analyze the above files somehow,
> to compare them with each other, but I really don't know where to start.
> Suggestions? I could upload the test-files if anyone is interested in
> looking at them.

You can e-mail me that file and, if there are, all the necessary include
files to render it.
Please send the unmodified file.
Then I will examine why it doesn't render on MegaPOV.

Yvo Smellenbergh


-- 
-----------------------------------
MegaPOV at:  http://megapov.inetart.net
MacMegaPOV at:  http://users.skynet.be/smellenbergh
E-mail: yvo### [at] cancel_This_first_gmxnet

[Tiger] Re: Eagle 3D File will not render [6795 days 15 hours and 27 minutes ago]

Tue, 11 Sep 2007 18:13:50 GMT

On 11-09-07 00:39, Thorsten Froehlich wrote:
> Tiger wrote:

>> about every combination of line-ending and character set I can't get it
>> to become un-greyed in the POVray file-selector.
> 
> The files being grayed-out has nothing to do with the contents of the files.
> It is just an artifact of the way they were created - recall that Eagle is
> an X11 application rather than a truly native Mac application (well, the
> Eagle 5.0 betas are actually native Mac applications, but that is another
> story). So just don't worry about files being grayed-out by default.

OK, I'll leave that for now.
All this testing has left me quite confused, so I've done it all again.
Since MegaPOV seems more forgiving with "problem files" than POVray on 
the Mac (the latter just freezes when it encounters problematic POV 
files while MegaPOV just gives me error messages) I decided to try them 
both out with my files.

TEST #1
-------
First, I tested "bezier.pov" (from Mac-POVray's "scenes" folder).
* POVray (Mac)	: worked OK
* MegaPOV (Mac)	: worked OK
* POVray (Windows): worked OK


TEST #2
-------
Next, (using Eagle and Eagle 3D on the Mac) I created a very simple 
circuit board which I made a POV file from:
* POVray (Mac)	: opening the file freezes POVray (I need to "force-quit" 
in order to exit)

* MegaPOV (Mac)	: error message shows up when trying to render:
-----------------------------------------------------
File: /Users/Tiger/Desktop/From Mac/Eagle 3D (Mac) 
created/mac_eagle3d.pov  Line: 42
File Context (5 lines):
#declare col_preset = 2;
#declare pin_short = on;
#declare environment
Parse Error: Expected 'undeclared identifier', environment found instead
-----------------------------------------------------

* POVray (Windows): worked OK


TEST #3
-------
Finally, I took the very same file that I had created with Eagle/Eagle 
3D on the Mac (above, in test #2), opened it with Eagle on the PC, did 
some very minor changes (just moved some circuit traces ever so slightly 
so as to tell Eagle I had made changes), saved the file and created a 
POV file with Eagle 3D (Windows):
* POVray (Mac)	: opening the file freezes POVray (I need to "force-quit" 
in order to exit)

* MegaPOV (Mac)	:
----------------------------------------------------
File: /Users/Tiger/Desktop/From PC/Mac created, opened and edited on 
PC/mac_eagle3d.pov  Line: 42
File Context (5 lines):

#declare environment
Parse Error: Expected 'undeclared identifier', environment found instead
----------------------------------------------------

* POVray (Windows): worked OK


I suspect Eagle 3D saving the POV files in a specific format which 
Mac-POVray can't use. We really should analyze the above files somehow, 
to compare them with each other, but I really don't know where to start.
Suggestions? I could upload the test-files if anyone is interested in 
looking at them.

[Thorsten Froehlich] Re: Eagle 3D File will not render [6796 days 11 hours and 1 minute ago]

Mon, 10 Sep 2007 22:39:38 GMT

Tiger wrote:
> So, using a text editor I tried to copy the entire text contents of the
> working POV file (a file I found in the "scenes" folder). That way I'll
> know that the actual data is correct,

So do the files work then? Or do you at least get an error message of some kind?

> but even though I've tried just
> about every combination of line-ending and character set I can't get it
> to become un-greyed in the POVray file-selector.

The files being grayed-out has nothing to do with the contents of the files.
It is just an artifact of the way they were created - recall that Eagle is
an X11 application rather than a truly native Mac application (well, the
Eagle 5.0 betas are actually native Mac applications, but that is another
story). So just don't worry about files being grayed-out by default.

	Thorsten

[Tiger] Re: Eagle 3D File will not render [6796 days 11 hours and 36 minutes ago]

Mon, 10 Sep 2007 22:04:49 GMT

On 10-09-07 23:01, Thorsten Froehlich wrote:
> Tiger wrote:

>> Are there any websites where I can download .POV files that are sure to
>> work on a Mac (perhaps they've been created on a Mac)?
> 
> The Mac version, like all official versions of POV-Ray, comes with samples
> scenes.

You're right. I just didn't know that .POV files are also known as "scenes".
Good news -those POV files work fine on my Mac, so at least I know that 
POVray on my Mac is configured properly and works :-)

I'm still looking at the POV files I have from Eagle 3D, but haven't 
figured it out yet.
I do notice that my (Eagle 3D generated) POV files are greyed out in the 
POVray file-selector when trying to open them while the ones from the 
"scenes" folder that came with POVray aren't greyed out, but are selectable.

So, using a text editor I tried to copy the entire text contents of the 
working POV file (a file I found in the "scenes" folder). That way I'll 
know that the actual data is correct, but even though I've tried just 
about every combination of line-ending and character set I can't get it 
to become un-greyed in the POVray file-selector.
Any ideas?

[Thorsten Froehlich] Re: Eagle 3D File will not render [6796 days 12 hours and 40 minutes ago]

Mon, 10 Sep 2007 21:01:02 GMT

Tiger wrote:
> What would be really helpful for me in continuing my troubleshooting
> would be to see if I can get POVray to work at all!
> Are there any websites where I can download .POV files that are sure to
> work on a Mac (perhaps they've been created on a Mac)?

The Mac version, like all official versions of POV-Ray, comes with samples
scenes.

	Thorsten

[Tiger] Re: Eagle 3D File will not render [6796 days 13 hours and 46 minutes ago]

Mon, 10 Sep 2007 19:54:38 GMT

On 10-09-07 21:13, Thorsten Froehlich wrote:
> Tiger wrote:
>> I've tried several different POV files generated with my Mac, and they
>> all rendered perfectly on the PC.
> 
> Somehow this sounds like the files have DOS style line endings, which would
> of course confuse POV-Ray on a Mac, but not on Windows.

I wish it was that easy, but I've tried changing the line-endings as 
well as the character sets, but it made no difference.

What would be really helpful for me in continuing my troubleshooting 
would be to see if I can get POVray to work at all!
Are there any websites where I can download .POV files that are sure to 
work on a Mac (perhaps they've been created on a Mac)?

[Thorsten Froehlich] Re: Eagle 3D File will not render [6796 days 14 hours and 28 minutes ago]

Mon, 10 Sep 2007 19:13:05 GMT

Tiger wrote:
> I've tried several different POV files generated with my Mac, and they
> all rendered perfectly on the PC.

Somehow this sounds like the files have DOS style line endings, which would
of course confuse POV-Ray on a Mac, but not on Windows. It would also
explain why the Mac editor has problems opening the file, as it may not
actually have proper line endings the editor might go into putting
everything in one line, which makes it rather slow, which in turn would
explain why POV-Ray *appears* to be hanging when trying to open the file.

	Thorsten, POV-Team

[Tiger] Re: Eagle 3D File will not render [6796 days 16 hours and 4 minutes ago]

Mon, 10 Sep 2007 17:37:30 GMT

On 02-03-07 20:01, Laurence H Smith wrote:
> I have produced a .pov file from an Eagle circuit board file and I am trying 
> to Render it in Pov-Ray for Mac OS X 3.6.0. Here is what is happening: 
> 
> 	I double clicked the .pov file and it launches POV-RAY just fine
> 
> 	The spinning beach ball stays on for about 10 minutes and finally shows me 
> the file.
> 
> I select Render and the spinning beach ball stays on for about 10 minutes.

I'm on a Mac as well and experience much of the same thing as you.
I haven't waited 10 minutes though, but as soon as I load the POV file 
into POVray (http://mac.povray.org/) the beachball starts to spin.
If I press ALT-CMD I can see that POVray "not responding", so I do a 
force quit.
The strange thing is that the beachball starts to spin as soon as I 
*open* the POV file, not because I've chosen "render"!!??!?!?!
Very strange.

And yes, I've taken care to define the path to Eagle 3D's "POVray" 
folder (by going to POVray's "Edit"-"Preference"-"Scenes" menu.

Now even stranger is the fact that the above happens only when I open 
the file by going to POVray's "File"-"Open" menu, but then only if I 
choose "All documents". If the file-selector's choices are set to any of 
the other choices (POVray documents etc.) the POV files are greyed out, 
making them unselectable!

However, if the Eagle 3D POVray folder isn't defined I don't get the 
spinning beachball, but an error message about not finding the files in 
that folder.

Seeing that I didn't have much success with POVray I came across and 
decided to try out MegaPOV (http://megapov.inetart.net/).

Like with POVray I had to define the path to Eagle 3D's "POVray" folder.
It's a little confusing because it seems like this can be done in one of 
two places:
"MegaPOV"-"Preferences"-"System includes"
or
"Window"-"Render preferences"-"Files & paths"-"Set search paths for 
additional include files"

In any case, when opening the POV file I don't end up with a spinning 
beachball (and "not responding") as with POVray, but whenever I try to 
render ("Render"-"Render" menu) I get a bunch of different error 
messages such as:

-------------------------
Line: 38
File Context (5 lines):
#declare col_preset = 2;
#declare pin_short = on;
#declare environment
Parse Error: Expected 'undeclared identifier', environment found instead
-------------------------

or:
-------------------------
Parse Error: Illegal character in input file, value is 02
-------------------------

So no success so far on my Mac (PowerBook G4 (1.67GHz), MacOS 10.4.10, 
1.5Gbytes RAM).

Next, since I'm an Eagle novice and have never used neither Eagle 3D nor 
POVray, I decided to see if I got into the same problems when running it 
on a Windows PC.

Once having installed both Eagle 3D and POVray on the PC I transferred 
my previously made POV files (with Eagle 3D on my Mac) over to the PC, 
then tried to render them with POVray. Worked right away!
And I had deliberately chosen a very simple board, in order to make the 
rendering process fast. It took about 5 seconds to do (and this is on a 
5 year old Pentium 4, 1.9GHz, 256Mbytes RAM which is a lot less powerful 
than my Powerbook).
So I don't think processing power has anything to do with these issues.

I've tried several different POV files generated with my Mac, and they 
all rendered perfectly on the PC.
And of course POV files generated with Eagle 3D in Eagle on the PC work 
fine as well.

All this tells me that either there's a problem with POVray/MegaPOV on 
my Mac, or that the POV files aren't cross-platform compatible (even 
though the files were created on the Mac the same ULP script file as 
with the PC has been used).

It would be very interesting to try other POV files than the ones I've 
made with Eagle 3D myself, created by both PCs and Macs.
Are there any such files available for download somewhere?

[Tiger] Re: Configuring POVray for use with Eagle 3D [6799 days 17 hours and 39 minutes ago]

Fri, 7 Sep 2007 16:01:55 GMT

On 07-09-07 15:50, Gilles Tran wrote:
> "Tiger" <nos### [at] nospam> a écrit dans le message de news: 
> 46e15054@news.povray.org...
>> Upon contacting the author of Eagle 3D I was told that I need to tell 
>> POVray the location of a specific folder which came with Eagle 3D. 
>> However, I don't see any way of configuring this in POVray.
> 
> Here:  http://www.povray.org/documentation/view/3.6.1/751/

Thanks. Now *something* is happening instead of that error message, 
which isn't necessarily a good thing.
Instead, the Mac "beachball" spins indefinitely. By pressing ALT-COMMAND 
I can see that POVray is "not responding", so I had to do a "force quit".

This seems to happen every time I run it, and the file I've given to it 
is a very small one as well (I just placed one small IC on a board, so I 
can't possibly think POVray would see it as a major task; the whole POV 
file is 399 lines long).

Then I tried it in another application which I found called MegaPOV it 
seemed to work better, but even after setting the path to those files 
(in the "Files & paths" section of preferences) I got an error message:

Parse Error: Illegal character in input file, value is 02.
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  0 minutes  0 seconds (0 seconds)
   Postpr. Time:  0 hours  0 minutes  0 seconds (0 seconds)
   Total Time:    0 hours  0 minutes  0 seconds (0 seconds)

What does that mean, and what can I do in order to fix it?

[Stephen] Re: Configuring POVray for use with Eagle 3D [6799 days 19 hours and 41 minutes ago]

Fri, 7 Sep 2007 14:00:01 GMT

Tiger <nos### [at] nospam> wrote:
> I'm a complete newbie when it comes to POVray and need some help
> configuring and using it.
> I'm on a Powerbook G4 (1.67GHz) running MacOS 10.4.10.
> I've installed POVray 3.6.
>
> I barely know what POVray is (excuse my ignorance), but have an interest
> in it because of "Eagle 3D" which is a script that produces a .POV file
> out of an electronic circuit board design.
[snip]

> Possible Parse Error: Could not find file 'tools.inc'
>
> File test.pov line 117
> Parse Error: Cannot open include file tools.inc.
>
> File test.pov line 117
> Parse Warning: Check that the file is in a directory specifed with a +L
> switch or 'Library_Path='
> .INI item. Standard include files are in the include directory or
> folder. Please read your
> documentation carefully.
>

Welcome Tiger,
 I’m not a Mac user but I know that someone will give you detailed
instructions. The error message you got tells you that there is a file that
cannot be found (tools.inc) and you should enter a search path into, what in
windows is POVRAY.INI. The documentation should tell you what to do. Or you
could put tools.inc in the same folder as the Pov file, that should work
too.
Do try and take some time to learn a bit about Pov-Ray in its own right
before you start using it as a render engine, it might not be what you
expect. To get good quality images you will need to understand how Pov-Ray
works.
WARNING Pov-Ray can be addictive :-)
I wandered in here about eight years ago because I read that Pov-Ray could
render heightfields and I can’t get out. :-)

Stephen

[Gilles Tran] Re: Configuring POVray for use with Eagle 3D [6799 days 19 hours and 49 minutes ago]

Fri, 7 Sep 2007 13:52:00 GMT

"Tiger" <nos### [at] nospam> a écrit dans le message de news: 
46e15054@news.povray.org...
> Upon contacting the author of Eagle 3D I was told that I need to tell 
> POVray the location of a specific folder which came with Eagle 3D. 
> However, I don't see any way of configuring this in POVray.

Here:  http://www.povray.org/documentation/view/3.6.1/751/

G.

[Tiger] Configuring POVray for use with Eagle 3D [6799 days 20 hours and 20 minutes ago]

Fri, 7 Sep 2007 13:21:24 GMT

I'm a complete newbie when it comes to POVray and need some help 
configuring and using it.
I'm on a Powerbook G4 (1.67GHz) running MacOS 10.4.10.
I've installed POVray 3.6.

I barely know what POVray is (excuse my ignorance), but have an interest 
in it because of "Eagle 3D" which is a script that produces a .POV file 
out of an electronic circuit board design.
The POV file is then (as far as I know) run through POVray to create a 
3-dimensional drawing of the actual circuit board.
Check out this website for more info about Eagle 3D as well as pictures:
http://www.matwei.de/doku.php?id=en:eagle3d:eagle3d

What I've done so far is download the installation files from the above 
site, the direct file-link being: 
http://www.matwei.de/lib/exe/fetch.php?id=en%3Aeagle3d%3Aeagle3d&cache=cache&media=files:eagle3d:eagle3d_1_05_27112006.zip

And then I placed the ULP (script file) where my electronic design 
application; Eagle (http://www.cadsoft.de/) can find it.

However, when it comes to POVray and how to treat the Eagle-generated 
.POV file I'm totally lost.
I've so far double-clicked the POV file which loaded it into POVray, and 
following that I assumed that I should just go to the "Render" menu and 
choose to render this file. Well, I seemed to have gotten several error 
messages.
Upon contacting the author of Eagle 3D I was told that I need to tell 
POVray the location of a specific folder which came with Eagle 3D. 
However, I don't see any way of configuring this in POVray.

A folder named "POVray" comes with Eagle 3D which contains the following 
files:

total 1712
-rwx------   1   21456 Nov 27  2006 alphalcd.ttf
-rw-r--r--   1   39231 Nov 27  2006 cap.inc
-rw-r--r--   1   13141 Nov 27  2006 capwima.inc
-rw-r--r--   1      78 Nov 27  2006 col.inc
-rw-r--r--   1  210961 Nov 27  2006 connector.inc
-rw-r--r--   1   65218 Nov 27  2006 diode.inc
-rwx------   1   54344 Nov 27  2006 eagle3d.ttf
-rw-r--r--   1   59350 Nov 27  2006 ic.inc
-rw-r--r--   1   14237 Nov 27  2006 qfp.inc
-rw-r--r--   1   81236 Nov 27  2006 resistor.inc
-rw-r--r--   1   16955 Nov 27  2006 socket.inc
-rw-r--r--   1   95898 Nov 27  2006 special.inc
-rw-r--r--   1   48831 Nov 27  2006 switch.inc
-rwx------   1     223 Nov 27  2006 tex_elko.png
-rwx------   1    3039 Nov 27  2006 tex_elko_axial.png
-rw-r--r--   1   46472 Nov 27  2006 tools.inc
-rw-r--r--   1   33623 Nov 27  2006 trafo.inc
-rw-r--r--   1   31581 Nov 27  2006 transistor.inc
-rw-r--r--   1       0 Nov 27  2006 user.inc


I tried placing all those files in POVray's "include" folder, but I'm 
still getting error messages when I try to render the POV file, so I 
assume I have to place them somewhere else or I'm not understanding how 
to use POVray properly.
Here are those error messages:


POV-Ray 3.6 for Mac OS Frontend Build 197
Copyright © 1991-2003 Persistence of Vision Team™
Copyright © 2003-2004 Persistence of Vision Raytracer Pty. Ltd.
Persistence of Vision(tm) Ray Tracer Version 3.6.1 (Mac CodeWarrior)
This is an official version prepared by the POV-Ray Team. See the
  documentation on how to contact the authors or visit us on the
  internet at http://www.povray.org/.
POV-Ray is based on DKBTrace 2.12 by David K. Buck & Aaron A. Collins
Copyright 1991-2003 Persistence of Vision Team
Copyright 2003-2004 Persistence of Vision Raytracer Pty. Ltd.
Parsing Options
   Input file: Internal_drive:Users:Tiger:Desktop:test.pov (compatible 
to version 3.60)
   Remove bounds........On   Split unions.........On
   Library paths:
Output Options
   Image resolution 160 by 120 (rows 0 to 120, columns 0 to 160).
   Output file: test.pict, 24 bpp (system format)
   Graphic display.....On  (gamma:  1.8)
   Mosaic preview.......Off
   CPU usage histogram.Off
   Continued trace......Off
Tracing Options
   Quality:  9
   Bounding boxes......On  Bounding threshold: 1
   Light Buffer.........On   Vista Buffer.........On   Draw Vista 
Buffer....Off
   Antialiasing........Off
   Radiosity............Off
Animation Options
   Clock value....   0.000  (Animation off)
Possible Parse Error: Could not find file 'tools.inc'

File test.pov line 117
Parse Error: Cannot open include file tools.inc.

File test.pov line 117
Parse Warning: Check that the file is in a directory specifed with a +L 
switch or 'Library_Path='
.INI item. Standard include files are in the include directory or 
folder. Please read your
documentation carefully.

File test.pov line 117
Total Scene Processing Times
   Parse Time:    0 hours  0 minutes  0 seconds (0 seconds)
   Photon Time:   0 hours  0 minutes  0 seconds (0 seconds)
   Render Time:   0 hours  0 minutes  0 seconds (0 seconds)
   Total Time:    0 hours  0 minutes  0 seconds (0 seconds)

[David] Batch processing on Mac OS X [6822 days 1 hour and 21 minutes ago]

Thu, 16 Aug 2007 08:20:01 GMT

All,

I have some data generated by the ODE solvers from Matlab stored in a file
named odeoutput.txt, the last few lines of which look like:

bame $ tail odeoutput.txt
0.993566 0.394262 61.187156
0.994448 0.409454 61.278525
0.995562 0.430981 61.384690
0.996677 0.454422 61.480981
0.997791 0.479111 61.568231
0.998905 0.504504 61.647431
0.999179 0.510797 61.665778
0.999453 0.517097 61.683718
0.999726 0.523398 61.701265
1.000000 0.529694 61.718432

The first column contains time, the second values of theta, the third values
of phi.

I have a little ini file, defs.ini, in the same directory, that looks like:

bame $ cat defs.ini
#declare theta=var1;
#declare phi=var2;

I have a script file that will sketch the scene for each line of data in
odeoutput.txt.

bame $ cat generate_data
#! /bin/bash

for a in `cat odeoutput.txt|sed "s/ /_/g"`; do
        TIME=`echo $a|cut -d'_' -f1`;
        THETA=`echo $a|cut -d'_' -f2`;
        PHI=`echo $a|cut -c'_' -f3`;
        cat defs.ini|sed s/var1/$theta/|sec s/var2/$PHI/>newdefs.ini;
        povray -W640 -H480 +Oanim-$TIME.png anim.pov;
done;

At each step of the way, newdefs.ini will look something like this:

bame $ cat newdefs.ini
#declare theta=1.25;
#declare phi=3.18;

My question is how to do this on the Mac OS X version of Povray? Possible
somehow?

[Caligula] Re: My first render (my first problem) [6878 days 20 hours and 21 minutes ago]

Wed, 20 Jun 2007 13:20:01 GMT

Thorsten Froehlich <tho### [at] trfde> wrote:
> You have "Allow rendering of .pov files only" enabled but your file does not
> have a proper .pov extension.
>
>  Thortsne

Wow, I was having the same problem, but I didn't think it was so simple.

[drewbert] Re: Truncated Render Dialog [6904 days 3 hours and 46 minutes ago]

Sat, 26 May 2007 05:55:01 GMT

Well, I'll go ahead and reply to a two year old unanswered question :D

Damfino why it does this. But I'm glad to finally know *when* it does it.
Until your post I hadn't noticed the connection with quitting with the
window partially off screen. All I knew was that once in a while the window
would appear too cut off!

My fix for it is to open the file with a plain old text editor (TextEdit,
TextWrangler, etc.) and "save as", replacing the original file. Of course
you'll lose a bunch of render settings, but at least now you'll be able to
actually reset them.

[promotions] Wavefront OBJ,3DS,LightWave,PDB, PLY to POV-Ray ... [6933 days 6 hours and 51 minutes ago]

Fri, 27 Apr 2007 02:50:02 GMT

Hi

Pipeline3D has just been released! A free full-featured 30 day trial is
available from www.kalsaya.com and converts from Wavefront
OBJ, 3DS, LightWave LWO, Polygon PLY and Protein Databank PDB files into
POV-Ray file format. Pipeline3D is available for Mac OSX (as well as
Microsoft Windows and Linux).


Kalsaya Promotions

[Yvo Smellenbergh] Re: Macs and POV-Ray [6943 days 18 hours and 7 minutes ago]

Mon, 16 Apr 2007 15:33:59 GMT

Paul H <PCH### [at] gmailcom> wrote:

> Has there been any development from either Apple or POV-Ray regarding
> getting the software to work on Intel macs?  The most recent stuff I've
> seen on it on these forums are back from the summer and fall of 2006 so I
> figured I'd check in.  I'm new to the Mac line myself, and wouldn't know if
> there was an update from apple or how to get it.
> 
The official version runs under Rosetta.
If you want a native version you can try MegaPOV which is available as a
universal binary at:

http://megapov.inetart.net/download.html#Mac

Of course, all this info is already available in this newsgroup ;-)

Yvo

-- 
-----------------------------------
MegaPOV at:  http://megapov.inetart.net
MacMegaPOV at:  http://users.skynet.be/smellenbergh
E-mail: yvo### [at] gmxnet

[Paul H] Macs and POV-Ray [6944 days 17 hours and 21 minutes ago]

Sun, 15 Apr 2007 16:20:01 GMT

Has there been any development from either Apple or POV-Ray regarding
getting the software to work on Intel macs?  The most recent stuff I've
seen on it on these forums are back from the summer and fall of 2006 so I
figured I'd check in.  I'm new to the Mac line myself, and wouldn't know if
there was an update from apple or how to get it.

Thanks for any assistance!

[sahraoui] Re: How to compile [6968 days 11 hours and 16 minutes ago]

Thu, 22 Mar 2007 22:25:01 GMT

hey Charles

Cool. Actually I learnt how to do it. Thanks.
I have harder questions now.
I posted them on images newgroup

cheers

"Charles C" <nomail@nomail> wrote:
> "sahraoui" <sch### [at] uiucedu> wrote:
> > Hi
> >
> > I have downloaded a POV today. I have no idea how or where to start.
> > I use Mac OsX. I tried to look into the reference booklet and the tutorial
> > but I cannot take off. I tried to open a variety of files .pov. .ini, .inc
> > (I know
> > that .inc are C specific) but it seems that I need to compile
> > some files before I can have an image.
> >
> > Can any one tell me HOW can I get that BLOODY image so that i can use
> > it in my article.
> >
> > thanks for the pointer
>
> It sounds like you want to render an image from a .pov file, correct?
> Normally "compile" isn't used for this.  At first I thought you wanted to
> compile the program's source code into an executable.  By convention,
> POV-Ray include-files happen to share the same .inc file extension as C
> include-files, but it is not C. Instead POV-Ray uses it's own "Scene
> Description Language" or SDL.  The part of running POV-Ray which is similar
> to compiling is refered to as "parsing."
>
> I don't actually have a Mac* (I use the Windows version), but as I
> understand it, the Mac version of POV-Ray also has an editor.  What file
> are you wanting to render?  If it's anything like the Windows version, it
> should be a matter of dragging your scene-file into POV-Ray's editor and
> then hitting the "Run" button, or similar.    You might also want to read
> in the documentation about .ini files or command-line settings which will
> tell you how to set resolution, library paths, output directory, and other
> settings.
>
> Hope this helps,
> Charles
>
> *so somebody else can probably answer more clearly than I can.

[Charles C] Re: How to compile [6970 days 16 hours and 41 minutes ago]

Tue, 20 Mar 2007 17:00:02 GMT

"sahraoui" <sch### [at] uiucedu> wrote:
> Hi
>
> I have downloaded a POV today. I have no idea how or where to start.
> I use Mac OsX. I tried to look into the reference booklet and the tutorial
> but I cannot take off. I tried to open a variety of files .pov. .ini, .inc
> (I know
> that .inc are C specific) but it seems that I need to compile
> some files before I can have an image.
>
> Can any one tell me HOW can I get that BLOODY image so that i can use
> it in my article.
>
> thanks for the pointer

It sounds like you want to render an image from a .pov file, correct?
Normally "compile" isn't used for this.  At first I thought you wanted to
compile the program's source code into an executable.  By convention,
POV-Ray include-files happen to share the same .inc file extension as C
include-files, but it is not C. Instead POV-Ray uses it's own "Scene
Description Language" or SDL.  The part of running POV-Ray which is similar
to compiling is refered to as "parsing."

I don't actually have a Mac* (I use the Windows version), but as I
understand it, the Mac version of POV-Ray also has an editor.  What file
are you wanting to render?  If it's anything like the Windows version, it
should be a matter of dragging your scene-file into POV-Ray's editor and
then hitting the "Run" button, or similar.    You might also want to read
in the documentation about .ini files or command-line settings which will
tell you how to set resolution, library paths, output directory, and other
settings.

Hope this helps,
Charles

*so somebody else can probably answer more clearly than I can.

[sahraoui] Re: My first render (my first problem) [6971 days 11 hours and 6 minutes ago]

Mon, 19 Mar 2007 22:35:02 GMT

Thorsten Froehlich <tho### [at] trfde> wrote:
> You have "Allow rendering of .pov files only" enabled but your file does not
> have a proper .pov extension.
>
>  Thortsne

i have the proper extension but I still cannot have an image.
I am using the files supplied with the package. Let's say that I dowloaded
the stuff today and I did not get a chance to get a single image.

thanks

[sahraoui] How to compile [6971 days 11 hours and 21 minutes ago]

Mon, 19 Mar 2007 22:20:02 GMT

Hi

I have downloaded a POV today. I have no idea how or where to start.
I use Mac OsX. I tried to look into the reference booklet and the tutorial
but I cannot take off. I tried to open a variety of files .pov. .ini, .inc
(I know
that .inc are C specific) but it seems that I need to compile
some files before I can have an image.

Can any one tell me HOW can I get that BLOODY image so that i can use
it in my article.

thanks for the pointer

[Laurence H Smith] Re: Eagle 3D File will not render [6987 days 14 hours and 11 minutes ago]

Sat, 3 Mar 2007 19:30:05 GMT

On Fri, 2 Mar 2007 11:47:58 -0800, Thorsten Froehlich wrote
(in article <45e87f72@news.povray.org>):

> Laurence H Smith wrote:
>> I get a progress screen for Rendering, which it takes about 1.5 hours to 
>> finish, but nothing shows up.
> 
> So you turned preview off? There must have been some messages that told you 
> what happened and where the file was saved...

Unless preview is set to OFF by default, I didn't turn it off. There was no 
message that I could find and I searched my Hard Drive and could not find the 
file with that name.
> 
>> Move the same file over a PC and ran the file. Loaded in less the 5 
>> seconds, 
>> Rendered at low Res. in less than 20 seconds.
>> 
>> What am I doing wrong?
> 
> The Mac doesn't have enough memory to load the file, so it has to swap. At 
> least that is the most likely guess. -- You did not provide enough useful 
> information for anybody to provide you with any help that will actually help 
> you. One can only guess...
> 
> 	Thorsten

I am guessing you need more information about my computer. It is a 17" 
PowerBook G4. 
  CPU Type:	PowerPC G4 (1.5)
  Number Of CPUs:	1
  CPU Speed:	1.67 GHz
  L2 Cache (per CPU):	512 KB
  Memory:	2 GB
  Bus Speed:	167 MHz
  Boot ROM Version:	4.9.6f0

The file Micro.pov is 388 KB. It took 13 minutes and 38 seconds to load. I 
didn't try to Render because I didn't want to wait another 1.5 hours to find 
out it didn't work.

In the preferences for POV-RAY under "Scenes", I added "Macintosh 
HD:Applications:POV-RAY:Include:" This is the only thing that shows up in 
Scenes.

Could you use more information?

[Thorsten Froehlich] Re: Eagle 3D File will not render [6988 days 13 hours and 53 minutes ago]

Fri, 2 Mar 2007 19:48:02 GMT

Laurence H Smith wrote:
> I get a progress screen for Rendering, which it takes about 1.5 hours to 
> finish, but nothing shows up.

So you turned preview off? There must have been some messages that told you 
what happened and where the file was saved...

> Move the same file over a PC and ran the file. Loaded in less the 5 seconds, 
> Rendered at low Res. in less than 20 seconds.
> 
> What am I doing wrong?

The Mac doesn't have enough memory to load the file, so it has to swap. At 
least that is the most likely guess. -- You did not provide enough useful 
information for anybody to provide you with any help that will actually help 
you. One can only guess...

	Thorsten

[Laurence H Smith] Eagle 3D File will not render [6988 days 14 hours and 40 minutes ago]

Fri, 2 Mar 2007 19:01:24 GMT

I have produced a .pov file from an Eagle circuit board file and I am trying 
to Render it in Pov-Ray for Mac OS X 3.6.0. Here is what is happening: 

	I double clicked the .pov file and it launches POV-RAY just fine

	The spinning beach ball stays on for about 10 minutes and finally shows me 
the file.

I select Render and the spinning beach ball stays on for about 10 minutes.

I get a progress screen for Rendering, which it takes about 1.5 hours to 
finish, but nothing shows up.

Move the same file over a PC and ran the file. Loaded in less the 5 seconds, 
Rendered at low Res. in less than 20 seconds.

What am I doing wrong?

[Anton Sherwood] Re: missing library? [7013 days 4 hours and 56 minutes ago]

Tue, 6 Feb 2007 04:45:26 GMT

Anton Sherwood wrote:
> I wiped and reinstalled MacOS recently, and the first time I go to run 
> Povray (Unix-style, not as a Mac-style app) I get this:
> 
>     dyld: Library not loaded: /usr/X11R6/lib/libXpm.4.dylib

	...

Well I downloaded the source again and recompiled, and now it's happy.

-- 
Anton Sherwood, http://www.ogre.nu/
"How'd ya like to climb this high *without* no mountain?" --Porky Pine

[Anton Sherwood] missing library? [7014 days 23 hours and 17 minutes ago]

Sun, 4 Feb 2007 10:24:15 GMT

I wiped and reinstalled MacOS recently, and the first time I go to run 
Povray (Unix-style, not as a Mac-style app) I get this:

	dyld: Library not loaded: /usr/X11R6/lib/libXpm.4.dylib

I sure don't remember having to install that before.  I go to that 
directory and see that "libXpm.4.11.dylib" exists, so I make 
"libXpm.4.dylib" a link to it, and try again.

	dyld: Library not loaded: /usr/X11R6/lib/libSM.6.dylib

Sigh.  The nearest thing this time is libSM.a, and linking doesn't work.

Have I missed something obvious?

-- 
Anton Sherwood, http://www.ogre.nu/
"How'd ya like to climb this high *without* no mountain?" --Porky Pine

[Nell] Re: Command line povray for OS X? [7050 days 17 hours and 21 minutes ago]

Sat, 30 Dec 2006 16:20:01 GMT

Thanks Günther!

I just tried option 3 and downloaded the Unix source, installed as you said,
and it works great!

Nell

[Günther Dietrich] Re: Command line povray for OS X? [7051 days and 56 minutes ago]

Sat, 30 Dec 2006 08:45:11 GMT

"Nell" <emo### [at] colbyedu> wrote:

>I am also new to POV-Ray, and wondering the answer to Miguel's first
>question.  Is there any command line version that works with OS X?

There are three options:
- As with Blender, you could use the binary contained in the application
  bundle (POV-Ray.app/Contents/MacOS/pov-ray). Oops -- POV-Ray is not a
  bundled application. Sorry, only two options remain.
- There might be anybody who offers a command line version on his web
  site. Be aware of his reputation and think about the possibilities of
  malware.
- Download the (Unix) source package from the POV-Ray web site and
  compile it yourself. Macs bring all necessary tools along when you
  have installed the Development Tools, contained on one of the software
  disks you got with your Mac.

Formerly, it was a bit complicated to compile POV-Ray, but the last 
versions (3.6, 3.6.1, and, maybe, 3.5.x) were very simple to compile -- 
only three commands:

./configure
make
sudo make install

That's the way, how I got the command line version of 3.6 and 3.6.1 for 
batch rendering.



Regards,

Günther

[Nell] Re: Command line povray for OS X? [7051 days 9 hours and 51 minutes ago]

Fri, 29 Dec 2006 23:50:00 GMT

I am also new to POV-Ray, and wondering the answer to Miguel's first
question.  Is there any command line version that works with OS X?  Trying
to write a Java application that renders and displays POV-Ray images and
having a little trouble.

Thanks for the help!
Nell

[jtico] Re: MacMegaPOV 1.2.1 Universal Binary update nov... [7099 days 10 hours and 9 minutes ago]

Sat, 11 Nov 2006 23:31:54 GMT

Thanks for the ubpates Yvo. I appreciate it very much. :)
Cheers.

[FurBall] Re: Subset_Start_Frame doesn't work? [7106 days 17 hours and 1 minute ago]

Sat, 4 Nov 2006 16:40:00 GMT

Thorsten Froehlich <tho### [at] trfde> wrote:
> FurBall wrote:
> > Am I missing something here?
> > I'm running POV-Ray version 3.7.0.beta.16.msvc8.win64
>
> This group is for the Mac version of POV-Ray. Questions about beta versions
> should be asked in the beta-test group, and nowhere else.
>
>  Thorsten

You're right, my mistake!
I tried to post this to the Windows-group, but did something wrong and
couldn't find the message again. So I thought the post was lost in transit,
but here it is.
Sorry.
Posted it in the right group and got my answer!

[Thorsten Froehlich] Re: Subset_Start_Frame doesn't work? [7107 days 17 hours and 57 minutes ago]

Fri, 3 Nov 2006 15:44:31 GMT

FurBall wrote:
> Am I missing something here?
> I'm running POV-Ray version 3.7.0.beta.16.msvc8.win64

This group is for the Mac version of POV-Ray. Questions about beta versions
should be asked in the beta-test group, and nowhere else.

	Thorsten

[FurBall] Re: Multiple POV-Ray instances possible on Mac? [7107 days 18 hours and 1 minute ago]

Fri, 3 Nov 2006 15:40:00 GMT

Thorsten Froehlich <tho### [at] trfde> wrote:
> FurBall wrote:
> > Is it possible to run multiple instances of POV-Ray on a Mac?
> > I haven't been able to find a setting for this.
>
> Mac GUI applications cannot be run in multiple instances, that is a Windos
> thing helping users to work around applications that cannot perform certain
> tasks in parallel (the way POV-Ray for Windows uses it, as you can that way
> have multiple renders running that way), or applications that are so
> unstable you don't want them to run as a single instance (the way Internet
> Explorer needs that feature ;-) ). You can make copies of POV-Ray and run
> each of those on Macs if you want to have multiple parallel renders running.
>
>  Thorsten

Thanks for your advice!
I would never have tried that, but it works!
Thanks again!!

[FurBall] Subset_Start_Frame doesn't work? [7107 days 18 hours and 11 minutes ago]

Fri, 3 Nov 2006 15:30:00 GMT

When I render an animation from an INI-file that contains the following
lines:
   Final_Frame=675
   Subset_Start_Frame=125
   Subset_End_Frame=276
I get frames 1 through 276 and not 125 through 276.
Apparently, Subset_Start_Frame doesn't work and Subset_End_Frame does.
Same behaviour when I use +SF125 in the INI-file.
Same behaviour when I use the commandline to specify the startframe.

Am I missing something here?
I'm running POV-Ray version 3.7.0.beta.16.msvc8.win64

Thanks for your help and your time!

[Thorsten Froehlich] Re: Multiple POV-Ray instances possible on Mac? [7107 days 19 hours and 19 minutes ago]

Fri, 3 Nov 2006 14:21:56 GMT

FurBall wrote:
> Is it possible to run multiple instances of POV-Ray on a Mac?
> I haven't been able to find a setting for this.

Mac GUI applications cannot be run in multiple instances, that is a Windos
thing helping users to work around applications that cannot perform certain
tasks in parallel (the way POV-Ray for Windows uses it, as you can that way
have multiple renders running that way), or applications that are so
unstable you don't want them to run as a single instance (the way Internet
Explorer needs that feature ;-) ). You can make copies of POV-Ray and run
each of those on Macs if you want to have multiple parallel renders running.

	Thorsten

[FurBall] Multiple POV-Ray instances possible on Mac? [7107 days 19 hours and 36 minutes ago]

Fri, 3 Nov 2006 14:05:00 GMT

Is it possible to run multiple instances of POV-Ray on a Mac?
I haven't been able to find a setting for this.

Thanks for your time!!

[Yvo Smellenbergh] MacMegaPOV 1.2.1 Universal Binary update nov 2006 [7108 days 23 hours and 2 minutes ago]

Thu, 2 Nov 2006 10:38:38 GMT

A small update is available of MacMegaPOV v 1.21  Universal Binary (Nov
2006).

http://megapov.inetart.net/download.html#Mac

This is a list with the major fixes and changes since the last version.
- A new menu item "Insert Menu", was added to the template
  menu,compatible with the official Windows version of POV_Ray.

- A small progress window was added.

- If the message window is closed, it will not open when a render is
  starting, only when an error occurs.

- A few changes for the window menu.

- Using the "Render" icon on the editor window will no longer put the
  preferences panel to the front or show it if it is hidden. It will
  simply render the current scene with the options set in the
  preferences window. To change settings before rendering, hit the "Set
  Up" icon on the toolbar of the editor window.

- There were a few bugs when using the option "Maintain indentation".
  These have been fixed.

- Tuning text streams on and off fixed.

Yvo
-----------------------------------
MegaPOV at:  http://megapov.inetart.net
MacMegaPOV at:  http://users.skynet.be/smellenbergh
E-mail: yvo### [at] gmxnet

-- 
-----------------------------------
MegaPOV at:  http://megapov.inetart.net
MacMegaPOV at:  http://users.skynet.be/smellenbergh
E-mail: yvo### [at] gmxnet

[Francois LE COAT] Fw: [Re: Real-time raytracing test] [7109 days 22 hours and 55 minutes ago]

Wed, 1 Nov 2006 10:45:56 GMT

Hi Chris,

Chris Cason wrote :
 > For those interested, please visit <http://www.povray.org/beta/rtr/>
 > It's not very well tested (only on the systems I had available to me),

 > so YMMV. Expect it to have some rough edges. Please report issues
 > here.

It's such a pity I can't test this nice feature on my dua### [at] 125GHz
using the Altivec Multimedia Instruction Set, either under MacOSX or
Yellow Dog Linux, taking advantage of my iSight FireWire camera :(

I'm sure that Persistence Of Vision is not intended to Win users !
Furthermore for little-endian (x86 - x86_64) architectures.

Do you really mind the huge amount of work that will need to be done ?

This configuration is the typical devel system for the upcoming
PlayStation3 multimedia platform, embedding a big-endian CPU (Cell),
that is shipping the 17th of November in the USA and Japan, or at
March 2007 for the rest of the world.

c.f. <http://www.terrasoftsolutions.com/products/ydl/delivery.shtml>
or <http://www.us.playstation.com/PS3/> :-D

Regards,

-- François LE COAT
Author of Eureka 2.12 (2D Graph Describer, 3D Modeller)
<http://eureka.atari.org/>

[Thorsten Froehlich] Re: POV-files greyed out [7110 days 13 hours and 50 minutes ago]

Tue, 31 Oct 2006 19:50:48 GMT

FurBall wrote:
>> Ah, that would explain it. likely somewhere along the way the fact that they
>> are text files gets lost, and without knowing the extension on the Mac side
>> they when you unpack or just download them, they get marked as data. One way
>> to go is to zip them, download the zip and then unpack the unzip file via
>> the command line (using Terminal) or with StuffIt Expander. That way they
>> should survive. The command line unzip does not set any file types, and
>> StuffIt Expander can currently detect most text files. So either will work.
>>
>>     Thorsten
> 
> I tried what you suggested.
> This works a little better!
> POVRay still has the files greyed out, BUT double-clicking them from Finder
> will open them in POVRay!!
> So, I guess I will be opening them from Finder for the next couple of
> months.

Note that the reason they are greyed out is has nothing to do with their
file extension: If you can open files by drag and drop from the Finder, you
can just as well open them in the file open dialog. All you have to do is
select "All Documents" as previously outlined. What makes POV-Ray decide
that it can handle a file is independent of that of the file selection
dialog (which is supplied by the operating system and operates under some
annoying constraints)!

In fact, the method used to pass a file selected in the dialog to POV-Ray to
open it is identical to the method the Finder users to tell POV-Ray to open
it - both use Apple Events, aka Apple Scripts "open" event you can also
create in the Apple Script editor.

	Thorsten

[FurBall] Re: POV-files greyed out [7110 days 14 hours and 51 minutes ago]

Tue, 31 Oct 2006 18:50:00 GMT

>
> Ah, that would explain it. likely somewhere along the way the fact that they
> are text files gets lost, and without knowing the extension on the Mac side
> they when you unpack or just download them, they get marked as data. One way
> to go is to zip them, download the zip and then unpack the unzip file via
> the command line (using Terminal) or with StuffIt Expander. That way they
> should survive. The command line unzip does not set any file types, and
> StuffIt Expander can currently detect most text files. So either will work.
>
>     Thorsten

I tried what you suggested.
This works a little better!
POVRay still has the files greyed out, BUT double-clicking them from Finder
will open them in POVRay!!
So, I guess I will be opening them from Finder for the next couple of
months.

Thanks an awful lot for all your help, Thorsten!!

[Thorsten Froehlich] Re: POV-files greyed out [7111 days 13 hours and 7 minutes ago]

Mon, 30 Oct 2006 20:34:20 GMT

FurBall wrote:
> The .pov- and .inc-files I started with, were created on a PC.
> Uploaded them to my webspace and downloaded them again with the Mac.
> Maybe their creation on PC or their transport through Unix has something to
> do with it.
> I don't understand why most, but not all, of these files were greyed out.

Ah, that would explain it. likely somewhere along the way the fact that they
are text files gets lost, and without knowing the extension on the Mac side
they when you unpack or just download them, they get marked as data. One way
to go is to zip them, download the zip and then unpack the unzip file via
the command line (using Terminal) or with StuffIt Expander. That way they
should survive. The command line unzip does not set any file types, and
StuffIt Expander can currently detect most text files. So either will work.

    Thorsten

[FurBall] Re: POV-files greyed out [7111 days 15 hours and 56 minutes ago]

Mon, 30 Oct 2006 17:45:01 GMT

Thorsten Froehlich <tho### [at] trfde> wrote:
>
> Ah, OK, now I understand what you are doing. Indeed, other than three beeps
> there currently is no feedback if you force POV-Ray to open a file it cannot
> handle. There is only one condition under which this can happen: The file
> is, or at least claims to be, no ordinary text file. Are you certain you
> have plain text files, and did not accidentally create an Rich Text or
> Unicode text file? If I create a new file with TextEdit and select "Western
> (Mac Roman)" as encoding when saving the file, it works just fine in POV-Ray.
>
>     Thorsten

The .pov- and .inc-files I started with, were created on a PC.
Uploaded them to my webspace and downloaded them again with the Mac.
Maybe their creation on PC or their transport through Unix has something to
do with it.
I don't understand why most, but not all, of these files were greyed out.

I don't know how to check the file-format on a Mac, but here's what I did:
Load a test.pov-file in TextEdit and select Save As test.pov(same name,
"Western > Mac Roman" is default).
The file will still be greyed out in POVRay, but this time I can open it by
selecting All Documents in File/Open.

So, unfortunately, re-saving the files in TextEdit doesn't completely solve
the problem.
Seems that the first workaround (paste text in POVRay in new document)
remains my only option.

Thanks a lot for your help!!!!

[Thorsten Froehlich] Re: POV-files greyed out [7112 days 13 hours and 51 minutes ago]

Sun, 29 Oct 2006 19:50:05 GMT

FurBall wrote:
> OK, here's what I mean:
> I select File/Open and most of the files that I see, are greyed out.
> I select "All Documents" from the Enable-pulldown-menu and all files become
> selectable
> - If I select a .pov-file that was previously NOT greyed out and press
> Enter, the Text Editor-window opens and when I select the Window-menu I see
> the pov-file.
> - If I select a .pov-file that WAS previously greyed out and press Enter,
> nothing happens. No Text Editor-window, no pov-file in the Window-menu, no
> error-message. 

Ah, OK, now I understand what you are doing. Indeed, other than three beeps
there currently is no feedback if you force POV-Ray to open a file it cannot
handle. There is only one condition under which this can happen: The file
is, or at least claims to be, no ordinary text file. Are you certain you
have plain text files, and did not accidentally create an Rich Text or
Unicode text file? If I create a new file with TextEdit and select "Western
(Mac Roman)" as encoding when saving the file, it works just fine in POV-Ray.

    Thorsten

PS: It is expected behavior that applications ignore files dropped on them
that they cannot handle (well, POV-Ray beeps). However, I agree that there
should be an error message in case the user forced opening of an unsupported
file type if that file type cannot be handled at all.

[FurBall] Re: POV-files greyed out [7112 days 17 hours and 26 minutes ago]

Sun, 29 Oct 2006 16:15:00 GMT

Thorsten Froehlich <tho### [at] trfde> wrote:
> FurBall wrote:
> > Thanks for your reply, Thorsten!
> >
> > I tried that, but the greyed out files just don't show up in POVRay.
>
> What do you mean with "just don't show up", yet you also say "greyed out"?
> Clearly, both cannot be the case, so you omitted some step you took, which
> is likely the clue to explain and thus correct your mistake.
>
>     Thorsten

OK, here's what I mean:
I select File/Open and most of the files that I see, are greyed out.
I select "All Documents" from the Enable-pulldown-menu and all files become
selectable
- If I select a .pov-file that was previously NOT greyed out and press
Enter, the Text Editor-window opens and when I select the Window-menu I see
the pov-file.
- If I select a .pov-file that WAS previously greyed out and press Enter,
nothing happens. No Text Editor-window, no pov-file in the Window-menu, no
error-message.

The same happens when I double-click a .pov-file in Finder. POVRay starts
and:
- a file that was NOT greyed out (in POVRay) opens as expected
- a file that WAS greyed out (in POVRay) is not displayed in a Text Editor
window, is not visible in the Window-menu and I get no error-message.
---------

In the meantime I tried something else:

I moved all POVRay-folders to another harddisk, so it's no longer in the
Applications folder where I "installed" (copied) POVRay.
The behaviour is the same as described above, EXCEPT:
- when I copy the text of a greyed out test.pov-file to the clipboard in
TextEdit, paste it to a New file in POVRay and save it with the same name
test.pov (overwrite it), close test.pov in POVRay and try to open it again,
it's greyed out and will not open, etcetera.
BUT,
- when I copy the text of a greyed out test.pov-file to the clipboard in
TextEdit, paste it to a New file in POVRay and save it with a NEW name
testnew.pov, close testnew.pov in POVRay and open it again, it will open.

It looks like some files have a (MacOS?)-attribute that is no problem for
Finder  or TextEdit, but is for POVRay.
When POVRay saves a new file to disk, this file doesn't get this attribute
and is handled properly by POVRay's File/Open.
So, I have a (terrible) workaround and/but would still like solve this
problem.
Thanks for your help!!

[Thorsten Froehlich] Re: POV-files greyed out [7113 days 8 hours and 25 minutes ago]

Sun, 29 Oct 2006 01:15:59 GMT

FurBall wrote:
> Thanks for your reply, Thorsten!
> 
> I tried that, but the greyed out files just don't show up in POVRay.

What do you mean with "just don't show up", yet you also say "greyed out"?
Clearly, both cannot be the case, so you omitted some step you took, which
is likely the clue to explain and thus correct your mistake.

    Thorsten

[FurBall] Re: POV-files greyed out [7113 days 9 hours and 41 minutes ago]

Sun, 29 Oct 2006 00:00:01 GMT

Thorsten Froehlich <tho### [at] trfde> wrote:

> Yes, there is a popup menu like in all other file selection dialogs, that
> allows you to select files that don't have the right file type. Select to
> show all documents there, and you can get POV-Ray to open any file type.
>
>     Thorsten

Thanks for your reply, Thorsten!

I tried that, but the greyed out files just don't show up in POVRay.
If I load a non-greyed out file that way, it does show up.
Almost all of my files are greyed out, so this is a big problem.
All of the files were copied to the Mac in 1 copy-action, so there's no
difference between files there.
I also tried changing Ownership & Permissions for all relevant folders and
files to Read & Write, but that doesn't make any  difference.

What am I doing wrong here?

[Thorsten Froehlich] Re: POV-files greyed out [7113 days 15 hours ago]

Sat, 28 Oct 2006 18:41:11 GMT

FurBall wrote:
> I usually work with POVRay for Windows.
> The next few months I have a 4x2.5 GHz PowerPC G5 (OSX 10.4.8)at my
> disposal. Nice to try it out with POVRay!!!
> So, I copied POVRay 3.6 (Mac-version, of course) to the Mac.
> It works pretty OK, except for the fact that only certain .pov- and
> ..inc-files can be opened  from the File/Open-dialogue box: most .pov-files
> are greyed out and are not selectable.
> I even tried this:
> - open .pov-file with TextEdit and copy all text,
> - File/New in POVRay, paste text in and File/Save As
> - it will render, but I still cannot open that file with File/Open
> 
> Is there anything I can do to make ALL .pov-files selectable from POVRay's
> File/Open-dialogue?

Yes, there is a popup menu like in all other file selection dialogs, that
allows you to select files that don't have the right file type. Select to
show all documents there, and you can get POV-Ray to open any file type.

    Thorsten

[FurBall] POV-files greyed out [7113 days 15 hours and 36 minutes ago]

Sat, 28 Oct 2006 18:05:00 GMT

I usually work with POVRay for Windows.
The next few months I have a 4x2.5 GHz PowerPC G5 (OSX 10.4.8)at my
disposal. Nice to try it out with POVRay!!!
So, I copied POVRay 3.6 (Mac-version, of course) to the Mac.
It works pretty OK, except for the fact that only certain .pov- and
..inc-files can be opened  from the File/Open-dialogue box: most .pov-files
are greyed out and are not selectable.
I even tried this:
- open .pov-file with TextEdit and copy all text,
- File/New in POVRay, paste text in and File/Save As
- it will render, but I still cannot open that file with File/Open

Is there anything I can do to make ALL .pov-files selectable from POVRay's
File/Open-dialogue?

I appreciate any help!

[Thorsten Froehlich] Re: Povray crashes [7116 days 16 hours and 19 minutes ago]

Wed, 25 Oct 2006 17:21:52 GMT

Allan wrote:
> Oops, in my previous note I wrote "Craig".  I meant to write "Cray".  My
> friend works at Cray, Inc., and has rather nice things to say about gcc but
> I guess he is just another ignorant doofus like me.
> 
> BTW, Objective-C is not proprietary to Apple.  There are many
> implementations of Obj-C, even one on Windows.  Cocoa, on the other hand is
> Apple's but it is an API of classes for Apple's GUI, much like MFC is for
> Windows.  Interfacing a GUI front-end written in Objective-C with legacy
> code written in C is trivial

<irony>What an amazing news! -- Code written in different programming
languages can be interfaced, really, amazing news!!! </irony>

For those still lost: Of course, it would be even more amazing if it hadn't
been old news many decades ago. Back in times when parts were written in
assembler, and others in higher-level languages. Naturally, there always
were way to interface the two, otherwise no program could run on an
operating system not written in the same language...

	Thorsten

[Allan] Re: Povray crashes [7116 days 16 hours and 56 minutes ago]

Wed, 25 Oct 2006 16:45:00 GMT

Oops, in my previous note I wrote "Craig".  I meant to write "Cray".  My
friend works at Cray, Inc., and has rather nice things to say about gcc but
I guess he is just another ignorant doofus like me.

BTW, Objective-C is not proprietary to Apple.  There are many
implementations of Obj-C, even one on Windows.  Cocoa, on the other hand is
Apple's but it is an API of classes for Apple's GUI, much like MFC is for
Windows.  Interfacing a GUI front-end written in Objective-C with legacy
code written in C is trivial, but only a real Mac programmer would know
that.

Good Bye.

[Thorsten Froehlich] Re: Povray crashes [7116 days 19 hours and 32 minutes ago]

Wed, 25 Oct 2006 14:08:42 GMT

Allan wrote:
>> This claim is complete nonsense: Mac OS X has not been available on x86
>> processors until last year (in beta versions on a single system
>> configuration). I suppose you are confusing Mac OS X with the Mach kernel,
>> which indeed has been running on x86 processors for decades now.
> 
> Fact: Apple has been running OS X on intel processors since the inception of
> OS X.  Just look at the frigin 10.0, 10.1, 10.2, 10.3, etc, source code!  Do
> you think they were coding #ifdef i386 for practice?

Apple has only released the source code of the kernel, and thus your
statement is definitive proof that you do not understand what you are
talking about!!! The GUI and anything above kernel level (except standard
Unix OSS tools of course) were never released as source code, and have not
been to this day, all for very obvious reasons (they are confidential Apple
intellectual property).

Binary-only releases of those x86 system layers above the kernel level were
made available last year as part of the x86 versions of Mac OS X. And that
Mac OS X is more than its kernel and Unix environment should be clear to
even the most ignorant and clueless around. Of course, assuming you actually
know what a kernel is, which I suppose you don't know either :-(

> Considering the GUI interface on POV-ray for the Mac, what you need to
> understand is this: forget Code Warrior, Code Warrior is dead, dead, dead.
> Long live XCode.  Code Warrior can RIP for all we Mac programmers care.
> Take a few hours to learn Objective-C and Interface Builder and put a
> decent front-end on the POV-ray C code and build a universal app for PPC
> and intel.

Which again shows you absolutely do not understand what you are talking
about. XCode, which is just an unreliable IDE for gcc, supports Apple Carbon
API (aka standard C and C++) development just fine, much better than Cocoa
API (aka Objective-C) in fact.  Objective-C is a proprietary Apple-only
extension to gcc, and hence does not enjoy the widespread support as the
standard C and C++ compilers within gcc. That CodeWarrior has been
discontinued for Macs has absolutely nothing to do with porting.

In fact, you conveniently overlooked or did not understand that part in my
Sept 25 reply to you, where I explicitly point out the porting problems. If
you had understood what I was talking about, you would instantly have
noticed that neither of the issues listed there have anything to do with the
GUI frontend for POV-Ray. Porting that is almost trivial.

> I have said enough on this thread and will not be posting to it any more.

Thank you! You really have wasted my time long enough :-(

	Thorsten

[ABX] Re: Povray crashes [7116 days 20 hours and 23 minutes ago]

Wed, 25 Oct 2006 13:18:32 GMT

On Tue, 24 Oct 2006 22:50:59 EDT, "Allan" <all### [at] WholeCheesecom> wrote:
> Could you please be a just a little bit more condescending?

http://www.google.pl/search?q=poor+gcc+performance+mac gives
http://www.ctoforaday.com/articles/000019.html which repeats general notes
about gcc internal design problems I saw here and there.

HTH,

ABX

[Allan] Re: Povray crashes [7117 days 6 hours and 46 minutes ago]

Wed, 25 Oct 2006 02:55:00 GMT

Thorsten Froehlich <tho### [at] trfde> wrote:

>Then you clearly have insufficient experience. Try Google if you seriously
>want specifics on the many gcc performance problems. The gcc mailing lists
>are a good resource, too.

Could you please be a just a little bit more condescending?  I am not sure
if you are really trying to piss me off or are just flaunting your vast
knowledge of everything and anything.  While I do not claim to have a PHd
in anything, I do know a thing or two about computers having been
programming on the beasts since 1972.  Plus, I have a number of
acquaintances, one who is a systems engineer at Craig and the other
formally of Pixar, who are fairly knowledgeable about gcc and they both
laughed when I told them what you said about gcc.  Basicaly, unless you are
simulating atomic bomb blasts or running climate models, gcc is plenty fine
enough for ray tracing.  (Take a look at MegaPOV on an intel Mac: it beats
the pants off of the G5 running PPC POV-ray any day.)

>> to the "rushed and incomplete port" of OS X to the intel architecture:
>> where have you been hiding the last few years?  OS X has been running on
>> intel processors since version 10.0.

>This claim is complete nonsense: Mac OS X has not been available on x86
>processors until last year (in beta versions on a single system
>configuration). I suppose you are confusing Mac OS X with the Mach kernel,
>which indeed has been running on x86 processors for decades now.

Fact: Apple has been running OS X on intel processors since the inception of
OS X.  Just look at the frigin 10.0, 10.1, 10.2, 10.3, etc, source code!  Do
you think they were coding #ifdef i386 for practice?   Yes, indeed, they did
release OS X for intel just last year but it was hardly "rushed and
incomplete", it was just the right time to release it.  The G5 was the top
of the line for PPC and they were not going to milk any more speed or
dollars out of it.  Along comes intel dual core and now they have something
faster and better than the G5.

>To understand the difference between a rushed introduction and a planned
>introduction, compare the current mess with the 68K to PowerPC transition:

Considering the GUI interface on POV-ray for the Mac, what you need to
understand is this: forget Code Warrior, Code Warrior is dead, dead, dead.
Long live XCode.  Code Warrior can RIP for all we Mac programmers care.
Take a few hours to learn Objective-C and Interface Builder and put a
decent front-end on the POV-ray C code and build a universal app for PPC
and intel.

I have said enough on this thread and will not be posting to it any more.

-Allan

[Thorsten Froehlich] Re: Povray crashes [7120 days 4 hours and 53 minutes ago]

Sun, 22 Oct 2006 04:48:22 GMT

Allan wrote:
> I have never heard
> anyone in my years of experience ever say the gcc compiler was "poor". 

Then you clearly have insufficient experience. Try Google if you seriously
want specifics on the many gcc performance problems. The gcc mailing lists
are a good resource, too.

> to the "rushed and incomplete port" of OS X to the intel architecture:
> where have you been hiding the last few years?  OS X has been running on
> intel processors since version 10.0. 

This claim is complete nonsense: Mac OS X has not been available on x86
processors until last year (in beta versions on a single system
configuration). I suppose you are confusing Mac OS X with the Mach kernel,
which indeed has been running on x86 processors for decades now.

> Apple took their time to release the intel version for obvious marketing
> reasons.

To understand the difference between a rushed introduction and a planned
introduction, compare the current mess with the 68K to PowerPC transition:
At least by the time the first PowerPC systems shipped there was a working
and fully supported debugger available that would work on emulated and
native code. Further, native and emulated code could even be linked together
transparently by design. Neither is the case for the PowerPC to x86
transition. In fact, Apple quickly abandoned all attempts of even providing
a debugger for emulated code (and quite obviously to date there is none),
and to further rush the "transition", Apple also elected to provide
absolutely no way for native and emulated code to work together by any
means, let alone linking.

Of course, maybe a timeline is easier to understand for you: There were over
three years between the announcement of the transition to the initial
switch, while this time around everything from the announcement to
abandoning all previous hardware took just barely one year. Compare that to
similar transitions at HP/Compaq/DEC, Sun, SGI, or IBM. They all
concurrently develop their systems on different architectures for many
years, and most certainly none of them over dropped one processor
architecture for another literary from one day to the next, by public
announcement to developers and users at the same time. Not even SGI, which
certainly had every financial motivation to do so!

> As for the "broken emulator", Apple clearly states that well written and
> well behaved applications will run with no problem under Rosetta.

I have yet to read such a statement: I suppose you simply misinterpreted
some statement by Apple, but effectively it does not matter as fact is
Rosetta does not work with POV-Ray, yet POV-Ray runs on every real
PowerPC-based Mac, so how you can argue anything but that Rosetta is broken
is beyond logic :-(

Fact is that POV-Ray is an industry-standard benchmark application. If
Rosetta cannot handle it, it actually is either sign of incompetence on part
of the Rosetta developers or managers deciding to ignore Rosetta's problems.
My personal suspicion is that it is a management problem (aka Apple-"god"
Jobs), which also explains the rushed transition in general.

> I also have Silo v1.42 running with no problems.  These are hardly trivial
> applications.  What kind of platform dependent tricks do you employ in
> POV-ray that b) breaks Rosetta?

I have no idea what "tricks" you think there exist for such purpose. Either
you know very little about programming, or you are asserting POV-Ray 3.6 -
released years before Rosetta was even developed - was intentionally
designed to not work with Rosetta. As such, I can only conclude you either
don't know what you are talking about or you need serious help from a
psychiatrist...

> a) makes it difficult to port

I have already answered this question in a reply to you on September 25th.

	Thorsten

[Allan] Re: Povray crashes [7120 days 14 hours and 51 minutes ago]

Sat, 21 Oct 2006 18:50:00 GMT

Good grief!  With an attitude like this it is no wonder that POV-ray for the
Mac is all but doomed for extinction.  Where you get such authority to
dismiss OS X like this is beyond my comprehension.  I have never heard
anyone in my years of experience ever say the gcc compiler was "poor".  As
to the "rushed and incomplete port" of OS X to the intel architecture:
where have you been hiding the last few years?  OS X has been running on
intel processors since version 10.0.  It was not rushed, on the contrary,
Apple took their time to release the intel version for obvious marketing
reasons.

As for the "broken emulator", Apple clearly states that well written and
well behaved applications will run with no problem under Rosetta.  I have
the latest version of Photoshop v9.0.2 running on my MacPro: it is not yet
a native intel app and it runs under Rosetta with no problems whatsoever.
I also have Silo v1.42 running with no problems.  These are hardly trivial
applications.  What kind of platform dependent tricks do you employ in
POV-ray that a) makes it difficult to port, and b) breaks Rosetta?

Fortunately, MegaPOV is running great on the MacPro.  It is a native intel
app and has a number of very nice features that are not available in
POV-ray.  My advice to all the intel Mac users here: get MegaPOV and be
happy.

Thorsten wrote:

>Porting is not the problem: A quick and dirty port of almost
>anything is mostly trivial indeed, assuming it already works
>with a poor compiler like gcc and its even worse C and C++
>libraries in the first place.

>I have to seriously doubt your experience if you claim about
>yourself "Every app I've ever written for PPC Macs have ported
>easily over to Intel."

>The x86 PCs sold by Apple, unfortunately, are everything but
>reliable mostly due to the rushed and incomplete port of the
>Mac OS X.

>As previously stated, you should not expect an official version
>of POV-Ray for Mac OS X natively running on x86 PCs sold by
>Apple before 2008. However, there is of course some slim hope
>that if you keep bugging Apple, they will eventually fix their
>broken emulator

[Thorsten Froehlich] Re: Povray crashes [7146 days 11 hours and 21 minutes ago]

Mon, 25 Sep 2006 22:19:36 GMT

David Healy wrote:
> anything new or further on this?

Apple sells some nice and reliable refurbished G5 Macs. If you need a Mac
system for daily work, I strongly recommend you look into getting one. The
x86 PCs sold by Apple, unfortunately, are everything but reliable mostly due
to the rushed and incomplete port of the Mac OS X. Alternatively, x86 PCs
sold by Apple run Windows rather well, and most certainly POV-Ray on Windows
runs fast on them. There even is software that makes on the fly switching
between Windows and Mac OS X really easy.

As previously stated, you should not expect an official version of POV-Ray
for Mac OS X natively running on x86 PCs sold by Apple before 2008. However,
there is of course some slim hope that if you keep bugging Apple, they will
eventually fix their broken emulator such that POV-Ray can run on all x86
PCs sold by Apple. Bugging the POV-Team will not help, as Apple software and
hardware problems are beyond our control.

	Thorsten, POV-Team

[Thorsten Froehlich] Re: Povray crashes [7146 days 11 hours and 32 minutes ago]

Mon, 25 Sep 2006 22:09:29 GMT

Allan wrote:
> Like I said in my previous post: if the POV-Ray team would like some help
> with porting POV-Ray to the Intel Mac then let me know.  Every app I've
> ever written for PPC Macs have ported easily over to Intel.

Porting is not the problem: A quick and dirty port of almost anything is
mostly trivial indeed, assuming it already works with a poor compiler like
gcc and its even worse C and C++ libraries in the first place. However, a
proper port for POV-Ray means adding back what currently makes it fast, like
the just-in-time compiler for functions. Neither is done "easily", and I
have to seriously doubt your experience if you claim about yourself "Every
app I've ever written for PPC Macs have ported easily over to Intel."
because every application I ever had to port anywhere did not work out of
the box for many, many, many different reasons. Of course, you are welcome
to show me wrong, the source code of the Mac version is, as you probably
know, available for download...

	Thorsten

[David Healy] Re: Povray crashes [7146 days 14 hours and 56 minutes ago]

Mon, 25 Sep 2006 18:45:00 GMT

Allan,

anything new or further on this?

DHealy
Las Vegas, Nv.

"Allan" <all### [at] WholeCheesecom> wrote:
> Thorsten,
>
> Thanks for the info but I hope you did not misunderstand my note:  I did not
> say it was POV-Ray's problem, I simply said it was not an Intel app.  I do
> realize that Rosetta is not a very robust environment and it is no wonder
> that it fails with POV-Ray.
>
> That said, the very fact that Rosetta is not acceptable is the very reason
> why POV-Ray needs to be ported to run as an Intel Mac app.  I think it is
> much more likely that POV-Ray can be ported than expecting Apple to fix
> Rosetta.  Rosetta, while it does work for most old applications, was never
> meant to be a long lived solution for old PPC software.
>
> Like I said in my previous post: if the POV-Ray team would like some help
> with porting POV-Ray to the Intel Mac then let me know.  Every app I've
> ever written for PPC Macs have ported easily over to Intel.
>
> -Allan
>
>
> Thorsten Froehlich <tho### [at] trfde> wrote:
> > Allan wrote:
> > > I just tried POV-Ray 3.6 on an Intel iMac and I get the same crash.  (It
> > > works great on the "old" G5.)  A look at the crash log shows that the crash
> > > happens in LaunchCFMApp.  It would appear that POV-Ray 3.6 is not yet ready
> > > for the Intel Macs?  It should run on the Intels under Rosetta but maybe
> > > the old Mac CFM (Code Fragment Manager, kind of like DLL's in Windows)
> > > doesn't work under Rosetta?
> > >
> > No, the problem are the countless bugs in Apple's software emulator. If the
> > PowerPC emulator is crashing, that is *Apple's* problem, not POV-Ray's.
> > Report problems with crashes to Apple. POV-Ray is a perfectly working and
> > cleanly written PowerPC application, and it does run on every real PowerPC
> > processor. On the other hand, the emulator Apple supplies is known to have
> > problems, and they won't get fixed unless Apple is told they exist.
> >
> > Report it to Apple, or nothing will change. Unlike with the much better
> > planned 68K to PowerPC transition, Apple has neglected to develop a working
> > debugger for the PowerPC emulation environment called "Rosetta" and instead
> > rushed out unstable systems to end users. Even today there is no reasonable
> > way to debug within Rosetta, except using a barely working hack documented
> > by Apple to use an unreliable low-level command-line-based debugger with
> > plenty of restrictions.
> >
> > BTW, effectively the poor development environments available, and the rushed
> > transition is also the reason why major software vendors (i.e. Adobe) have
> > been unable to deliver native software yet. There is just no way to properly
> > develop and test on the x86 PCs sold by Apple yet.
> >
> > As for POV-Ray, do not expect a native version earlier than 2008 or as part
> > of POV-Ray 4.0, whichever comes first. In the meantime, you can always
> > compile and run the Unix version natively on Mac OS X.
> >
> >  Thorsten, POV-Team