On Wednesday, January 29, 2020 at 11:02:48 AM UTC+1, Robert Osfield wrote:
>
> 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
Hi Robert,
That commit does indeed seem to have fixed my minimal reproducible example,
and, unlike with my other minimal reproducible examples, it's fixed the
issue with the OpenMW-CS, too. Thanks for getting that sorted.
Now I just have to remember what my favourite workaround for 3.4.1
Hi Robert,
Compiling and a few simple runs worked fine, using
windows 10 Enterprise 1909 18363,592
Visual Studio 15.9.19
CMake 3.15.5
Regards, Laurens.
On Thu, Jan 30, 2020 at 5:30 PM OpenSceneGraph Users <
osg-users@lists.openscenegraph.org> wrote:
> Hi Chris et. al,
>
> On Thursday, 30 January
Hi Chris et. al,
On Thursday, 30 January 2020 14:39:08 UTC, OpenSceneGraph Users wrote:
>
> I slowly closing in on the cause of the Font issue, currently it looks
> like the removeView() is behaving differently form the CompositeViewer
> destructor and not handling clean up of contexts
Hi Chris,
I slowly closing in on the cause of the Font issue, currently it looks like
the removeView() is behaving differently form the CompositeViewer
destructor and not handling clean up of contexts correctly. I need to
refactor how things are done internally, but expect to have a solution
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 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
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
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 branches are here:
https://github.com/Eli2/openmw/tree/eli2-openmw-static
Hi Fabian,
Link-time optimisation should be fine - we do it on release builds with no
problems. It's either something you've changed, or it's the static linking.
We still don't know exactly which version of OpenMW and OSG you've built,
though. It's pretty obviously not the RC this thread is
On Tuesday, January 28, 2020 at 10:11:49 AM UTC+1, OpenSceneGraph Users
wrote:
>
> Hi Fabian,
>
>
>> My build is using static osg, static osg-plugins and link time
>> optimization.
>> I created an address sanitizer enabled build.
>> It exhibits a heap-use-after-free.
>> I will try to further
Hello again.
The googlegroup has search options, here's what I get if I search for
> OpenMW. it comes up with several threads with you contributing:
>
> https://groups.google.com/forum/#!searchin/osg-users/OpenMW%7Csort:date
>
I can find chunks of the right thread (this is some:
Hi Fabian & Chris,
I was curious about the clean up of the global getGlobalReferencedMutex()
so I added some debug messages to OpenThreads and to relevant calls in the
OSG to track the creation and clean up of mutexes. I tried an alternative
means of static initialization of the static
Hi Fabian,
> My build is using static osg, static osg-plugins and link time
> optimization.
> I created an address sanitizer enabled build.
> It exhibits a heap-use-after-free.
> I will try to further investigate this week.
>
> =
>
Hi Chris,
On Mon, 27 Jan 2020 at 23:51, OpenSceneGraph Users <
osg-users@lists.openscenegraph.org> wrote:
> As I've mentioned in the past, I'm an OpenMW (note the single M)
> developer. It was actually me who reported the issues with the default
> font, and only a subset were resolved before you
Am Montag, 27. Januar 2020 10:57:23 UTC+1 schrieb Robert Osfield:
>
> Hi Fiabian,
>
> On Monday, 27 January 2020 09:41:43 UTC, Fabian Roth wrote:
>>
>> Hi,
>> I am currently testing this RC with openmw.
>> If i have the fps display or profiler open while exiting the application
>> i get a crash
Hi Robert,
As I've mentioned in the past, I'm an OpenMW (note the single M) developer.
It was actually me who reported the issues with the default font, and only
a subset were resolved before you went on hiatus. I've lost the thread
where we were discussing it as I'd bookmarked the forum
Hi Fiabian,
On Monday, 27 January 2020 09:41:43 UTC, Fabian Roth wrote:
>
> Hi,
> I am currently testing this RC with openmw.
> If i have the fps display or profiler open while exiting the application i
> get a crash on exit.
> I am not sure if this is due to a bug in my build, a bug in openmw
Hi,
I am currently testing this RC with openmw.
If i have the fps display or profiler open while exiting the application i
get a crash on exit.
I am not sure if this is due to a bug in my build, a bug in openmw or a
real issue with osg.
The issue seems to be related to the destruction of the
>
>
> It would be best to have 3.6.5 go out with support for recent VC and FBX
> versions so would appreciate if you could generate a PR for them. I can
> merge them and make 3.6.5-rc3
>
> Cheers,
> Robert
>
>
OK, done. https://github.com/openscenegraph/OpenSceneGraph/pull/907
These
Hi Stuart,
On Sun, 26 Jan 2020 at 13:46, Stuart Mentzer wrote:
> OSG 3.6.5-rc2 built fine on Windows with VC2019 (so VC2017 is probably OK)
> and appears to be running properly in our application. If there are more
> RCs I can try to test those and I should be able to get 3.6.5 binaries
>
Hi Robert,
OSG 3.6.5-rc2 built fine on Windows with VC2019 (so VC2017 is probably OK)
and appears to be running properly in our application. If there are more
RCs I can try to test those and I should be able to get 3.6.5 binaries
posted soon after it is released.
Other than the usual mods I
Hi,
Seems to work fine here!
Win10 Home
CMake 3.16.0-rc3
Visual Studio Express 2013
Regards,
Andreas
On 2020-01-24 20:26, Robert Osfield wrote:
HI All,
Still waiting on feedback on how well 3.6.5-rc2 is working OK. I'm
ready to tag 3.6.5 at my end as there are no Issue reported yet that
HI All,
Still waiting on feedback on how well 3.6.5-rc2 is working OK. I'm ready
to tag 3.6.5 at my end as there are no Issue reported yet that I can look
into resolving.
If there are no Issue's raised by Monday I'll go ahead and tag 3.6.5 stable
release.
Cheers,
Robert.
--
You received
24 matches
Mail list logo
