Re: [Flightgear-devel] fgfs-build cvs password
Le Friday 23 March 2007 17:59:21 cyprien, vous avez écrit : Hi all, Sorry for that stupid question, but when i'm trying to build flightgear with fgfs-build, it ask me for many password to log in cvs. I put guest everywhere and i've an error with the fgrun cvs : (i've tried also with the last version of fgfs-builder...) Logging in to :pserver:[EMAIL PROTECTED]:2401/cvsroot/fgrun CVS password: cvs login: authorization failed: server fgrun.cvs.sourceforge.net rejected access to /cvsroot/fgrun for user anonymous make[2]: *** [/home/cyprien/fgfs-builder-20061209/src/config/fgrun/cvs_passfile] Erreur 1 make[2]: quittant le répertoire « /home/cyprien/fgfs-builder-20061209 » make[1]: *** [fgrun-prepare] Erreur 2 make[1]: quittant le répertoire « /home/cyprien/fgfs-builder-20061209 » make: *** [prepare] Erreur 2 No password on souceforge, just press enter. -- Didier Fabert [EMAIL PROTECTED] KFreeFlight project : A FlightGear GUI-Frontend designed for KDE users http://kfreeflight.sourceforge.net - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] altimeter - encoder - kap140.nas
* Dave Perry -- Saturday 24 March 2007: Does anyone know what happened to John Denker? My way or the highway? I am still interested in the improved altimeter/atmosphere model being added to FlightGear. So am I. I had just done code review and pointed out why *I* didn't consider the patches in a committable state yet. Everyone was free to disagree. JD did, and it ended in a clash with notorious teacher attitude and (willful?) misinterpretation. After that *I* was no longer willing to deal with the matter. No idea about all the other developers with write access. My code review was based on what changes *I* would demand before I'd commit. After all, the one who finally commits code is really responsible for its quality, not (only) the author. Maik and Vivian can probably confirm that I take this rather seriously. :-} I keep adding these back in after cvs/svn updates. CVS is supposed to keep your local changes intact when you do a cvs up. No need to add anything back in. You can just re-submit the code. m. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] altimeter - encoder - kap140.nas
On Saturday 24 March 2007 04:01, Dave Perry wrote: Hi all, Does anyone know what happened to John Denker? I am still interested in the improved altimeter/atmosphere model being added to FlightGear. I keep adding these back in after cvs/svn updates. I think we should ask someone to add these changes into cvs now. All the patches from John Denker should be available from his web site http://www.av8n.com/fly/fgfs/ -- Roy Vegard Ovesen - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] altimeter - encoder - kap140.nas
Melchior wrote: * Dave Perry -- Saturday 24 March 2007: Does anyone know what happened to John Denker? My way or the highway? I am still interested in the improved altimeter/atmosphere model being added to FlightGear. So am I. I had just done code review and pointed out why *I* didn't consider the patches in a committable state yet. Everyone was free to disagree. JD did, and it ended in a clash with notorious teacher attitude and (willful?) misinterpretation. After that *I* was no longer willing to deal with the matter. No idea about all the other developers with write access. My code review was based on what changes *I* would demand before I'd commit. After all, the one who finally commits code is really responsible for its quality, not (only) the author. Maik and Vivian can probably confirm that I take this rather seriously. :-} True, but remember that constructive criticism is an oxymoron. :-) Vivian - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Euler rates VS body rates - what do we see in FG?
Hi Guys. Thanks for the mails. Some of the comments are 100% true (in my modest opinion), and some of them are unfortunately ... not 100% mathematically correct... What have we established: you are looking at BODY-AXIS rates and accelerations. If you are in a turn, the pitch and roll are going to show values. No: if you are looking at body rates, then pitch and yaw (q and r) should be non-zero. p,q,r are body rates. In a *steady* turn, I would expect body rates (p,q,r) to be zero. Phi, theta, psi (Eluer angles) are measured with respect to the local frame. In a steady turn, the euler *rates* would be non-zero. Nope. Not 100% true. (p,q,r) zero in steady turn: very wrong! Jon said it: Therefore q and r should have values and so should psidot, but thetadot and phidot should be zero or close to zero. I agree 100%. THANKS FOR CONFIRMATION! Before we continue... I am sticking to the definitions: phi, theta, psi / roll, pitch, yaw - Euler angles (earth ref) p, q, r - body rates (body roll rate, body pitch rate, body yaw rate if you have to - but I personnally don't really like it) Having sorted out what we SHOULD be seeing in FG is: 1) Is what is labeled in the native-fdm packet (i am receiving via UDP) as phidot, thetadot and psidot really that, or is it p,q,r - they are NOT the same thing (I think you all know it, but if there was any doubt, let's get it out the way!) 2) Did I see non-zero / near zero phidot in a constant turn? I am pretty sure I was not on drugs!! If so, what is causing this problem? Just to confirm, I ran the test a little differently this morning: I used a different machine, installation, and message interface. Yesterday I received the data via the UDP packet. This time I turned to the FG Properties drop down menu - Browse Internal Properties - Orientation. What did I find: same story... Pitch (deg): -6 Pitch-rate (deg per sec): -0.9 ... low enough ... did not spend too much time getting it perfect Roll (deg): -43 Roll-rate (degps): 6 ... too high! I check it a number of times... That would be 7 sec to get level... Yaw ... none ?? Don't understand, but not too worried. Yaw-rate: -6 (that I can believe!) Pausing in flight is not a great method. Yesterday I was monitoring all of these 6 parameters via UDP... and the results were VERY similar. I could maintain a contant bank/phi angle, and non zero phidot... So: if these are body rates (given in the internal browsing and via UDP)... then the labels/documentation is WRONG for the Native-FDM UDP packet (also on the Mathworks/Matlab site). The labels for the internal browsing is debatable if that is the case ... and even if it is body rates, q (body pitch rate if you like) should be non zero rather than p/roll rate is... Something is fishy... Who can help?? Am I missing something? Could it really be that no one else has picked it up? Are there not 100s of people using it at least in conjunction with Matlab toolboxes? I must say the idea of running the flight dynamics model as a script without need for FG sounds cool to me (an electronic/control/aero nerd in the making) :-) Thanks VERY much again for the support/emails, and having the source in public domain. AWESOME work... Let's make it even better! Cheers, Nicol. _ Share folders without harming wildlife! http://www.communicationevolved.com/en-za/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Euler rates VS body rates - what do we see in FG?
p,q,r are body rates. In a *steady* turn, I would expect body rates (p,q,r) to be zero. Phi, theta, psi (Eluer angles) are measured with respect to the local frame. In a steady turn, the euler *rates* would be non-zero. Nope. Not 100% true. (p,q,r) zero in steady turn: very wrong! Jon said it: Yes, did you see the email I sent last night? I mentioned my mistake and added more information. Can you verify which aircraft you are flying with (which FDM?)? I see you mention the Native FDM, but it's not clear what your setup is to me. I must say the idea of running the flight dynamics model as a script without need for FG sounds cool to me (an electronic/control/aero nerd in the making) :-) If you are interested in running an FDM in a standalone mode by itself (which I do for testing, and other purposes), see these references: www.jsbsim.org www.jsbsimcommander.org (for control system development in JSBSim aircraft) http://jsbsim.sourceforge.net/wiki/index.php/User%27s_Manual http://jsbsim.sourceforge.net/AutomaticFlightInJSBSim.pdf Theoretically, a JSBSim script should work the same with JSBSim by itself and with FlightGear - I designed it that way for testing. But, I haven't yet tested that capability. There would be a couple of small changes needed to allow a JSBSim script to work in FlightGear. Anyhow, it works fine by itself, which is useful in a lot of circumstances. Jon - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Euler rates VS body rates - what do we seein FG?
Nicol: If you are interested in running an FDM in a standalone mode by itself (which I do for testing, and other purposes), see these references: www.jsbsim.org www.jsbsimcommander.org (for control system development in JSBSim aircraft) http://jsbsim.sourceforge.net/wiki/index.php/User%27s_Manual http://jsbsim.sourceforge.net/AutomaticFlightInJSBSim.pdf I need to add that JSBSim Commander is under development - though it seems to work well and is fairly stable. The Automatic Flight document needs a little touch-up, and it is not up-to-date. Some new components have been added (PID, actuator) that are not included. Jon - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgfs-build cvs password
hi cyprien, for fightgear repositories use 'guest' as password (as explained at http://www.flightgear.org/cvs/anoncvs.html), for osg products just type the enter-key, but I'm not sure that your fgfs-builder version takes care about the change of osg repositories (it uses cvs, but osg is now released using svn). once you've download all the sources you want you can use a little bash script I've made to help the update of products code source and compilation using fgfs-builder. you can find it at http://seb.marque.free.fr/fichiers/flightgear/compile. if you want to use it, just place it under your fgfs-builder root directory and type ./compile hope this helps regards seb cyprien a écrit : Hi all, Sorry for that stupid question, but when i'm trying to build flightgear with fgfs-build, it ask me for many password to log in cvs. I put guest everywhere and i've an error with the fgrun cvs : (i've tried also with the last version of fgfs-builder...) Logging in to :pserver:[EMAIL PROTECTED]:2401/cvsroot/fgrun CVS password: cvs login: authorization failed: server fgrun.cvs.sourceforge.net rejected access to /cvsroot/fgrun for user anonymous make[2]: *** [/home/cyprien/fgfs-builder-20061209/src/config/fgrun/cvs_passfile] Erreur 1 make[2]: quittant le répertoire « /home/cyprien/fgfs-builder-20061209 » make[1]: *** [fgrun-prepare] Erreur 2 make[1]: quittant le répertoire « /home/cyprien/fgfs-builder-20061209 » make: *** [prepare] Erreur 2 Thanx for your help !!! - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgfs-build cvs password
Hello! The passwords should be asked for once when you run make prepare. You can then update all the sources of your enabled products by running make download. I still was not able to figure out how to build things like OSG and CGAL out of tree, so the make download may have some funny side-effects on these (like, forcing them to recompile even though I try to preserve file-dates). But I'm a bit behind on maintaining fgfs-builder anyway. Maybe it would be a good idea to include password-files with the default passwords in the distribution. I currently don't know why I didn't do so from the beginning. Cheers, Ralf - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Chat, ridealong
Ron, you wrote, 2. In-game chat, ideally with tunable private and global channels, so a teacher could communicate with their student without spamming the global chat. This is doable now. Under View-Rendering Options check Enable chat messages then open the chat window under View-Chat to input your text. Is this part of the CVS build? I'm still using the last 'official' release -- 0.9.10, not CVS, and I can't find this function in either the in-game View menu or the Advanced options in my fgrun (I'm using the Win version of FG). I've used it a few times, it seems to work. 3. Shared cockpit, even if one person must remain as a passive ride-along. Preferably with shared instrument readings. Passive ride-along should be doable now, as well: See Docs/README.IO: example to slave one copy of fgfs to another fgfs1: --native=socket,out,30,fgfs2,5500,udp fgfs2: --native=socket,in,30,,5500,udp --fdm=external This instructs the first copy of fgfs to send UDP packets in the native format to a machine called fgfs2 on port 5500. This will let you ride with a student, or a student ride with you. Cool! I'll have to check this out. Again, is this a CVS version function, or will it work on 0.9.10? Thanks for the help, Ron. Need Mail bonding? Go to the Yahoo! Mail QA for great tips from Yahoo! Answers users. http://answers.yahoo.com/dir/?link=listsid=396546091- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] what happened?
On 03/23/2007 11:01 PM, Dave Perry wrote: Does anyone know what happened to John Denker? If I thought for a moment DP sincerely cared what happened to me, it would be a touching, heartwarming moment. However, he knows full well nothing happened to me. Secondly, if he actually cared about my well-being, he would talk *to* me rather than talking *about* me on this list. He has my email address. He last wrote to me about a month ago, on 25-Feb-2007. I responded later that day. I am still interested in the improved altimeter/atmosphere model being added to FlightGear. I don't think that talking about people in insincere stage-whispers is the way to motivate them to write code. On 03/24/2007 05:07 AM, Vivian Meazza wrote: but remember that constructive criticism is an oxymoron. :-) I disagree. Numerous people on this list have cheerfully given and received constructive criticism. Recent examples that pop to mind include Jon, Ron, Roy, Stu, Alex, and others. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Interfacing Visual Basic 6 with Flight Gear 0.9.8
LucaG_libero ha scritto: and where can i find a tutorial or simple code examples? i don't need and i hope it is non necessary to write complex script.. i want to find the easiest way to have a good visualization of my platform data (latitude, long, altitude and euler angles).. sorry, but i'm not an excellent programmer - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel . On 3/21/07, LucaG_libero [EMAIL PROTECTED] wrote: hello, i'm beginning now to use flightgear simulator and i'm not a phaenomenon in programming, so i'm sorry if my questions will seem to you too much unimportant. i'm implementing an inerttial measurement platform with Gyroscope and accelerometres. i made a managment sw with VB and i need to debug and make simulations with implemented alghoritms (euler angles and quaternions). so i need to interface flightgear with visualbasic but i don't know how (i didn't find ocx controls). for example i saw the aerospace toolbox of matlab that has a bloc that interfece simulink with flightgear. i have to do the same: i hope it is simple.. simply send to the simulator Euler angles (roll pitch yaw) and position (lat lon alt) and visualize it on the simulator. is there a simple manner to do this? thank you please, can you give me any suggestions :)? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] JSB vs YAsim in FG, and pqr??
Hi guys. Nope. Not 100% true. (p,q,r) zero in steady turn: very wrong! Jon said it: Yes, did you see the email I sent last night? I mentioned my mistake and added more information. Misunderstanding, I think. What Jon said was right ;-) Any case: does not really matter who said what, as long as those contributing understand the problem... and not make it worse!! Can you verify which aircraft you are flying with (which FDM?)? I see you mention the Native FDM, but it's not clear what your setup is to me. Having had a quick look at it again, here are the results 172 flying JSB looks bad. 310 flying JSB looks bad. 310 flying YAsim looks fine. Hunter flying YAsim looks fine... But we know (well, sounds like you guys are happy) that the JSB on its own is fine. So where do we go from here? Cheers, Nicol. _ Share folders without harming wildlife! http://www.communicationevolved.com/en-za/ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] JSB vs YAsim in FG, and pqr??
Hi guys. ... Having had a quick look at it again, here are the results 172 flying JSB looks bad. 310 flying JSB looks bad. 310 flying YAsim looks fine. Hunter flying YAsim looks fine... But we know (well, sounds like you guys are happy) that the JSB on its own is fine. So where do we go from here? Try to output data using the JSBSim data logging feature and see if that data looks any better to you. I've already checked that out and it seems to be OK. Just to be clear: P, Q, R, are body rates, phi, theta, psi are euler angles relative to the local frame (X positive north and parallel to local horizontal, Y positive east and parallel to local horizontal, and Z positive down). At rest on the runway P, Q, R are zero, and phidot, thetadot, and psidot are zero. If you'd like to look at the code in JSBSim, look at FGPropagate::Run() in FGPropagate.cpp. Jon - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] what happened?
On Sat, 2007-03-24 at 12:33 -0400, John Denker wrote: On 03/23/2007 11:01 PM, Dave Perry wrote: Does anyone know what happened to John Denker? Secondly, if he actually cared about my well-being, he would talk *to* me rather than talking *about* me on this list. This is not about you. It is about getting your good work into cvs so others can benefit from that work. All my communication has been targeted at getting agreement so the improved altimeter and atmosphere model would go into cvs. Thus I wrote again today ... I am still interested in the improved altimeter/atmosphere model being added to FlightGear. Therefore I ask all interested parties on this list, what remains to make that happen? - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] JSB vs YAsim in FG, and pqr??
Any case: does not really matter who said what, as long as those contributing understand the problem... and not make it worse!! Can you verify which aircraft you are flying with (which FDM?)? I see you mention the Native FDM, but it's not clear what your setup is to me. Having had a quick look at it again, here are the results 172 flying JSB looks bad. 310 flying JSB looks bad. 310 flying YAsim looks fine. Hunter flying YAsim looks fine... If the above is true, and since the output you are getting from FlightGear is (I assume) FDM-independent, then I am confused, because (as I pointed out) JSBSim seems to give correct values by itself. Can you set up a steady turn, record the data (P, Q, R and dots of same, phi, theta, psi, and dots of those, too). I've checked the JSBSim interface with FlightGear, JSBSim.cxx, and that seems OK, too. Jon - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] radar
Hello people! Looks like radar has been broken since Revision 1.72 of AIManager.cxx some 4 months back. The radar supports a fixed number of aircraft, and the nodes for these are created at initialization. The aforementioned 1.72 revision however ignores these, and creates others. Attached simple patch (in radar.diff) should fix it, by considering any slot without an id unused. The number of allocated slots are somewhat limited but creating them dynamically does not seem to be an easy task. As a workaround I hacked together a little awk script that generates a configuration xml for any given number. (radar.awk and radar.in.xml). A pre-built radar.xml for 8 AI and 32 MP planes is included. XML is huge, but I have not run into any problems yet. YMMV. I also poked around a little more and added target selection and altitude display. (As I understand it, the altitude was only displayed for the first slot.) For this I modified 2 textures, radar_frame.rgb and radar_misc.rgb. In the latter I used some seemingly empty space for the target boxes. The target selection could be beefed up with a little nasal, so that only existing in-range targets are selected. Grab the tarball here: http://w3.enternet.hu/jester/fgfs/radar-20070325.tgz Hopefully I didn't break anything. Let me know what you think. Greets, Csaba (alias Jester) - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Chat, ridealong
On Sat, 2007-03-24 at 09:31 -0700, pebble garden wrote: Ron, you wrote, 2. In-game chat, ideally with tunable private and global channels, so a teacher could communicate with their student without spamming the global chat. This is doable now. Under View-Rendering Options check Enable chat messages then open the chat window under View-Chat to input your text. Is this part of the CVS build? I'm still using the last 'official' release -- 0.9.10, not CVS, and I can't find this function in either the in-game View menu or the Advanced options in my fgrun (I'm using the Win version of FG). Yes, it is about 5 months old in CVS. I've used it a few times, it seems to work. 3. Shared cockpit, even if one person must remain as a passive ride-along. Preferably with shared instrument readings. Passive ride-along should be doable now, as well: See Docs/README.IO: example to slave one copy of fgfs to another fgfs1: --native=socket,out,30,fgfs2,5500,udp fgfs2: --native=socket,in,30,,5500,udp --fdm=external This instructs the first copy of fgfs to send UDP packets in the native format to a machine called fgfs2 on port 5500. This will let you ride with a student, or a student ride with you. Cool! I'll have to check this out. Again, is this a CVS version function, or will it work on 0.9.10? I think this one will work on 0.9.10. Ron - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Weekly CVS Changelog Summary: SimGear
2f585eeea02e2c79d7b1d8c4963bae2d - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Weekly CVS Changelog Summary: FlightGear source
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-03-18_05:52:11 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Scripting/NasalSys.cxx
revert condition() patch. This can as easily be done in pure Nasal.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-03-18_05:52:12 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Scripting/NasalSys.cxx
revert condition() patch. This can as easily be done in pure Nasal.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-03-19_11:37:33 (mfranz)
/var/cvs/FlightGear-0.9/source/src/FDM/JSBSim/JSBSim.cxx
/var/cvs/FlightGear-0.9/source/src/FDM/JSBSim/JSBSim.hxx
/var/cvs/FlightGear-0.9/source/src/FDM/JSBSim/input_output/FGPropertyManager.cpp
/var/cvs/FlightGear-0.9/source/src/FDM/JSBSim/input_output/FGPropertyManager.h
- FGPropertyManager.{cpp,h}: fix memory corruption bug
- JSBSim.?xx: use guarded SGPropertyNode pointers
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-03-19_11:37:36 (mfranz)
/var/cvs/FlightGear-0.9/source/src/FDM/JSBSim/JSBSim.cxx
/var/cvs/FlightGear-0.9/source/src/FDM/JSBSim/JSBSim.hxx
- FGPropertyManager.{cpp,h}: fix memory corruption bug
- JSBSim.?xx: use guarded SGPropertyNode pointers
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-03-19_11:37:37 (mfranz)
/var/cvs/FlightGear-0.9/source/src/FDM/JSBSim/input_output/FGPropertyManager.cpp
/var/cvs/FlightGear-0.9/source/src/FDM/JSBSim/input_output/FGPropertyManager.h
- FGPropertyManager.{cpp,h}: fix memory corruption bug
- JSBSim.?xx: use guarded SGPropertyNode pointers
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-03-23_05:45:11 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Sound/voice.cxx
- turn \n, \t, \r into spaces. Otherwise Festival spells out .^M as
period.
- fix rather embarrassing string concatenation bug :-)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-03-23_05:45:13 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Sound/voice.cxx
- turn \n, \t, \r into spaces. Otherwise Festival spells out .^M as
period.
- fix rather embarrassing string concatenation bug :-)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-03-23_10:53:54 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Sound/voice.cxx
If text contains {display|voice} groups, skip the delimiters and
discard the display part. The curly braces wouldn't be spoken anyway,
and the | would be spoken as vertical bar, which is completely
useless (which is why it had been disabled in the past already).
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-03-23_10:53:58 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Sound/voice.cxx
If text contains {display|voice} groups, skip the delimiters and
discard the display part. The curly braces wouldn't be spoken anyway,
and the | would be spoken as vertical bar, which is completely
useless (which is why it had been disabled in the past already).
2f585eeea02e2c79d7b1d8c4963bae2d
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] radar
On Sun, 2007-03-25 at 02:14 +0100, Csaba Halász wrote: Hello people! Looks like radar has been broken since Revision 1.72 of AIManager.cxx some 4 months back. The radar supports a fixed number of aircraft, and the nodes for these are created at initialization. The aforementioned 1.72 revision however ignores these, and creates others. Attached simple patch (in radar.diff) should fix it, by considering any slot without an id unused. The number of allocated slots are somewhat limited but creating them dynamically does not seem to be an easy task. As a workaround I hacked together a little awk script that generates a configuration xml for any given number. (radar.awk and radar.in.xml). A pre-built radar.xml for 8 AI and 32 MP planes is included. XML is huge, but I have not run into any problems yet. YMMV. I also poked around a little more and added target selection and altitude display. (As I understand it, the altitude was only displayed for the first slot.) For this I modified 2 textures, radar_frame.rgb and radar_misc.rgb. In the latter I used some seemingly empty space for the target boxes. The target selection could be beefed up with a little nasal, so that only existing in-range targets are selected. Grab the tarball here: http://w3.enternet.hu/jester/fgfs/radar-20070325.tgz Hopefully I didn't break anything. Let me know what you think. Greets, Csaba (alias Jester) The radar works again! Thanks Jester! Ron - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Weekly CVS Changelog Summary: FlightGear data
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-03-18_05:52:08 (mfranz) /var/cvs/FlightGear-0.9/data/Nasal/globals.nas revert condition() patch. This can as easily be done in pure Nasal. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-03-18_08:57:32 (mfranz) /var/cvs/FlightGear-0.9/data/Nasal/props.nas add a props.condition(property) command that evaluates a property branch as condition according to the rules set out in $FG_ROOT/Docs/README.condition =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-03-18_10:49:11 (mfranz) /var/cvs/FlightGear-0.9/data/Nasal/props.nas boolify property result =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-03-19_13:17:05 (mfranz) /var/cvs/FlightGear-0.9/data/Nasal/props.nas undefined conditions are true =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-03-19_16:06:17 (mfranz) /var/cvs/FlightGear-0.9/data/Input/Joysticks/Saitek/X36.xml Anders GIDENSTAM: X36 gamport js driver =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-03-19_18:29:54 (mfranz) /var/cvs/FlightGear-0.9/data/gui/dialogs/marker-adjust.xml adjustment dialog for tutorial markers =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-03-19_18:30:22 (mfranz) /var/cvs/FlightGear-0.9/data/Models/Aircraft/marker.ac /var/cvs/FlightGear-0.9/data/Models/Aircraft/marker.xml tutorial marker and positioning cross =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-03-19_18:46:50 (mfranz) /var/cvs/FlightGear-0.9/data/Nasal/tutorial.nas major overhaul/part I: - add marker support (blinking magenta circle to point to switches etc.) - use real conditions instead of tutorial-only ones - list of error with message and condition children, instead of one error group with check items (necessary because of condition) - only one exit (use conditionand... to define a set - rename properties propvalmsg to propertyvaluemessage (consistency with other systems) - endmessage/voice instead of endtext and endtext-voice etc. - add nasal support everywhere, with separate namespace and predefined tutorial functions in it (currently only say(), next(), previous()) - make timeofday property actually work TODO: - more cleanup/re-organization - add optional view group, to direct user view to switches (for startup tutorials etc.) 2-space indentation changed to tabs (with Stuarts permission), and braces to KR style (rationale on request :-) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-03-19_18:47:40 (mfranz) /var/cvs/FlightGear-0.9/data/Aircraft/c172p/c172-tutorial.xml adapt to tutorial.nas changes =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-03-19_18:49:41 (mfranz) /var/cvs/FlightGear-0.9/data/Aircraft/Lightning/Models/lightning-model.xml - add tutorial marker object to animation xml file - adapt startup tutorial to tutorial.nas changes (blinking magenta circle over switches) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-03-19_18:49:42 (mfranz) /var/cvs/FlightGear-0.9/data/Aircraft/Lightning/Tutorials/startup_tutorial.xml - add tutorial marker object to animation xml file - adapt startup tutorial to tutorial.nas changes (blinking magenta circle over switches) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-03-19_19:07:00 (mfranz) /var/cvs/FlightGear-0.9/data/gui/dialogs/autopilot.xml fix broken and inconsistent indentation =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-03-20_11:17:47 (mfranz) /var/cvs/FlightGear-0.9/data/gui/dialogs/marker-adjust.xml - reverse longitudinal axis - add reset button (moves cursor back to origin) - make Ctrl/Shift scale movements (coarser/finer) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-03-20_11:22:26 (mfranz) /var/cvs/FlightGear-0.9/data/Nasal/tutorial.nas - add dialog wrapper, so that tutorial.dialog() typed into the Help-Nasal-Console opens the adjustment dialog - reset Nasal namespace for emebedded Nasal for every tutorial - rename voice to audio (in the hope that this won't be mixed up with Festival voice synthesis; should we call it audio-sample?) - rename instruction to message for consistency reasons, so there are now stepmessages, errormessages, and endmessages =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-03-20_11:23:23 (mfranz) /var/cvs/FlightGear-0.9/data/Nasal/props.nas better condition() comment cosmetics =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-03-20_11:25:11 (mfranz) /var/cvs/FlightGear-0.9/data/Nasal/screen.nas - trim/sanitize screen messages, so that tabs aren't displayed as question marks - make listeners one-shot (saves a couple of bytes of RAM :-) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2007-03-20_11:26:00 (mfranz) /var/cvs/FlightGear-0.9/data/Aircraft/c172p/c172-tutorial.xml adapt for tutorial.nas
