[Flightgear-devel] Re: Autopilot
* Buchanan, Stuart -- Wednesday 30 November 2005 18:27: > I would think the .nas file for the KAP140 should be able to > disable the appropriate parts of the menu tree dynamically when initialized. What should be disabled? Only the "Autopilot settings" entry, or the whole "Autopilot" menu? I wouldn't add this to the KAP140, though, but rather to gui.nas' INIT function. (Currently we operate with full property paths, and when someone inserts a menu entry, the full paths might not address the same menu entry. Better have everything in the same place if possible. At least for now. I think about adding tags to menu entries that are to be disabled/enabled for safe access.) m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Help with Multiple Instances
Also, I got a tip concerning the views to use the "--view-offset" parameter, but I tested it out just using a command line such as: c:\Program Files\FlightGear\bin\win32>fgfs.exe --fg-root="c:\Program Files\FlightGear\data" --view-offset=-45 and the view didn't change at all. I tried putting the value in () and "" but nothing worked. Is my syntax wrong or am I leaving out a necessary parameter or what? It seems pretty straight forward but is producing no change. I used the "--fov" parameter to mess around with it and it worked fine, but nothing on the view offset. Thanks -Ryan ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Help with Multiple Instances
[EMAIL PROTECTED] wrote: Also, I got a tip concerning the views to use the "--view-offset" parameter, but I tested it out just using a command line such as: c:\Program Files\FlightGear\bin\win32>fgfs.exe --fg-root="c:\Program Files\FlightGear\data" --view-offset=-45 and the view didn't change at all. I tried putting the value in () and "" but nothing worked. Is my syntax wrong or am I leaving out a necessary parameter or what? It seems pretty straight forward but is producing no change. I used the "--fov" parameter to mess around with it and it worked fine, but nothing on the view offset. Thanks For setting up slaved visual channels, here are some of the options I have used: --enable-game-mode (--enable-fullscreen depending on glut vs. sdl) --prop:/sim/menubar/visibility=false --prop:/sim/ai/enabled=false (prevents the ai ATC text at the top of the screen.) --prop:/sim/ai-traffic/enabled=false (prevents strange planes from flying across a single view) --prop:/sim/rendering/bump-mapping=false --fov=35 --prop:/sim/view/config/heading-offset-deg=-35 --prop:/sim/view/config/pitch-offset-deg=3 --native-fdm=socket,in,60,,5505,udp --native-ctrls=socket,in,60,,5506,udp --fdm=null Regards, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Autopilot GUI
On Wed, 07 Dec 2005 12:00:22 -0600, you wrote: >What should be disabled? Only the "Autopilot settings" entry, or the >whole "Autopilot" menu? I wouldn't add this to the KAP140, though, >but rather to gui.nas' INIT function. (Currently we operate with >full property paths, and when someone inserts a menu entry, the >full paths might not address the same menu entry. Better have >everything in the same place if possible. At least for now. >I think about adding tags to menu entries that are to be >disabled/enabled for safe access.) What if the Autopilot menu entry was bound to a function in gui.nas that looks at a property for the location of the autopilot dialog. The default could point to the existing one, but an aircraft could specify the location for the autopilot it was using. I am not sure this is possible with the existing way configuration files work. The existing Autopilot settings menu could be seen as applying to the default autopilot now, and could be replaced for each autopilot. The configuration file could even be moved to the generic instruments folder or somewhere. You could have a null autopilot for when an aircraft does not define one. It asks a lot of non-technical users to modify the menubar.xml to add the dialog for an autopilot. I am happy supporting enabling/disabling a menu item, but an item still must be added to the menu bar manually, unless I am missing something. -sek ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: gui menu disable/enable diff
On Tue, 06 Dec 2005 12:41:02 -0600, you wrote: >* Melchior FRANZ -- Tuesday 06 December 2005 17:50: >> http://members.aon.at/mfranz/menu_disable.diff [5 kB] > >Committed. And I forgot to mention in the cvs log message: >OK'ed by Erik. :-) Oops, I missed this. Will update my cvs. -sek ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Autopilot GUI
* Steve Knoblock -- Wednesday 07 December 2005 20:35: > >What should be disabled? Only the "Autopilot settings" entry, or the > >whole "Autopilot" menu? > What if the Autopilot menu entry was bound to a function [...] Thanks, but I didn't ask *how* to do it (which I know pretty well), but *which* *entry* to disable. I assume that the whole "Autopilot" menu isn't functional when using the KAP140 (waypoints etc.). m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Autopilot GUI
* Melchior FRANZ -- Wednesday 07 December 2005 21:00: > * Steve Knoblock -- Wednesday 07 December 2005 20:35: > > What if the Autopilot menu entry was bound to a function [...] > > Thanks, but I didn't ask *how* to do it [...] But, yes, I had planned to let menubar.xml just call gui.autopilot(), which would then by default open the dialog that it opens now. And everyone could redefine gui.autopilot() to open some other dialog or do other fancy stuff. :-) m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] 2D-Panel for 707
Hi all, just for your information. I'm still working on a 2D-panel for the 707: http://wunderhg.homepage.t-online.de/fgfs-screen-016.jpg In the next weeks, I will release a first version. Kind regards Hans-Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 2D-Panel for 707
Hans-Georg Wunder schrieb: Hi all, just for your information. I'm still working on a 2D-panel for the 707: Hi Hans-Georg, looks really impressive, this old style layout with all the "clocks" :-) Your work will be a good reason to try to fly the old lady and rembering the days when I was young (707 and Caravelle were very impressive for me those days). Georg EDDW BTW: what city is displayed in your screenshot? ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Flight Director
I'm thinking of doing some work to impliment a flight director (such as the bendix-king KFC 200.) Has anyone made an AI that includes a movable "V-bar"? Thanks, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Black and White mode
Is there a way to configure FlightGear to display black and white imagery? I'd like to be able to switch between color and black & white modes during a sim session. Thanks, Drew ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 2D-Panel for 707
Absolutely great! Thanks:-) - Original Message - From: "Hans-Georg Wunder" <[EMAIL PROTECTED]> To: "FlightGear developers discussions" Sent: Wednesday, December 07, 2005 7:47 PM Subject: [Flightgear-devel] 2D-Panel for 707 Hi all, just for your information. I'm still working on a 2D-panel for the 707: http://wunderhg.homepage.t-online.de/fgfs-screen-016.jpg In the next weeks, I will release a first version. Kind regards Hans-Georg -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.13.12/194 - Release Date: 7/12/2005 ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 2D-Panel for 707
Georg Vollnhals wrote: > BTW: what city is displayed in your screenshot? According to the buildings this must be Paris (find the large TV set right hand behind the turtle :-) I'm surprised to see such a panel layout - it's almost as flat and straight as your C172's are. Did the early airliners really have such a simple panel layout ? Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] 2D-Panel for 707
Hans-Georg Wunder writes Hi all, just for your information. I'm still working on a 2D-panel for the 707: http://wunderhg.homepage.t-online.de/fgfs-screen-016.jpg In the next weeks, I will release a first version. Nice one Hans-Georg that is one less job I need to do.Look forward to using it. Kind regards Hans-Georg Cheers Innis ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 2D-Panel for 707
Martin Spott schrieb: Georg Vollnhals wrote: BTW: what city is displayed in your screenshot? According to the buildings this must be Paris (find the large TV set right hand behind the turtle :-) Thank you, next flight from LFPG Charles de Gaulle airport, checking :-) I'm surprised to see such a panel layout - it's almost as flat and straight as your C172's are. Did the early airliners really have such a simple panel layout ? Cheers, Martin. I think he did it in a functional style like many of the old MSFS panels were as I remember. Parts of the side panel (flight ing) also integrated. You may hate this or love it. After my opinion the combination of a nice 3D-panel where you have all the things at the right place and the instruments in sight although you are not looking straight forward and a 2D "working" panel where you have all necessary information concentrated and readable is the best. The pros and cons of 3D panels with very small instruments have already been discussed in this forum, I don't want to get back again, but although I use a 19' display many instruments (ie. b1900, citation) are not readable without zooming onto them and that is sometimes a real pain if you are flying a more complicated approach. For that purpose a more "composed" 2D panel with big readable instruments and all necessary information needed is more functional than the 3D variant. If I am not wrong it is already possible to switch between the 3D panel and the 2D panel by the "s" key??? So you could choose what you want for every flight situation. Regards Georg EDDW ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Flightgear-devel Digest, Vol 32, Issue 22
Hi Curt, the B1900D and Bravo have flight director bars as separate movable objects ... just waiting for a flight director :) Syd ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Flightgear-devel Digest, Vol 32, Issue 22
syd wrote: Hi Curt, the B1900D and Bravo have flight director bars as separate movable objects ... just waiting for a flight director :) Perfect, thanks! I'll take a look at those. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] RenderTexture bug
https://bugs.freedesktop.org/show_bug.cgi?id=5142 So, the problem seems to be that pbuffer is not supported? Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Flight Director
On Wednesday 07 December 2005 03:54 pm, Curtis L. Olson wrote: > I'm thinking of doing some work to impliment a flight director (such as > the bendix-king KFC 200.) Has anyone made an AI that includes a movable > "V-bar"? I had a split axis type flight director working in the 737 panel back when I was making an autoflight system for it. It just displayed values from the middle of the controller cascades. I've since dropped it and lost all the work, but I can say it's do-able. Never did like the Collins style v-bar thingy. Dave ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] RE: Help with Multiple Instances
>For setting up slaved visual channels, here are some of the options I >have used: > >--enable-game-mode (--enable-fullscreen depending on glut vs. sdl) >--prop:/sim/menubar/visibility=false >--prop:/sim/ai/enabled=false (prevents the ai ATC text at the top of the >screen.) >--prop:/sim/ai-traffic/enabled=false (prevents strange planes from >flying across a single view) >--prop:/sim/rendering/bump-mapping=false >--fov=35 >--prop:/sim/view/config/heading-offset-deg=-35 >--prop:/sim/view/config/pitch-offset-deg=3 >--native-fdm=socket,in,60,,5505,udp >--native-ctrls=socket,in,60,,5506,udp >--fdm=null > > >Regards, > >Curt. Could you explain in a little more detail some of what these options do such as "fdm=null", "bump-mapping", etc? Also, using these options how would you output the fdm and ctrls from the master? I'm guessing something like "--native-fdm=socket,out,60,(ip address),5505,udp", but just want to check. I had previously be using just "native=socket,out,30,(ip address),5500,udp" and this did not produce the correct results. I'm guessing the way you suggested is the correct way? Also, is 35 the default field of view? I think this is all for now. Thanks for the help. -Ryan ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
