The screenshot gallery does not work.
There is a broken link, i think.
IS
Not Found
The requested URL /Gallery/ was not found on this server.
Apache/1.3.34 Server at www.flightgear.org Port 80
___
Flightgear-devel mailing list
On 19 Nov 2005, at 01:49, Arthur Wiebe wrote:I have found the problem. My Xcode projects seem to be buggy. The PLIB project is fine but something is wrong with the SimGear project. I just built using the autoconf system and everything worked fine. It even fixed my spash screen problem! :) I'll
This looks very much like you do not have the matching version of
simgear compiled/installed, or you have multiple versions on your system
and the compiler is finding the wrong one.
Regards,
Curt.
Steve Knoblock wrote:
I checked out the CVS base lat night and tried to compile with an
Curt, the link is on the front page... I just checked and go the same
404 error.
Broken link is http://flightgear.org/Gallery/ on http://flightgear.org/
I'm sure it is something simple.
George Patterson
On Sat, 2005-11-19 at 05:59 -0600, Curtis L. Olson wrote:
Hi Ioan,
Try reloading the
Curt, the link is on the front page... I just checked and go the same
404 error.
To be a bit more precise, it's the screenshots link at the bottom
of the page.
The one on the left is fine, which points to
http://flightgear.org/Gallery-v0.9.9/
Pigeon.
Curtis L. Olson schrieb:
Ampere K. Hardraade wrote:
Perhaps we can have a weekly screenshot competition? The best
screenshot of the week get uploaded to FlightGear's frontpage.
Sounds like a great idea. ...
Curt.
...
Ok, I want to win the prize and stop working :-):
hey all...
i have only contributed by just trying out new stuff in cvs, but i am
nontheless proud of what *we* did and i feel that we should try to give this
release a bit more publicity.
anyone feeling responsible for alerting major anouncement sites (such as
happypenguin.org) about the new
Hi,
I recognized instrument display errors with the Beaver (a really
wonderful FG plane!!!).
Have a look at the screenshots, pics can explain more than words:
http://home.arcor.de/vollnhals-bremen/BeaverInErr/InFail0002.jpg
http://home.arcor.de/vollnhals-bremen/BeaverInErr/InFail0003.jpg
Pigeon wrote:
Curt, the link is on the front page... I just checked and go the same
404 error.
To be a bit more precise, it's the screenshots link at the bottom
of the page.
The one on the left is fine, which points to
http://flightgear.org/Gallery-v0.9.9/
Ok, I got the one in
* Erik Hofman -- Friday 18 November 2005 18:36:
After this release we'll only accept bug-fixes to the code, except for
the new JSBSim version. Any major code changes that are not intended to
fix one or more bugs will have to wait.
One new feature *must* go in. Otherwise the 1.0.0 release
And if none of this is possible, then I'm afraid I don't have a
TODO list and this will be the most boring release cycle ever.
m.
Heh. Maybe. Maybe not. I hope that from your point of view it turns out to be a
boring
release cycle. In one respect, it should not be very noticeable to users
I also hoped that a few Nasal improvements could be committed,
such as file I/O. That's hardly dangerous for overall fgfs
stability, and would allow to implement some nice features
in Nasal scripts. (Not that this had to be in 1.0.0, but I
wouldn't like to wait some months for it. :-)
m.
Melchior FRANZ wrote:
* Erik Hofman -- Friday 18 November 2005 18:36:
After this release we'll only accept bug-fixes to the code, except for
the new JSBSim version. Any major code changes that are not intended to
fix one or more bugs will have to wait.
One new feature *must* go in.
Melchior FRANZ wrote:
And finally, this is my TODO list:
* try to get rid of a few more hardcoded dialogs, or at least
make them accept gui colors
Not that I explicitly stated no major updates to the *source* *code*.
Removing code would be no problem (and neither would be putting an
Stefan Seifert wrote:
Another thing that's really missing (and was mentioned in the
linux-user.de review) is handling of any cases other than normal flight.
Redout and Blackout are a good start, but everything from structural
failures to things like skid sounds if you turn too quick on ground
I'm now working on the unsafe throws/catches in the
SimGear/FlightGear/Atlas/fgrun codebase.
A hefty amount of things to change is in the scope of the JSBsim code.
What should I do --- ignore them and hope for JSB doing a correct cleanup
upstream, or patch these as well?
Vassilii
If you
Hi,
I have 3D clouds, but can´t see the shadows. I also noticed that
FG 0.9.9 don´t work with full screen mode because using this feature
FG starts with a strange green colour and very slow fps.
Finally, the old fonts in the FG 0.9.8 format are still there, couldn´t
see the fonts showed in the
On Saturday 19 November 2005 15:30, Erik Hofman wrote:
Melchior FRANZ wrote:
And finally, this is my TODO list:
* try to get rid of a few more hardcoded dialogs, or at least
make them accept gui colors
Not that I explicitly stated no major updates to the *source* *code*.
Removing
I'll experiment as well - I had some strange issues earlier in the year
building FG with my own X-Code projects; I was being more ambitious, and
building PLIB and SimGear as frameworks, but on reflection that's not such a
great idea. One change I have made is to use a 'copy files' stage for
* Rodrigo Flores -- Saturday 19 November 2005 16:18:
Finally, the old fonts in the FG 0.9.8 format are still there, couldn´t
see the fonts showed in the Concorde screenshot.
You have to switch the GUI style with Shift-F10, or put this into your
~/.fgfsrc or use it on the command line or in
I agree with Franz Melchior.
And my question is, why it is so essential to call the next version release
1.0?
What's wrong with version numbers like 0.9.10, 0.9.11, 0.9.12 etc. until the
above issues are fixed?
That's what's been getting done for years. The question now is, why not? Curt's
My video is set to 32 bit color, is this a FG config issue?
About new fonts is working fine now, thanks to Melchior.
- Original Message -
From: Oliver C. [EMAIL PROTECTED]
To: FlightGear developers discussions flightgear-devel@flightgear.org
Sent: Saturday, November 19, 2005 1:49 PM
On Saturday 19 November 2005 16:35, Jon Berndt wrote:
To turn the argument around, there's nothing to fear from calling it 1.0,
either.
I don't think so, in my opinion the status of version 1.0 will decide how many
new contributers and public interest this project will get.
In other words, my
Oliver C. wrote:
I don't think so, in my opinion the status of version 1.0 will decide how many
new contributers and public interest this project will get.
In other words, my estimation is (when i look into my crystal ball :) ), that
we will get more people that start contributing to FlighGear
Just a small update...
I discovered the key for 32bit color on FG, and now is set to
32 color, but still no shadow.
I wonder could be my old 64mg video?
Thanks!
- Original Message -
From: Rodrigo Flores [EMAIL PROTECTED]
To: FlightGear developers discussions
Hi,
I recognized instrument display errors with the Beaver (a really
wonderful FG plane!!!).
Have a look at the screenshots, pics can explain more than words:
http://home.arcor.de/vollnhals-bremen/BeaverInErr/InFail0002.jpg
http://home.arcor.de/vollnhals-bremen/BeaverInErr/InFail0003.jpg
On November 19, 2005 10:18 am, Rodrigo Flores wrote:
Hi,
I have 3D clouds, but can´t see the shadows. I also noticed that
FG 0.9.9 don´t work with full screen mode because using this feature
FG starts with a strange green colour and very slow fps.
Finally, the old fonts in the FG 0.9.8
On November 18, 2005 09:11 pm, Curtis L. Olson wrote:
Ampere K. Hardraade wrote:
Perhaps we can have a weekly screenshot competition? The best screenshot
of the week get uploaded to FlightGear's frontpage.
Sounds like a great idea. Are you volunteering to manage it? :-)
Curt.
On
On 11/16/05, Ethan D. Schur [EMAIL PROTECTED] wrote:
So I'm getting about 4273 unresolved externals when linking flightgear
in MSVC7. I build simgear and all the dependencies. The errors look
something like this
FlightGear error LNK2001: unresolved external symbol bool __cdecl
Hello again..
Trying to load FG it comes this message:
opening file: C:/Arquivos de
programas/FlightGear/data/Navaids/carrier_nav.dat
C:/Arquivos de programas/FlightGear/data/Navaids/TACAN_freq.dat
Unknown exception in the main loop. Aborting...
Possible cause: No error
Thanks!
--
No
I can work on aircraft thumbnails for the download page. What is the best way to submit them? Regards, Paul Bohnert "Curtis L. Olson" [EMAIL PROTECTED] wrote: Aircraft authors (or other interested parties.)Take a look at the latest aircraft download
Hi,
Georg Vollnhals schrieb:
http://home.arcor.de/vollnhals-bremen/FGScrSh/FGSrSh0005.jpg
http://home.arcor.de/vollnhals-bremen/FGScrSh/FGSrSh0006.jpg
can I trust my eyes? This must be from the lake-constance scenery...near
Bregenz...cool! ;-)
Ralf
Well I'm not seeing any cloud shadows either.
Hardware/libGL thing? (Or are shadows drawn underground for some of us?)
I have: Nvidia GeForce FX 5200 with 256M, X-server at 24 bpp, fgfs with --bpp=24
with or without --enable-fullscreen. libGL is nvidias No 7676 driver
(latest)
I've been spying
Ralf Gerlich schrieb:
can I trust my eyes? This must be from the lake-constance
scenery...near Bregenz...cool! ;-)
Hi Ralf,
you must know better than I :-). To be honest, I started from EDNY to
combine your very detailled scenery together with the Citation Bravo
aircraft on a screenshot.
Hello all,
Since I can't get my copy of FlightGear to run, I can't test these scripts
myself. Therefore, if you could play around with the two scripts in
http://www.cs.yorku.ca/~cs233144/ and tell me about any error that you may
receive, that would be great.
The two scripts are
35 matches
Mail list logo
