[osg-users] Please test OpenSceneGraph-3.6 branch in prep for 3.6.1

[Terry Welsh]

Looks like I had a graphics driver problem. Originally, I didn't think
that was the problem because the computer I'm working on has dual
graphics and it was crashing in Intel graphics mode and AMD graphics
mode. As it turns out, my dual graphics was broken and running Intel
graphics the whole time.

Now that's fixed and both drivers are broken, but at least they're
broken in different ways :P Sorry for the false alarm.
- Terry

P.S. Buy NVidia graphics.

>
> Hi Terry,
>
> On 23 April 2018 at 16:12, Terry Welsh <mogumbo at gmail.com> wrote:
>> Using the 3.6.0 tag I have crashes whenever an osgText::Text appears
>> on screen in my application. The osgtext example just doesn't show
>> anything at all and crashes when I press Esc. No problems with
>> osgText::Text3D or anything else so far. These problems occur when
>> compiling with Visual Studio Community 2017 on Win7. I have not had
>> any problems compiling with MS Build Tools on Win10 or any problems on
>> Fedora or Ubuntu. Last night while I was sleeping I compiled a debug
>> build of 3.6.0, and I'll try to look at it tonight. Do you think any
>> of the bug fixes you already made would affect this?
>
> You are the first to report a crash with osgText, so what you find
> with your debug version of the OSG will be invaluable.
>
> What graphics hardware are you working with?
>
> I don't think the fixes I made to the OpenSceneGraph branch will fix
> anything related to your crash, but you never know we might get lucky
> :-)
>
> FYI. the new osgText::Text implementation uses shaders to it's work,
> in theory it shouldn't do anything radical without checking the
> available functionality, but perhaps your driver/hardware aren't
> handled well.
>
>> By the way, the new shaderized Text outlines are very pretty.
>
> That was key deliverable for this work so it's good to hear that you
> are seeing an improvement.
>
> Robert.