On 2/10/19 8:08 AM, William F Pokorny wrote:
> On 2/10/19 5:20 AM, clipka wrote:
>> Am 09.02.2019 um 19:41 schrieb William F Pokorny:
>>
>>> I then tried the version where "Water" all in one text object. 
>>> Unfortunately this hangs immediately in a way which only the kill 
>>> command can stop.
>>
>> Is that with your own merged version only, or with the "pure" freetype 
>> branch as well?
> 
> Merged. Give me a little to get coffee, download the freetype branch 
> straight up, compile and run it.
> 
> Bill P.

Well... Sip or two of coffee and I think I probably originally missed 
the point of your question or reading it again.

The hang is happening only when I merge both the freetype branch AND my 
soft/hard object branch where there are two or more characters in the 
string used in the soft_object pattern -> function -> isosurface.

The soft_object.pov demo scene has both single text object of "Water" 
through the isosurface to the top and individual character text objects, 
through individual isosurfaces to the top given coded up as the former 
is so much faster. Something true even with my text branch performance 
improvements merge in too.

---
Anyway, I download the freetype branch directly off github (no github 
merge into master), compiled and ran it. The text_i.pov results with two 
or more characters are still scrambled (also very slow) compared to the 
current master (v38) branch on github. (master 5.27sec -> freetype 18.539)

Possible I guess I'm just not waiting long enough for the first 
non-black square to show, but doubt it. I've not done a debug compile 
and tried to attach gdb to the running process to verify I've "really" 
got a hang.

My thinking was given something is wrong in the freetype branch itself, 
as shown by text_i.pov with two or more characters, that should be fixed 
first. If lucky that fix fixes my "hang" issue too.

In short run text_i.pov with master and again with the freetype branch. 
Results should match and they don't when I run it.

Bill P.

Post a reply to this message