Hi,
Recently, I found a display problem with using remote desktop connection.
If I used RDC connected to remote machine and then start the an application
with embed osg viewer, the viewer cannot display volume image probably (empty
image). If the application is already started at remote ma
HI Sebastian,
On 3 March 2015 at 17:09, Sebastian Messerschmidt <
sebastian.messerschm...@gmx.de> wrote:
> Hi Robert,
>
> Hi Stephan,
>
> You don't seem to like my name ;-)
>
Sorry about that, too many hours coding of late.
> The fix works great! All older VPB-databases are running smoothly a
I'm using a CompositeViewer ("viewer") to have multiple cameras with their own
graphics contexts imaging a single scene. I've wrapped all this up in function
calls that I expose to a separate UI, and so far I have the capability to
change scene configuration on the fly and take simultaneous snap
Hi Robert,
Hi Stephan,
You don't seem to like my name ;-)
I have return to the issue of the visualization problems with the
database you provided. Eventually was able to isolate the problem to
the binary parsing of the ClusterCullingCallback which in the end was
fixable by just adding a osg
Hi,
...
I just buy some fbx 3D model with some animation,each 3D model have one main
part .fbx file and some separate animation .fbx file.
main part .fbx dose not has animation effect if not loading other animation
.fbx file .
The problem is,when loaded a main part .fbx with osgviewer ,I
Hi All,
>From the
http://www.openscenegraph.org/index.php/download-section/developer-releases
page:
*O**pen**SceneGraph-3.3.5, **released on 3rd March **2015*, key
deliverables in this dev release are:
- No new features this dev release as we are now focusing on refining
the software for t
Hi Steven,
I never came across that compute shader execution stopped , but in som
cases I experienced some "flickering" that could somehow depend on
culling, but I did not find the reason for this. You could try to track
if glDispatchCompute() in Program.cpp is called properly and at the
rig
Hi Stephan,
I have return to the issue of the visualization problems with the database
you provided. Eventually was able to isolate the problem to the binary
parsing of the ClusterCullingCallback which in the end was fixable by just
adding a osg::Callback entry into the ClusterCullingCallback ser
Thanks a lot for your efforts! Yes, for the former version exporting as .osgb
and .ive works fine and also by passing -O "ddsNoAutoFlipWrite" to osgdem I can
export in .osg without problems. After pulling your changes I can confirm that
no workaround is needed any more. Superb!
Happy Michi
---
Hi John,
I have ran osgconv on the file:
osgconv group.osg out.osgt
And the resulting files looks like:
#Ascii Scene
#Version 117
#Generator OpenSceneGraph 3.3.5
osg::Group {
UniqueID 1
Name "dummy group"
}
Which is correct. So svn/trunk works correctly w.r.t Name. I expect
OSG-3.2.x w
Hi,
Robert, I've attached both files (or I've tried, looks like it ignores the
second attachment...)
Another interesting part is, as far as I can see, the UserData should be
serialized as well. The patch posted
http://forum.openscenegraph.org/viewtopic.php?t=5561 seems to be already in
3.0.1
Hi John,
In principle the code snippets you have provided look OK.
Like in my previous email, it could well be a bug that has long been fixed
- OSG-3.0.1 was released along time ago. Without specific code to test
against there isn't any way to know the answer.
Robert.
On 3 March 2015 at 12:25
Hi John,
Could you post the .osg file that is revealing this problem? I can run an
osgconv on my system and see if the problem exists in OSG-3.2.x or
svn/trunk.
It does sounds like a bug. This is OSG-3.0.1 which was the first stable
release that had the new serializers. A great deal of improve
Hi,
using OSG 3.0.1 I've implemented a custom class deriving from osg::Object that
should support serialization:
The register object wrapper looks like this:
Code:
REGISTER_OBJECT_WRAPPER( MyLights,
new dx::MyLights,
dx::MyLights,
"osg::Object dx::MyLights" )
{
ADD_USER_SER
Hi,
using 3.0.1 I created the following test code:
Code:
osg::ref_ptr group = new osg::Group();
group->setName( "dummy group" );
auto path = destDir_ + "/group.osg";
osgDB::writeNodeFile( *group, path );
osgDB::writeNodeFile( *group, path+"t" );
The resulting group however is entirely diffe
Can't you attach user data element to your Geodes or Geometry objects that
roughly correspond to render bins or rendering order? Then in the
intersection code, get a list of all hits, and sort it by render order
first, followed by depth. This of course means that you have to pretty
tightly control
Hi Konstantin,
Thanks for the full name.
I haven't decided how best to tackle this submission yet. As is it would
cause a performance hit as Pjotr explained. I'm open to suggestions of how
best to resolve this issue whilst addressing the bug your change sought to
address.
Cheers
Robert.
On
Hi Clement,
Yesterday I merged a submission to OSG svn/trunk that added read/write
support for inlined image data within .osgt and .osgx ascii files.
To tell the .osgt, .osgx writer to inline the data you should use the
OptionsString "WriteImageHint=IncludeData".
Robert
_
Hi Stephan,
This type of issue isn't something that others can really help with, there
are simply too many unknowns. It could be a driver bug, a problem with
your shaders, a hardware problem, an OS problem, a problem in the OSG, a
problem in your application. Even if you have everything in front
Hi Mattias,
It looks like a revision to the PolygonMode.cpp to better handle GL3
onwards has caused this regression. I have amended the #ifdef usage to
avoid compiling the glPolygonMode call under GLES1 and GLES2. Could you do
an svn update and let me know how you get on.
Cheers,
Robert.
On 3
Hi all,
As I said in a previous I occasionally build the OSG using an older
ndk (r7 something). I'm not really using it right now, I just wanted
to test out the PlatformSpecifics/Android/android.toolchain.cmake
stuff that was added a couple of months ago. However:
The builds have been failing for
Hi John-Luke,
The osgUtil::IntersectionVisitor/LineSegmentIntersector is based of pure
geometry calculations, there isn't any reference to rendering elements so
has no knowledge of what may or may not have been rendered.
If you want to have picking based on rendering results you'll need to
implem
22 matches
Mail list logo