Hi,
On 28 Jan 2011, at 09:02, James Turner wrote:
Looks good to me, from a visual inspection. I'll apply over the
weekend, and poke some people to test. Depending on when 2.2.0 happens
this might even be worth back-porting, but we should wait for some
positive testing feedback before
2. if I do Reload input with the joystick already recognized, axes
goes wrong and I have to do a Reset to initialize them.
3. if I remove the joystick while the joystick information dialog is
displayed and reload input, fgfs segfault.
Don't see these problems under debian linux
- Csaba Halász a écrit :
On Sun, Jan 30, 2011 at 1:58 PM, Frederic Bouvier
wrote:
I noticed three things under Windows :
1. the state of menu entry Help Joystick information is not modified
when I remove or add a joystick after start
Confirmed, but unrelated to the patch
Class 1: fgfs and fgrun handle recursion of paths differently.
Anders, you are correct concerning the failure of fgrun to load both the Short
Empire and the ZLT-NT-copilot. These as well as the Jaguar fail to load in
fgrun because of differences in the way recursive paths are handled in
Wrong statement in the forum. TerraSync only updates the models,
not the terrain.
If this would be true, then you've identified a bug ;-)
This one might help:
http://hans.fugal.net/blog/2007/06/05/terrasync-prefetch/
Something equivalent (the prefetch) is implemented in fgrun
Le 21/01/2011 14:25, Alan Teeder a écrit :
Yes, that's true. For a reason I don't know, I missed that one.
For the moment, fg-aircraft is not used in the aircraft chooser.
-Fred
Thanks for the reply. At least I know that it is not another of my
stupidities. ;-)
It was only mine. It should
Hi All,
the next FG release is imminent now. It is time to check if the FGrun
translation for your language is OK and complete. Pay attention to overlapping
or truncated text as well as untranslated sentence. It is also possible to
submit new translations if your language use the latin
Yes, that's true. For a reason I don't know, I missed that one.
For the moment, fg-aircraft is not used in the aircraft chooser.
-Fred
- Alan Teeder a écrit :
Fgrun however does not seem to see any aircraft that are only in
the --fg-aircraft path.
--
Frédéric Bouvier
- Vadym Kukhtin a écrit :
It is also possible to submit new translations if your language use the latin
alphabet.
Is it 2011UTF8 now?
Not yet. I am migrating slowly to fltk 1.3 that has utf8, but no release :(
That's why the latin alphabet is mandatory for the moment
-Fred
--
Is it 2011UTF8 now?
BTW, I don't know what 2011 relates to, except the current year ;-)
-Fred
--
Frédéric Bouvier
http://www.youtube.com/user/fgfred64 Videos
--
Special Offer-- Download ArcSight Logger for FREE
c) Doesn't 213 seem like a small number compared to the thousands of
updates that have been applied to Robin's apt.dat since FG forked
it in 2008?
If you are looking for a project, we need someone to incorporate the
new X-Plane format into TerraGear - while keeping polygon counts as
low
I confirm that setting environment variables doesn't work anymore on Windows
-Fred
- Michael Sgier scrat_h...@yahoo.com a écrit :
yes but the:
On the new window, titled Advanced Options highlight the Environment from
the list on the left
---
etc doesn't work anymore? At
Hi Dave,
- dave perry a écrit :
On 01/06/2011 03:01 AM, Jari Häkkinen wrote:
find / -name version.h | grep simgear
I had already looked at config.log. The check was against
simgear/version.h. But since --prefix=$FG_ROOT, the config checks
Why are you using $FG_ROOT to install your
- James Turner a écrit :
On 14 Dec 2010, at 11:51, henri orange wrote:
II do not notice any similar error with, others fdm (yasim, uiuc
) though i did not tried all of these ~400 models
Is it just me ? is it specific to some jsbsim Aircraft ? is it
specific to jsbsim ?
You can post a comment in the tracker
Link? The only bug tracker I know of
(http://code.google.com/p/flightgear-bugs/) stops at #187.
The link was in my original post. It's the fgrun tracker
Regards,
-Fred
--
By the way, look what I received in my inbox :
Support Requests item #3117965, was opened at 2010-11-24 20:24
Message generated for change (Tracker Item Submitted) made by gwself
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=510694aid=3117965group_id=65363
By the way, look what I received in my inbox :
Support Requests item #3117965, was opened at 2010-11-24 20:24
Message generated for change (Tracker Item Submitted) made by gwself
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=510694aid=3117965group_id=65363
Take a screenshot with one of the system tools. I want to know which
traversal -- update, cull, draw, or gpu -- appears to be slower.
http://frbouvi.free.fr/flightsim/fgfs-20101108-KSFO-28R.png : from a nightly
build
http://frbouvi.free.fr/flightsim/fgfs-20101127-KSFO-28R.png : compiled
- Gene Buckle ge...@deltasoft.com a écrit :
On Sat, 27 Nov 2010, Frederic Bouvier wrote:
By the way, look what I received in my inbox :
Support Requests item #3117965, was opened at 2010-11-24 20:24
[snip]
Initial Comment:
The proflightsimulator launch control does not launch
- Martin Spott a écrit :
J. Holden wrote:
There is no land cover layer for waterfalls.
which doesn't mean that such thing can't be introduced ;-)
Typically this requires someone to create a suitable texture, the
rest is just admin stuff.
and a particle system ;-)
-Fred
--
I have 15 FPS here with a GeForce 9500 GT (MSI) and a quad-core.
How
can I change that draw distance? It is really far. :(
The visibility shouldn't have changed with this update - except that
the visibility selected at start-up is immediately effective now.
You can set a fixed
Hi Gene,
- Gene Buckle a écrit :
Ah, sorry to disappoint, but you have to commit to Git first - unlike
some setups, we haven't engineered a 'compile before publish' system.
Hence my ensuring I have time to watch Hudson *after* a commit, and, for
example, make a fix commit if I
...
6) Click Input/Output (it shows
--generic=socket,out,10,localhost,16661, udp,fgcom, which is
io-item-1 in the settings file)
7) Click on --generic=socket,out,10,localhost,16661, udp,fgcom
8) BOOM, Segmentation fault (core dumped). There is no time to click
Delete or OK, it just
- Gene Buckle a écrit :
On Fri, 12 Nov 2010, Curtis Olson wrote:
Are you able to test local changes? What would happen if you
changed line
#203 of simgear/io/raw_socket.cxx to:
setsockopt( handle, SOL_SOCKET, SO_REUSEADDR,
(void *)opt_boolean,
Thanks Fred! We're back to a green board. :D
Would you mind restarting a linux build, just in case ?
-Fred
--
Frédéric Bouvier
http://my.fotolia.com/frfoto/ Photo gallery - album photo
http://www.youtube.com/user/fgfred64 Videos
Op 10-11-10 09:57, Frederic Bouvier schreef:
Thanks,
could you zip (or tar.gz ;-) ) and a attach the file instead ?
Certainly.
Thank you, I will look at it tonight
-Fred
--
Frédéric Bouvier
http://my.fotolia.com/frfoto/ Photo gallery - album photo
http://www.youtube.com
- Deborah Tay a écrit :
Hey guys!
Many thanks to Fred :D I found out what was wrong with my first build, the
version.h file wasn't saved correctly, now I've got it! (:
As I was saying I wasn't sure what this step meant:
15. Add any_directory_on_any_drive /install/ msvc90 /
Hi m.
could you be more specific on the sequence of actions that lead to this problem
?
Regards,
-Fred
- fiers...@zonnet.nl a écrit :
Hi
In the fgrun of this moring, I can reproduce a segmentation fault. Has anyone
else noticed?
In my settings file, there is a parameter for
Hi Deborah,
- Deborah Tay tay.debo...@gmail.com a écrit :
Hey guys!
I've tried following the steps in
http://gitorious.org/fg/flightgear/blobs/next/docs-mini/README.MSVC#line89 as
suggested by Fred, and got this after my build
== Build: 11 succeeded, 1 failed, 0
The artifacts of the fgrun build are fgrun.exe and the locale
directory
It looks like there are also some dependencies missing. FlightGear-next-Win64
and FGRun-Win32 are not rebuilt when simgear is updated.
Regards,
-Fred
--
Frédéric Bouvier
http://my.fotolia.com/frfoto/ Photo
Hi James,
- James Turner a écrit :
On 7 Nov 2010, at 10:09, Frederic Bouvier wrote:
It looks like there are also some dependencies missing.
FlightGear-next-Win64 and FGRun-Win32 are not rebuilt when simgear is
updated.
Yes, good catch Fred. This was because Gene/I tend to leave out
- Gene Buckle a écrit :
Fred, is there any advantage to using VS2010 to build the Windows
binaries with over the VS2008 compiler? I don't follow the C++ side of the
house so I don't know of any compiler improvements that FG would benefit
from.
I'd stick to VS2008 until the next fg
Le 06/11/2010 05:31, Gene Buckle a écrit :
On Fri, 5 Nov 2010, Frederic Bouvier wrote:
Google is your friend :
http://connect.microsoft.com/VisualStudio/feedback/details/324846/the-resolvevcprojectoutput-task-failed-unexpectedly-when-building-projects-in-parallel-msbuild
Try the command
Le 06/11/2010 10:52, James Turner a écrit :
On 6 Nov 2010, at 09:27, Frederic Bouvier wrote:
The x64 build is now available from the build server and I changed what it
made available to include all the .exe files. I updated the win32 build
to include all the .exes as well.
Did you
Le 06/11/2010 11:03, Frederic Bouvier a écrit :
BTW: I will update the 3rd party archive in the next days, maybe
including gettext
I updated the 3rdparty archives :
ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/fgfs-win32-VS90-3rdParty+OSG-20101106.zip
ftp://ftp.ihg.uni-duisburg.de
- Gene Buckle a écrit :
It's exploding on the Portugese translation.
Build started 11/6/2010 8:21:23 AM.
1Project D:\FGFSHudson\FGRun\msvc\9.0\fgrun.sln on node 0
(default
targets).
Building solution configuration Release|Win32.
1Project : error PRJ0019: A
- James Turner zakal...@mac.com a écrit :
On 6 Nov 2010, at 16:22, Frederic Bouvier wrote:
Now that I updated the vs2008 projects, all win32/x64 build should
fail until you update the 3rdparties. Then the msgfmt tool used to
compile the portugese translation (and others
Hi Gene,
- Gene Buckle ge...@deltasoft.com a écrit :
I've gotten the SimGear build working for the x64 target, but
FlightGear
is still giving me problems:
D:\FGFSHudson\FlightGear\projects\VC90msbuild FlightGear.sln
/p:Configuration=Release /p:Platform=x64 /m
Microsoft (R)
Hi Gene,
- Gene Buckle ge...@deltasoft.com a écrit :
I've gotten the SimGear build working for the x64 target, but
FlightGear
is still giving me problems:
D:\FGFSHudson\FlightGear\projects\VC90msbuild FlightGear.sln
/p:Configuration=Release /p:Platform=x64 /m
- fiers...@zonnet.nl a écrit :
I am assuming a faster graphics card would solve this for me. Right?
Sure
Op 31-10-10 17:14, Frederic Bouvier schreef:
I'll make it switchable with the quality level then. But not before
next week.
Done in Git. The improved effect is available
I'll make it switchable with the quality level then. But not before next week.
-Fred
- Message d'origine -
De: fiers...@zonnet.nl
Env: dimanche 31 octobre 2010 14:46
À: flightgear-devel@lists.sourceforge.net
Objet: Re: [Flightgear-devel] Am I the only one experiencingdropping
- Frederic Bouvier a écrit :
I am tracking a crash when selecting the c172p. Not sure it is related
to the other crash already seen, but anyway :
In JSBSim.cxx, line 147 :
fdmex = new FGFDMExec( (FGPropertyManager*)globals-get_props() );
in FGFDMExec.cpp, line 99
Hi James,
- James Turner a écrit :
On 28 Oct 2010, at 10:05, James Turner wrote:
Looking at the code now, both in gui.nas and NasalSys.cxx, I can
make a more specific guess: the 'directory exists' check seems to be
failing, which means we return naNil, which doesn't have a .size
- Vivian Meazza a écrit :
That fixes the Nasal bug, but now exposes another one - the view runs
to the zenith and cannot be moved.
This happens here with Fred's latest binary, and with a locally
produced
binary including today's FG/SG fixes. It does not happen with Fred's
previous
I am tracking a crash when selecting the c172p. Not sure it is related to the
other crash already seen, but anyway :
In JSBSim.cxx, line 147 :
fdmex = new FGFDMExec( (FGPropertyManager*)globals-get_props() );
in FGFDMExec.cpp, line 99:
FGFDMExec::FGFDMExec(FGPropertyManager* root) :
Hi Torsten,
- Torsten Dreyer a écrit :
Hi all,
currently my GIT fails to merge with the error message in the
subject.
I suspect this is a line-ending conflict. I did not touch the file
locally.
I tried
git checkout -- Aircraft/Jaguar/Models/jaguar.xml
git checkout --ours
Hi m,
Le 07/10/2010 17:12, fiers...@zonnet.nl a écrit :
I used OSG version 2.9.10. The error probably has something to do with a
recent change, because yesterday's compilation was fine.
I guess I could roll back to an older version of OSG, like you
suggested, but I was rather hoping my
Hi Chris,
You may have an incorrect line break in a XML file, in a property name. You
should write
property/my/own/property/property
instead of
property
/my/own/property
/property
Regards,
-Fred
- Chris Wilkinson blobster...@yahoo.com.au a écrit :
Hi there,
I've
Hi Gene,
- Gene Buckle a écrit :
On Mon, 4 Oct 2010, Frederic Bouvier wrote:
Hi Chris,
You may have an incorrect line break in a XML file, in a property
name. You should write
property/my/own/property/property
instead of
property
/my/own/property
/property
Fred
Hi,
if you look closely, these are warnings and not errors ;-) You may look
at the discussion regarding VS2010 and OSG on the OSG list.
BTW : these messages are warnings and not errors because I added
/FORCE:MULTIPLE to the solution. It seems to affect projects that link
to osgDB
-Fred
Le
Hi Geoff,
In case you didn't notice, your fix has been committed to git 5 hours ago, and
was announced in the thread you mention.
A win32/x64 build is available at the usual place
Regards,
-Fred
- Geoff McLane ubu...@geoffair.info a écrit :
An inner inner loop using 'j', in the build
used to get with cvs?
Regards,
Geoff.
On Sat, Oct 2, 2010 at 4:23 PM, Frederic Bouvier fredfgf...@free.fr
wrote:
Hi Geoff,
In case you didn't notice, your fix has been committed to git 5
hours ago, and was announced in the thread you mention.
A win32/x64 build is available
My bad : terragear-cs is not on gitorious. You'll have to wait an answer from
Martin or Ralf.
-Fred
- Frederic Bouvier a écrit :
Create an account on Gitorious, follow the project and opt-in for
email notifications
-Fred
- Geoff McLane ubu...@geoffair.info a écrit :
Hi Fred
Check you six^H^H^Hgit
-Fred
- Alan Teeder ajtee...@v-twin.org.uk a écrit :
--
And today flightgear\src\FDM\JSBSim\math\FGModelFunctions.cpp and .h
are
needed.
Alan
Did you notice there is a while loop begining line 223 ?
-Fred
- Message d'origine -
De: Alasdair ali...@btinternet.com
Env: mardi 14 septembre 2010 03:57
À: FlightGear developers discussions flightgear-devel@lists.sourceforge.net
Objet: [Flightgear-devel] A puzzling problem with FG
- James Turner a écrit :
On 12 Sep 2010, at 09:28, Frederic Bouvier wrote:
Overall, it's less hassle to add the files by hand in the studio,
so, don't bother.
Do you remember which file you added to the MSVC100 project ?
simgear/misc/ResourceManager.cxx|.hxx
(to the SimGear
Hi Thorsten,
- thorsten i renk a écrit :
I get the same message on start.
Yes, there's a script that checks if a hard-coded vector elevation
sampling works or if you have to do repeated goedinfo calls. If the
system is to be compatible with 2.0.0 and to make use of GIT features to
- James Turner a écrit :
On 11 Sep 2010, at 22:38, Frederic Bouvier wrote:
saw that you updated MSVC project files and that's nice of you, but
it happens that for the MSVC100 (2010) files, things are a little bit
more complicated than for MSVC90 (2008).
Basically, you added .hxx
Torsten,
I saw that you updated MSVC project files and that's nice of you, but it
happens that for the MSVC100 (2010) files, things are a little bit more
complicated than for MSVC90 (2008).
Basically, you added .hxx files in FlightGear.vcxproj file, with the clause :
ClCompile
Jon,
- Jon S. Berndt a écrit :
On Sat, 4 Sep 2010, Jon S. Berndt wrote:
Which directory should one be under when they execute the git
command?
Hi,
You should be in the directory where you want to have the fgdata
directory, i.e. git creates fgdata in the current
try to remove the trailing slash, or use fgrun that is in the official 2.0.0
package
-Fred
- Jon S. Berndt jonsber...@comcast.net a écrit :
That helped, but now I am getting different errors:
--- start ---
$ FlightGear/projects/VC90/Win32/Release/fgfs --fg-
- Jon S. Berndt a écrit :
From: Alan Teeder [mailto:ajtee...@v-twin.org.uk]
Why are you using cygwin for this?
Alan,
I happily built FlightGear under MSVC, but much prefer the cygwin bash
shell
to cmd.exe. I am only running FlightGear under cygwin - not building
it
under
- Jon S. Berndt jonsber...@comcast.net a écrit :
From: Frederic Bouvier
try to remove the trailing slash, or use fgrun that is in the
official
2.0.0 package
-Fred
Still no joy. Where is the fgrun command located?
Download and install the official Win32 release
in the windows command shell. What is it
looking for??
-Original Message-
From: Frederic Bouvier fredfgf...@free.fr
Sent: Sunday, September 05, 2010 8:04 AM
To: FlightGear developers discussions
flightgear-devel@lists.sourceforge.net
Subject: Re: [Flightgear-devel] Building FlightGear
Please post the result of the set PATH command (under Windows prompt,
not cygwin)
As said in the updated instructions, you must also have the 3rdParty/bin
directory in your path as well
To diagnose DLL loading problems, Dependency Walker is your friend.
-Fred
Le 05/09/2010 18:04, Jon S.
Le 05/09/2010 18:24, Jon S. Berndt a écrit :
From: Frederic Bouvier
Please post the result of the set PATH command (under Windows
prompt,
not cygwin)
As said in the updated instructions, you must also have the
3rdParty/bin
directory in your path as well
To diagnose DLL loading
Le 05/09/2010 18:54, Jon S. Berndt a écrit :
From: Frederic Bouvier
BTW: I had several times issues with Cygwin setting odd permissions on
files and directories that prevented me to remove files until I
assigned ownership on the files and folders to my Windows account
-Fred
Bingo!
I
Le 05/09/2010 19:14, Jon S. Berndt a écrit :
To not use Cygwin ? ;-)
-Fred
Heh. Almost. But, I can't stand the Windows command shell.
I am still having a few minor issues, though.
1) The audio device is problematic:
Error: Audio device not available, trying default
Error: Default Audio
Le 05/09/2010 19:36, Jon S. Berndt a écrit :
I am still having a few minor issues, though.
1) The audio device is problematic:
Error: Audio device not available, trying default
Error: Default Audio device not available.
Try to run 3rdparty/bin/OpenALwEAX.exe
Permission denied :-(
- Jon S. Berndt jonsber...@comcast.net a écrit :
I can only repeat: your cygwin setup wrecked the vista permissions.
Go
in the explorer, open properties, go to security tabs, Advanced,
Owner
tabs and check the owner of the files and directories is really
your
Windows account, and
Hi Jon,
- Jon S. Berndt a écrit :
I updated this document recently :
http://gitorious.org/fg/flightgear/blobs/next/docs-mini/README.MSVC
I tested the described procedure in a blank virtual machine, so you
have good chances to succeed ;-) All the prerequisites are
available
- Jon S. Berndt a écrit :
Also, what's the best way to get the base package? From the FlightGear
page?
Is there a git checkout for that, as well?
You have to ensure that your base package is consistent with your sources. If
you compiled the git version of FGFS, get the data from git.
- Jon S. Berndt a écrit :
Also, what's the best way to get the base package? From the
FlightGear
page?
Is there a git checkout for that, as well?
Jon
Speaking of git, you might mention in your install procedure that for
those developers who are using Cygwin, they can
? Or, is there a page that explains the git
packages somewhere? Thanks - and again, I was pleasantly surpised by
how well the process went. It was a big help.
Jon
-Original Message-
From: Frederic Bouvier fredfgf...@free.fr
Sent: Sunday, August 29, 2010 9:50 AM
To: FlightGear developers
- HB-GRAL flightg...@sablonier.ch a écrit :
Am 14.08.10 00:20, schrieb Tim Moore:
Let
me know of any new problems.
Tim
A new problem is the last line in default.vert:
fogCoord = abs(ecPosition.z / ecPosition.w);
For what is this needed exactly?
It kills the light or light
Hi Tat,
- Tatsuhiro Nishioka a écrit :
Hi there,
First of all, I'm back to FlightGear after a bit longer vacation :-)
I'm very happy that I released a fg-git for Mac OS, but immediately
after that, a user gave me a bug report. X-)
The core problem is that an implicit cast
- Tatsuhiro Nishioka a écrit :
Hi Fred,
Thanks for the quick fix. I really appreciate it!
Tat
You're welcome, you did all the diagnostic work.
-Fred
--
Frédéric Bouvier
http://my.fotolia.com/frfoto/ Photo gallery - album photo
http://www.youtube.com/user/fgfred64 Videos
:
both are showing 0
--- On Wed, 18/8/10, Frederic Bouvier fredfgf...@free.fr wrote:
From: Frederic Bouvier fredfgf...@free.fr
Subject: Re: [Flightgear-devel] Running compiled version of flightgear 2.0 on
windows gives blank screen
To: FlightGear developers discussions
flightgear
Hi Yves,
- HB-GRAL a écrit :
Tim Moore schrieb:
I've checked in some changes to the shaders in attempt to fix bugs
on some
platforms and generally optimize them. I've eliminated the use of
gl_FrontFacing, which seems to give us problems on certain
Macintosh
platforms. I've also
sending the download link . Sometimes the panel is getting displayed. but
the moment I change the view, that also disappears. Is it a problem with OSG?
http://rapidshare.com/files/413600761/flightgear2.0.JPG
Please see that.
Thanks
Vijeesh T
--- On Tue, 17/8/10, Frederic Bouvier
- HB-GRAL flightg...@sablonier.ch a écrit :
Frederic Bouvier schrieb:
The crop shader has its snow level hardwired to 2000m and it is so
from the beginning.
-Fred
Hi Fred
What is the reason for this I miss? I mean, this is not so nice having
a
slider to get snow below
- HB-GRAL a écrit :
Frederic Bouvier schrieb:
- HB-GRAL flightg...@sablonier.ch a écrit :
Frederic Bouvier schrieb:
The crop shader has its snow level hardwired to 2000m and it is so
from the beginning.
-Fred
Hi Fred
What is the reason for this I miss? I mean
, Frederic Bouvier fredfgf...@free.fr wrote:
From: Frederic Bouvier fredfgf...@free.fr
Subject: Re: [Flightgear-devel] Running compiled version of flightgear 2.0 on
windows gives blank screen
To: FlightGear developers discussions
flightgear-devel@lists.sourceforge.net
Date: Wednesday, 18
smoothly. I
could even see the framerate to be 20(through property manager). But the
screen is only bluish white. I can attach the screen if required. I'll try to
take the latest code and build.
Vijeesh T
--- On Tue, 17/8/10, Frederic Bouvier fredfgf...@free.fr wrote:
From: Frederic
Hi,
if you compiled released v2.0 sources and try to run it in debug mode, there
are tens of thousands exceptions thrown by the flight plan manager that makes
the loading very, very, very slow. The issue has been fixed since then in the
git repository.
-Fred
- vijeesh theningal
- HB-GRAL a écrit :
Is it possible to add (or blend) a texture in the shaders to steep=
gray instead of calculating a 'simple colour cloud'? In combination with a
texture it probably looks like all the 'perhaps' and is a very nice
feature.
You can add the rock texture to the effect file
- HB-GRAL a écrit :
Hm,
I noticed today a small problem with random placement of some models
(houses) with scenery point feature 'town'. I see that some of the
houses are flying where terrain isn’t completely flat. I guess the
houses where placed near a single 'town point' all at same
Hi,
- Chris Baines cbain...@gmail.com a écrit :
Hello,
I am trying to update the SimGear package in Debian (from 1.9.1 to
2.0.0), I have packaged the current version of fgrun and plan to
upload
it, but it only compiles with SimGear (v2.0.0).
The current Debian Maintainer is as far
Hi Durk,
Le 30/07/2010 09:38, Durk Talsma a écrit :
And, as an aside, but I'm sure everybody is aware of that: only the _default_
compilation behavior is changed. If you compile with --enable-atcdcl, you'll
still be able to get ATIS messages.
By the way, kln89_page_apt.cxx (
vs2008 express doesn't support 64bit compilation. You're stuck to 32bit
-Fred
- Message d'origine -
De: Jon S. Berndt jonsber...@comcast.net
Env: mardi 29 juin 2010 02:48
À: 'FlightGear developers discussions' flightgear-devel@lists.sourceforge.net
Objet: Re: [Flightgear-devel] Building
Hi James,
There is already an inno-setup script in Packages/ that builds fgsetup.exe,
with data, but for snapshot builds, I only make zip files of exe and dll,
including fgrun. You can see by yourself by downloading from
ftp://ftp.ihg.uni-duisburg.de/Flightgear/Win32 . There is a wiki page
Hi Jon,
- Jon S. Berndt a écrit :
Where will I find the best, most up-to-date guide on downloading
the development version of FlightGear from CVS and building it?
Can I used MSVC++ Express 2008? 2010?
Thanks. I haven't done this in a long, long, time.
Jon
On the
The files config.h-msvc8 and config.h-msvc90 are necessary for a
windows build but are now in .gitignore making them inaccessible.
Natively windows has no method to generate these files from the .in
files, although this is probably possible by installing Perl, and GNU
versions of
- Alan Teeder a écrit :
Is there any need for this to be done by all new cloners before
compilation?
It seems to be an unnecessary complication.
All GIT users should be currently working with the same version
(2.0.0) in both simgear and flightgear. As and when a new version comes
- Michael Sgier a écrit :
- Fgrun
export OSG_STEREO_MODE=ANAGLYPHIC;export OSG_STEREO=ON;fgrun
These parameters are already settable in the advanced environment section. As
always, they are preserved from session to session
-Fred
--
Frédéric Bouvier
Le 22/05/2010 20:20, Torsten Dreyer a écrit :
Hi,
after cloneing the flightgear sources and running make, git status says
# modified: config.h-msvc71
# modified: config.h-msvc8
- Ron Jensena écrit :
On Thursday 13 May 2010 20:43:06 小龙 陈 wrote:
Hi,
I use a Flightgear under windows, so How can I enable the stereo to
see the
red and cyan effect in Flightgear? Thanks!
You must set ENVIRONMENT VARIABLES for OSG. I can not tell you how to
do that
on windows
- HB-GRAL a écrit :
There seems to be a (maybe only ATI related) bug in fragment shaders.
I
could not find any information about this in the list/forum/bug
tracker.
Can you please check this:
Following does not work in default.frag, terrain-default.frag and
mat-anim.frag for
- James Turner a écrit :
On 12 May 2010, at 05:37, Alex Perry wrote:
Two screenshots that demonstrate a use case.
http://picasaweb.google.com/alex.pamurray/FlightGearAndroid?authkey=Gv1sRgCLXWsq_p96GFPQfeat=directlink
I'd appreciate it if someone could review and commit this
- Alex Perry a écrit :
On Wed, May 12, 2010 at 1:35 AM, Frederic Bouvier
wrote:
BTW, I never managed to build these OSG plugins with MSVC
Not having the plugins doesn't break the SimGear side code, but the
new feature doesn't end up doing anything interesting. The OSG
plugins
301 - 400 of 887 matches
Mail list logo
