On 03/09/2014 20:34, Le_Forgeron wrote:
> On 03/09/2014 18:39, LanuHum wrote:
>> Le_Forgeron <jgr### [at] freefr> wrote:
>>
>>> Will have to get a set of freshly compiled binaries to go further, so do
>>> not hold your breath today.
>>
>> Great!
>> The mistake disappeared.
>> Thanks a lot!
>>
> I have not yet changed anything... so it's probably just luck and some
> non-initialised memory... or something else.
> 
> The bug-hunt is scheduled for this week-end.
> 
Ok, I found the source of the issue (propagation of NaN).

Now I wonder how to fix it.

Notice that your original spline, a cubic_spline, is repeating 3 times
the first point's coordinates: the first one is for the slope at start,
the second one is for the first actual point (start), but what is the
third one for ?

That's also happening at the end of your spline (last point is repeated
3 times).

So, a fast workaround would be to avoid triplicated extremities (and
probably duplicated intermediates), but that's

The NaN is created when two consecutive points (of the actual spline
segments) are strictly identical, so their difference is exactly a null
vector. (due to noise and numerical computation, it does not always
happens as easy as it seems). As that vector, once normalized is used as
part of the base with local U & V vector, having a degenerated 3D-base
is not a good thing to compute the new U & V vectors. Current code is
like Roman arithmetic: no expectation or notion of zero. Need some
Indian's innovation to fix it, sort of.


-- 
IQ of crossposters with FU: 100 / (number of groups)
IQ of crossposters without FU: 100 / (1 + number of groups)
IQ of multiposters: 100 / ( (number of groups) * (number of groups))

Post a reply to this message

On 03/09/2014 21:52, LanuHum wrote:
> Sorry.
> Old version configure with --disable-optimiz (standard (official) Mageia
> specfile)
> Today I edited the specfile and removed an option --disable-optimiz
> 
> %configure2_5x --with-x COMPILED_BY="LanuHum" LIBS="-lboost_system
> -lboost_thread -lboost_date_time"
> 
> 
> 
> 
Should be fixed now.

-- 
IQ of crossposters with FU: 100 / (number of groups)
IQ of crossposters without FU: 100 / (1 + number of groups)
IQ of multiposters: 100 / ( (number of groups) * (number of groups))

Post a reply to this message

Le_Forgeron <jgr### [at] freefr> wrote:
> On 03/09/2014 21:52, LanuHum wrote:
> > Sorry.
> > Old version configure with --disable-optimiz (standard (official) Mageia
> > specfile)
> > Today I edited the specfile and removed an option --disable-optimiz
> >
> > %configure2_5x --with-x COMPILED_BY="LanuHum" LIBS="-lboost_system
> > -lboost_thread -lboost_date_time"
> >
> >
> >
> >
> Should be fixed now.
>
> --
> IQ of crossposters with FU: 100 / (number of groups)
> IQ of crossposters without FU: 100 / (1 + number of groups)
> IQ of multiposters: 100 / ( (number of groups) * (number of groups))

Thanks! :)

Post a reply to this message

Mr Le_Forgeron,

I again made something so?
undeclared identifier proximity
undeclared identifier voronoi
undeclared identifier masonry
and so on

Post a reply to this message

On 10/09/2014 19:22, LanuHum wrote:
> Mr Le_Forgeron,
> 
> I again made something so?
> undeclared identifier proximity
> undeclared identifier voronoi
> undeclared identifier masonry
> and so on
> 
> 
> 
Did you build from Hgpovray branch ?
(the master branch does not have the proximity/... )


-- 
IQ of crossposters with FU: 100 / (number of groups)
IQ of crossposters without FU: 100 / (1 + number of groups)
IQ of multiposters: 100 / ( (number of groups) * (number of groups))

Post a reply to this message

Le 10/09/2014 19:34, Le_Forgeron a écrit :
> On 10/09/2014 19:22, LanuHum wrote:
>> Mr Le_Forgeron,
>>
>> I again made something so?
>> undeclared identifier proximity
>> undeclared identifier voronoi
>> undeclared identifier masonry
>> and so on
>>
>>
>>
> Did you build from Hgpovray branch ?
> (the master branch does not have the proximity/... )
> 
> 
My bad, I did not successfully pushed in github the Hgpovray branch
(bitbucket is ok, not yet github).

And it remind me that gts_save sucks so far with big mesh... must update
its code to fix it. (well, it's just so slow... too slow!)

-- 
Just because nobody complains does not mean all parachutes are perfect.

Post a reply to this message

On 11/09/2014 09:53, Le_Forgeron wrote:
> Le 10/09/2014 19:34, Le_Forgeron a écrit :
>> On 10/09/2014 19:22, LanuHum wrote:
>>> Mr Le_Forgeron,
>>>
>>> I again made something so?
>>> undeclared identifier proximity
>>> undeclared identifier voronoi
>>> undeclared identifier masonry
>>> and so on
>>>
>>>
>>>
>> Did you build from Hgpovray branch ?
>> (the master branch does not have the proximity/... )
>>
>>
> My bad, I did not successfully pushed in github the Hgpovray branch
> (bitbucket is ok, not yet github).
> 
> And it remind me that gts_save sucks so far with big mesh... must update
> its code to fix it. (well, it's just so slow... too slow!)
> 
Github now display the patch in both branches, so hopefully it should be ok.

One day, I might understand how to work cleanly with github and hg/git.
So far, tag/branch/bookmarks are just escaping me...

-- 
IQ of crossposters with FU: 100 / (number of groups)
IQ of crossposters without FU: 100 / (1 + number of groups)
IQ of multiposters: 100 / ( (number of groups) * (number of groups))

Post a reply to this message

Le_Forgeron <jgr### [at] freefr> wrote:
> On 11/09/2014 09:53, Le_Forgeron wrote:
> > Le 10/09/2014 19:34, Le_Forgeron a écrit :
> >> On 10/09/2014 19:22, LanuHum wrote:
> >>> Mr Le_Forgeron,
> >>>
> >>> I again made something so?
> >>> undeclared identifier proximity
> >>> undeclared identifier voronoi
> >>> undeclared identifier masonry
> >>> and so on
> >>>
> >>>
> >>>
> >> Did you build from Hgpovray branch ?
> >> (the master branch does not have the proximity/... )
> >>
> >>
> > My bad, I did not successfully pushed in github the Hgpovray branch
> > (bitbucket is ok, not yet github).
> >
> > And it remind me that gts_save sucks so far with big mesh... must update
> > its code to fix it. (well, it's just so slow... too slow!)
> >
> Github now display the patch in both branches, so hopefully it should be ok.
>
> One day, I might understand how to work cleanly with github and hg/git.
> So far, tag/branch/bookmarks are just escaping me...
>
> --
> IQ of crossposters with FU: 100 / (number of groups)
> IQ of crossposters without FU: 100 / (1 + number of groups)
> IQ of multiposters: 100 / ( (number of groups) * (number of groups))

I understood nothing. What is bitbucket is ok?
I began this subject being guided by this address
http://wiki.povray.org/content/User:Le_Forgeron

Additional cameras, pigments and so on are interesting to me.
But, I was fond of copying of the exporter to use nodes. It took away from me
time to study your work very in detail.
When work on the exporter ends, I will try to finish animation which we did, but
didn't order:
http://www.youtube.com/watch?v=07E2eejYjRM&feature=youtu.be
For a render Blender Internal Render was used.
Now I want to use Povray, and to show its advantages in creation of animation in
comparison with Blender Internal and Cycles
Your brick (masonry) would be necessary for me for walls,
proximity pattern can also be applied. :)

Post a reply to this message

Interestingly.
Why this operation wasn't included into the official version?
The person worked in vain (in vain)?
These are very good tools. I saved the source code for a patch. I can use it,
but other users can't use it.
You say that you have no time, but you use time and you throw out a code in a
dustbin.
In what problem? There are more than 20 cameras which the user doesn't know.
Where proximity pattern? Where tessel, tesselate, bend, voronoi, masonry???
Now include it in the official version!!! There are no problems for this
purpose!
:) :) :)

Post a reply to this message

The hgpovray connection with the Blender continues.

There is an error: camera type "platecarree"
https://bitbucket.org/LeForgeron/povray/wiki/Camera

Here it is written correctly: camera type "plate_carree"
http://wiki.povray.org/content/User:Le_Forgeron#plate_carree

camera {
    plate_carree  // NOT platecarree
}

Post a reply to this message