-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Holger Wirtz wrote:
> Hi Arvid,
> No, yes, no... yes it's a kind of bug. I had such things not in mind as
> I wrote fgcom. There should be a feature that allows to use the echo box
> even if you are authenticated to the server but this works only as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Yes much easier to see what is happening.:D
Regards,
Arvid Norlander
gerard robin wrote:
> On mer 19 décembre 2007, gerard robin wrote:
>> On mer 19 décembre 2007, AnMaster wrote:
>>> Hm another issue: in S-51-on_carrier one o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Chris Metzler wrote:
> On Wed, 19 Dec 2007 12:33:26 +0100
> Melchior FRANZ wrote:
>
> (snip good suggestions about various pictures in the gallery)
>
> The one big suggestion I'd make is to drop the current caption for
> each photo, which appears t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Wow nice. Can I get the aircraft somewhere? Maybe a tarball and help test it? :D
Regards,
Arvid Norlander
flying.toaster wrote:
> Yet work in progress but it may become a worthwhile addition to the carrier
> borne aircraft in a short while
> Done
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I don't know where it is on windows but on Linux there is an xml in
$HOME/.fgfs/autosave.xml and for each aircraft $HOME/.fgfs/aircraft-data/*.xml.
Regards,
Arvid Norlander
Shad Young wrote:
> Hi all,
>
> Again not sure if I should post this to t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I tried doing this but I couldn't get it to work. How do you "set a trace with
it"?
Regards,
Arvid Norlander
Melchior FRANZ wrote:
> * Georg Vollnhals -- Wednesday 19 December 2007:
>> You asked on the FG forum for driving cars. I made an example
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Holger Wirtz wrote:
> Hi,
>
> after thinking about this feature I recognized that there are some
> problems:
>
> Real radio has a limited range. So you can use the same frequency at
> every point on the world. If you can hear someone on the same fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Indeed AltGr is broken with SDL last I tried (Swedish keyboard here) so I
recommend glut in that case until the osgviewer input works nicely.
Regards,
Arvid Norlander
Cédric Lucantis wrote:
> Hi,
>
I'd like to know if the 'repeatable' flag i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I was working on trying to find the cause why tower altitude set to 70 in
apt.dat wasn't correct and
caused ATC aircraft to end up under ground.
As far as I understood we use same format as x-plane for apt.dat? Then the
tower elevation in
apt.dat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I went in on www.flightgear.org just a few minutes ago and noticed it changed a
lot. The menu on the
left was gone. And there were no menu anywhere else. Someone else said there
was a new menu at the
top. I couldn't see it. Then I got an idea, mayb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Curtis Olson wrote:
> On Dec 21, 2007 1:15 PM, AnMaster wrote:
>> I went in on www.flightgear.org just a few minutes ago and noticed it
>> changed a lot. The menu on the
>> left was gone. And there were no menu anywhere el
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
It seems like fgtracker no longer registers flights on mpserv02, is it broken.
http://fgfs.i-net.hu/modules/fgtracker/?FUNCT=FLIGHTS&CALLSIGN=AMaster doesn't
show any flights
since December 15, and I have done several on 02.
Regards,
Arvid Norlan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
fg never worked well around the poles, iirc with fg/osg you get a crash at
south poles. Also we lack
scenery for the poles. Any scenery south or north of a certain point that is.
How did you take off from the water btw?
Regards,
Arvid Norlander
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Currently I'm unable to reach the cvs server and some other people on IRC
confirmed this.
It seems like both cvs and terrasync/scenery server is down (apart from my
terrasync mirror, it is up).
Regards,
Arvid Norlander
-BEGIN PGP SIGNATURE--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Torsten Dreyer wrote:
>> fg never worked well around the poles, iirc with fg/osg you get a crash at
>> south poles. Also we lack scenery for the poles. Any scenery south or north
>> of a certain point that is.
> Oh - no rich-people-cocktail-party wit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Maik Justus wrote:
> Hi Gerard,
> gerard robin schrieb am 24.12.2007 01:14:
>> BTW: i could not use the c172 because mine makes difference between water
>> and
>> solid
>>
>> Cheers
>>
>>
> Yes, all YASim aircrafts do. But while the default sce
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
It seems like all the modes are overlayed with the map though, like the old
hybrid mode (that seems
gone). I miss the mode without all the labels and road lines on it. :/
Regards,
Arvid Norlander
Gijs de Rooy wrote:
> Hi,
>
> First to all of yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
How does this work with windowed mode (that I always use, as maximized window,
still showing the 64
pixels high KDE taskbar at the bottom, and window edges). My monitor is 4:3,
but the window isn't.
Regards,
Arvid Norlander
Maik Justus wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
My resoltion is 1400x1280, but you also have to consider window borders. Not
sure how large they
are, however the screenshots I took at www.flightgear.org (A10-KNID-01 for
example), were in
maximized window. Should be possible to calculate from tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Maik Justus wrote:
> Hi Arvid,
> AnMaster schrieb am 04.01.2008 23:13:
>> My resoltion is 1400x1280,
> not 4:3 nor 16:9 ?
20" 1400x1280 TFT. I got no idea what format it is, but the monitor works well
for me.
The screen area of
such member: trim
at /home/anmaster/src/flightgear/data/Nasal/screen.nas, line 99
called from: /home/anmaster/src/flightgear/data/Nasal/screen.nas, line 267
called from: /home/anmaster/src/flightgear/data/Nasal/screen.nas, line 305
called from: /home/anmaster/src/flightgear/data/Nasal/global
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Maik Justus wrote:
> Hi Arvid,
> maybe your pixels are not of square size? If yes: can you look to
> /sim/current-view/aspect-ratio-multiplier? If it is not 1, then we need
> to scale 47.5 with this factor (to get a larger fov).
Hm, my fault it se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Csaba Halasz wrote:
> On Jan 5, 2008 11:46 AM, AnMaster <[EMAIL PROTECTED]> wrote:
>> Nasal runtime error: No such member: trim
>> at /home/anmaster/src/flightgear/data/Nasal/screen.nas, line 99
>>
>> This happen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
It seems like OSG-based FlightGear locks up or slows down to less than 1 FPS if
a 787 joins over mp
near you. For example, today I was flying concorde, had just landed and was
taxing to KSFO terminal
and a 787 joined:
Chat [*FGMS*] NJ7983 is now o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Curtis Olson wrote:
> On Jan 5, 2008 8:56 PM, Csaba Halasz <> wrote:
>
>> Hi!
>>
>> I have changed Tiago's patch somewhat, it now iterates over all the
>> ground layers.
>> Debug output looks like this for KSFO:
>>
>> Found tower ground layer at 1
is a considerable problems for Sweden and Canada as shown on these
screenshots of Atlas:
Sweden: Notice the area without elevation data (in which I live...)
http://pics.ww.com/v/AnMaster/fgfs/bugs/fgfs-altproblem.png.html
And this one is just strange (North Canada):
http://pics.ww.com/v/AnMaster
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thanks to timoore on IRC for helping find the cause of this.
It seems that a recent checkin broke the build system if osg is installed in a
custom location.
- --with-osg=/home/anmaster/local/flightgear-osg in my case.
I got this from configure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Curtis Olson wrote:
> Are you building on the Mac OSX platform?
>
No. On Gentoo Linux (x86_64)
Regards,
Arvid Norlander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.7 (GNU/Linux)
iD8DBQFHh5iRWmK6ng/aMNkRCq+ZAJwJ2ZtB0M2k2lytUbDWHBk31JOM8QCeLW
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
This does NOT solve it:
from configure after update to your patched version:
checking for osg/Version... yes
checking for osgViewerGetVersion in -losgViewer... no
checking for osgGAGetVersion in -losgGA... no
checking for osgTextGetVersion in -losgT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
After talking to AndersG on IRC I tried rebuilding from a clean checkout, same
result but earlier:
checking osg/Version usability... yes
checking osg/Version presence... yes
checking for osg/Version... yes
checking for osgViewerGetVersion in -losgV
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Jon Stockill wrote:
> AnMaster wrote:
>> After a report from a windows user about broken artificial horizon after a
>> roll in c172p and
>> SenecaII (using 1.0), I tried this. I do not know if it is a feature or a
>&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
After a report from a windows user about broken artificial horizon after a roll
in c172p and
SenecaII (using 1.0), I tried this. I do not know if it is a feature or a bug,
but after a roll in
c172p the artificial horizon is indeed no longer correct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Stefan Seifert wrote:
> Curtis Olson wrote:
>
>> Don't bother listening to Melchior, he's busy coming up with absurdly long
>> strings of obscure unix commands that are just a huge waste of time to
>> type. You can do the same check with this much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
First: Please don't hijack a thread like you did. Most clients that allow
displaying threaded view
of messages don't base it on subject but on other, normally hidden headers
(that are more reliable
normally, unless someone hijack the thread like yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Durk Talsma wrote:
> Hi all,
>
> I'm getting the following compilation error, using today's cvs version of
> OSG,
> SimGear, and FlightGear. Any clue as to what might be going on?
>
> Cheers,
> Durk
CVS of OSG? They changed to SVN a long time ago
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
George Patterson wrote:
> Not a bad idea.. but don't we need water bombing aircraft first in
> order to put out the fires?
> (unless you are happy to wait for the wind to change direction which
> means that the fire burns itself out.)
>
>
> Just ca
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I don't have time to debug this, but this patch broke the rudder pedals under
Linux and
FreeBSD (I run both OS) for me. Rudder no longer works. Toe brakes still work.
The axis is
axis 2 according to js_demo.
Regards,
Arvid Norlander
Sven Almgren
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I found the problem, the tag "" should be changed to "". Don't we
have a DTD
or XML Schema to test these things? And don't people proof read and test before
committing?
Regards,
Arvid Norlander
AnMaster wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
It does indeed look like 0.9.8 had best coast line. Why is it so much worse in
more recent
scenery? Wouldn't it be possible to get the same good coastline as in 0.9.8?
Regards,
Arvid Norlander
gerard robin wrote:
| On jeu 20 mars 2008, gerard rob
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Curtis Olson wrote:
| On Fri, Mar 21, 2008 at 11:00 AM, AnMaster wrote:
|
|> -BEGIN PGP SIGNED MESSAGE-
|> Hash: SHA512
|>
|> It does indeed look like 0.9.8 had best coast line. Why is it so much
|> worse in more re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
It seems fg tracker no longer tracks mpserver02 at least. My log there show no
flights
done since March 1 and I did several today (March 24) and last week. I'm not
sure who
exactly to contact for this so I'm sending the mail to -devel, hoping someo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I found such a case near Göteborg in Sweden:
57*28 41.8N 11*51 56.1E is what the HUD show when I'm above it.
Regards,
Arvid Norlander
Ralf Gerlich wrote:
| Hi!
|
| Jocelyn Couetdic wrote:
|> I hope you'll find without too much trouble the bug behi
llowing the coast north
of ESGG a
bit) look crap in 1.0 scenery.
Regards,
Arvid Norlander
AnMaster wrote:
| I found such a case near Göteborg in Sweden:
| 57*28 41.8N 11*51 56.1E is what the HUD show when I'm above it.
|
| Regards,
| Arvid Norlander
-BEGIN PGP SIGNATURE-
Version: G
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello everyone,
Sadly I'm unsure how long I will be able to keep my terrasync mirror up, atm
I'm dropping
mirroring of 0.9.10 scenery due to disk space (only keeping 1.0.0 scenery). I
see that on
the other hand Curt's server only mirrors Scenery-0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I'm not sure how to extract that from the logs. The server in question hosts a
lot of
other stuff that use a lot of bw so just looking at stats for the server would
not help.
/Arvid Norlander
Sven Almgren wrote:
| How much data/trafic are we talk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The ip for my terrasync mirror changed to 67.202.82.26. Curt: please update DNS
for the
round robin scenery.flightgear.org to reflect this as soon as possible.
Regards,
Arvid Norlander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
It should also be possible to use some daemon talking to FlightGear using TCP
or UDP and
then get that daemon to talk to the USB device. On Linux try using libusb, I
assume
something similar exists for Windows.
Regards,
Arvid
Curtis Olson wrote:
201 - 247 of 247 matches
Mail list logo
