Re: [osg-users] AutoTransform cannot be picked up correctly

Thanks for your reply. I changed it based on osgPick, and since I only use OSG on Windows, I added those headers. At present, I have no time to find out the problem. I have avoided this problem, and I will study it when I have time. Thanks again. 在 2020年2月19日星期三 UTC+8下午10:39:47，Robert

Re: [osg-users] AutoTransform cannot be picked up correctly

Thanks tor the test program. I've got it compile on my Linux system with just removing the Windows headers you added, why were these added? I can confirm the problem, I can pick the cessna without the AutoTransform by zooming in but not the one under the AutoTransform. I haven't yet had a

Re: [osg-users] AutoTransform cannot be picked up correctly

OSG version is 3.6.4 在 2020年2月14日星期五 UTC+8下午4:29:10，OpenSceneGraph Users写道： > > Hi, All > AutoTransform cannot be picked up correctly when it is a child node of > LOD. Does anyone have the same problem as me? How did it work out? > Thanks > > > > -- You received this message because you are

[osg-users] AutoTransform cannot be picked up correctly

Hi, All AutoTransform cannot be picked up correctly when it is a child node of LOD. Does anyone have the same problem as me? How did it work out? Thanks/* OpenSceneGraph example, osgpick. * * Permission is hereby granted, free of charge, to any person obtaining a copy * of this software and

Re: [osg-users] AutoTransform for scale 3.6.0

This is broke for 3.6.0 as well. -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=74692#74692 ___ osg-users mailing list osg-users@lists.openscenegraph.org

[osg-users] AutoTransform for scale 3.6.0

Hi Folks, I have an AutoTransform set to maintain the axes model to the same screen size but I'm guessing I'm using it incorrectly. It behaves just like a scale node with a constant fixed scale instead of changing the scale to maintain a constant screen size. I've tried all sorts of param's for

Re: [osg-users] AutoTransform, ROTATE_TO_SCREEN and small feature culling

Hi Robert, I want to come back to my original remark that culling does not work correctly with AutoTransforms and ROTATE_TO_SCREEN. I have modified the example osgautotransform.cpp by adding a new class that contains an AutoTransform and a drawable. An object of this class is added to the

Re: [osg-users] AutoTransform, ROTATE_TO_SCREEN and small feature culling

Hi Hartwig, On 29 March 2018 at 22:51, Hartwig Wiesmann wrote: > what I would like to produce is an object that is always oriented towards the > user (screen) and has the same size independent of the zoom level. Though the > zoom level is limited in a certain range

Re: [osg-users] AutoTransform, ROTATE_TO_SCREEN and small feature culling

Hi Robert, what I would like to produce is an object that is always oriented towards the user (screen) and has the same size independent of the zoom level. Though the zoom level is limited in a certain range by an additional LOD. Therefore, I think that AutoTranslate is the only viable option,

Re: [osg-users] AutoTransform, ROTATE_TO_SCREEN and small feature culling

HI Hatwig, The code is correct, you can't cull something that you don't have a valid bounding volume for. Distabling culling for a particular node only affect that node and all it's parents, it does affect culling of the children which can still have their own culling be effective. If you don't

Re: [osg-users] AutoTransform, ROTATE_TO_SCREEN and small feature culling

Hi Hartwig, On 27 March 2018 at 17:44, Hartwig Wiesmann wrote: > I was not talking about the cullingActive flag but the method > isCullingActive! isCullingActive checks besides the cullingActive flag if the > boundary sphere is valid. As long as the boundary sphere

Re: [osg-users] AutoTransform, ROTATE_TO_SCREEN and small feature culling

Hi Robert, I was not talking about the cullingActive flag but the method isCullingActive! isCullingActive checks besides the cullingActive flag if the boundary sphere is valid. As long as the boundary sphere is invalid isCullingActive() returns false. This is the problem I reported. Code:

Re: [osg-users] AutoTransform, ROTATE_TO_SCREEN and small feature culling

Hi Hartwig, CullingActive flag is only effective for the Node that you set it for and all it's parents, it doesn't disable culling for the children of the node with CullingActive set. Robert. On 26 March 2018 at 22:28, Hartwig Wiesmann wrote: > Hi, > > I found a

[osg-users] AutoTransform, ROTATE_TO_SCREEN and small feature culling

Hi, I found a very old article covering this issue: https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg15948.html. In the meantime it seems to be that proposal (2) has been implemented and the AutoTransform's computeBound() method returns an invalid bounding sphere during the

[osg-users] AutoTransform can't leave unchanged the form of graphic item

Hi, I trying to draw the plus symbol on the view using osg::AutoTransform This is my code http://pastebin.com/Jzpgz376 The problem is that, when I move the symbol it's form changed. Is it osg::AutoTransform problem? Thank you! Cheers, Vitaliy -- Read this topic online here:

[osg-users] AutoTransform and multiple views

Hi, I am using the Drag handlers with an autotransform on them (see code below). I have it set to AutoscaleToScreen. This works great as long as I only have 1 view of the scene. When I have multiple views though, I get a problem where zooming in on one will cause the autotransform to change

Re: [osg-users] AutoTransform and multiple views

Hi, On 18/07/2011 13:19, David Cofer wrote: Hi, I am using the Drag handlers with an autotransform on them (see code below). I have it set to AutoscaleToScreen. This works great as long as I only have 1 view of the scene. When I have multiple views though, I get a problem where zooming in on

[osg-users] AutoTransform scale to screen algorithm - reference?

Hi, Is there any reference for the calculations in AutoTransform::accept(), when getAutoScaleToScreen() is true? It seems to do the right thing, but I really need to understand how it works for an application. Thank you! Cheers, Frank -- Read this topic online here:

Re: [osg-users] AutoTransform scale to screen algorithm - reference?

Reference as in a research paper? As far as I know, AutoTransform's calculations are just linear algebra and a firm grasp of the OpenGL transformation pipeline. Both OpenGL Programming Guide (red book) and OpenGL Distilled (my book) describe the transform pipeline found in OpenGL =3.0, and

Re: [osg-users] AutoTransform scale to screen algorithm - reference?

As I look at it some more, the good news is that I think I understand the part I needed to know about. :) That said, I'm curious about the stuff going on when you have _autoScaleTransitionWidthRatio set to non-zero (default is 0.25), and then set _minimumScale or _maximumScale away from their

Re: [osg-users] AutoTransform scale to screen algorithm - reference?

It's the block of code that starts here: http://www.openscenegraph.org/projects/osg/browser/OpenSceneGraph/trunk/src/osg/AutoTransform.cpp#L232 -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=40499#40499

[osg-users] AutoTransform and traversals

I'm not sure why the calculations done in AutoTransform are done in the cull traversal, rather than in update. I'd have thought that update was for objects setting things in themselves, and the cull was read only. Does the update not accumulate transform matrices? Something else? thanks andy

Re: [osg-users] AutoTransform and traversals

Hi Andy, On Fri, Oct 1, 2010 at 1:20 PM, Andy Skinner andy.skin...@mathworks.com wrote: I’m not sure why the calculations done in AutoTransform are done in the cull traversal, rather than in update. The AutoTransform is view dependent so requires the accumulated transform matrices from the

Re: [osg-users] AutoTransform

Hi Sunil, I would like to know as to what is the difference between /ROTATE_TO_SCREEN/ /ROTATE_TO_CAMERA/ in the AutoTransform class. ROTATE_TO_SCREEN will rotate the sub-graph to face the view plane, while ROTATE_TO_CAMERA will rotate the sub-graph to face the camera's eye point. Check

Re: [osg-users] AutoTransform

Thanks John, I had run the example before .. but after you told me the difference .. I could figure out the difference in the output... Sunil. On Thu, Apr 8, 2010 at 11:39 AM, John Vidar Larring larr...@weatherone.tvwrote: Hi Sunil, I would like to know as to what is the difference

[osg-users] AutoTransform

Hello Everybody, I would like to know as to what is the difference between *ROTATE_TO_SCREEN* *ROTATE_TO_CAMERA* in the AutoTransform class. I was also wondering if there is some inbuilt feature to place an axis in the corner of the screen indicating the world axis .. as is common in most cad

Re: [osg-users] Autotransform, compositeviewer and small feature culling problems

Hi J.P, The issue you are hitting up against is a limitation of osg::AutoTransform in that it only has a single set of state so when you have two or more views that require different stats you'll get issues with both views attempting to sets it's value. The only way to solve this would be to

Re: [osg-users] Autotransform, compositeviewer and small feature culling problems

Hi Robert, Robert Osfield wrote: Hi J.P, The issue you are hitting up against is a limitation of osg::AutoTransform in that it only has a single set of state so when you have two or more views that require different stats you'll get issues with both views attempting to sets it's value. The

[osg-users] autotransform and fit

Hi All, I have a scene graph with an autotransform in it (I want the size of an arrow be preserved from any change that might happen on window size). So, to fit my model in that window, I would need to get the whole bounding sphere. Is there a visitor that does what I need, without redrawing

[osg-users] AutoTransform and Draggers

Hello all, I'm having a little trouble wrapping my head around getting AutoTransform and Draggers to play together so I thought I'd turn to the trusty mailing list. What I'm trying to do: 1) Populate a scene with many things. One of which is an object - let's assume it's a sphere

Re: [osg-users] AutoTransform scaling precision.

closely resembling localized screen space. Jon -Original Message- From: Marjamaa, Jonathon E Sent: Thursday, November 20, 2008 4:23 PM To: osg-users@lists.openscenegraph.org Subject: [osg-users] AutoTransform scaling precision. Hello, I am seeing some odd behavior

Re: [osg-users] AutoTransform scaling precision.

Subject: Re: [osg-users] AutoTransform scaling precision. Hi Jon, The pixelSize function is an approximation of the mapping, making assumptions, for the purposes of speed, with the intention of providing good enough results for most purposes. So rather than being wrong, is just not accurate

Re: [osg-users] AutoTransform scaling precision.

get me to something more closely resembling localized screen space. Jon -Original Message- From: Marjamaa, Jonathon E Sent: Thursday, November 20, 2008 4:23 PM To: osg-users@lists.openscenegraph.org Subject: [osg-users] AutoTransform scaling precision. Hello, I am seeing some odd

[osg-users] AutoTransform scaling precision.

Hello, I am seeing some odd behavior with AutoTransform. The following .osg file creates an AutoTransform with a grid of lines attached. The lines are each separated by one unit of space. When I look at the file in osgviewer, I see that this spacing is not kept. It looks like the

[osg-users] AutoTransform and small feature culling

Hi, We have searched the archive and already found a post about this subject: http://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg15948.html First our build setup: OS: Windows (sorry robert) OSG: osg2.6.0 DELTA3D: 2.1.0 Ok,.. our problem is that AutoTransform nodes get culled and

Re: [osg-users] AutoTransform and small feature culling

On Tue, Oct 28, 2008 at 1:14 PM, Peter Wraae Marino [EMAIL PROTECTED] wrote: To our application we don't need our AutoTransform objects to be small feature culled, so we would like to ask is there a reason why there isn't a flag on all nodes to enabled/disable small feature culling? Because

[osg-users] AutoTransform and small feature culling again

I have been through an issue that has been discussed previously on the osg-users mailing list. I have put the previous discussion below (it was end of august). The culling traversal was never called on an AutoTransform with auto scale because of small feature culling. So Robert answers with three

Re: [osg-users] AutoTransform and SMALL_FEATURE_CULLING

Hi Sherman, I don't think your code is in error, nor that AutoTransform or small feature culling is in error, rather it's unfortunately chicken and the egg which came first? type dependency. The ways to break the culling of custom node in the first frame would be: To switch off small feature

[osg-users] AutoTransform and SMALL_FEATURE_CULLING

I've attached a small demo app that illustrates an issue I've discovered (known?) with AutoTransform nodes and small feature culling. Briefly summarized, if I add a custom AutoTransform node (see code for trivial example) to the scenegraph just under the root node everything seems fine, with or

[osg-users] AutoTransform scale implementation

I'd like to know more about the AutoTransform auto-scale implementation. We want something similar, but we think we need to account for non-uniform scaling. Could I get a description of CullingSet::computePixelSizeVector()? I see it was written in 2002, but I'd appreciate any help in

[osg-users] AutoTransform and reference frame

I'm trying to understand how to use AutoTransform to make an object that keeps its rotation and scale the same as I transform the scene or change the size of the window. The rotation part seems fine, but I've had some problem with the scale. I set AutoScaleToScreen to true and apply a scale for

[osg-users] Autotransform Frustum Update

Hi, My scene graph has an Autotransform with a geode containing geometry for a textured quad to display an icon. The transform is set to auto rotate and scale to the screen. I am noticing two problems with this set up: - When the frustum changes (e.g. fov change), the icons no longer scale to