Re: [Flightgear-devel] fgfs and bi-directional protocols
Hi Holger,Try not using the -l on netcat. The way you did it can't work because netcat is already bound to the server port , so FG can't also bind to it.Of course, you'd have to start FG first, then run the netcat. I took a look at the code in SimGear that handles this. bi still means it will be the server side of the connection, but that it will then be read/write.Don't know if this helped any, but I could see why it wasn't working so I thought I'd drop you a note. Mike. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Not only landing lights...
Ah, that explains it. Thanks for the quick response. Will await the next patch. :)Mike. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2d panel ...
On 10/23/06, syd [EMAIL PROTECTED] wrote: Hi Mike,Ive run across the same problem occasionally , with 2d panels in a 3dcockpit. I think the best solution is to addsomething like this...--- snip ---Thanks for the help, Syd! I'll try that out. Makes sense. Well, it wasn't a loss since I learned tons about z-orders in OpenGL, and how FlightGear does it, what z-order fighting is, etc... I think I figured out the problem was generally caused by the texture not having an alpha channel. But as soon as I added one, all the instruments went away. Can't win on that one... ;)Anyways, since then, I've restarted from the C172P model and added some rough pillboxes on the landing gear. Needs work, but coming along. I dropped in the right engine and prop from the c172r. Starting to look good. Now, I've got the 3 backup gauges with 3d instruments and a beginning of the PFDs (also 3d) properly placed in the cockpit. Obviously, I'm going through your Primus-1000 implementation, since it's very close to the Garmin G1000. First off, the attitude, altitude and speed displays. And thanks again for the help, and all the excellent stuff you've done in FlightGear. :)Mike. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Fix to turn co-ordinator to give me proper standard turns
So I was practicing standard turns and timing myself. By the turn co-ordinator, I would complete 180 degrees too fast. The attitude indicator showed my bank angle to be more than I expected for a standard turn as well (this is in the Cessna 172P). And I realised the problem with the 50 second standard turns I've heard about and was noticing myself are because the turn co-ordinator is off. I figured out where to put the attitude indicator for a good 180 in 60 seconds standard turn and that lead me to exactly what's wrong. The little airplane image is actually slightly too high. I have a picture of one in my book, and the plane should line up with the side bars when level, not be just slightly above it. Anyways, if you move it down by 2 in the y-transform, everything lines up properly. Just tested it and got 180 degrees in 60 seconds almost exactly with the turn indicator in the right place. Here's a patch for the very simple fix: --- turn.xml.orig 2006-10-22 02:48:27.0 -0400+++ turn.xml 2006-10-22 02:48:32.0 -0400@@ -140,7 +140,7 @@ properties' values. /transformation transformation typey-shift/type- offset8/offset+ offset6/offset /transformation /transformations /layerI also found a bug in the gear stuff in limits.nas, which I'll post in the next day or so once I get time to make sure it's all ok.Back to practicing my turns, WITH working co-ordinator. You know, you've got to love having the sources. If something doesn't work, I can just fix it. :) Later,Mike. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] 2d panel in 3d cockpit drawing over everything
Ok, I've been trying to figure out how to fix this for HOURS and I really hope someone has a clue how to fix this. I'm starting out a C172R model with the Nav III avionics (i.e. glass cockpit). So I'm trying to get the basics up and working properly from the C172R plane. If you try it out and move the yoke, you'll notice the yoke ends up rendered behind the 2d panel in the 3d cockpit. Ok, so the panel was actually a ways off the panel, which I already fixed. Still, the panel renders on top of the yoke (and other parts too like the inner Cockpit model and the seats, but not the fuselage). I've scrutinized the model in Blender and even VI, nothing looks like it could cause it that I can tell. Tried adding a depth-test tag in the panel section, which didn't work. The list goes on. This doesn't happen in the regular c172p, so I figure it must be fixable. I've practically converted it to the same as the c172p trying to fix it, but nothing seems to work.I'm sure this is relatively simple once you know - bugs usually are. Please, oh please, someone tell me you know what's going on here? :-/ As for what now works, I fixed the ailerons, which don't quite work properly. I can submit a patch to fix it in the C172R if that would be useful? Just needs some signs flipped.Thanks,Mike. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Creaking under high loads
Hi folks,I've been playing around with the c172p, trying to make it give me more feedback when I overstress the structure. I added some limits (with the script in Aircraft/Generic), which helps. I just managed to get it to creak when I go past load limits. I remember loving the creaking when doing aerobatics in Flight Unlimited long ago and wanted to have something like that in FG.First, I included the limits.nas script by adding this to the end of the nasal block at the end of c172p-set.xml: failures fileAircraft/Generic/limits.nas/file /failuresAnd added this new block:limits max-flap-extension-speed flaps0.3/flaps speed110/speed /max-flap-extension-speed max-flap-extension-speed flaps0.6/flaps speed85/speed /max-flap-extension-speed max-flap-extension-speed flaps0.9/flaps speed85/speed /max-flap-extension-speed !-- Skyhawk is in Utility Class, hence max load factors -- max-positive-g4.4/max-positive-g max-negative-g-1.76/max-negative-g vne158/vne/limitsI'm open to critique for those values. I added this to c172-sound.xml: overstress namecreak/name pathSounds/wingscreak.wav/path condition or less-than property/accelerations/pilot/z-accel-fps_sec/property value-140.8/value /less-than greater-than property/accelerations/pilot/z-accel-fps_sec/property value56.32/value /greater-than /or /condition volume offset0.8/offset /volume /overstress I can share the WAV file, of course. If you have better, please do share!Very cool, now it creaks when I dive and pull up hard. :)A few questions:1. Is there a better way to compare this against the G limits I set in the limits block without hard coding the accelerations in feet per sec^2 ? I'd rather not put the values in there, but use the configurable limits. 2. I think they should actually creak before you hit the max G's. Good as a warning. My question is: Around where should it start creaking (roughly) relative to the max G limits?I'd also love to do something with landing gear stresses in the same direction, including lateral stresses. If anyone has any ideas there, I'd love to hear them. I can't find anything about max landing gear stresses anywhere. As an aside, I've got the logging set up to give me gear compression/forces and other stats, which I'm graphing in Octave (like Matlab) to critique my take-offs and landings. Oh what fun is FlightGear! :) Thanks,Mike. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Small bug fix for Cessna Citation-Bravo radio stack
Couldn't find Syd's email address, so I figured I could get a fix to him here... And anyone having problems with the ADF down button on the Bravo's radio stack can fix it by removing that back tick character. Pure chance I noticed, but I remembered that button not working when I tried it earlier. Who knows, might already have been caught, but just in case... Hope nobody minds me posting the patch here... It's the only place I could think of to let someone know. On line 517, there's an extra character that shouldn't be there before the number. Here's a patch:*** radiostack.xml.orig 2006-10-07 03:03:19.0 -0400--- radiostack.xml 2006-10-07 03:27:17.0 -0400** 514,520 button0/button x38/x y-35/y! w`12/w h16/h binding commandproperty-adjust/command--- 514,520 button0/button x38/x y-35/y! w12/w h16/h binding commandproperty-adjust/commandAnd Syd, very nice work! Having fun with this one right now. I'd love to hear what else you might be planning on doing to it. It's great as it is, but it does look like there are a few areas still being worked on and a few things missing - not complaining here, mind you :). Would love to know what's planned for the Primus 1000's MFD stuff, and it would sure be awesome if the radar/weather stuff actually worked. Probably dreaming there :). BTW, in passing and a little off topic, if anyone knows where I can find the Bravo's rotation speed, stall speed, V1, V2, and some other useful parameters, I'd love to know exactly. WIsh there was a list like that for each aircraft. It would really help speed up learning to fly each one. I have the Primus 1000 docs, but very little for the Bravo (or any other plane). Will just have to experiment, I suppose. And thanks to everyone for such an awesome sim!Mike. - 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
