Hi Chris,
Thanks the links. I've tracked down the example you created and re-run it
on my system and on the scene graph creation of the second window/view I
get text without textures.
In summary:
>
>- Fabian has done something weird with either OSG or OpenMW that
>hasn't been specified
I have been testing with trunk and have only come across one problem so
far (this might not be a new issue).
I have a simple viewer set up with two nodes. The first is loaded from
an osgb. Internally it sets the glBlendFunci(0, GL_MAX) via
osg::BlendFunci.
The second node also sets
Hi Robert,
I'm reasonably sure that Fabian's crash isn't the same issue as that
example exposes.
>>- Fabian has done something weird with either OSG or OpenMW that
>>hasn't been specified yet.
>>
>> If the codebase is the same perhaps it comes down to a sensitivity to
> compiler
Hi Robert,
In relation to the DefaultFont crash issue, I noticed that my code would
occasionally crash on creation of osgText::Text.
Most of my osgText::Text is not created on the main thread.
In order to avoid the DefaultFont crash, I created a
osg::ref_ptr necessaryFont =
Hi all,
I have new information about what Fabian has done that's weird. When he's
been saying he's doing static linking, he's not doing what most people
would associate that phrase with (i.e. building OSG to a library file such
that all code is contained within and consuming that when linking
Hi Dan,
Thanks for all the details. Seeing a difference between the same scene
graph in our Qt based viewer vs OSG suggests that the Qt side is changing
OpenGL state, or setting up the graphics context+frame buffers in a
different way to the OSG does.
I don't have any Qt expertise so can't
Hi Fabian,
On Wednesday, 29 January 2020 00:24:35 UTC, Fabian Roth wrote:
>
> Hi Chris,
> I am using the latest openmw master with the compatibility patch from the
> pull request cherry picked, my build changes and minor other tweaks.
> I use the osg rc with a only a cmake version change.
> The
7 matches
Mail list logo