On Wed, Jun 20, 2018 at 8:14 AM, Robert Osfield
wrote:
> Hi Scott,
>
> On Wed, 20 Jun 2018 at 08:09, Scott Bailey
> wrote:
> > Wow is this ever good news! I'm glad to see OSG will move into the
> future, albeit as VSG. I'm especially excited to see modern c++ targeted.
> Personally, my
Hi Robert,
thanks for your quick response.
so here's what I'm doing:
Code:
if (viewer)
{
returnValue =
ReactOnLCSPointClick(
*viewer, i_eventAdapter.getX(), i_eventAdapter.getY());
}
I tried as well with
Hi Jochen,
There is too many unknowns about what you are doing for us to be provide
any specific advice as to what is going wrong.
It could be that your are passing in the mouse coords incorrectly. It
could be that you are interpreting the intersections coordinates
incorrectly. It could be
Hi Laurens, thanks for answering so quickly.
I'll try your suggestion when I get home.
L. Voerman wrote:
> This looks like a driver bug, an reminds me of a problem in the nvidia driver
> having problems with display lists combined with depth_clamp.
> the osgviewer doesn't do the depthclamp,
Hi,
fixed the issue. I was using a defect Drawer. Thanks anyway
Thank you!
Cheers,
Jochen
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=74103#74103
___
osg-users mailing list
Hi Robert,
On Thu, Jun 21, 2018 at 9:35 AM, Robert Osfield
wrote:
> Hi Tim,
>
> On Thu, 21 Jun 2018 at 08:25, Tim Moore wrote:
>
>> Before you move on, the big advantage of std::shared_ptr over intrusive
>> reference counting is that support for weak pointers is rock solid. In the
>> intrusive
That does indeed fix the flickering.
My driver is Intel(R) HD Graphic 4000 ver 10.18.10.4885.
ceranco wrote:
> Hi Laurens, thanks for answering so quickly.
> I'll try your suggestion when I get home.
>
>
>
> L. Voerman wrote:
> > This looks like a driver bug, an reminds me of a problem in
Hi Tim,
On Thu, 21 Jun 2018 at 08:25, Tim Moore wrote:
> Before you move on, the big advantage of std::shared_ptr over intrusive
> reference counting is that support for weak pointers is rock solid. In the
> intrusive model, you can't implement thread-safe weak pointers without an
> auxiliary
On Thu, 21 Jun 2018 at 12:11, Tim Moore wrote:
> This is not the way shared_ptr is implemented, at least in gcc. The shared
> pointer contains a pointer to the object as well as to the control block.
> You could argue that this makes a shared_ptr twice the size of an
> osg::ref_ptr, but I really
Hi,
I compiled OpenSceneGraph 3.6.1 on a recently formatted Windows 10 laptop with
up-to-date drivers.
When I tried to run osgViewer with cow.osg, the model and screen started to
'flicker':
[Image: https://preview.ibb.co/dbVWFT/photo.jpg ] (https://ibb.co/jeAnpo)
but interestingly, when I
This looks like a driver bug, an reminds me of a problem in the nvidia
driver having problems
with display lists combined with depth_clamp.
the osgviewer doesn't do the depthclamp, but the display lists might be a
problem here.
can you try:
set OSG_OPTIMIZER=INDEX_MESH
osgviewer cow.osg
Laurens.
Something came up in a conversation earlier this week that I thought I
would point out.
Is VulkanSceneGraph potentially opening itself to
trademark-related hassle by incorporating the trademark "Vulkan" name into
its own name?
The Khronos trademark guidelines are here:
On Thu, 21 Jun 2018 at 17:25, Scott Bailey wrote:
> Regarding smart pointers, Boost Libs has a mature implementation that
> includes intrusive_ptr<>. Adding another dependency is, of course, a mixed
> bag; however, if you go header only with boost libs it's reasonable.
>
> For my projects, I
Hi Chris,
I am not a lawyer, but I think this is in a muddy area and it concerns
> me. I don't think anyone here can answer this, probably the only way to
> know is to ask Khronos directly for their interpretation in writing. But I
> suspect the answer will be "find a different name that
Regarding smart pointers, Boost Libs has a mature implementation that includes
intrusive_ptr<>. Adding another dependency is, of course, a mixed bag;
however, if you go header only with boost libs it's reasonable.
For my projects, I have found one advantage of Boost is how often it's
A short note on "The importance of working in a isolation."
This thread has been ended straying away from what I intended. It was
announcement, and never intended to a discussion or technical issues
or wish-lists, personal preferences, from the community. It's
devolved a bit into this as I
>
> If the branding is very distinct, and the word itself isn't something that
> can be owned as there is lots of prior art in active use
>
well the case of Apple (computer) vs Apple (the music company) was very
similar: a common word and very different industries (at the time Apple was
not in
On Fri, 22 Jun 2018 at 00:55, Maurizio Vitale wrote:
> well the case of Apple (computer) vs Apple (the music company) was very
> similar: a common word and very different industries (at the time Apple was
> not in the music/multimedia industry).
Khronos, a standards body, and an open source
18 matches
Mail list logo
