Thomas de Groot <tho### [at] degrootorg> wrote:
> On 20-3-2014 10:17, Mr wrote:
>
> > POV-Ray was the first ray tracer to render an image in orbit, rendered by Mark
> > Shuttleworth inside the International Space Station.
> >
>
> I think you need to add the names of the artists, and a link to the image.
>
> Thomas


It might read like an Oscar acceptance speech. :-)

Maybe a link to the HOF would be better?

Post a reply to this message

On 20-3-2014 13:54, Stephen wrote:
> Thomas de Groot <tho### [at] degrootorg> wrote:
>> On 20-3-2014 10:17, Mr wrote:
>>
>>> POV-Ray was the first ray tracer to render an image in orbit, rendered by Mark
>>> Shuttleworth inside the International Space Station.
>>>
>>
>> I think you need to add the names of the artists, and a link to the image.
>>
>> Thomas
>

> It might read like an Oscar acceptance speech. :-)
>
> Maybe a link to the HOF would be better?
>

My statement was muddy. The HOF was in fact the place I had in my mind.

Thomas

Post a reply to this message

"Stephen" <mcavoys_AT_aolDOT.com> wrote:
> Thomas de Groot <tho### [at] degrootorg> wrote:
> > On 20-3-2014 10:17, Mr wrote:
> >
> > > POV-Ray was the first ray tracer to render an image in orbit, rendered by Mark
> > > Shuttleworth inside the International Space Station.
> > >
> >
> > I think you need to add the names of the artists, and a link to the image.
> >
> > Thomas
>

> It might read like an Oscar acceptance speech. :-)
>
> Maybe a link to the HOF would be better?


I am sorry, I had to cut down a lot of the description for it to be suitable to
that webpage's format, besides it had to be done quickly as  it was done by Ton
Roosendaal himself. It's very kind of his as his time is so valuable and he has
much more important tasks than webmastering, but nobody else was available to do
it for several weeks.

Here is the updated page: http://www.blender.org/download/external-renderers/

Povers, be prepared to welcome a few more Blenderheads in the future :)
And thanks again for your guidance so far.

Post a reply to this message

On 20/03/2014 4:39 PM, Mr wrote:
> I am sorry, I had to cut down a lot of the description for it to be suitable to
> that webpage's format, besides it had to be done quickly

You did a good job.

> as  it was done by Ton
> Roosendaal himself. It's very kind of his as his time is so valuable and he has
> much more important tasks than webmastering, but nobody else was available to do
> it for several weeks.
>

That deserves an "Oo! and an Ah!" ;-)

> Here is the updated page:http://www.blender.org/download/external-renderers/
>
> Povers, be prepared to welcome a few more

> Blenderheads

Not a nice image, BTW. ;-)

> in the future:)

And very welcome, they will be. :-D

We have had a few new people recently (and a few old ones, too). It 
would be good to have a more active forum, as a side effect.


> And thanks again for your guidance so far.

And thanks for your enthusiasm.

-- 
Regards
     Stephen

I solemnly promise to kick the next angle, I see.

Post a reply to this message

I second that.

Thomas

Post a reply to this message

Mr! If you use my work, I ask to include my name in structure of developers.
I regret that I don't know English for full communication.
For me it is important that our community knew that I make the feasible
contribution to creation of the exporter.
It is very important to apply Boolean operations. I over it work.

Post a reply to this message

"LanuHum" <Lan### [at] yandexru> wrote:
> Mr! If you use my work, I ask to include my name in structure of developers.
> I regret that I don't know English for full communication.
> For me it is important that our community knew that I make the feasible
> contribution to creation of the exporter.
> It is very important to apply Boolean operations. I over it work.

I credited you in the release logs and such community discussions as are
happening here because I would like to encourage your efforts. I would like to
do it even more than I do now. But so far, that's the best I can do. As a
sidenote I do have to rewrite your code every time because you suppressed from
your version some existing features of the exporter (mostly Blender texture
channels support). It is not really your fault, it is rather because of POV-Ray
syntax not designed to suit that approach: I can agree that having to implement
some kinds of "finish map" hacks to emulate specular maps and the like makes the
script much less straightforward to write, grasp and maintain. As I already
explained to you, support of that basic native Blender workflow is the strategy
for the first development stage of the exporter. Additional interface to native
POV-Ray features is the next step and I am glad that you are already working on
it, but the end product should keep both capacities not cut out blender users
for POV only approach, because POV users already had software for that, like
Moray, Poseray and many others.

The day you decide to keep, port or rewrite these features into your code. I am
sure it will be easier to work on a common version. That is indeed something I
look forward to.

I take note of your attachment to POV-Ray booleans as a user and contributor and
thereby put it as a number one priority on new features request list.

Thanks for your enthusiasm. Please bear with me.

Post a reply to this message

First of all, I'm very happy with current Blender exporter. I use it very
extensively in paid work. I don't want it to be broken.

However, if someone would be kind enough to add Povray native functionality,
like Booleans, to it, I would be very happy. I currently use my own Python
generator scripts when I need native Povray functionality (i.e. Booleans). Btw,
the current Blender exporter supports adding "native" POV script too! :D

Anyway, we should always respect other developers and remember that co-operation
is very important. It is much better to have one exporter with trustworthy
functionality than two half baked ones. Unnecessary competition can cause
problems.

I strongly suggest that Blender official routes are used as much as possible,
then we can have continuity. In the long run, continuity means you have the
tools even if someone is not willing to develop any more.

Btw, I am really grateful of the things already achieved!

Post a reply to this message

"Mr" <nomail@nomail> wrote:
>
> I take note of your attachment to POV-Ray booleans as a user and contributor and
> thereby put it as a number one priority on new features request list.
>
> Thanks for your enthusiasm. Please bear with me.

It is difficult for me to understand your code, it is very confused.
Objects used in Boolean operations shouldn't be declared in a scene, but have to
be declared.
Here to you my help:
render.py line 2539

        for data_name, inst in data_ref.items():
            for ob_name, matrix_str in inst:
                use_in_boolean = 0
                for obj in bpy.data.objects:
                    obj_name = "OB" +
string_strip_hyphen(bpy.path.clean_name(obj.name))
                    if obj.type == 'MESH':
                        for mod in obj.modifiers:
                            numberModifiers = 0
                            if mod.type == 'BOOLEAN':
                                numberModifiers += 1
                                mod_obj_name = "OB" +
string_strip_hyphen(bpy.path.clean_name(mod.object.name))
                                if mod_obj_name == ob_name:
                                    use_in_boolean += 1
                            if numberModifiers > 0 and obj_name == ob_name:
                                use_in_boolean += 1
                if use_in_boolean == 0:
                    tabWrite("//----Blender Object Name:%s----\n" % ob_name)
                else:
                    tabWrite("//----Declare Blender Object Name:%s----\n" %
ob_name)
                    tabWrite("#declare %s =\n" % data_name)
                tabWrite("object { \n")
                tabWrite("%s\n" % data_name)
                tabWrite("%s\n" % matrix_str)
                tabWrite("}\n")

    def exportBooleanObjects():
        pass

Post a reply to this message

> First of all, I'm very happy with current Blender exporter. I use it very
> extensively in paid work. I don't want it to be broken.
>
> However, if someone would be kind enough to add Povray native functionality,
> like Booleans, to it, I would be very happy. I currently use my own Python
> generator scripts when I need native Povray functionality (i.e. Booleans). Btw,
> the current Blender exporter supports adding "native" POV script too! :D
>
> Anyway, we should always respect other developers and remember that co-operation
> is very important. It is much better to have one exporter with trustworthy
> functionality than two half baked ones. Unnecessary competition can cause
> problems.
>
> I strongly suggest that Blender official routes are used as much as possible,
> then we can have continuity. In the long run, continuity means you have the
> tools even if someone is not willing to develop any more.
>
> Btw, I am really grateful of the things already achieved!

If I use Povray for a render, it is more convenient to me to use own version of
the exporter
But, if my version takes place to be for me, I offer it to another.
If users begin to ask very difficult texture map, developers of the official
version should reconsider the position.

Post a reply to this message