Re: [osg-users] collada animation?

2007-09-30 Thread Robert Osfield
Hi Abe,

Could you be more specific what you mean by animation.

Different plugins support different classes of animation.

Robert.

On 9/29/07, Abe Stephens [EMAIL PROTECTED] wrote:
 Hi,

 Does the OSG collada1.4 plugin support animation?

 I'm attempting to bring simple pre-baked animations from a tool
 (blender/maya) into the OSG runtime. I've also tried using a .osg
 exporter from blender with mixed results.  Is there another tool
 chain into OSG I should try?

 Thanks-
 Abe
 ___
 osg-users mailing list
 osg-users@lists.openscenegraph.org
 http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] osgmanipulator example questions

2007-09-30 Thread sicong he
-- Forwarded message --
From: sicong he [EMAIL PROTECTED]
Date: 2007-9-10 下午6:49
Subject: Re: [osg-users] osgmanipulator example questions
To: Public OpenSceneGraph Users discussion list. 
osg-users@lists.openscenegraph.org

I tried by best and I found a way to solve thi problem.
The idea is:
First see the scene structure:

SceneRoot
Teapot01 Box01

Teapot01 and Box01 are the children of SceneRoot.
When I select Teapot01, the osgManipulator::selection (I call it in my
program Selection) set Teapot01 as one if its children.
Then I find all the parents of Teapot01, in this example, is SceneRoot and
Selection.
Then I replace the Teapot01 child of SceneRoot with Selection. Now the scene
structure is:

SceneRoot
Selection  Box01
Teapot01

And then I connect the dragger with Selection. All things go right.
When Box01 is selected, I replace the Selection child of SceneRoot with
Teapot01 and calculate the matrix of Teapot01.
The matrix of Selection is also reset. Then repeat the above steps to make
Box01 dragable.

My demo program and test scene is attached. If you have better ideas, please
tell me! Thanks in advanced!

2007/9/10, David Callu [EMAIL PROTECTED]:

 Hi,


 Can you send the osgmanipulator.cpp modified and your scene to test?

 David Callu

 2007/9/10, hesicong2006 [EMAIL PROTECTED] :
 
  I know why. root should add an Child include the scene.
 
  But another question. I can drag the Teapot01, but the whole scene now
  has two Teapot. Then how can I fix it?
 
  hesicong2006 wrote:
   Hi, Robert
   Someday before I asked a question about drag object in OSG and you
  told
   me to see osgmanipulator example. It's great.
   I tried to modify it as I want to move one object in the scene but the
   whole scene. I tried to do this in addDraggerToScene function:
  
   osg::Node* addDraggerToScene(osg::Node* scene,
   osgManipulator::CommandManager* cmdMgr, const std::string name)
   {
  scene-getOrCreateStateSet()-setMode(GL_NORMALIZE,
   osg::StateAttribute::ON);
  
  osg::Node* selectedObject=FindByName(Teapot01);
  
  osgManipulator::Selection* selection = new
  osgManipulator::Selection;
  selection-addChild(selectedObject);
  
  osgManipulator::Dragger* dragger = createDragger(name);
  
  osg::Group* root = new osg::Group;
  root-addChild(dragger);
  root-addChild(selection);
  root-addChild(createHUD());
  
  float scale = selectedObject-getBound().radius() * 1.6;
  dragger-setMatrix(osg::Matrix::scale(scale, scale, scale) *
  
   osg::Matrix::translate(selectedObject-getBound().center()));
  cmdMgr-connect(*dragger, *selection);
  
  return root;
   }
  
  
   And here my scene has two objects, one teapot, one box. But when I run
 
   the program, I see only the Teapot01 which really can drag and move,
   but the box is lost!
   I don't know how to only move one object in the scene. Please give me
   some ideas. Thanks.
  
  
 
  ___
  osg-users mailing list
  osg-users@lists.openscenegraph.org
  http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
 
 


 ___
 osg-users mailing list
 osg-users@lists.openscenegraph.org
 http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org




NativePick.rar
Description: Binary data
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] osgDB::writeNodeFile -- no Options?

2007-09-30 Thread Paul Martz
Hi Robert -- I'm getting ready to make this change, and I've noticed that I
need to change the Registry::write*() interfaces. If I change them to match
the read*() functions, then this will not be backwards compatible. E.g.,
anyone who currently calls:

osgDB::Registry::instance()-writeNode( rootNode, fName );

...will now have to call:

osgDB::Registry::instance()-writeNode( rootNode, fName,
osgDB::Registry::instance()-getOptions() );

In the core distribution, at least osgconv requires this change (haven't
checked the examples yet but will soon). Outside of core OSG, this could
affect lots of existing code.

I'm assuming the same change was made previously to the read*() interface,
so my intent is to go ahead with this incompatible change, unless you advise
otherwise.

Thanks,

Paul Martz
Skew Matrix Software LLC
http://www.skew-matrix.com
303 859 9466


 
 HI Paul,
 
 Your analysis is correct, the ReaderWriter::Options post 
 dates the original read/write*File methods.  In the case of 
 read*File the Options was added as it was required by users.  
 No one until has piped up and pointed at the lack of Options 
 parameter in the the
 write*File() methods.  Feel free to add them.
 
 Robert.
 
 On 9/19/07, Paul Martz [EMAIL PROTECTED] wrote:
 
 
  Hi Robert -- A couple questions on passing Options into the osgDB 
  read/write methods.
 
  First, the write methods (e.g., writeNodeFile, writeImageFile, etc) 
  don't take ReaderWriter::Options as a parameter. Instead, they 
  implicitly pass the osgDB's _options member variable to the 
 plugin. Is 
  there a design reason for this to be different from the 
 analogous read 
  interface? Or, more to the point, if I added Options as a 
 command line 
  parameter to the write methods, would you reject such a 
 submission for any a priori reason?
 
  Second, looks like the read interface has two methods each for 
  readNodeFile, readImageFile, etc., one taking Options the other not 
  (and getting it from the registry). I assume this was done for 
  historical reasons to preserve backwards compatibility? The 
  non-Options interface was first, and the interface with 
 Options came along later?
 
  Of course, I'd have to do essentially the same thing if I were to 
  modify the write interface to take Options.
 
  (Stumbling across all sorts of fun stuff as I try to create this 
  OpenFlight exporter. :-)
 
  Thanks,
 
  Paul Martz
  Skew Matrix Software LLC
  http://www.skew-matrix.com
  303 859 9466
 
  ___
  osg-users mailing list
  osg-users@lists.openscenegraph.org
  
 http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.
  org
 
 
 ___
 osg-users mailing list
 osg-users@lists.openscenegraph.org
 http://lists.openscenegraph.org/listinfo.cgi/osg-users-opensce
negraph.org

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


[osg-users] osgDB::writeNodeFile -- no Options?

2007-09-30 Thread Paul Martz
Hi Robert -- A couple questions on passing Options into the osgDB read/write
methods.
 
First, the write methods (e.g., writeNodeFile, writeImageFile, etc) don't
take ReaderWriter::Options as a parameter. Instead, they implicitly pass the
osgDB's _options member variable to the plugin. Is there a design reason for
this to be different from the analogous read interface? Or, more to the
point, if I added Options as a command line parameter to the write methods,
would you reject such a submission for any a priori reason?
 
Second, looks like the read interface has two methods each for readNodeFile,
readImageFile, etc., one taking Options the other not (and getting it from
the registry). I assume this was done for historical reasons to preserve
backwards compatibility? The non-Options interface was first, and the
interface with Options came along later?
 
Of course, I'd have to do essentially the same thing if I were to modify the
write interface to take Options.
 
(Stumbling across all sorts of fun stuff as I try to create this OpenFlight
exporter. :-)
 
Thanks,
 
Paul Martz
Skew Matrix Software LLC
http://www.skew-matrix.com http://www.skew-matrix.com/ 
303 859 9466
 
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] Releasing file handles in osgDB

2007-09-30 Thread Robert Osfield
Hi Antoine,

Is it just the OSGA plugin that you are having an issue with it
holding a file handle?  If so you could try calll close() on the
Archive the the plugin has loaded - the Archive will be cached in the
Registry.  Or you could try the Regisytr::clearArchiveCache() method.

Robert.

On 9/30/07, Antoine Hue [EMAIL PROTECTED] wrote:
 Hello,

 I want to overwrite a .osga file from a child process while the same
 file is shown in the main process's viewer.
 At the beginning I did it brutal: rewrite the file without checking. It
 worked OK for Linux but was crashing on Windows in case of LODed scene
 graph within the .osga. I have added a temporary/shadow file and it
 works still  under Linux but not under Windows. The only case it works
 is when the file does not already exist. I suspect that Windows file
 protection is sticking again: Cannot delete file XXX since it is used
 by another application..

 I have removed (many frames ahead) the top node from the scene graph of
 the main viewer but still cannot overwrite the file.

 Is there a way to check or force that osgDB is releasing completely the
 file handle ?

 Thanks in advance,

 Antoine
 ___
 osg-users mailing list
 osg-users@lists.openscenegraph.org
 http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


[osg-users] Please test SVN version of OpenSceneGraph

2007-09-30 Thread Robert Osfield
Hi All,

I'll be making the 2.1.13 dev release tomorrow morning, so would very
much appreciate some testing of the SVN version on different platforms
before then to make sure we have a stable point to tab the release.

I would also like to 2.2 out pretty sharp.  If possible even Thursday
this week. This will require a couple more dev releases this week and
lots of build/runtime testing.  In general I believe the recent 2.1.x
look pretty stable, so hopefully this isn't too much of a tall order.

Thanks in advance for your help,
Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] Please test SVN version of OpenSceneGraph

2007-09-30 Thread Paul Martz
A warning for those of you who missed the discussion...

The Registry::write*() interface now takes an osgDB::Options parameter. If
you call this directly, you'll need to change your code. Best way is to use
the osgDB::write*File() functions.

Sorry for any inconvenience.
   -Paul

 
 Hi All,
 
 I'll be making the 2.1.13 dev release tomorrow morning, so 
 would very much appreciate some testing of the SVN version on 
 different platforms before then to make sure we have a stable 
 point to tab the release.
 
 I would also like to 2.2 out pretty sharp.  If possible even 
 Thursday this week. This will require a couple more dev 
 releases this week and lots of build/runtime testing.  In 
 general I believe the recent 2.1.x look pretty stable, so 
 hopefully this isn't too much of a tall order.
 
 Thanks in advance for your help,
 Robert.
 ___
 osg-users mailing list
 osg-users@lists.openscenegraph.org
 http://lists.openscenegraph.org/listinfo.cgi/osg-users-opensce
negraph.org

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] OpenSceneGraph-2.1.1 dev Examples

2007-09-30 Thread Robert Osfield
Hi Jason,

You should generate the build system from the root
OpenSceneGraph/CMakeLists.txt file rather local directory ones.

Robert.

On 8/1/07, Fry, Jason (UK) [EMAIL PROTECTED] wrote:

 Hello,

 I am trying to build the examples for OpenSceneGraph.  I have been
 trying to utilise the Cmake utility to build the examples for Windows.

 But I get the error message :

 ../osgstaticviewer/CMakeLists.txt:7:Unknown Cmake command
 SETUP_EXAMPLE.

 This can't be true, as I would have thought it would of been brought to
 somebodies attention by now.  Anyone know what is going on here?

 Any help would be greatly appreciated

 jason

 
 This email and any attachments are confidential to the intended
 recipient and may also be privileged. If you are not the intended
 recipient please delete it from your system and notify the sender.
 You should not copy it or use it for any purpose nor disclose or
 distribute its contents to any other person.
 

 ___
 osg-users mailing list
 osg-users@lists.openscenegraph.org
 http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] Trackball and view question

2007-09-30 Thread Robert Osfield
Hi Bill,

The camera manipulators role is to modifying the view matrix so I'm a
bit perplexed that you are suprised by this.

Also please considering move from SimpleViewer up to osgViewer::Viewer
working as an embedded viewer in 2.x rather than using SimpleViewer as
it only existed for a short while and has been totally superseded.

Robert.

On 9/18/07, Poirier, Guillaume [EMAIL PROTECTED] wrote:




 Hello everyone,

  I am using a SimpleViewer. I set up a post draw callback on its main
 camera. In it
  I read the camera eye, center, and up vectors. Initially, this give me (0,
 0, 0),
  (0, 0, -1), and (0, 1, 0) respectively. This is what I expect and it gives
 me a
  particular view of my scene.

  Now I add a trackball manipulator to the main camera and set up the view
 similar
  to what I had previously. When I read back the data it is quite different.
 I would have
  expected the same camera position / orientation than before since what I
 see is
  similar. Unless the trackball affects the model position / orientation and
 not just
  the view ? How can I use a trackball and read back in the post draw
 callback the
  values I want ?


  sincerely,


  Bill
 ___
 osg-users mailing list
 osg-users@lists.openscenegraph.org
 http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] Please test SVN version of OpenSceneGraph

2007-09-30 Thread Jean-Sébastien Guay
Hello Robert,

 I'll be making the 2.1.13 dev release tomorrow morning, so would very
 much appreciate some testing of the SVN version on different platforms
 before then to make sure we have a stable point to tab the release.

Everything seems fine on my machine at home: WinXP SP2, Visual C++  
2005 Express.

Compiling on Linux (FC6) at school as I type this, will report once it's done.

J-S
-- 
__
Jean-Sebastien Guay [EMAIL PROTECTED]
 http://whitestar02.webhop.org/


This message was sent using IMP, the Internet Messaging Program.


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


Re: [osg-users] Please test SVN version of OpenSceneGraph

2007-09-30 Thread Brian Keener
Robert Osfield wrote:
 
  #define log2(x) (log(x) / M_LOG2_E)
  #define log2f(x) (logf(x) / (float) M_LOG2_E)
 
 That looks like it might well be the proplem.  Added a if #ifndef log2
 might be what is required around the include/osg/Math definition.

That got it to compile.  I also still have to add the flags:

-DWIN32 -DNOMINMAX -W -Wall -mnop-fun-dllimport -DOSG_LIBRARY

to CMAKE_CXX_FLAGS - tried only using some parts but ultimately used all the 
flags and added to CMAKE_C_FLAGS too.  This change is required for some 
reason to get Tessellator to compile and ignore those GLvoid conversion 
errors but that it probably all it is doing is ignoring them and allowing 
Tessellator to compile.

I also had to make the change for wsock32.lib to wsock32.a in CMakeLists.txt 
in the root of the svn tree so the compile would find the correct library in 
Cygwin.

I also had to make a change for osgviewerMFC in the examples/CMakelists.txt 
so it would not build and had to remove the references for the wxWidgets 
(that whole routine could be nicer).

Most of the above I think I have reported before and OSG did build an install 
but I guess still not enough thread changes in Cygwin as osgconv still hangs 
on exit and has to be killed.

bk



___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org