date:20080626

[osg-users] Error with drawable

2008-06-26 Thread Ahmed Nawar


Dear All,

I think this is a bug:
If you have a pointer to Drawable. if you add it to geode and 
removed it from this geode.
You can not use this geode again.
I think that OSG remove the Drawable vertex from the memory.

I solve this by adding this drawable to another geode and i don't use this new 
geode.
so the Drawable will be under one geode at least in all cases.

Thanks
Ahmed Nawar


From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Ahmed Nawar [EMAIL 
PROTECTED]
Sent: Thursday, June 26, 2008 8:38 AM
To: OpenSceneGraph Users
Subject: Re: [osg-users] callback

Sorry for late.

  It is an update callback.

Thanks,
Ahmed Nawar

From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Serge Lages [EMAIL 
PROTECTED]
Sent: Wednesday, June 25, 2008 6:14 PM
To: OpenSceneGraph Users
Subject: Re: [osg-users] callback

Hi,

Is it an update callback or a cull calback ?

On Wed, Jun 25, 2008 at 5:11 PM, Ahmed Nawar [EMAIL PROTECTED]mailto:[EMAIL 
PROTECTED] wrote:

Dear All,

i attached  a callback to a geode node.

CallBack operator:

void GeodeCallBack::operator()( osg::Node* node, osg::NodeVisitor* nv )
{

   osg::Geode* geode =
   dynamic_castosg::Geode*( node );

   geode-removeDrawables(0,geode-getNumDrawables ());

  // get different drawable.
   osg::Drawable *d =  drawableBuilder-getDrawable(dataPoint-shape);

   geode-addDrawable( d );

   traverse( node, nv );
}


1- is it Ok to change the geode's contains in the callback?
2- some times the  geode-addDrawable( d );   terminate the program. any 
ideas?

Thanks,
Ahmed Nawar
___
osg-users mailing list
osg-users@lists.openscenegraph.orgmailto:osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org



--
Serge Lages
http://www.tharsis-software.com
___
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] [osg-submissions] API configuratio ns in aseparateConfig include file

2008-06-26 Thread Mathias Fröhlich


Hi,

On Wednesday 25 June 2008 17:59, Jean-Sébastien Guay wrote:
 I think you're mixing things up. There are three different issues here:

 1. The choice to use Config headers.
 2. The fact that the Atomic header includes windows.h.
 3. The fact that your version of CMake chooses the wrong configuration
 and does not generate the Config header.
Yep.

 Number 1 is a design choice. The choice is basically between having a
 file that defines options that affect the build, and needing to specify
 those options as defines in *each* project that uses OSG. I can see why
 the choice to have a Config file was taken. Otherwise, you would have to
 support people configuring their OSG build one way and then linking to
 it in a project where the incorrect define was being used, which would
 happen more often than you'd think. Having a Config header ensures that
 both the built version of OSG and your project use the same options (as
 long as the same Config header is included for both).
Yep, thanks!

 Number 2 was a mistake (by the person who made the change, but still
 unrelated to the choice in number 1), and is being rectified as we
 speak. Check the messages from yesterday. *That* is what's breaking the
 build on Windows right now.
Yep, I took that from two other open source projects I have provided that code 
for. None of them where that sensitive with including Windows.h. These 
projects could benefit from inlining the functions directly. osg cannot ...
Patch is prepared ...

 As for Number 3, I believe that is caused by CMake 2.4.x. This can be
 investigated and fixed *after* the windows.h issue is fixed, which is
 much more major (as it affects *everyone* building on Windows,
 independently of the version of CMake they use). A workaround for you
 would be to get CMake 2.6 from cmake.org. Then you would get the right
 configuration (interlocked), the Config header would be generated and
 used, and you would see the windows.h include problem... At least that's
 what I think. :-)
That is a bug in the implementation of the configure check.
Alternatively an invocation problem with cmake. I need to call cmake with the 
right output target to make it set up configuration test correct for the 
msvc8 win64 build for example.

  
   you don't need anything different than
  before, since the Config headers are installed with your other OSG
  headers.
  
  Do you have an out-of-source configuration or in source?
  I use the out-of-source configuration and so the config headers are
  installed in the build directory.

 I use an out-of-source build with CMake 2.6, and the Config header is
 being generated just fine. But what I was talking about in the line you
 quoted above is that OSG headers are including the Config headers. If
 you don't do an INSTALL (or make install), then the Config headers are
 not together with your other OSG headers.

 Config headers:
 OpenSceneGraph/build/include/OpenThreads/Config
 OpenSceneGraph/build/include/osg/Config

 Other headers:
 OpenSceneGraph/include/OpenThreads/*
 OpenSceneGraph/include/osg/*

And installed headers and libs:
prefix/include/*
prefix/lib/*
... note: just one single directory to care for.
On *NIX often in a prefix so that you do not need to do anything on the 
compiler command line to make the compiler find that library.

 So the other headers won't find #include OpenThreads/Config or
 #include osg/Config unless you add the directories above (in build)
 to your include file search path. Which was not required before.

 But if you do an INSTALL, you don't have that problem, because the
 INSTALL target copies the Config headers to the same place as the other
 headers, and so #include OpenThreads/Config will work without any
 change to your project files.

Yep, an install will provide all files together in one directory tree. The 
build stage is just an intermediate step that I was surprised somebody will 
use as is. Plenty libraries I know of are only usable when installed. Before 
you will not have any chance to find the shared or static libraries or 
includes somewhere deep in the build/source tree.

When you execute that intall step, you will not notice any difference between 
before that change and past that change. Just that difference that you do no 
longer need to care for keeping defines in sync across probably many 
libs/apps using osg. And that is a benefit IMO ...

 I hope that clears things up.
Thanks, for writing!

GReetings

Mathias

-- 
Dr. Mathias Fröhlich, science + computing ag, Software Solutions
Hagellocher Weg 71-75, D-72070 Tuebingen, Germany
Phone: +49 7071 9457-268, Fax: +49 7071 9457-511
-- 
Vorstand/Board of Management:
Dr. Bernd Finkbeiner, Dr. Florian Geyer,
Dr. Roland Niemeier, Dr. Arno Steitz, Dr. Ingrid Zech
Vorsitzender des Aufsichtsrats/
Chairman of the Supervisory Board:
Prof. Dr. Hanns Ruder
Sitz/Registered Office: Tuebingen
Registergericht/Registration Court: Stuttgart
Registernummer/Commercial Register No.: HRB 382196

Re: [osg-users] Error with drawable

2008-06-26 Thread Paul Melis


Hi,

Ahmed Nawar wrote:

I think this is a bug:
If you have a pointer to Drawable. 
A pointer (osg::Drawable*) or a ref_ptr (osg::ref_ptrosg::Drawable)? 
As Drawable is reference-counted, you should preferably use the latter 
to store pointers to drawables.

if you add it to geode and removed it from this geode.
You can not use this geode again.
I think that OSG remove the Drawable vertex from the memory.
  
If the geode holds the only reference to the drawable and you then 
remove that drawable from the geode, then yes, the drawable is destructed.
But as long as you still have a reference to the drawable somewhere, 
using a osg::ref_ptr, it should not be destructed and you can add/remove 
it to the geode as much as you want.


Do you do something like this?

osg::Drawable *d = ...  // initial reference count = 0
osg::Geode *g =  // initial reference count = 0

g.addDrawable(d); // drawable reference count now 1
g.removeDrawable(d);   // drawable reference count will be decreased, 
reaches zero and the object is therefore destructed



I solve this by adding this drawable to another geode and i don't use this new 
geode.
so the Drawable will be under one geode at least in all cases.
  
You would be better off to store a reference to the drawable somewhere 
in your application without having to use an extra geode. This geode 
will need to be referenced somewhere as well, so it doesn't solve the 
problem.


And as you care that the drawable can be _re-used_ after it is removed 
from the geode it sounds like you want to add the drawable back again at 
some later point in time. For that you need to keep a reference to the 
drawable anyway...


Paul


Thanks
Ahmed Nawar


From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Ahmed Nawar [EMAIL 
PROTECTED]
Sent: Thursday, June 26, 2008 8:38 AM
To: OpenSceneGraph Users
Subject: Re: [osg-users] callback

Sorry for late.

  It is an update callback.

Thanks,
Ahmed Nawar

From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Serge Lages [EMAIL 
PROTECTED]
Sent: Wednesday, June 25, 2008 6:14 PM
To: OpenSceneGraph Users
Subject: Re: [osg-users] callback

Hi,

Is it an update callback or a cull calback ?

On Wed, Jun 25, 2008 at 5:11 PM, Ahmed Nawar [EMAIL PROTECTED]mailto:[EMAIL 
PROTECTED] wrote:

Dear All,

i attached  a callback to a geode node.

CallBack operator:

void GeodeCallBack::operator()( osg::Node* node, osg::NodeVisitor* nv )
{

   osg::Geode* geode =
   dynamic_castosg::Geode*( node );

   geode-removeDrawables(0,geode-getNumDrawables ());

  // get different drawable.
   osg::Drawable *d =  drawableBuilder-getDrawable(dataPoint-shape);

   geode-addDrawable( d );

   traverse( node, nv );
}


1- is it Ok to change the geode's contains in the callback?
2- some times the  geode-addDrawable( d );   terminate the program. any 
ideas?

Thanks,
Ahmed Nawar
___
osg-users mailing list
osg-users@lists.openscenegraph.orgmailto:osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org



--
Serge Lages
http://www.tharsis-software.com
___
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 mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Error with drawable

2008-06-26 Thread Ahmed Nawar

Dear Paul,

  Drawable is reference-counted?
  This is new to me. Thanks.

  I used osg::Drawable* and not smart pointer.
  Because i think that this will make the drawable stay and not delete if i 
removed it from geode. Thanks for help.

  I need to put my drawables in a vector. How can i keep the smart pointers in 
a vector?

Thanks,
Ahmed Nawar

From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Paul Melis [EMAIL 
PROTECTED]
Sent: Thursday, June 26, 2008 10:50 AM
To: OpenSceneGraph Users
Subject: Re: [osg-users] Error with drawable

Hi,

Ahmed Nawar wrote:
 I think this is a bug:
 If you have a pointer to Drawable.
A pointer (osg::Drawable*) or a ref_ptr (osg::ref_ptrosg::Drawable)?
As Drawable is reference-counted, you should preferably use the latter
to store pointers to drawables.
 if you add it to geode and removed it from this geode.
 You can not use this geode again.
 I think that OSG remove the Drawable vertex from the memory.

If the geode holds the only reference to the drawable and you then
remove that drawable from the geode, then yes, the drawable is destructed.
But as long as you still have a reference to the drawable somewhere,
using a osg::ref_ptr, it should not be destructed and you can add/remove
it to the geode as much as you want.

Do you do something like this?

osg::Drawable *d = ...  // initial reference count = 0
osg::Geode *g =  // initial reference count = 0

g.addDrawable(d); // drawable reference count now 1
g.removeDrawable(d);   // drawable reference count will be decreased,
reaches zero and the object is therefore destructed

 I solve this by adding this drawable to another geode and i don't use this 
 new geode.
 so the Drawable will be under one geode at least in all cases.

You would be better off to store a reference to the drawable somewhere
in your application without having to use an extra geode. This geode
will need to be referenced somewhere as well, so it doesn't solve the
problem.

And as you care that the drawable can be _re-used_ after it is removed
from the geode it sounds like you want to add the drawable back again at
some later point in time. For that you need to keep a reference to the
drawable anyway...

Paul

 Thanks
 Ahmed Nawar

 
 From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Ahmed Nawar [EMAIL 
 PROTECTED]
 Sent: Thursday, June 26, 2008 8:38 AM
 To: OpenSceneGraph Users
 Subject: Re: [osg-users] callback

 Sorry for late.

   It is an update callback.

 Thanks,
 Ahmed Nawar
 
 From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Serge Lages [EMAIL 
 PROTECTED]
 Sent: Wednesday, June 25, 2008 6:14 PM
 To: OpenSceneGraph Users
 Subject: Re: [osg-users] callback

 Hi,

 Is it an update callback or a cull calback ?

 On Wed, Jun 25, 2008 at 5:11 PM, Ahmed Nawar [EMAIL PROTECTED]mailto:[EMAIL 
 PROTECTED] wrote:

 Dear All,

 i attached  a callback to a geode node.

 CallBack operator:

 void GeodeCallBack::operator()( osg::Node* node, osg::NodeVisitor* nv )
 {

osg::Geode* geode =
dynamic_castosg::Geode*( node );

geode-removeDrawables(0,geode-getNumDrawables ());

   // get different drawable.
osg::Drawable *d =  drawableBuilder-getDrawable(dataPoint-shape);

geode-addDrawable( d );

traverse( node, nv );
 }


 1- is it Ok to change the geode's contains in the callback?
 2- some times the  geode-addDrawable( d );   terminate the program. any 
 ideas?

 Thanks,
 Ahmed Nawar
 ___
 osg-users mailing list
 osg-users@lists.openscenegraph.orgmailto:osg-users@lists.openscenegraph.org
 http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org



 --
 Serge Lages
 http://www.tharsis-software.com
 ___
 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 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] Error with drawable

2008-06-26 Thread Paul Melis


Ahmed Nawar wrote:

Dear Paul,

  Drawable is reference-counted?
  This is new to me. Thanks.
  
Everything that derives from osg::Object (which derives from 
osg::Referenced) is reference-counted, including osg::Drawable.

  I used osg::Drawable* and not smart pointer.
  Because i think that this will make the drawable stay and not delete if i 
removed it from geode. Thanks for help.

  I need to put my drawables in a vector. How can i keep the smart pointers in 
a vector?
  

std::vectorosg::ref_ptrosg::Drawable 

Paul

Thanks,
Ahmed Nawar

From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Paul Melis [EMAIL 
PROTECTED]
Sent: Thursday, June 26, 2008 10:50 AM
To: OpenSceneGraph Users
Subject: Re: [osg-users] Error with drawable

Hi,

Ahmed Nawar wrote:
  

I think this is a bug:
If you have a pointer to Drawable.


A pointer (osg::Drawable*) or a ref_ptr (osg::ref_ptrosg::Drawable)?
As Drawable is reference-counted, you should preferably use the latter
to store pointers to drawables.
  

if you add it to geode and removed it from this geode.
You can not use this geode again.
I think that OSG remove the Drawable vertex from the memory.



If the geode holds the only reference to the drawable and you then
remove that drawable from the geode, then yes, the drawable is destructed.
But as long as you still have a reference to the drawable somewhere,
using a osg::ref_ptr, it should not be destructed and you can add/remove
it to the geode as much as you want.

Do you do something like this?

osg::Drawable *d = ...  // initial reference count = 0
osg::Geode *g =  // initial reference count = 0

g.addDrawable(d); // drawable reference count now 1
g.removeDrawable(d);   // drawable reference count will be decreased,
reaches zero and the object is therefore destructed

  

I solve this by adding this drawable to another geode and i don't use this new 
geode.
so the Drawable will be under one geode at least in all cases.



You would be better off to store a reference to the drawable somewhere
in your application without having to use an extra geode. This geode
will need to be referenced somewhere as well, so it doesn't solve the
problem.

And as you care that the drawable can be _re-used_ after it is removed
from the geode it sounds like you want to add the drawable back again at
some later point in time. For that you need to keep a reference to the
drawable anyway...

Paul

  

Thanks
Ahmed Nawar


From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Ahmed Nawar [EMAIL 
PROTECTED]
Sent: Thursday, June 26, 2008 8:38 AM
To: OpenSceneGraph Users
Subject: Re: [osg-users] callback

Sorry for late.

  It is an update callback.

Thanks,
Ahmed Nawar

From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Serge Lages [EMAIL 
PROTECTED]
Sent: Wednesday, June 25, 2008 6:14 PM
To: OpenSceneGraph Users
Subject: Re: [osg-users] callback

Hi,

Is it an update callback or a cull calback ?

On Wed, Jun 25, 2008 at 5:11 PM, Ahmed Nawar [EMAIL PROTECTED]mailto:[EMAIL 
PROTECTED] wrote:

Dear All,

i attached  a callback to a geode node.

CallBack operator:

void GeodeCallBack::operator()( osg::Node* node, osg::NodeVisitor* nv )
{

   osg::Geode* geode =
   dynamic_castosg::Geode*( node );

   geode-removeDrawables(0,geode-getNumDrawables ());

  // get different drawable.
   osg::Drawable *d =  drawableBuilder-getDrawable(dataPoint-shape);

   geode-addDrawable( d );

   traverse( node, nv );
}


1- is it Ok to change the geode's contains in the callback?
2- some times the  geode-addDrawable( d );   terminate the program. any 
ideas?

Thanks,
Ahmed Nawar
___
osg-users mailing list
osg-users@lists.openscenegraph.orgmailto:osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org



--
Serge Lages
http://www.tharsis-software.com
___
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 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 mailing list
osg-users@lists.openscenegraph.org

Re: [osg-users] [Not OSG related question] Virtual memory management on Windows

2008-06-26 Thread Serge Lages

Thanks a lot for your explanation Gordon, I ended to the same conclusion,
I'll need to go to a 64bits platform. I'll install an XP 64, and not a Linux
David... :)

Thanks again !

On Thu, Jun 26, 2008 at 12:30 AM, Gordon Tomlinson 
[EMAIL PROTECTED] wrote:

  Hi



 There's many issues why you will struggle with this and no it's not just a
 windows issues it effects other OS's some do a better job off moving the
 issues forward but they will still crop up



 Simplest solution is to go to a 64bit OS with a good 8gb or more.



 There is another limitation you will hit on 32bit windows is you can only
 have an address space per process of 1.8gb , other OS's such as Unix's and
 Linux's do a much better job and get you near the true 32bit limit



 Another problem is that you need a contiguous memory area for malloc/new on
 windows  this is a  big problem ,



 Some of the reasons why this is an issue is that Windows has already eaten
 up a chunk of the available memory, not only with programs , services ,
 dll's being loaded they sadly  simply  don't get then next serial  memory
 address, they may be load smack bang in the middle of the address space, so
 straight away that can l half the size of the max malloc/new you can do. As
 you load more programs more dll's the longer windows is running the more
 fragmented the memory will get and the smaller the max malloc/new can create
 will get lower, the MAC's OS's are the best at handling this sort of thing
 and Linux is typically better than window's



 What you can try is all the normal traditional tips, only run [processes,
 services that absolutely need to  etc see
 http://www.vis-sim.com/vega/vegafaq1.htm#f39 ( needs modernizing but the
 gist is valid)



 This use be a big problem back in the heyday of IRIX, it would load is
  system SO's(dll's)  smack bang in the middle of memory the same for
 programs. What had to be do there was to force the system to load its libs
 either high or low and you has to rebase the loading address of all the SO's
 your program used.



 You can do a similar thing in Windows and for all your dll's to re-base and
 control were they load. If you do that the final  trick is that as some as
 your application starts you need to create the large memory stuff straight
 away, otherwise your address space will get fragmented and your back to
 square one



 At my company we have to handle multi-terra byte imagery and have to use
 processes like I have described, so it can be done. you just need an
 engineer that knows this hard stuff, thankfully  we have an engineer that
 does ;) and no you cannot have him ;)







 __
 *Gordon Tomlinson *

 Email   : [EMAIL PROTECTED]
 YIM/AIM : *gordon3dBrit*
 MSN IM  : [EMAIL PROTECTED]
 Website : *www.vis-sim.com www.gordontomlinson.com*

 __



 *From:* [EMAIL PROTECTED] [mailto:
 [EMAIL PROTECTED] *On Behalf Of *David Callu
 *Sent:* Wednesday, June 25, 2008 3:05 PM
 *To:* OpenSceneGraph Users
 *Subject:* Re: [osg-users] [Not OSG related question] Virtual memory
 management on Windows



 power linux Serge ;-).

 Regards
 David Callu

 2008/6/25 Serge Lages [EMAIL PROTECTED]:

 Hi all,

 I have a question not related to OSG but I can't find any answer, and this
 is something that some of you probably knows. That's why I try here to find
 some help.

 Here is my problem : I have a big image database with some images larger
 than 1.5Go uncompressed, and I fail to load them (Win XP SP2 32bits with
 Visual Studio 8). My computer has 3Go of virtual memory and the option /3GB
 is activated on the system. In this document (page 13) :

 http://actes.sstic.org/SSTIC05/Vulnerabilites_et_gestion_des_limites_memoire/SSTIC05-article-Delalleau-Vulnerabilites_et_gestion_des_limites_memoire.pdf
 It says it's not possible to allocate more than 1.3Go in one call, and it's
 actually the limit where it crashs. If I do 2 allocations of 1Go each, it
 works, but 1 allocation of 1.4Go crashs...

 Has someone any idea if it's possible to change this limit ? My only hope
 will be to make smaller images, or even to develop under Linux ? :)
 Thanks in advance !

 --
 Serge Lages
 http://www.tharsis-software.com
 ___
 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




-- 
Serge Lages
http://www.tharsis-software.com
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Particles being culled

2008-06-26 Thread CG

Hi Charles,
 
I've tried the setParticleAlignment and it didn't work.Regards,
Cg



 Date: Wed, 25 Jun 2008 23:28:53 -0600 From: [EMAIL PROTECTED] To: 
 osg-users@lists.openscenegraph.org Subject: Re: [osg-users] Particles being 
 culled  try: 
 ps-setParticleAlignment(osgParticle::ParticleSystem::BILLBOARD);   On 
 Wed, Jun 25, 2008 at 11:23 PM, CG [EMAIL PROTECTED] wrote:  Hi Charles, 
   Thanks for the reply, what are the settings for the eye point facing? 
   Regards,  Cg     Date: Wed, 25 
 Jun 2008 23:18:07 -0600  From: [EMAIL PROTECTED]  To: 
 osg-users@lists.openscenegraph.org  Subject: Re: [osg-users] Particles 
 being culled   I think the default for particle systems is that 
 particles are little  billboards which always face the viewer's eye point. 
 It looks like  you've undone that setting somehow, and that the billboards 
 are facing  different directions.   On Wed, Jun 25, 2008 at 11:07 
 PM, CG [EMAIL PROTECTED] wrote:   Hi all, I'm trying to 
 simulate a smoke trail
  emitting from a moving tank by   using   Joseph's codes but some 
particles are being culled (see attached   picture).   Any ideas what 
are the causes? Thanks, Cg 
   Make the most of what you can do on your 
PC and the Web, just the way   you   want. Windows Live   
___   osg-users mailing list 
  osg-users@lists.openscenegraph.org 
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org  
   --  AsymptopiaSoftware | [EMAIL PROTECTED]  
www.asymptopia.org  ___  
osg-users mailing list  osg-users@lists.openscenegraph.org  
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org  
    Share your beautiful moments with 
Photo Gallery. Windows Live Photo Gallery  ___
   osg-users mailing list  
osg-users@lists.openscenegraph.org  
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org  
--  AsymptopiaSoftware | [EMAIL PROTECTED] www.asymptopia.org 
___ osg-users mailing list 
osg-users@lists.openscenegraph.org 
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
_
Check out Barclays Premier League exclusive video clips here!
http://fc.sg.msn.com/index.aspx___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] CMake build on OSX

2008-06-26 Thread Robert Osfield

Hi Guys,

We'll need to add a version check into the CMake build so that under
OSX you need 2.6 or later.  Once I've done my trawl through the
email/support backlog I'll look at this.  Others are welcome to dive
in and implement it before I get to it ;-)

Robert.

On Tue, Jun 24, 2008 at 2:31 PM, Stephan Maximilian Huber
[EMAIL PROTECTED] wrote:
 Hi Gerrick,

 Gerrick Bivins schrieb:

 I updated my osg build area to the latest and greatest and found that
 turning on applications and examples flags
 causes CMake to error out on Mac OSX 10.5.3. Turning these off allows for
 a
 successful compile/install. Is anyone else
 seeing this?

 What version of cmake are you using? Try updating cmake to 2.6, I had
 similar problems with cmake 2.4


 cheers,
 Stephan
 ___
 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] [osg-submissions] API configurations in aseparateConfig include file

2008-06-26 Thread J.P. Delport

Hi,

I was (thankfully) sleeping over some possibly nasty response last night
to the earlier discussions, but was pleasantly surprised with all the
messages this morning.

Bob, thanks for your honesty.

The force strong with this community is ;)

Bob Kuehne wrote:

osg-users,

what fun would this list be if someone (lucky me) didn't get to stick their
foot in their mouth from time to time. :)

don't get me wrong:

i think osg is by _far_ the best designed and implemented scenegraph out
there. and robert does the best job at balancing an admittedly difficult
task - incorporating changes from users, his own ideas and designs, and
criticism from all fronts (mine included). i use osg for 100% of the
projects i do work on and would have it no other way.

having been involved with osg since it's inception, i'm both very satisfied
and very critical of it, out of concern that it continues to evolve in
a way that takes care of it's users yet adapts to the ever-changing
graphics landscape. and i do try to contribute to make it better in little
ways here and there.

and so, as an act of contrition (yes, i was raised a catholic child),
i submit my updated 'FindOSG.cmake' which i use to create builds of apps
with osg on windows, linux, and the mac. this cmake FIND_PACKAGE tool will
setup the variable OSG_INCLUDE_DIRS to point to both the generated and
installed source of osg, as well as the OSG_LIBRARY_DIR for the discovered
osg libraries.

i'll post an entire standalone example to submissions later, because i
think having a way for users to build a standalone app would be a useful
addition, especially with the changing build landscape.

sheepishly, (not a scotland joke)
bob

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

--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.

This message has been scanned for viruses and dangerous content by MailScanner,
and is believed to be clean. MailScanner thanks Transtec Computers for their support.

1 2 >

1 - 100 of 145 matches

Mail list logo