Re: [Norton AntiSpam] Re: [Flightgear-users] Helicopters in Flight Gear
On Wednesday 26 October 2005 04:11, Bill Galbraith wrote: Wow, I almost deleted this posting, but did go out to this web site. There is a scary article about someone trying to claim a patent on XML. You might want to read this: http://www.groklaw.net/article.php?story=20051021183953795 Bill You think that is scary? Apparently, somebody I have never met in America has patented bits of my gentic code!! -- Dave Martin http://museum.bounce-gaming.net ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re-Re: 1900D Issue
On Sunday 18 September 2005 21:47, syd wrote: Hi Georg Just to clear things up, I did the modelling and original flight model,and Dave tweaked the flight model for much better performance. What other panel funcionality would you suggest , I am only going on photos , so there is a lot of guess work here , and any tips or suggestions from someone who knows this aircraft better would be a great help .Thanks Absolutely, the B1900D is 100% Syd's work - and incredible work it is too. I just tinkered in the FDM at the behest of a B1900C/D pilot to make it fly someway like the real thing. Syd is one of several grand-master modellers we have been lucky enough to see in the FG project and they are the sole reason I have never shown my (comparably pathetic) 3d models ;) Syd: I'm somewhat out of touch with the fellow who flies the 1900's for a little while but I'm pretty good at digging for info. If you want something specific, I'll have a go at finding it. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re-Re: 1900D Issue
Is thrust reverse and autobrake found on the real b1900d? Most of the King Airs and all the 1900's have 'negative pitch' thrust reverse. Not sure on autobrake; if you mean the aircraft equivalent of ABS then I *think* they do. I'm fairly sure they don't have the auto/optimised braking found on larger aircraft tho. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] 1900D Issue
On Saturday 17 September 2005 09:19, Paul Surgeon wrote: Not sure if I should hijack this thread or start another one but ... Has anyone else noticed that the B1900D is very twitchy on the runway at low speeds? I just have to touch the rudder and it wants to veer off in either direction. I have to toggle it down the runway until the rudder has enough authority to override the nosewheel. Otherwise the handling is great - snap rolls at 200 knots in level flight work perfectly too! :) Regards Paul I deliberately boosted the ground steering response on the B1900D at the suggestion of a pilot familiar with the type. It was quite a while ago that I made those changes to the FDM and he's since been back and had a go with the rudder pedals and he thinks it's 'spot on' for the ground handling (although I can see that its a handful with the KB). Aside from that, he gave me a good few pointers on things that need changing in the FDM so I shall probably have a word with Syd again soon and have another go at it. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] 1900D Issue
On Saturday 17 September 2005 21:09, Paul Surgeon wrote: On my Sidewinder Force Feedback Pro the twist grip increments in steps of 1213 from -32767 to 32767. So that means I only have 27 steps either way. Maybe we could have an option for dampening the response for twist grips that can be selected at run time for the B1900D because there are several people who battle with the sensitivity. Otherwise I like the handling - it's my third favourite aircraft behind the Seahawk and Hunter. Regards Paul I don't have my thinking cap on right now but perhaps there is a way of sorting this in the joystick config. I just had a go with the b1900d on the version of the FDM that I last worked on and keeping the centreline was quite easy using the keyboard so perhaps something has gone awry in a later iteration. One thing that I really want to sort out is the nose-leg oleo - It seems to allow the nosewheel to break contact very early. There is bucketloads of torque even tho the props are lightweight composite so there should be some swing, if you could try forcing the nose down during the takeoff run using nose-down elevator and then get back with what you find? In the mean time, I'm going to check-out the latest b1900d. Cheers. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] gyro
On Friday 09 September 2005 22:01, Edward Cawley wrote: New user with a Mac. Two questions, I have a feeling of being in a small minority, I would be happy to know some other Mac users. I have FG up and going, but with many questions. Such as- I'm trying to run ADF on the autopilot. All the directions I have found refer to setting the bug on the DG, but the default DG doesn't seem to have one, but the gyro xml refers to the bug? This seems to be a conflict. Any ideas why there is a difference? IIRC the gyro reference would be the DI (gyrocompass) rather than the ADF. There is definitely a working bug on the DI on some aircraft. As for the ADF, I think I had it working with the autopilot on the Hunter. Perhaps someone can shed some more light here ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Beechcraft 1900D, Help Please!
On Monday 29 August 2005 12:17, T J wrote: I recently downloaded the 1900D from the FlightGear homepage. The trouble is the mouse cannot be used to adjust the propellor feather, or any of the instruments. How can you get the mouse to adjust this? It works fine on all other aircraft. The same problem occurs on the Cessna Citation (by the same author.) Please can you help! I would also like to know how you shut down the engines on these aircraft. AFAIK, The B1900d is still under development and as such should be viewed as 'note quite done yet'. I did some work on the B1900's FDM a while back and it has come along quite a bit since then. The panel radio instruments still suffer a bug which affects all texture-drawn instruments and the only way to set the frequencies right now is via the FG menu. I'm not sure that controls for the props or the ail/rudder trim are available either yet - In fact I don't think they are. There is a way to stop the engines on the B1900d and that is to pull the 'condition' levers back to FCO and cause a flame-out. Use M/m for this. AFAIK the Citation is also under development alongside the B1900d. Dave Martin. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] slow framerates with NvidiaPIC Express underLinux solved !
On Saturday 30 July 2005 12:40, Matthias Boerner wrote: Hi, I tested the NVIDIA-7667 driver yesterday again. I have tested it before but with problems using shadows. It is true that framerates are much better compared to all previous 7xxx versions. But I still have problems with version 7667 and enabling shadows: There are no shadows at all. So I will stick with version 6629. I am using NVIDIA 6600GT PCI Express on an AMD64. Flightgear version is CVS snapshot of 30-07-2005. Matthias Just asked about this on the developer's list. You need to start FlightGear with the --bpp=24 switch for shadows to work on the 1.0-7667 driver. Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Rotating the Display
Just a little to add to this. (I haven't read all the posts) The new Nvidia driver for Linux has XRandR support. (7167) http://www.nvidia.com Dave Martin. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Cool photo
On Friday 18 Feb 2005 14:55, David Luff wrote: On 17/02/2005 at 14:42 Josh Babcock wrote: Found a link to this on fark.com. http://www.airliners.net/open.file?id=777174size=Lsok=photo_nr=prev_id = next_id= Incredibly, another photographer appears to have snapped the very same landing from a different perspective moments earlier: http://www.airliners.net/open.file?id=779790size=Lsok=JURER%20%20%28cynpr % 20%3D%20%27Fna%20Senapvfpb%20-%20Vagreangvbany%20%28FSB%20%2F%20XFSB%29%27% 2 9%20%20beqre%20ol%20cubgb_vq%20QRFPphoto_nr=17prev_id=779791next_id=7793 7 8 Cheers - Dave This message has been checked for viruses but the contents of an attachment may still contain software viruses, which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d I really hope they only do that in CAVOK conditions :-O Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] What the hell am I doing wrong?
On Monday 07 Feb 2005 04:32, reg hughson wrote: Problem : No matter what I do, I cannot get the Cessna to go above 800-1000 feet...even the slightest climb causes a stall (I think). I don't have this problem with other planes. For example, I used to cruise around the San Francisco area in a 747 (until the 747 disappeared in 0.98) (and yes, I know, I could have found a smaller plane) with no problems and have even set the thing to go cross country at 35000 feet without any problems. Can anyone point me in a direction that may help me get my Cessna in the air? The 747 for 0.98 is available here: http://www.flightgear.org/Downloads/aircraft/index.shtml When you takeoff in the Cessna 172, set first stage of flaps, park-brake off, full-trottle and then don't rotate till about 55-60kts to ensure good lift. Climb-out attitude in the 172 should be significantly less than the airliners. Dave Martin. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] OpenGL Flightgear and Mandrake 10.0
On Wednesday 02 Feb 2005 07:44, Innis Cunningham wrote: Hi Guys This is my first attempt at building FG under Linux so please be kind.:-) I have a dual boot system using a 2G athalon and a Nvidia FX5200. When I run configure in Plib it says no openGL. My questions are. 1)Would Mandrake be using openGL from the install or would it be using something else to drive the graphics card. 2)If openGL is loaded and working how do I know and why if it is can,t Plib find it. I downloaded and installed a Mesa openGL rpm but still no go with Plib. I know these are probably realy dumb questions but there the smartest I can ask at this time. Thanks for any help. Cheers Innis Do you have the Nvidia (proprietary) drivers installed? (currently 6629 from http://www.nvidia.com) Also, can you run glxgears? (just type glxgears in a console) Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] OpenGL Flightgear and Mandrake 10.0
On Wednesday 02 Feb 2005 09:45, Jon Stockill wrote: Innis Cunningham wrote: No.I get this reply Xlib: extension GLX missing on display 0.0 and Error:couldn't get an RGB, double-buffered visual. Will this problem be fixed by downloading and installing the Nvidia drivers.Don't suppose they come in a rpm.:-) No, they don't - it's even easier than that - you just download it, run it, and it installs itself. Like Jon says but if its your first time: *Download the package. *Log out of your Window Manager *Ctrl-F1 for a command console *Login as root *type: init 3 *cd to the directory where the downloaded package resides. *type: sh NVIDIA*.run (now follow instructions) *type: init 5 *Now log yourself back in to the Window Manager and try glxgears. Please somebody correct the above if Mandrake uses different runlevels. Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: Spitfire Starting (was FlightGear v0.9.8 onWindows XP)
On Tuesday 01 Feb 2005 17:25, Vivian Meazza wrote: Melchior FRANZ wrote: AnthonyL -- Tuesday 01 February 2005 12:19: By trial and error I have found that from a stationery engine: 1. Press C (case is important) 2. Press space bar until the prop is rotating as a blur 3. Press { and the engine will spark into life. If that is correct [...] If it works it can't be *totally* wrong. :-) More correct would AFAIK be: 1. { } turn left *and* right magneto switch on 2. O manually inject fuel (yes, five times Shift-o) 3. increase throttle to 1/3 (or more?) 4. SPACE fire starter cartridge 5. B release parking brake then give throttle and pull stick for better ground contact of the tail wheel. (I get best results if I do this until I lift off, others may only do it until they can raise the tail.) Don't know if flaps are recommended for take off, and how much. Vivian? You need C only to select the *next* ignition cartridge. The first one is already selected at startup, so you don't need it. (And, of course, case is important. It always is on sane systems.) To quote from the Pilot's Notes: The Pilot's Operational Handbook (POH) is available here: http://home.clara.net/wolverine/BOB/misc/Spit_Hurri_Manuals.zip Read it - the simulator is pretty close. But yes, you have summarized the start procedure. Flaps are not recommended for take-off, but the aircraft will take off if they are inadvertently extended. They blow in as speed increases anyway. Yes, keep the tail down until there is sufficient rudder authority to counter the swing to port. This is different to the real aircraft, because the backwash from the prop is not simulated. Remember to use the differential brakes to keep straight at slow speed. Don't forget the radiator flap, the door and canopy, mixture and propeller advance levers ... well you can read it in the POH. Regards, Vivian I'm still having trouble with starting the Spitfire; if I follow the start procedure, I just get a 'cough' on the starter and a fraction of a rotation. Bit like the engine has suffered 'hydraulic lock really' :-/ Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: Spitfire Starting (was FlightGear v0.9.8 onWindows XP)
On Tuesday 01 Feb 2005 18:46, Patrick DEFLANDRE wrote: 1. { } turn left *and* right magneto switch on 2. O manually inject fuel (yes, five times Shift-o) 3. increase throttle to 1/3 (or more?) 4. SPACE fire starter cartridge 5. B release parking brake I'm still having trouble with starting the Spitfire; if I follow the start procedure, I just get a 'cough' on the starter and a fraction of a rotation. Bit like the engine has suffered 'hydraulic lock really' :-/ I have the same problem. I find it start only if I replace the Space by a click on the engine starting pushbutton on the panel. (The second black one from right to left, just over the 2 fuel cock lever). Everything else is OK. Patrick DEFLANDRE Cheers, that worked. Looks like the spacebar fails to 'repeat'. Dave Martin. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Running probs
On Tuesday 01 Feb 2005 20:36, Dean Williams wrote: Trying to run flightgear on windows xp pro I choose my aircraft and the location, the loading screen starts then.nothing. It either reverts back to the initial screen or gives me this beloved message: The installaton at 0x0938b08b reference memory at 0x0b41d2ff. The memory could not be written!...whatever that means. In the flight gear launcher MSDOS screen it says: Unknown exception in the main loop. AbortingPossible cause: No such file or directory. HELP!! My OS is windows XP Pro. AMD Duron 1200Mhz (Slow, I know!) 256MB RAM, ATI Radeon 9200 128MB RAM. Are you using FlightGear 0.9.8? Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] running probs.
On Monday 31 Jan 2005 19:26, Dean Williams wrote: Hi, hope someone can help. Installed Flightgear but will not run. I choose my aircraft, the the location, the loading screen starts then.nothing. It either reverts back to the initial screen or gives me this beloved message: The installaton at 0x0938b08b reference memory at 0x0b41d2ff. The memory could not be written!...WHAT THE HELL DOES THAT MEAN Please help because it looks like a great sim. Thanks I'm guessing you're using Windows rather than Linux because that error message looks rather unintelligible? If it is a Windows error, it would be helful to people here to know what version you are running and what sort of system you have. Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] 2D-Panel for A320
On Monday 31 Jan 2005 21:32, Hans-Georg Wunder wrote: Hi all, I started to create a 2D-panel for the A320. Here is the first shot: http://home.t-online.de/home/wunder.hans-georg/A320-200_31012005.jpg You can download it from : http://home.t-online.de/home/wunder.hans-georg/A320-200_31012005.tar.bz2 You also need to install the 747, because the A320-modell refers to it. But now i got stuck, because I have 3 questions: - How can I pass a waypoint to the route-manager with Nasal ? (I want to enter the waypoint in the MCDU and pass it via Nasal to the route manager) - How can I display only a part of the speed ribbon ? - How can I improve the fonts ? Thank you for help. Can I suggest that you join the developers list and post this there too as you are more likely to be seen by people who know how to help you with the intricate details of the 2d panel system. Great work! Dave Martin. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Airports
On Wednesday 26 Jan 2005 05:30, Grayham Smith wrote: Hi all, I am running FG on Windows XP and the package is running without errors. 1/In the Airport selection menu there are some 57 US Airports to choose from. The documentation suggests there should be over 2000 airports to select from. How does one access these other airports? 2/I have the three DVD's containing worldwide scenery. The documentation describes what to do with the scenery files up to a point. e.g. unzip the files e000n20.tar.gz into the terrain directory. This intern creates a directory called e000n20 which contains many directories like e000n20,,,21,,,22,,,23,,,24. These directories each contain files like 2956160.btg.gz and 2956160.stg. This creates a directory structure and file of:- E:\flightgear\data\scenery\terrain\e000n20\e000n20\2956160.btg.gz Is this correct? It appears so. do I need to unzip the resulting .btg.gz files as they contain a .btg file? do I need to do anything with the .stg files? No. Grayham Smith... Go here, http://www.airport-technology.com/icao-codes/ pick an airfield within the US corresponding to an area of scenery that you have installed and enter it's four-letter ICAO code (LocationPosition Aircraft on ground). Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] 3D Rendering Problem
On Monday 24 Jan 2005 02:41, Li-lun Wang wrote: Hi, My computer is a ThinkPad X31 with Pentium-M 1.4G CPU and ATI Radeon Mobility M6 LY. I manually tweaked the ports tree and installed FlightGear 0.9.8 on my FreeBSD 5.3-STABLE. Everything seemed to work except that the frame rate was only around 3 fps and the CPU usage was near 100%. It seemed to me that FlightGear was not using hardware acceleration. My X-Window system is X.Org 6.8.1. According to glxinfo, the log file of X server, and the system dmesg, DRI and drm are successfully loaded and should be working. The frame rate for glxgears is 225 fps with rather low CPU usage. -- Leland Wang ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d Hi there. You will find that FG always runs at near 100% CPU usage on even quite high end systems; there is plenty for it to do when it is running the FDM (Flight Dynamics Model) and the OpenGL display simultaneously. Flightgear is also *very* GPU intensive; I would think that a Radeon M6 (16Mb DDR IIRC) may not be up to the job really. For example, I have a 'middle of the road' card by modern standards, an FX5800U with a 500Mhz core and 128Mb 1000Mhz (DDR) driven by an AMD 3200XP whith 1GB dual-channel DDR. Comparatively with your card, I get 6000-6500fps in GLXGears. On my system I can expect at most 100fps but often 50 when there is a lot of detail on screen. Runway lights really reduce the frame rate - a trip to London Heathrow at night can drag the FPS down to 15-20. The basic idea here is that running FlightGear on a mid-end laptop may not work too well. Your best options are to: always fly in daylight, reduce the FG window size, deselect specular highlights and always fly low-poly or 2d-cockpit aircraft. Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-users] EU Software Patents *Fisheries* A-List Monday (Again)
Sorry to be spammy again but I'm still firmly of the belief that this is something that could affect FlightGear or any other FOSS in future. The EU Council is once again pushing the patent bill back onto the A-List of the *Fisheries and Agriculture* meeting on Monday. This is *extremely* underhand and I am personally furious at such erosion of the democratic system in Europe. The Council has obviously realised that they could push this for a Monday meeting without having it discovered until the preceeding Friday making counteraction hard. From the FFII: On Monday, software patents are likely to be passed by the Fisheries and Agriculture Ministries. Dear FFII supporter [1], at the Agricultural Council's meeting next Monday, the Software Patent Directive is likely to be inserted into the list of agenda items in the last minute. The aim seems to be to preempt ongoing efforts in the European Parliament for a restart of the procedure. [2] Please write today to your minister of Agriculture, Fisheries and other political representatives, and ask to have the software patent directive taken off the agenda. Usable argumentation can be found on the webdemo page at http://www.ffii.org/index.en.html Kind regards, Felix Klee, Holger Blasum Please note, this method is being used (abused) to get an entirely unmoderated bill passed. If you are an EU Citizen and feel you want/need to help then please, at least sign the FFIIs protest letter: http://demo.ffii.org/cons0501/support_ltr.php Text of the letter: http://demo.ffii.org/cons0501/letter.html Many Thanks Dave Martin --- ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: Flying Helicopters ?
On Friday 21 Jan 2005 12:40, Dan Duris wrote: I also have to ask FlightGear users for implementing keyboard control for FG helicopters. I have been playing SearchRescue 2 civilian coast-guard helicopter simulator and it was possible to control it via keyboard. If they are interested, I can find manual and just write the key combinations here. Daniel The difference with SR is that it essentially stabilises the helicopter for you (or rather it uses an unrealistic flightmodel). FlightGear uses the most realistic flightmodel it can and as such the helicopter has to be finely controlled in 3-axes at all times to remain in the hover / slow flight (As in real-life) Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: Flying Helicopters ?
On Friday 21 Jan 2005 14:52, Vincent Trouilliez wrote: FlightGear uses the most realistic flightmodel it can and as such the helicopter has to be finely controlled in 3-axes at all times to remain in the hover / slow flight (As in real-life) Dave Martin About the FDM for the Heli, I would not mind having the opinion of a real Heli pilot (hopefully there is one on this list ?). The only reference point I have, is a few weeks flying the Bell 206 in Microsoft flight simulator, and that was 5 years ago, but in Fligh Gear, I feel that two things are wrong. 1) If I climb to say 2,000 feet then set collective pitch to 0%, and maintain a constant and very high speed of say 120 or 140 knots, it nonetheless takes litterally several minutes before I reach the ground, almost feeling like I didn't zeroed the collective pitch at all. Feels really weird. It 'floats' quite a bit; it would be worth asking the opinion of a real-world heli pilot on this (several frequent this list). 2) If I climb to say 2,000 feet again, then turn the engine off, I instantly lose control big time, going all over the place, instead of entering auto-rotation (sorry for the French word, don't know how it's called in English) and let me land smoothly. AFAIK the bo105 doesn't yet have a modelled clutch so when you cut the power, the engine stays connected to the rotor and causes it to slow. The bo105 looks about the same size/kind of heli as the Bell 206, so I was expecting the heli in FG to behave in the same way as the Bell 206 in MS Flight Simulator. The bo105 is actually quite different to a Bell 206; things such as non-flapping blades on the bo105 give it very different flight characteristics. Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: Flying Helicopters ?
On Friday 21 Jan 2005 16:37, Bill Galbraith wrote: Vince wrote: With zero colelctive, you should assume the flight profile of a homesick brick... Oh, sorry. In clearer terms, yes, you should fall out of the sky. So, means that either the FDM is faulty, or that the Pg Up/Dn keys can't zero the collective. In either case, it's not fixable and I can only wait and pray that it's fixed soon in a future version of the program ! :o( That's not the right attitude. You are intersted, so dig in, investigate, try some code changes, ask questions, become part of the ommunity. What a great way to learn new things, huh? Bill Well said. Vince: You can find the FDM (Flight Dynamics Model) for the bo105 in $FGROOT/data/Aircraft/bo105/bo105.xml You can find some pointers on configuring the (YASim) FDM in $FGROOT/data/Docs/README.yasim Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: Flying Helicopters ?
On Thursday 20 Jan 2005 20:21, Vincent Trouilliez wrote: With a joystick, it will be just fantastic, and once we have a few good looking heli models, it will be mind blowing ! :o)) FG is really marvelous ! :o) THe weather effect are superb, clouds, lighting effect etc. So now, all they need to do is sort out the terrain. The ground looks horrible, flat, and all the moutains are very angular, not very natural at all. That said, X-plane is just as bad in this respect, so there must be some serious technical problem that needs to be overcome here... :-/ But hopefully, nothing that the Linux community, and time, can't sort out ! :o) Don't forget that FG is a cross platform community; there are both developers and users running Linux, BSD, Windows, OSX, IRIX, Solaris etc. I'll be making some tutorials 'soon' to demonstrate how to make controls like a full-size cyclic, yoke, collective and pedals from cheap off-the-shelf joysticks and parts. Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Multiple monitors...
On Tuesday 18 Jan 2005 20:59, Bill Galbraith wrote: So, I've heard some imklings that people are using multiple monitors in their FlightGear simulations. I tried to stretch the FlightGear window across multiple monitors, but it didn't like that idea at all. Ideally, I'd like to put an instrument panel on one screen, and the out-the-window view on one or three screens, of course depending on available hardware. So, has anyone done this, is it being looked at, or will I be blazing the path on this one? Thanks, Bill Unfortunatley quite a few have been there before ;-) If you look at the bottom of the flightgear.org screenshot page there are a few examples: http://www.flightgear.org/Gallery/ Also here: http://www.flightgear.org/Projects/ALTAIR/index.html The best method for running multiple displays is to use multiple systems on a good switched network. (info in the Docs directory) Flightgear has a very comprehensive networking system to enable many 'slaved' systems to be driven by a primary. Using this method, each display or 'head' has 1 CPU(or more), 1 GPU, its own memory and each slave doesn't have to do the FDM work so the frame-rate does not suffer. You might also like to look at Open Glass Cockpit for high-quality displays: http://www.opengc.org/ This can also run 'slaved' to a FlightGear master system. Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: FW: [Flightgear-users] Multiple monitors...
On Tuesday 18 Jan 2005 23:18, Bill Galbraith wrote: How about a little What If... Run two versions of FlightGear on the same computer and slave them together internally. Yes, no, maybe? I have a wimpy little 1.7 Ghz Dell without any fancy video cards, and I can get 12 hzs in one window, and 6 hz in the other, when both are running full-up models. Thanks, Bill I'd say a tentative 'no' on that one; the 'slave' still has to load all the scenery and aircraft meshes etc and would probably still demand a fair chunk of CPU time. The best solution would be a second machine as the slave; perhaps you could stretch to a used system of simmilar specs to your current one. You can always _try_ the slave on the same machine (not sure if it works with loop-back tho) and see how it behaves. If you want to see improvements in frame-rate, a decent but low-end Nvidia GPU will help a lot. Dave Martin. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] bo105 - Always turning right?
On Monday 10 Jan 2005 18:42, Andy Ross wrote: Dave Martin wrote: I've just about got the hang of the bo105 (I think) but It continually rotates to the right in 'level-cruise'. Helicopters have no built-in stability in yaw. Under different conditions, you need to apply different rudder inputs to counter the main rotor torque and stay pointed in the same direction. I don't know if the magnitude or direction of the zero-rudder rotation is correct, but the general effect (you need to constantly be working the rudders) is definitely right. Andy ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d That I know. We were discussing that the bo105 always flies in the cruise with bank - any rudder inputs in the cruise just cause deflection from the track. (crabbing) The bo105s non-flapping rotor seems to be the reason for requiring bank to maintain a heading; have a go yourself; no ammount of rudder in any direction in the bo105 with nil-roll will prevent an inexorable turn to the right. Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Speaking of always turning...
On Monday 10 Jan 2005 20:50, [EMAIL PROTECTED] wrote: Why is it that every plane I take off in pulls to the left upon take off? I keep having to hit the right rudder to keep the plane on the runway. Wassupwiddat? :) In piston engine aircraft your are experiencing the effect of the propeller's torque forcing the airframe to turn. You may also find that you have a cross-wind (wind blowing at an angle in relation to the direction of travel) causing a 'weather-cocking' effect as the airframe tries to head into its natural aerodynamic flow. Welcome to the world of realistic flight-simulation ;-) Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-users] bo105 - Always turning right?
I've just about got the hang of the bo105 (I think) but It continually rotates to the right in 'level-cruise'. Now, I'm not a heli man myself (all my realworld experience is fixed wing) so I'm a bit rusty on the principals. I've tested this with all wind at 0 and 0 turbulence set. I've found that at any collective setting, the rate of rotation to the right in the cruise is the same. Applying left rudder(?) bar just causes a deflection into a 'crabbed' track and the aircraft continues its steady rotation to the right. - I've also checked this at various collective positions and speeds. I've found that the only way to maintain a straight track over the ground is with 10-15deg bank. Based on having watched many helis fly, I don't think they usually bank to maintain track (I could be wrong on this). So.. Can anyone fill me in? - Is the FDM doing something funny or am I way off the mark with the principals of rotary flight? Cheers Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Landing and Take-Off in Ship
On Saturday 08 Jan 2005 08:09, senthil kumar wrote: Hai, Whether it is possible to take off and land in the ship (saratoga.ac). When I try to land in ship, the aircraft enter into the carrier and finally it reach the bottom of carrier(saratoga.ac) Can anyone help me in takeoff from carrier? Yours, M.Senthil Kumar Yahoo! India Matrimony: Find your life partneronline. I'm not sure that the work on the carriers is completed yet (to make the deck solid). There is a scenario for the 'Nimitz' but that doesn't seem to be solid yet either. I should think it will be done fairly soon. (The Nimitz is looking great). Dave Martin. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: bo105 - Always turning right? - Rotor going the wrong way?
On Saturday 08 Jan 2005 17:57, Melchior FRANZ wrote: * Vivian Meazza -- Saturday 08 January 2005 18:46: My rotary wing experience is very limited, but I seem to remember that the advancing/retreating blade effect, which you correctly describe, is at least in part compensated by hinging the blades so that they flap up and down and fore and aft. Yes. But the bo105 doesn't have flapping hinges. :-) m. ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d I've just been googling about tying to find out more about the normal cruise orientation for bo105s. In my travels I discovered from several sources that on the bo105 and most other European helis, the mainrotor should rotate clockwise when viewed from above and as such, the torque forces are opposite to American helis. As far as I can discover this applies to all of the Eurocopter models which have a 'normal' configuration. As far as I can see, the animation and the torque forces on the FlightGear bo105 go in the opposite direction to the real aircraft. Dave Martin CORRECTION: Just to correct myself a moment before I was going to post. After studying several pictures of Eurocopter types, the bo105 seems to be the exception with a counter-clockwise rotating main-rotor while the others rotate clockwise. Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Flightgear not starting
On Tuesday 04 Jan 2005 17:27, Jörg Meyer wrote: Dear Flightgear gurus, can you please provide some hints? After compiling FG (v0.9.6) on a Linux (SuSE 9.1 IA32) box using - fg-base-0.9.6 - plib-1.8.3 - SimGear0.3.7 - Mesa-4.3.99 - freeglut-2.2.0 - openal-20030811-196 without any error messages and installing into /opt/FlightGear it refuses to work. The NVidia 3D-accelerated graphics driver The situation is this: - - - - - $ /opt/FlightGear/bin/fgfs --fg-root=/opt/FlightGear/data Object PanelInstruments not found Object ControlsGroup not found fgfs: pcm.c:1080: snd_pcm_writei: Assertion `pcm-setup' failed. $ /opt/FlightGear/bin/fgfs --fg-root=/opt/FlightGear/data \ --aircraft=B-52F fgfs: pcm.c:1080: snd_pcm_writei: Assertion `pcm-setup' failed. - - - - - The splash screen windows opens, remains black and closes again. Of course, there is no file called pcm.c in the source tree. What other information is needed to help solve this? Cheers, Joerg Are you using an SB Live or other SB brand card by any chance? Dave Martin ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Can't Configure Joystick
On Wednesday 22 Dec 2004 11:37, Sid Boyce wrote: With a XP2200+, it was normal, but with this XP3000+, it was a nightmare ride. Is that a Gameport joystick? - Would have thought there was an upper limit on polling at least for a gameport (baud rate) but for USB I'm not so sure. Do they behave nicely in jscal / jstest? ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Radios and other stuff.
On Tuesday 21 Dec 2004 13:10, David Megginson wrote: It took 3 months of solid 8 hours a day in aicraft radio school to learn how these systems work.And I am not sure 30 years later that I fully understand or believe what I was taught. Were you learning how to build or maintain the instruments, rather than just use them? All the best, David Depends how long ago he trained, I once saw an ancient ADF, the size of a dinner-plate. You probably had to know how to stoke the boiler on that one ;-) ___ Flightgear-users mailing list Flightgear-users@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] FG keeps crashing
On Monday 20 Dec 2004 15:54, James Nunnerley wrote: I'm running Win 2k SP2, if that helps. Probably not (sorry, but I couldn't resist :-) ) It seems to open fgfs momentarily, but then crashes. any thoughts? Can you give an idea of what hardware specifications you have? Cheers. ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Instrument Panel development tools?
Hmm, when you say you'd like to make an instrument panel - do you mean a 3d 'virtual' one such as we have in the c172p, pa28-161, 310-3d etc or a 2d panel? Incidentally - for much of the 3d modelling in FlightGear, AC3D is easiest while Blender with its .ac export filter is most powerful. As for visualisation 'while you work', I generally use trial (careful thought) and much error but its possible that there are other methods available which I haven't found yet. On Monday 20 Dec 2004 23:47, Bill Galbraith wrote: I'm looking to develop an instrument panel or more, and was wondering about tools for doing that. Ideally, what I'd like is: o Windows or Cygwin. Worst case, RedHat Linux o Free would be good. o XML support (or course) o Free (my favorite price) o A tool that allowed you to edit the code in one window of the screen, and show the rendering in another part of the screen. Being able to drive needles etc would be good too, to allow me to set up the interpolations. o Wizards or other assistance for setting up instruments would be nice too. Can anyone point me in the right direction? Thanks, Bill Galbraith ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Instrument Panel development tools?
On Tuesday 21 Dec 2004 00:47, Curtis L. Olson wrote: For visualization while you work try hitting F3 (or is it shift-F3?) One of those reloads the panel, and the other takes a screen shot, I always forget which is which. But that let's you work on your panel and see the results immediately in a live running copy of FG. Regards, Curt. I learn a new thing every day - Thanks! :-) ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-users] Software Patents.
Many of you are probably aware that the EU Council is trying to press through a draconian directive on EU software patents on Tuesday during a meeting of the Agriculture and Fisheries commision of all things. Anyway - I just received from the FFII: Dear FFII supporter [1], Please help us to stop EU Agriculture Ministers from taking a dreadful step towards software patents. This Tuesday the EU Ministers of Agriculture will be asked to vote through the Council's software patents directive text as an agenda A-item, without discussion, even though there no longer exists a qualified majority of countries in favour of it. [2] The Council text imposes unlimited patentability, with several layers of defences against any attempt at limitation. If this text text is adopted, it will be difficult to achieve a reasonable directive at a later stage of the co-decision procedure. Please help to make your Minister of Agriculture aware of the very real choice he/she has to make in the Agriculture Council on Tuesday. Please place the Please place the Open Letter http://demo.ffii.org/letter.html or the Banner http://demo.ffii.org/banner.html on your most important web page(s). Add your support to the wiki page http://demo.ffii.org/support.php This also points to pages where you may share the contact addresses of your ministry and letters already faxed to ministers of agriculture and environment. If enough supporters participate, then the story will reach media and the news will spread. Your agricultural minister then can be more easily convinced that his/her resistance is worth the effort. With kind regards, -- Gérald Sédrati-Dinet, Jonas Maebe, Felix Klee, James Heald, Peter Gerwinski, Holger Blasum, Hartmut Pilch [1] Login as dmartind in http://aktiv.ffii.org/ [2] http://kwiki.ffii.org/ConsRevers04En If you feel that Software Patents in Europe are a bad thing (and / or we are being led up the garden path by the EU council) you can at least jot your name on the Wiki above to show support. Thanks (and sorry if it seems a bit spammy but I'm furious about this). --- ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-users] C172P panel now hacked
I've done most of what I intended with the 172P now except for the landing/taxi lights on the wing (I'm having to learn a lot to get something looking good). I wanted everything to 'just work' so I re-added the alpha-layers to the textures which were transparent (you could see the panel thru the wings, seats, tail etc). Also added back the flap textures so you now see the ribs. In doing the interior texture I discovered that due to the panel sharing a texture with the interior, adding the alpha back made the panel invisible. So, I duplicated the interior texture with no alpha and applied that to just the panel and then applied the second texture to the interior with the alpha - This works fine, now the controls do not show the instruments behind. However - this is a bit of a 'hack' - is it acceptable? Also, I've reworked the panel instrument locations so they are now proportionally correct compared to a real 172. ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] C172P panel now hacked
Oops, I meant this one to go to the developers list to go with my other posts (I've been generally tidying up the 172P and getting geometries right etc.) It'd be great to see what you've done; I could certainly incorporte things that you have done while I'm at it :-) On Saturday 18 Dec 2004 23:57, Lee Elliott wrote: On Saturday 18 December 2004 22:14, Dave Martin wrote: I've done most of what I intended with the 172P now except for the landing/taxi lights on the wing (I'm having to learn a lot to get something looking good). I wanted everything to 'just work' so I re-added the alpha-layers to the textures which were transparent (you could see the panel thru the wings, seats, tail etc). Also added back the flap textures so you now see the ribs. In doing the interior texture I discovered that due to the panel sharing a texture with the interior, adding the alpha back made the panel invisible. So, I duplicated the interior texture with no alpha and applied that to just the panel and then applied the second texture to the interior with the alpha - This works fine, now the controls do not show the instruments behind. However - this is a bit of a 'hack' - is it acceptable? Also, I've reworked the panel instrument locations so they are now proportionally correct compared to a real 172. I did start on a C-172 3d model, with a view to using LODs with high-res parts for the stuff you see from the cockpit i.e. windows, front cowling etc. I can't remember exactly how far I got with it but you're welcome to a copy if you wish. LeeE ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] C172P panel now hacked
Just another thought on that; I've been reworking the 172P model so that the polygon count stays low at all distances (its the default model so high quality / polys may = bad thing for users with low-end systems). However, I do like the idea of making a very high quality C172 for use by people who do have the hardware to deal with it. This could be a totally seperate model with 'all the trimmings' :) Interestingly, I may have stumbled over a 'hack' for 3d cockpit illumination at night but I haven't tested out the idea yet. On Saturday 18 Dec 2004 23:57, Lee Elliott wrote: I did start on a C-172 3d model, with a view to using LODs with high-res parts for the stuff you see from the cockpit i.e. windows, front cowling etc. I can't remember exactly how far I got with it but you're welcome to a copy if you wish. LeeE ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] FG on Linux requirements?
Unfortunately, FG is pretty graphics-intensive and needs a recent-ish card to run well. (I've heard of it running okay on TNT class cards). I'd guess that the 8meg card would struggle with the texture sizes in FG too - some of them being fairly large. If you ask around here as to what the lowest spec card that runs FG resonably is, hopefully you can find one to buy second hand :) If the Mac version uses command line args like the Linux version, you could run it (from the CLI) with --geometry=320x200 and see if that gets everything loaded (in a small window). On Friday 17 Dec 2004 14:44, Francis X. Maier wrote: I'm trying to run FlightGear 0.9.5 on my iMac G3/350 using Ubuntu Linux. On the iMac Linux box I have 256 megs of RAM and an ATI Rage 128 RL card with 8 megs of VRAM using DRI. A variety of 3D-accelerated games run fine on my set-up. (Obviously, this is a lower-end graphics environment, but Cube, LxDoom, Tuxracer, Slune all run adequately if the window is small enough.) When I launch FG 0.9.5, it starts, but __very__ slowly, with primitive, choppy graphics -- and the scenery never seems to fully load. Am I doing something wrong? Any suggestions? Is my machine just too underpowered to run the sim? Fran ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] FG on Linux requirements?
I seem to remember that the GeForce 3ti (64MB) is available for the Mac. (some hardware differences for Mac AGP?) I had one on x86 hardware and it was a great card for the low price you can now purchase them at. On Friday 17 Dec 2004 16:12, Curtis L. Olson wrote: Dave Martin wrote: Unfortunately, FG is pretty graphics-intensive and needs a recent-ish card to run well. (I've heard of it running okay on TNT class cards). I'd guess that the 8meg card would struggle with the texture sizes in FG too - some of them being fairly large. If you ask around here as to what the lowest spec card that runs FG resonably is, hopefully you can find one to buy second hand :) If the Mac version uses command line args like the Linux version, you could run it (from the CLI) with --geometry=320x200 and see if that gets everything loaded (in a small window). I have been fortunate to be able to upgrade my computers around here, so the weakest card I have to test on is a 64Mb nvidia card. I would recommend a card with at least 32Mb of video ram, but 64 or 128 (or more) if you can get it. I don't know if you can just buy and swap video cards on the mac platform like you can on the pc platform, but between bargin basement retailers and ebay, you ought to be able to get a low end 64Mb nvidia (or ati) card really cheap these days. Curt. ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] [from AVSIM] Config file parseerror: C:/ProgramFiles/FlightGear/data/system.fgfsrc '--prop: encountered in XP
On Sunday 12 Dec 2004 11:16, Paul Surgeon wrote: Being able to select everything from inside the sim is going to make a lot of problems go away especially for noobs who don't know what a command line is. I'll bet tho that it would increase the incidence of people moaning that the aircraft is 'broken' and 'always pulling to the left'. ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] [from AVSIM] Config file parseerror: C:/ProgramFiles/FlightGear/data/system.fgfsrc '--prop: encountered in XP
On Sunday 12 Dec 2004 14:21, Roy Vegard Ovesen wrote: On the other hand we have persons that do know what a command line is. Obviously he/she who knows what a command line is also knows how an aircraft behaves, right. ;-) Thats a very good point that I hadn't thought of ;) ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-users] Something for the weekend (giggle)
I'm sure some of you will have read this before but seeing as we now have Concorde G-BOAC in FlightGear CVS, I thought we should have some proper technical documentation to go with her: From the Concorde Procedural Checklist (Emergencies - Runaway Electric Seat Procedure). 1. Initial Action: Determine which seat is running away. During the stress of routine operations, it is possible to mistake which seat is running away. Example: if the captain's seat is out of control forward, it shall appear to the captain that the first officer's is running backwards. This is a common form of disorientation and will only last until the capt. is emasculated on the control column. Do not disengage the autopilot at this time as a violent pitch down will result. In order to determine which seat is the runaway, suggested procedure is to awaken the flight engineer for trouble shooting. 2. Silence Aural Warnings: With the advent of a runaway seat, crew members describe noises of a low rumbling nature followed by the words Jesus, my seat is out of control, followed by a piercing scream of increasing intensity and pitch, especially in cases of forward runaways. As in all emergencies and in order to comply with regulations, the first officer will silence the aural warnings by clamping a hand over the captain's mouth and advise, Captain's mouth - shut. From this point on, refer to the checklist located on the underside of the captain's seat cushion. 3. Jammed Balls: Should the seat runaway in the forward mode, the ball bearings will interlock and jam the seat when it is four inches from the control panel. The seat will then be stuck in the forward position and travel no further forward, but begin traveling up in a vertical mode. The captain will advise crew, I have jammed ball, the flight engineer will immediately refer to the captain's Jammed Balls Checklist located in the aft lavatory. It is imperative that the crew check for the control column damage at this time. If the control column is broken, the crew will advise dispatch that the captain has a broken stick and jammed balls. 4. Circuit Breaker - Pull: The flight engineer at this time will pull the appropriate circuit breaker to prevent the seat from running up further in the vertical mode which could cause the bearings to overheat and possibly result in a ball burst. This would necessitate the use of the Broken Balls Checklist. Since the engineer can rarely find the correct CB, it is suggested that any CB be picked at random and pulled so as not to delay completion of the checklist. Example: Pull #1 CB; captains position will prevent him from cross-checking this step. 5. Fire, Check: When the seat bearings jam and stop forward seat travel, the electric motor may short out and start a fire under the captain, resulting in a captain's lower aft body overbeat. The flight engineer will advise the captain of the fire, to which the captain will reply Fire, my backside. 6. Seat Up - Up: Should the seat continue to run away in the vertical mode, the first officer will advise Seat up, to which it is suggested to place a pillow on the captain's head and land at the nearest suitable Airport ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] NASA Worldwind
Fedora Core 2 here but with a vanilla 2.6.9 kernel which has actually boosted performance by a fair chunk. On Wednesday 08 Dec 2004 20:02, Paul Surgeon wrote: On Wednesday, 8 December 2004 21:10, Roy Vegard Ovesen wrote: On Wednesday 08 December 2004 19:27, Paul Surgeon wrote: Sounds like a no-go to me unless you own a Micro$oft box. DirectX 9b and the .NET Runtime environment are required which probably excludes a large portion of the FlightGear community. You are right. But there are intentions to port this open source project to Linux and Mac. If I understood correctly the Mac port had a slightly higher priority. Just out of interest has anyone ever done a poll to find out who uses what OS for FG? It would be interesting and possibly useful info to see what OS's are the most popular for FG especially amongst the developer community. Paul ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-users] Hi! and Help! (Problem with ALSA errors with certain aircraft).
Hi to everyone (I'm new to the list). If anyone could possibly help me, I have a problem with using certain aircraft. The error generated (on start) is: ALSA lib pcm_hw.c:356:(snd_pcm_hw_hw_params) SNDRV_PCM_IOCTL_HW_PARAMS failed: Cannot allocate memory Aborted This error occurs after the window is spawned but before the splash-screen clears. I've tried this so far with Flightgear 0.9.6 and CVS (which I'm trying currently). I've also tried --disable-sound but this has no effect. The error only occurs with a large number certain (newer?) aircraft such as the Spitfire, Beaver, Concorde, c310-3d, DC-3 etc. The pa28-161, c172-3d all load fine and work great. Off the top of my head, I have installed: Fedora Core 2 SimGear CVS FlightGear CVS alsa 1.0.7 plib 1.8.3 And Flightgear is built with default (no configure options). Any ideas? Thanks in advance! :) ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: Hi! and Help! (Problem with ALSA errors with certain aircraft).
On Tuesday 30 Nov 2004 18:58, Melchior FRANZ wrote: I cannot say much about that very problem, but I had some sound problems in the past myself, and all of them went away after using OpenAL from their cvs (http://www.openal.org/) and recent ALSA drivers. The ones that are incorporated in the last few Linux kernels should be OK. I think there's a 2.6.* kernel available in FC2. Try that if you are still using 2.4.*. m. I hadn't thought to try updating OpenAL. So I grabbed the CVS version and rebuilt everything but unfortunately, I still get the same error :/ ALSA lib pcm_hw.c:356:(snd_pcm_hw_hw_params) SNDRV_PCM_IOCTL_HW_PARAMS failed: Cannot allocate memory Aborted Any further suggestions? Thanks. ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: Hi! and Help! (Problem with ALSA errors with certain aircraft).
On Tuesday 30 Nov 2004 20:32, Melchior FRANZ wrote: * Dave Martin -- Tuesday 30 November 2004 21:22: ALSA lib pcm_hw.c:356:(snd_pcm_hw_hw_params) SNDRV_PCM_IOCTL_HW_PARAMS failed: Cannot allocate memory Damn. And ALSA 1.0.7 *is* very recent. If you are using KDE you could try $ artsdsp fgfs If you are already running a sound daemon (esd etc.), you could try without. Apart from that I 'm afraid I'm out of ideas. m. ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d I'm usually in KDE so I tried with artsdsp but to no avail. Also tried outside of KDE etc etc :-/ Thanks for trying to help I'll have to offer this out to anyone else who might know of a solution then. Thanks. ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-users] Re: Hi! and Help! (Problem with ALSA errors with certain aircraft).
On Tuesday 30 Nov 2004 21:30, Chris Metzler wrote: The only other idea I'd have is heading off to the alsa-devel and posting. A quick Google shows that several drivers (notably the emu10k1 driver for the sblive/audigy/etc. family) have had this problem in the past, and they've worked with users to solve it and have patched the driver accordingly. -c I just had a thought - I have 2x soundcards in my system (1x SB Live and 1 AC97 onboard which is bios disabled at the moment). I could try switching these around and that should allow me to see if it is an issue caused by the hardware or a specific driver. I'll give that a try tommorow as I'm really tired and must sleep :) Thanks for the help so far everyone :) ___ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d