Hi,

I always dreamed of a multi threaded Povray and I see that is now available.

After many years I have come back to Povray and some of my old projects.

What I would like to be able to do is run some of my old animations from Moray
into Povray, now that there is so much more power available.

Unfortunately Moray puts some stuff in the .ini files that causes Povray 3.7 to
stop.    I think the same is true for Povray 3.5.

I can edit the .ini and fix it but for an animation that is not practical.

Can I somehow tell Povray to ignore errors in the ini files ?

Thx.

Post a reply to this message

On 30/09/2018 16:50, yagi wrote:
> Unfortunately Moray puts some stuff in the .ini files that causes Povray 3.7 to
> stop.    I think the same is true for Povray 3.5.


What stuff does Moray put in the .ini files? Could you post a copy?


-- 

Regards
     Stephen

Post a reply to this message

Stephen <mca### [at] aolcom> wrote:
> On 30/09/2018 16:50, yagi wrote:
> > Unfortunately Moray puts some stuff in the .ini files that causes Povray 3.7 to
> > stop.    I think the same is true for Povray 3.5.
>
>
> What stuff does Moray put in the .ini files? Could you post a copy?
>
>
> --
>
> Regards
>      Stephen

Thanks for your reply.

These are the variables that Povray dosn't like,

-

'Buffer_Output' is no longer
used and will result in an error in future versions of POV-Ray.

'Buffer_Size' is no longer
used and will result in an error in future versions of POV-Ray.
-

'Histogram_Name' is no longer
used and will result in an error in future versions of POV-Ray.
-

'Histogram_Grid_Size' is no
longer used and will result in an error in future versions of POV-Ray.
-

'Histogram_Type' is no longer
used and will result in an error in future versions of POV-Ray.
-
Unknown key 'Radiosity' in INI file.
-

Post a reply to this message

Am 01.10.2018 um 14:46 schrieb yagi:

> Unknown key 'Radiosity' in INI file.

Is this the only option that gives an outright error? I.e., does POV-Ray
render the scene when you remove it?

Post a reply to this message

> > Unknown key 'Radiosity' in INI file.
>
> Is this the only option that gives an outright error? I.e., does POV-Ray
> render the scene when you remove it?


Actually yes that's the only option that stops it.   Anyway to remove just that
?

thx
Steve

Post a reply to this message

Am 01.10.2018 um 16:16 schrieb yagi:
> 
>>> Unknown key 'Radiosity' in INI file.
>>
>> Is this the only option that gives an outright error? I.e., does POV-Ray
>> render the scene when you remove it?
> 
> 
> Actually yes that's the only option that stops it.   Anyway to remove just that
> ?

You can safely remove it, but there's no way to let POV-Ray
automatically ignore it.

The INI file option was removed entirely in POV-Ray v3.7 when it should
have been just marked as obsoleve. I'm working on a fix.

I'm not sure if we'll release a fixed v3.7 though, so maybe I'll have to
refer you to the next v3.8.0-alpha version.

Are you running Windows or Unix?

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:

>
> You can safely remove it, but there's no way to let POV-Ray
> automatically ignore it.

>
> Are you running Windows or Unix?

Windows 7 64bit.

I can remove it from the .ini in Povray, however that won't help with animation
generated in Moray as I can't edit the .ini for each frame.   Infact Povray just
locks if I use the Raytrace option in Moray.  I need to Export from Moray, edit
the .ini in Povray and then I can run the render from Povray.

I have been trying to run renders using Povray 3.5 but it just locks up when I
try to render a scene generated in Moray (either from Povray or from Moray).

Anyway I shall keep an eye out for the next alpha.    In the meantime I will
enjoy rendering some old scenes in "4K" with silly anti aliasing using 3.7...
its still cold here at this time of the year and that keeps the room warm !

Cheers
Steve

Post a reply to this message

Actually I have just realised (remembered) that Moray runs its own animation
renders and dosn't use Povray.   And its single threaded .. bummer .. that won't
keep the room warm !

Anyway thanks for the response.  Glad to see this community still healthy.

Steve

Post a reply to this message

Am 01.10.2018 um 17:10 schrieb yagi:

> Anyway I shall keep an eye out for the next alpha.    In the meantime I will
> enjoy rendering some old scenes in "4K" with silly anti aliasing using 3.7...
> its still cold here at this time of the year and that keeps the room warm !

I'm a bit disappointed by POV-Ray as a heater; CPUs have become far too
efficient these days.

We really need GPU assisted rendering.

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:
> Am 01.10.2018 um 16:16 schrieb yagi:
> >
> >>> Unknown key 'Radiosity' in INI file.
> >>
> >> Is this the only option that gives an outright error? I.e., does POV-Ray
> >> render the scene when you remove it?
> >
> >
> > Actually yes that's the only option that stops it.   Anyway to remove just that
> > ?
>
> You can safely remove it, but there's no way to let POV-Ray
> automatically ignore it.
>
> The INI file option was removed entirely in POV-Ray v3.7 when it should
> have been just marked as obsoleve. I'm working on a fix.

It was made obsolete in 3.6 (or maybe even 3.5) and removed in 3.7. Moray won't
work with 3.7 anyway. It is not a bug, but intentional design that hasn't
bothered anybody in a wopping 14 years...

Post a reply to this message

>>that Moray runs its own animation renders and dosn't use Povray.

Now I see the option for Moray to use Povray for animation rendering.   It's all
coming back, its been a long time.    I do like Moray and Povray, shame Moray is
no longer developed.

My overclocked 3770K still blows a bit of heat ... enough soak to actually make
the fans in my Titan X rev up !

Post a reply to this message

Am 01.10.2018 um 18:58 schrieb yagi:

> shame Moray is no longer developed.

Actually, it is. There's just not much talk about it at the moment.

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:

> Actually, it is. There's just not much talk about it at the moment.

Cool, I'll keep an eye on the news group !

Post a reply to this message

On 01/10/2018 18:23, clipka wrote:
> Am 01.10.2018 um 18:58 schrieb yagi:
> 
>> shame Moray is no longer developed.
> 
> Actually, it is. There's just not much talk about it at the moment.
> 

Chris Carson mentioned that there would be some news about it before the 
end of the year.

-- 

Regards
     Stephen

Post a reply to this message

Am 01.10.2018 um 18:01 schrieb Thorsten Froehlich:

>> The INI file option was removed entirely in POV-Ray v3.7 when it should
>> have been just marked as obsoleve. I'm working on a fix.
> 
> It was made obsolete in 3.6 (or maybe even 3.5) and removed in 3.7. [...]
> It is not a bug, but intentional design that hasn't
> bothered anybody in a wopping 14 years...

Probably as intentional a design decision as removing `Buffer_Output`
and `Buffer_Size` - a change that was revised by Chris just 10 days
later, presumably because people did complain.

People complaining is a good reason to review design decisions, but my
hunch is that what happened back then was just patching things that
people were complaining about, rather than coming up with a consistent
policy (or realizing that an existing policy had been violated) and
going with it all the way.


POV-Ray has a long-standing policy of trying to maintain backward
compatibility with legacy scene files (or files generated by legacy
tools). That policy is watered down if POV-Ray can't also read the
corresponding legacy INI file. Re-instating `Buffer_Output` and
`Buffer_Size` as "zombie" settings was a logical consequence of that
policy, but it only went half the way.

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:
> Am 01.10.2018 um 18:01 schrieb Thorsten Froehlich:
>
> >> The INI file option was removed entirely in POV-Ray v3.7 when it should
> >> have been just marked as obsoleve. I'm working on a fix.
> >
> > It was made obsolete in 3.6 (or maybe even 3.5) and removed in 3.7. [...]
> > It is not a bug, but intentional design that hasn't
> > bothered anybody in a wopping 14 years...
>
> Probably as intentional a design decision as removing `Buffer_Output`
> and `Buffer_Size` - a change that was revised by Chris just 10 days
> later, presumably because people did complain.

No, because those two were still in the 3.6 documentation. Radiosity was
obsolete in 3.5 already. And the removal is not all that unusual. Halo was
removed as a scene language feature in 3.1 without backward compatibility, btw.

Radiosity was moved to SDL control in 3.5 together with photons, making both
consistent. And to judge that it was unintentional or a problem to remove in 3.7
by a single report in 14 years is more than odd...

Thorsten

Post a reply to this message

Stephen <mca### [at] aolcom> wrote:
> On 01/10/2018 18:23, clipka wrote:
> > Am 01.10.2018 um 18:58 schrieb yagi:
> >
> >> shame Moray is no longer developed.
> >
> > Actually, it is. There's just not much talk about it at the moment.
> >
>
> Chris Carson mentioned that there would be some news about it before the
> end of the year.

Hooray! That's the most uplifting news I've heard all week. (There hasn't been
much uplifting news in the U.S. lately... :-P

Post a reply to this message

On 02/10/2018 00:30, Kenneth wrote:
> Stephen <mca### [at] aolcom> wrote:
>> On 01/10/2018 18:23, clipka wrote:
>>> Am 01.10.2018 um 18:58 schrieb yagi:
>>>
>>>> shame Moray is no longer developed.
>>>
>>> Actually, it is. There's just not much talk about it at the moment.
>>>
>>
>> Chris Carson mentioned that there would be some news about it before the
>> end of the year.
> 
> Hooray! That's the most uplifting news I've heard all week. (There hasn't been
> much uplifting news in the U.S. lately... :-P
> 
> 
> 
The news in the UK is not very uplifting either. :-(
The post was in OT and has expired, unfortunately.


-- 

Regards
     Stephen

Post a reply to this message