"LanuHum" <Lan### [at] yandexru> wrote:
> Thomas de Groot <tho### [at] degrootorg> wrote:
> > On 18-6-2015 11:50, Mr wrote:
> > >
> > > Another thing I do when I'm sick of no-one understanding the great potential of
> > > a Blender/POV synergy: rather than totally give up, let's pause development and
> > > make sample materials or pictures! That's what people need to see to realise
> > > what our exporters can do!
> > >
> > >
> >
> > Exactly so! I fully support this suggestion.
> >
> > To Lanuhum: Don't let silence discourage you. I think more people than
> > you think are interested, only most stay in stealth mode waiting for
> > further developments.
> >
> > --
> > Thomas
>
> Thomas, Mr, thanks!
> Not only silence discourage to me.
> The community Blender is very strongly attached to the renderer of Cycles.
> The Blender developers constantly create obstacles for those who wants to use
> other renderers.
> They constantly break Python API.
> Now my exporter doesn't work with Blender-2.74.5.
> Instead of development of the exporter I looked for the reasons which don't give
> to the program to work.
> I corrected, but lost nerves and time.
>
> Users of Povray can help if provide source of a full Povray-scene which Cycles
> won't be able to create. ( Either it is heavy, or it is difficult)
> Well for a scene:
> 1. Peeling paint isosurface.
> 2. Colored glass with refraction caustics
> 3. Reflecting surfaces with reflection caustics.
> 4. Both: 2 and 3
> 5. Polygon to circle loft.
> 6. Boolean with spline-based objects.
> 7. difference{
> sphere{} // or cylinder{}
> cone{}
> }
> and so on...
>
> If I have some samples of scenes, I will be able to adjust the exporter to
> repeat it using Blender.
> Independently I will long go.
> But I go!  :)


Although I know why you say that, I can't let you say it. Because I did receive
a lot of help from Ideasman 42,  and mont29 (I don't know if they whish to see
their real names written or prefer the nicks) both are two of the main Blender
developers (under paid contracts for the Blender Foundation). Here is how the
help was provided: Every time the api Broke, Ideasman changed the script
himself, to adapt to the change. the POV-Ray exporter served as a testbead for
it so it's been updated up to now, and I had to change almost nothing myself for
the api changes! This is why it is vital for you to try and get your branche
able to merge back with the trunk, this way you can get pauses without seeing
your code is broken when you get back to work. it's collectively maintained.
Mont 29 speaks french and is the developer of the FBX exporter so he knows well
the connected fields of Blender data structure, file formats, geometry, export
process... For all these reasons and also because he's like the second circle of
coders while ideasman (generalist) and brecht(cycles developer) are the first
circle, I tend to go to him first when I'm stuck (even though he does have a lot
of work too, the first circle are kind of always on fire, (look at
#blender-coders IRC channels and you'll see what I mean) so you need to be extra
careful with what time you steal from them, especially because all of these guys
are very generous and responsive (mont29 included). but they do need to sleep.
The last to date example of mont29 contribution is with export of smoke
simulation: I had managed to export the smoke cloud but it appeared with some
transformations, he helped me settle this, previously he also helped to do the
instancing system, and so many other improvements.

However, to be fair, I should add that the project is one among many for them,
so we can only hope for so much from them, they are already providing their
maximum assistance.

Post a reply to this message