On 31 Jul 2011, at 09:59, ThorstenB wrote:
> a new OSG stable release is available. Changes only involves a list of
> fixes since OSG 3.0.0. Do we have a chance to update jenkins to use OSG
> 3.0.1 for the windows installers (already using 3.0.0 right now)? Seems
> a good idea to include those
Hi,
a new OSG stable release is available. Changes only involves a list of
fixes since OSG 3.0.0. Do we have a chance to update jenkins to use OSG
3.0.1 for the windows installers (already using 3.0.0 right now)? Seems
a good idea to include those OSG patches in our release(-candidates).
cheer
Thanks for the info.
Chris
On Wed, 2010-07-21 at 14:47 +0100, James Turner wrote:
> On 21 Jul 2010, at 14:01, Chris Baines wrote:
>
> > Can I just ask what version of OpenSceneGraph is required to compile and
> > run Flightgear/Simgear (v2.0.0). The release page suggests that any
> > version wil
Hi Chris and James.
I use 2.9.8 with GIT version of SG/FG together and it is fairly stable,
sometimes a random crash while playing (mostly caused by "accident"
Traffic-Manager code or sometimes at exit.
So I have non-stable here?
Roland
signature.asc
Description: This is a digitally signed me
On 21 Jul 2010, at 14:01, Chris Baines wrote:
> Can I just ask what version of OpenSceneGraph is required to compile and
> run Flightgear/Simgear (v2.0.0). The release page suggests that any
> version will do however newer versions >=2.9.6 will run better but is
> this the case? Will the latest s
Hello,
Can I just ask what version of OpenSceneGraph is required to compile and
run Flightgear/Simgear (v2.0.0). The release page suggests that any
version will do however newer versions >=2.9.6 will run better but is
this the case? Will the latest stable release of OpenSceneGraph (2.8.3)
do?
Tha
On lundi 08 décembre 2008, Martin Spott wrote:
> "Fabian Grodek" wrote:
> > Is there any location other than
> > http://www.openscenegraph.org/projects/osg/wiki/Downloads
> >
> > to get the OpenSceneGraph libraries? The link above is not working.
>
> As a last resort you might try:
>
> ftp://ftp.
On 12/8/08, Martin Spott <[EMAIL PROTECTED]> wrote:
>
> "Fabian Grodek" wrote:
>
> > Is there any location other than
> > http://www.openscenegraph.org/projects/osg/wiki/Downloads
> >
> > to get the OpenSceneGraph libraries? The link above is not working.
>
> As a last resort you might try:
>
> ftp
"Fabian Grodek" wrote:
> Is there any location other than
> http://www.openscenegraph.org/projects/osg/wiki/Downloads
>
> to get the OpenSceneGraph libraries? The link above is not working.
As a last resort you might try:
ftp://ftp.ihg.uni-duisburg.de/FlightGear/OSG/
to get a source tr
On lundi 08 décembre 2008, Fabian Grodek wrote:
> Hello,
> Is there any location other than
> http://www.openscenegraph.org/projects/osg/wiki/Downloads
>
> to get the OpenSceneGraph libraries? The link above is not working.
> Thank you.
> Fabian
Your link is right, it does not answer :(
--
Gér
Hello,
Is there any location other than
http://www.openscenegraph.org/projects/osg/wiki/Downloads
to get the OpenSceneGraph libraries? The link above is not working.
Thank you.
Fabian
--
SF.Net email is Sponsored by MIX09,
Hello,
http://www.openscenegraph.org/downloads/developer_releases/OpenSceneGraph-2.2.0.zip
--
Gérard
http://perso.orange.fr/GRTux/
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find
Holger Wirtz wrote:
> I don't understand why there is this problem... is this a bug in the
> fglrx_dri.so? Why does fgfs worked until this problem occurs a month ago?
>
> I tried to use the ATI drivers from www.ati.com, but they have no DRI
> driver for Radeon X1400 Chips :-(
fglrx *is* the dri
Hi,
On Wed, Jul 11, 2007 at 02:55:44PM +0200, Csaba Halász wrote:
> On 7/11/07, John Denker <[EMAIL PROTECTED]> wrote:
> > On 07/10/2007 01:40 PM, Csaba Halász wrote:
> >
> > > Maybe try the sed hack with a shorter prefix, such as replacing
> > > _ZNSt6vector with _ZNSt6vectorX. Note that it is a
On 7/11/07, John Denker <[EMAIL PROTECTED]> wrote:
> On 07/10/2007 01:40 PM, Csaba Halász wrote:
>
> > Maybe try the sed hack with a shorter prefix, such as replacing
> > _ZNSt6vector with _ZNSt6vectorX. Note that it is a pretty brutal thing
> > to do for the whole binary, and might break it in a m
On 07/10/2007 01:40 PM, Csaba Halász wrote:
> Maybe try the sed hack with a shorter prefix, such as replacing
> _ZNSt6vector with _ZNSt6vectorX. Note that it is a pretty brutal thing
> to do for the whole binary, and might break it in a million ways.
1) It's more likely to work if the replacement
Hi Csaba,
On Tue, Jul 10, 2007 at 07:40:46PM +0200, Csaba Halász wrote:
> Hi Holger!
>
> Maybe try the sed hack with a shorter prefix, such as replacing
> _ZNSt6vector with _ZNSt6vectorX. Note that it is a pretty brutal thing
> to do for the whole binary, and might break it in a million ways. Or,
Hi Holger!
Maybe try the sed hack with a shorter prefix, such as replacing
_ZNSt6vector with _ZNSt6vectorX. Note that it is a pretty brutal thing
to do for the whole binary, and might break it in a million ways. Or,
set LD_DEBUG=bindings and LD_OUTPUT as appropriate. Then run fg, and
try to find s
Hi,
On Tue, Jul 10, 2007 at 01:58:36AM +0200, Csaba Halász wrote:
> On 7/9/07, Holger Wirtz <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > sorry for reanimating this thread, but since a week I have the old
> > problem regardless using the "sed"-hack to
> > /usr/lib/dri/fglrx_dri.so. :-(
> >
> > Does a
On 7/9/07, Holger Wirtz <[EMAIL PROTECTED]> wrote:
> Hi,
>
> sorry for reanimating this thread, but since a week I have the old
> problem regardless using the "sed"-hack to
> /usr/lib/dri/fglrx_dri.so. :-(
>
> Does anyone know what I can do or what is needed for debugging?
For a start, please prov
Hi,
sorry for reanimating this thread, but since a week I have the old
problem regardless using the "sed"-hack to
/usr/lib/dri/fglrx_dri.so. :-(
Does anyone know what I can do or what is needed for debugging?
Thanks, Holger
On Tue, Jun 19, 2007 at 11:22:30AM +0200, Holger Wirtz wrote:
> Hi all,
Hi all,
On Sun, Jun 17, 2007 at 07:37:41PM -0400, John Denker wrote:
[...]
> 2) Here is another way of achieving a similar result. This is more
> crude, but works better in batch files, i.e. doesn't require any
> skilled feedback. This works for 32- and 64-bit libraries.
>
> sed s/_ZNSt6vecto
There
On 06/17/2007 06:04 PM, Martin Spott wrote:
> You might want to give Pigeon a copy of your hacked driver for
> use with the FGLive CD,
We have discovered that there are multiple versions of
"the" driver. This means it is not easy to distribute
hacked copies or even to distribute a patch.
"Csaba Halász" wrote:
> Yesterday we seem to have successfully hacked the fglrx_dri.so. You
> can ask ndim or Jester (me) on irc for 32 bit and 64 bit patched
> versions respectively.
You might want to give Pigeon a copy of your hacked driver for
use with the FGLive CD,
Martin.
--
Unix
John Denker wrote:
> On 06/16/2007 05:25 PM, Martin Spott wrote:
> >
> > Ah, ok. Simply compile OSG from source and install just by "make
> > install" - this definitely works well, at least on Etch,
>
> How "definitely" is that?
I've been compiling OSG SVN on Etch for months now. In fact
On 6/17/07, John Denker <[EMAIL PROTECTED]> wrote:
>
> This is observed with recent (a few hours old) versions of
> osg-2.0, simgear, plib, and fg.
>
> This is observed with a variety of aircraft, including
> the default c172p, the c182r, and the pa24-250.
>
> First example (abort):
>
> #0 0xb74e7
On 06/17/2007 09:45 AM, I wrote:
> 100% of the CPU for 2.3 billion CPU clock cycles,
Correction: make that 140 billion CPU clock cycles.
(I left out a factor of 60 seconds/minute. Sorry.)
-
This SF.net email is sponsored
Ron Jensen wrote:
>> Thanks, but the problem is in OSG. I have been building and installing
>> debian packages. Its not the supported way to build, so when it quit
>> working I didn't complain.
On 06/16/2007 05:25 PM, Martin Spott wrote:
>
> Ah, ok. Simply compile OSG from source and install j
Ron Jensen wrote:
> On Sat, 2007-06-16 at 10:37 +, Martin Spott wrote:
> > This is everuthing I need to build FG with current OSG,
> >
>
> Thanks, but the problem is in OSG. I have been building and installing
> debian packages. Its not the supported way to build, so when it quit
> working
On Sat, 2007-06-16 at 10:37 +, Martin Spott wrote:
> Ron Jensen wrote:
>
> > I must agree. I haven't had a working flightgear for about a month
> > because OSG-SVN/head quit building for me.
>
> How does the error message look like ? I know, unfortunately I'm
> repeating myself, yet it mig
Nick Warne wrote:
> I have been building OSG over the last 3 months, and even updated today to
> rev. 7002 - everything builds/works great and I haven't had to touch a
> thing!?
Perhaps you've been building against old OSG headers. Few weeks ago
Robert Osfield has removed a header file that con
On Saturday 16 June 2007 11:37:35 Martin Spott wrote:
> Ron Jensen wrote:
> > I must agree. I haven't had a working flightgear for about a month
> > because OSG-SVN/head quit building for me.
>
> How does the error message look like ? I know, unfortunately I'm
> repeating myself, yet it might help
Ron Jensen wrote:
> I must agree. I haven't had a working flightgear for about a month
> because OSG-SVN/head quit building for me.
How does the error message look like ? I know, unfortunately I'm
repeating myself, yet it might help applying this patch to FlightGear:
--- FlightGear/src/Main/f
"Curtis Olson" wrote:
> Our approach with plib is that if we absolutely must depend on something in
> cvs, we push the plib folks hard to get that into an official release first,
> then we cut over and allow our code to depend on it. This is not without
> headaches, but it's worked pretty well fo
Jonathan Wagner wrote:
> Just a thought for the rest of the list. Now that OpenSceneGraph-2.0
> has been released, what are the thoughts on setting that as a "fixed"
> dependency for now (i.e., future development should work on
> OpenSceneGraph-2.0).
While we are at it, somebody could now add
On Fri, 2007-06-15 at 19:33 -0500, Curtis Olson wrote:
> On 6/15/07, Jonathan Wagner wrote:
> Just a thought for the rest of the list. Now that
> OpenSceneGraph-2.0
> has been released, what are the thoughts on setting that as a
> "fixed"
> dependency for no
On 6/15/07, Jonathan Wagner wrote:
Just a thought for the rest of the list. Now that OpenSceneGraph-2.0
has been released, what are the thoughts on setting that as a "fixed"
dependency for now (i.e., future development should work on
OpenSceneGraph-2.0). With one of the latest patches to the p
Just a thought for the rest of the list. Now that OpenSceneGraph-2.0
has been released, what are the thoughts on setting that as a "fixed"
dependency for now (i.e., future development should work on
OpenSceneGraph-2.0). With one of the latest patches to the plib branch
in CVS, FlightGear stil
Stuart Buchanan schrieb:
> --- Mathias Fröhlich wrote:
>> Hi,
>>
>> I need to have an other update to the openscenegraph tarball. For those
>> ones
>> not tracking cvs I have put together a tarball as usual. The key feature
>> I
>> need is the txf file font loader. That is with the time of packin
--- Mathias Fröhlich wrote:
>
> Hi,
>
> I need to have an other update to the openscenegraph tarball. For those
> ones
> not tracking cvs I have put together a tarball as usual. The key feature
> I
> need is the txf file font loader. That is with the time of packing that
> tarball included in
Hi,
I need to have an other update to the openscenegraph tarball. For those ones
not tracking cvs I have put together a tarball as usual. The key feature I
need is the txf file font loader. That is with the time of packing that
tarball included in osg's cvs and the tarball includes in fact a s
Martin Spott schrieb:
> Matthias Boerner wrote:
>
>
>> With the options
>>
>> --timeofday=noon --prop:/sim/rendering/fps-display=true --bpp=32
>>
>> both versions show almost the same rate of fps with a small advantage to OSG
>> about 1 to 10 percent.
>>
>
> Ah, I guess nobody tried runni
Matthias Boerner wrote:
> With the options
>
> --timeofday=noon --prop:/sim/rendering/fps-display=true --bpp=32
>
> both versions show almost the same rate of fps with a small advantage to OSG
> about 1 to 10 percent.
Ah, I guess nobody tried running at higher display depths, anybody ?
Hi,
I got everything compiled and did a short "performance test" compared
between the CVS-Version of FlightGear with PLIB of 26th, October and
yesterdays OSG release:
With the options
--timeofday=noon --prop:/sim/rendering/fps-display=true --bpp=32
both versions show almost the same rate of
Hi,
>> But there is one problem with the running flightgear than: it's about a
>> factor 2 slower than the flightgear with plib (and shadows on)!
>> I don't know if this can be improved with other compiler flags, but I am
>> a little bit surprised.
>>
>>
I moved the pre-osg branch to the sa
Maik Justus schrieb:
> Hi Olaf,
>
> I have used your project files / precompiled libs to compile fg with osg
> from the scratch. It worked with only negligible problems.
> A file simgear_config.h is missing; there is a simgear_config.h.vc5,
> after renaiming to *.h it works.
> 2 files had to be a
Vassilii Khachaturov wrote:
> Also, where does one take the files missing for the examples (e.g., the
> cow.osg, or the lz.osg mentioned in the runexamples.bat)?
Here for example:
http://www.openscenegraph.org/osgwiki/pmwiki.php/Downloads/SampleDataset
Martin.
--
Unix _IS_ user friendly - i
I was able to build the OSG from the OSG_OP_OT-1.2-Flightgear.tar.gz
on a Debian etch system (gcc Debian 4.1.1-13 -based), but not on a sarge
one (Debian 1:3.3.5-13 -based).
Tried osg cvs head (copied over the ac3d and rgb plugin directories
manually from the .tar.gz above), and had the same probl
Hi,
On Wednesday 01 November 2006 00:43, Georg Vollnhals wrote:
> I hope you did understand me right, all that feedback is not mentioned
> as "it is broken, please fix it" but just to inform you about what works
> on my O/S/PC hardware and what does not. If these feedbacks would come
That comment
Maik Justus schrieb:
>
> The missing blades are probably not due to the osg update. I think your
> data and your flightgear source are not from the same date. Please
> update both from cvs and then it should work.
>
> Maik
>
>
Thank you Maik!
Did not test the BO105 again after my data-update y
Georg Vollnhals schrieb:
Hi Mathias:
1. Further investigations, new insights regarding the "FG-OSG black
screen problem"
- must be a terrain/ground problem, the a/c is located under the
surface when one selects special airports.
- found it out by using the UFO, it is located under the surface bu
Hi,
Georg Vollnhals schrieb:
> Hi Mathias,
>
> http://home.arcor.de/vollnhals-bremen/OSGErr/fgfs-screen-0154.jpg [bo105:
> missing blades]
>
> Regards
> Georg
>
The missing blades are probably not due to the osg update. I think your
data and your flightgear source are not from the same dat
Hi Mathias,
Mathias Fröhlich schrieb:
> Yes, with the current implementation I expect more z buffer problems. That
> will change in the long term.
>
>
I hope you did understand me right, all that feedback is not mentioned
as "it is broken, please fix it" but just to inform you about what work
Hi Olaf,
I have used your project files / precompiled libs to compile fg with osg
from the scratch. It worked with only negligible problems.
A file simgear_config.h is missing; there is a simgear_config.h.vc5,
after renaiming to *.h it works.
2 files had to be added to the simgear project file:
Mathias,
Martin Spott wrote:
> 2.) Is the stuff in SimGear/simgear/scene/util/ still needed ?
Thanks for the solution !
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--
-
Hi,
A first try for a new build system including OSG for MSVC8 is at
http://www.oflebbe.de/oflebbe/FlightGear. I was able to compile and run
sucessfully a FlightGear executable from it.
Greetings
Olaf
-
Using Tomcat but n
Hi Georg,
On Tuesday 31 October 2006 00:10, Georg Vollnhals wrote:
> 3.2 At first sight all seems to display well except two cockpit display
> errors (Z-buffer problem???) and one outside view transparency error
Yes, with the current implementation I expect more z buffer problems. That
will chan
Mathias Fröhlich schrieb:
My feedback:
1. with your FlightGear OSG patch all compiled well (compiled the
original OSG before and got "data" errors when running FG)
2. System: OpenSuse 10.1 x86_64, Nvidia hardware accelerated driver,
AMD64 3700, 1GB RAM, Nvidia 6600GT 256 MB
3. FlightGear OSG
Mathias Fr?hlich wrote:
> On Monday 30 October 2006 12:56, Martin Spott wrote:
> > Would you consider separating the respective patches so people can
> > apply them to their home grown build tree ?
> Done.
I see, the one-liner against 'LightModel.cpp' is already in CVS.
Thanks,
Martin.
-
Hi all,
little message from Olaf. He does not have time to write. But I know that the
MSVC win32 build dependencies for osg are already available at his web page.
http://www.oflebbe.de/oflebbe/FlightGear/3rdparty.zip
The latest project files from last week will appear soon in cvs.
Hmm, I belie
On Monday 30 October 2006 18:37, Martin Spott wrote:
> "Works for me" - please apply to the repository.
> To be honest, this was simply copied from FlightGear ;-)
Sorry, that is because I have thought it is already in ...
I did for fg but not for simgear.
Greetings
Mathias
-
On Monday 30 October 2006 12:56, Martin Spott wrote:
> Mathias Fr?hlich wrote:
> > You can find that tarball at
> >
> > ftp://ftp.uni-duisburg.de/FlightGear/Misc_maf/OpenSceneGraph-20061029/OSG
> >_OP_OT-1.2-Flightgear.tar.gz
> >
> > I am working on getting the two patches upstream ...
>
> Would yo
Selon Martin Spott :
> cc-1018 CC: ERROR File = /opt/OSG/include/osg/BufferObject, Line = 175
> An unmatched left parentheses "(" appears in an expression.
>
> typedef void (APIENTRY * BufferDataProc) (GLenum target,
> GLsizeiptrARB size, const GLvoid *data, GLenum usage);
> [... a
Mathias Fr?hlich wrote:
> ... is now in.
Hi, does anyone have a proposal on how to deal with this one ?
Unfortunately this is beyond my scope as I'm unable to identify any
fault:
make[2]: Entering directory `/usr/local/src/FlightGear/src/ATC'
[...]
CC -DHAVE_CONFIG_H -I. -I. -I../../src/Include
Martin Spott wrote:
> Would this be the right way to do it in SimGear ?
> --- configure.ac~ Sun Oct 29 22:08:46 2006
> +++ configure.acMon Oct 30 18:21:07 2006
> @@ -119,6 +119,14 @@
> EXTRA_DIRS="${EXTRA_DIRS} $with_plib"
> fi
>
> +# specify the osg location
> +AC_ARG_WITH(
Hmmm, maybe its CPPFLAGS="-I/opt/OSG/include" ./configure (it's been a while and I'm going from memory here.)There once was a way to add to "EXTRA_DIRS" from the command line, but that apparently was lost along the way at some point.
Curt.On 10/30/06, Martin Spott <[EMAIL PROTECTED]> wrote:
"Curti
Martin Spott wrote:
> Would be nice - and consistent to the way it's done in FlightGear with
> PLIB, SimGear and OpenAL,
Would this be the right way to do it in SimGear ?
--- configure.ac~ Sun Oct 29 22:08:46 2006
+++ configure.acMon Oct 30 18:21:07 2006
@@ -119,6 +119,14 @@
E
"Curtis Olson" wrote:
> Quick way to do this is to add it to CFLAGS and CXXFLAGS (I think) ...
>
> CXXFLAGS="-I/opt/OSG/include" ./configure
I must admit that I already did that before asking around - but
surprisingly it didn't have the expected result.
> There's probably a way to make this hap
Quick way to do this is to add it to CFLAGS and CXXFLAGS (I think) ...CXXFLAGS="-I/opt/OSG/include" ./configureThere's probably a way to make this happen directly with configure options too.
Curt.On 10/30/06, Martin Spott <[EMAIL PROTECTED]> wrote:
Hi Mathias,Mathias Fr?hlich wrote:> ... is now in.
Hi Mathias,
Mathias Fr?hlich wrote:
> ... is now in.
Two comments, please:
1.) There are certain places in SimGear that require including
. Would you consider adding a 'configure' flag to
SimGear that allows pointing to the OSG installation ?
I have the OSG stuff in /opt/OSG/, so I
Hi,
Martin Spott wrote:
> Mathias Fr?hlich wrote:
>
>> You can find that tarball at
>>
>> ftp://ftp.uni-duisburg.de/FlightGear/Misc_maf/OpenSceneGraph-20061029/OSG_OP_OT-1.2-Flightgear.tar.gz
>>
>> I am working on getting the two patches upstream ...
>
> Would you consider separating the respect
Mathias Fr?hlich wrote:
> You can find that tarball at
>
> ftp://ftp.uni-duisburg.de/FlightGear/Misc_maf/OpenSceneGraph-20061029/OSG_OP_OT-1.2-Flightgear.tar.gz
>
> I am working on getting the two patches upstream ...
Would you consider separating the respective patches so people can
apply them
On Sunday 29 October 2006 22:24, Stuart Buchanan wrote:
> Hi Mathias,
>
> I tried compiling your OSG tarball on cygwin, but hit an error:
>
> c++ -O2 -DWIN32 -DNOMINMAX -W -Wall -mnop-fun-dllimport
> -I../../../../include -
> I/usr/local/OpenThreads/include -I/usr/local/Producer/include -c
> ../E
On Sunday 29 October 2006 21:42, Frederic Bouvier wrote:
> Selon Mathias Fröhlich :
> > For the Flightgear part, I will past that sent mail create the
> >
> > PRE_OSG_PLIB_20061029
> >
> > branch.
>
> We should branch the data and maybe the doc repositories. At some point,
> the improvement brought
> > For the Flightgear part, I will past that sent mail create the
> >
> > PRE_OSG_PLIB_20061029
> >
> > branch.
>
> We should branch the data and maybe the doc repositories. At some point, the
> improvement brought by OSG will show up in data files too.
>
Agreed. An extra label on a file never hu
--- Mathias Fröhlich wrote:
>
> ... is now in.
Hi Mathias,
I tried compiling your OSG tarball on cygwin, but hit an error:
c++ -O2 -DWIN32 -DNOMINMAX -W -Wall -mnop-fun-dllimport
-I../../../../include -
I/usr/local/OpenThreads/include -I/usr/local/Producer/include -c
../ESRIShape.c
pp
../ESR
Selon Mathias Fröhlich :
> For the Flightgear part, I will past that sent mail create the
>
> PRE_OSG_PLIB_20061029
>
> branch.
We should branch the data and maybe the doc repositories. At some point, the
improvement brought by OSG will show up in data files too.
-Fred
--
Frédéric Bouvier
http:
... is now in.
There are plenty if places where something is marked with an OSGFIXME
comment. At least these places need to be fixed at some time.
For everybody willing to help:
feel free to provide patches/fixes/improvements/cleanups.
I think that we should make use in the longer term of the P
Hi,
It took some time. And still not everything ready. But here the promised
checkin preparations.
As a first thing, you will need an updated OpenSceneGraph version that
containe 3 additional patches.
1. most important an updated ac3d loader - that is our most used one ...
2. a fix to the RGB
Vivian Meazza schrieb:
> Martin wrote
>
>
>> Subject: Re: [Flightgear-devel] OpenSceneGraph
>>
>> On Fri, Oct 27, 2006 at 09:52:25AM +0200, Martin Spott wrote:
>>
>>
>>> Building OSG on IRIX is really simple, just follow the rules, the same
&
Hi,
Mathias Fröhlich wrote:
> There is already preciptation code available in osg. So may be we have
> correct
> rain really fast. The lighting cannot be that hard ...
I just had a look at the precipitation demo and also the forrest demo
and they surely look impressive!
However, I wonder how t
On Fri, Oct 27, 2006 at 05:55:35PM +0100, Vivian Meazza wrote:
> Hmm, last time I looked OSG wasn't ported to Cygwin. Is it now, or do we
> have a potential problem here?
No idea, instructions are pretty old:
http://www.openscenegraph.org/osgwiki/pmwiki.php/PlatformSpecifics/Cygwin
Martin.
--
Martin wrote
> Subject: Re: [Flightgear-devel] OpenSceneGraph
>
> On Fri, Oct 27, 2006 at 09:52:25AM +0200, Martin Spott wrote:
>
> > Building OSG on IRIX is really simple, just follow the rules, the same
> > for Solaris. Yesterday I tried compiling from CVS on both pla
On Fri, Oct 27, 2006 at 09:52:25AM +0200, Martin Spott wrote:
> Building OSG on IRIX is really simple, just follow the rules, the same
> for Solaris. Yesterday I tried compiling from CVS on both platforms.
> FreeBSD will follow right now,
OSG CVS compiles and works great on FreeBSD-5.3 with Radeo
Hi,
On Fri, Oct 27, 2006 at 07:39:22AM +0200, Mathias Froehlich wrote:
> On Wednesday 25 October 2006 00:34, Stuart Buchanan wrote:
> > 2) How does this affect people running Windows. Do they have to install
> > OSG themselves, or does it get packaged up with the installer?
> I would recommend O
Vassilii,
On Thursday 26 October 2006 12:35, Vassilii Khachaturov wrote:
> > The 3d clouds are something to think about. osg can assist here but I
> > need to think about that.
>
> I'll be happy to try to help to port/switch these. Of the above, I don't
> quite find my way around the 3d clouds
Hi Vivian,
On Wednesday 25 October 2006 00:34, Vivian Meazza wrote:
> I see that you will be breaking the 3d clouds, at least temporarily, will
> you also be breaking the weather radar and the exhaust and chrome shaders?
Yep.
The shaders are expected to work in the near future. What is available
Hi,
On Wednesday 25 October 2006 00:34, Stuart Buchanan wrote:
> Sounds like a significant improvement. Presumably you haven't noticed any
> degradation in performance anywhere?
I have no specific test set that I compare - but what I compared is not
slower.
> Going on the assumption that this i
Hi,
On Wednesday 25 October 2006 00:55, Ampere K. Hardraade wrote:
> The current 3D clouds don't work on every machine, and I think its
> maintainer is gone as well. In my opinion, if 3D clouds is offered in OSG,
> then we should make use of it, because it probably is more robust and
> better te
Ok.
In summary I will create a branch this weekend in SimGears and FlightGears
CVS.
That branch will contain the old plib based code. Whoever needs to work on
that/stick with that - not recommended plib/ssg is deprecated now - can live
on that branch.
Past that branch I will push into CVS wha
Hi,
On Wednesday 25 October 2006 16:48, Frederic Bouvier wrote:
> I am eager to see it in CVS. It seems natural that the flow of innovation
> goes to HEAD and branches are used for freezing functionalities and doing
> maintenance release. Many big projects are doing like that, gcc for
> instance.
Great news! Thank you very much for the porting.
> The rain stuff as well as the render surface stuff is nothing too complicated
> and already available in osg, but that needs to be done and tested.
[SNIP]
> The 3d clouds are something to think about. osg can assist here but I need to
> think ab
Quoting Mathias Fröhlich:
>
> Hi,
>
> I had worked now for some time on an OSG port of flightgear.
...
> I would like to check that into our cvs.
> The usual way would be to create a cvs branch and do that work on that
> branch.
> In this case it would be good if we could avoid changes in the HEAD
On Tuesday 24 October 2006 17:44, Mathias Fröhlich wrote:
> Hi,
>
> I had worked now for some time on an OSG port of flightgear.
>
> At the moment many things are already working.
> - Scenery and 3d models are there.
> - Animations work mostly as expected.
> - The usual lights including the vasi ar
--- Mathias Fröhlich wrote:
> Hi,
>
> I had worked now for some time on an OSG port of flightgear.
>
> At the moment many things are already working.
> - Scenery and 3d models are there.
> - Animations work mostly as expected.
> - The usual lights including the vasi are there.
> - The 3d panel is
Mathias wrote:
>
> Hi,
>
> I had worked now for some time on an OSG port of flightgear.
>
> At the moment many things are already working.
> - Scenery and 3d models are there.
> - Animations work mostly as expected.
> - The usual lights including the vasi are there.
> - The 3d panel is displaye
awesome!
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mathias Fröhlich
Sent: Tuesday, October 24, 2006 3:45 PM
To: FlightGear discussions
Subject: [Flightgear-devel] OpenSceneGraph
Hi,
I had worked now for some time on an OSG port of flightgear
> Hi,
>
> I had worked now for some time on an OSG port of flightgear.
>
> At the moment many things are already working.
> - Scenery and 3d models are there.
> - Animations work mostly as expected.
> - The usual lights including the vasi are there.
> - The 3d panel is displayed and interactive.
>
Hi,
I had worked now for some time on an OSG port of flightgear.
At the moment many things are already working.
- Scenery and 3d models are there.
- Animations work mostly as expected.
- The usual lights including the vasi are there.
- The 3d panel is displayed and interactive.
- The sky looks a
99 matches
Mail list logo
