I'm frustrated.  All I want is for Moray 3.5 to output code that'll operate
within spec for Povray 3.7.  I simply can't get enough of Moray, and to
actually see the speed differences between Povray3.5 and the
multi-processor/core aware Povray3.7 is like touching a god's soul.  ...
Okay, imagery aside, I'm just so pissed from trying to get Moray3.5 to
output code without the silly parse errors springing up like crickets in
the night.  *sigh*

That's all I have to say.  Better output to Povray.  Obvious, but I wanted
to say it.

Post a reply to this message

Just out of curiosity, what is exactly the problem? If you try to render 
directly from Moray to pov 3.7, yes, you are in deep trouble. On the other 
hand, if you only export your Moray scene to Pov, then open pov 3.7 and 
render the exported scene, you shouldn't have that many problems, imho. 
Could you give us an example scene file to understand better?

Thomas

Post a reply to this message

Thomas de Groot <t.d### [at] internldotnet> wrote:
> If you try to render 
> directly from Moray to pov 3.7, yes, you are in deep trouble.

  Is this a problem with povray or with moray (do I remember correctly
that moray cannot properly call povray 3.6 either?).

  If it's the latter, why isn't moray updated to work with all povray
versions between 3.5 and 3.7?

-- 
                                                          - Warp

Post a reply to this message

"Warp" <war### [at] tagpovrayorg> schreef in bericht 
news:45a8b6de@news.povray.org...
> Thomas de Groot <t.d### [at] internldotnet> wrote:
>> If you try to render
>> directly from Moray to pov 3.7, yes, you are in deep trouble.
>
>  Is this a problem with povray or with moray (do I remember correctly
> that moray cannot properly call povray 3.6 either?).
>
>  If it's the latter, why isn't moray updated to work with all povray
> versions between 3.5 and 3.7?
>

The problem has indeed started with the release of  POV-Ray version 3.6.
Unfortunately, Lutz has never updated Moray to work properly with POV-Ray 
versions higher than 3.5. Real Life you know, as fas as I understand..... 
:-(

Thomas

Post a reply to this message

"Thomas de Groot" <t.d### [at] internlDOTnet> wrote:
> "Warp" <war### [at] tagpovrayorg> schreef in bericht
> news:45a8b6de@news.povray.org...
> > Thomas de Groot <t.d### [at] internldotnet> wrote:
> >> If you try to render
> >> directly from Moray to pov 3.7, yes, you are in deep trouble.
> >
> >  Is this a problem with povray or with moray (do I remember correctly
> > that moray cannot properly call povray 3.6 either?).
> >
> >  If it's the latter, why isn't moray updated to work with all povray
> > versions between 3.5 and 3.7?
> >
>
> The problem has indeed started with the release of  POV-Ray version 3.6.
> Unfortunately, Lutz has never updated Moray to work properly with POV-Ray
> versions higher than 3.5. Real Life you know, as fas as I understand.....
> :-(
>
> Thomas


Yes, that's what they say ("they" being the higher lifeforms who are in
charge of watching the life-living habits of people everywhere).  This is a
perfect example of making Moray OSS.  Something Lutz wants to hear?  Of
course not, but if no development work is being done on Moray, and hasn't
been done for years, it just amounts to a dead project.  Money can't be a
concern, considering it's shareware, so if real life is seriously that much
in the way, why not simply become principle developer and let everyone else
do the grunt work?  I mean, its not like there wouldn't be anyone willing
to pick it up...

Nonetheless, Lutz rules, but its becoming a token praise.

Post a reply to this message

"Lawrence W" <lwi### [at] daktelcom> schreef in bericht 
news:web.45ac669827a5e58463b265170@news.povray.org...
>
> Yes, that's what they say ("they" being the higher lifeforms who are in
> charge of watching the life-living habits of people everywhere).  This is 
> a
> perfect example of making Moray OSS.  Something Lutz wants to hear?  Of
> course not, but if no development work is being done on Moray, and hasn't
> been done for years, it just amounts to a dead project.  Money can't be a
> concern, considering it's shareware, so if real life is seriously that 
> much
> in the way, why not simply become principle developer and let everyone 
> else
> do the grunt work?  I mean, its not like there wouldn't be anyone willing
> to pick it up...
>
> Nonetheless, Lutz rules, but its becoming a token praise.
>
>

<sigh>
Yes, I agree...
I would have prefered a working update with pov version 3.6 (and 3.7) 
instead of all the beta work around a better mesh modeller inside Moray (or 
so I have understood the development). There are (and were) excellent mesh 
modellers available, so, imo, Moray does not need really it. It is far more 
powerful in other domains, not in the least in the plugin interface, that I 
would like to see developed in the same manner/philosophy as Leveller.
<sigh again>

Thomas

Post a reply to this message

"Thomas de Groot" <t.d### [at] internlDOTnet> wrote:

>
> <sigh>
> Yes, I agree...
> I would have prefered a working update with pov version 3.6 (and 3.7)
> instead of all the beta work around a better mesh modeller inside Moray (or
> so I have understood the development). There are (and were) excellent mesh
> modellers available, so, imo, Moray does not need really it. It is far more
> powerful in other domains, not in the least in the plugin interface, that I
> would like to see developed in the same manner/philosophy as Leveller.
> <sigh again>
>
> Thomas

I agree too. Creating meshes from a csg then being able to subdivide it is a
nice feature but working with a version of Pov from 2004 is a pain. Even
making the Moray 3.5 features work with Pov 3.6 would be more useful than
mesh editing.

to import Pov SDL. It has limitations but it is developing well.


Stephen

Post a reply to this message

"Stephen" <mcavoys_AT_aolDOT.com> schreef in bericht 
news:web.45ac9b7a27a5e584f1cb1e660@news.povray.org...
>
> I agree too. Creating meshes from a csg then being able to subdivide it is 
> a
> nice feature but working with a version of Pov from 2004 is a pain. Even
> making the Moray 3.5 features work with Pov 3.6 would be more useful than
> mesh editing.
> One feature from Hugo Arnaut's Bishop3D that is really good is the ability
> to import Pov SDL. It has limitations but it is developing well.
>
>

Now that you mention it, I believe that the conversion from CSG to mesh is a 
useful item in itself, but then I prefer to export the result and work 
further in Silo with that. It works not so well with Wings however, because 
the conversion is not that perfect and a lot of transparant faces are 
created, but Silo manages quite well.
Bisho3D looks interesting. I have not experimented with it, though.

Thomas

Post a reply to this message

On Tue, 16 Jan 2007 16:40:27 +0100, "Thomas de Groot" <t.d### [at] internlDOTnet>
wrote:

>
>Now that you mention it, I believe that the conversion from CSG to mesh is a 
>useful item in itself, but then I prefer to export the result and work 
>further in Silo with that. It works not so well with Wings however, because 
>the conversion is not that perfect and a lot of transparant faces are 
>created, but Silo manages quite well.

I've not used a mesh modeller for ages, relying on csg mostly. Although I do
have a need for one to modify some Poser clothes.

>Bisho3D looks interesting. I have not experimented with it, though.

It is interesting and I think that it will be quite useful when it's finished.
I've lost my muse so I've got time to test, it not needing to worry about having
a project to complete. I've nearly finished a model (a prop) of the London Eye.
It has a different feel to Moray even though the layout looks similar. Besides
being able to import a lot of SDL and allowing you to write SDL to be merged
with the scene as objects or textures. I like the animation feature where I
could not get to grips with Moray's.

Regards
	Stephen

Post a reply to this message

Hi Lawrence W, you recently wrote in moray.win:

> I'm frustrated.  All I want is for Moray 3.5 to output code that'll operate
> within spec for Povray 3.7.  I simply can't get enough of Moray, and to
> actually see the speed differences between Povray3.5 and the
> multi-processor/core aware Povray3.7 is like touching a god's soul.  ...
> Okay, imagery aside, I'm just so pissed from trying to get Moray3.5 to
> output code without the silly parse errors springing up like crickets in
> the night.  *sigh*
> 
> That's all I have to say.  Better output to Povray.  Obvious, but I wanted
> to say it.

I understand the frustrations expressed by the posters in this thread,
I am not oblivious to them. And it pains me to have had Moray come to
a standstill too....

I still did not see any specific problems listed that POV-Ray 3.7 has
with the output from Moray V3.5. Unfortunately, I haven't kept up with
POV-Ray development, but are POV-Ray V3.7 scene files not compatible
with POV-Ray V3.5 scene files?

- Lutz
- Lutz
  email : lut### [at] stmuccom
  Web   : http://www.stmuc.com/moray

Post a reply to this message