Menu
▾
▴
[Flightgear-cvslogs] Weekly CVS Changelog Summary: FlightGear data
|
From: Curtis L. O. <cu...@fl...> - 2006-04-23 05:07:13
|
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-16_08:09:28 (mfranz)
/var/cvs/FlightGear-0.9/data/Aircraft/ufo/ufo.nas
- fix unhiding in Dynamic.flash()
- some more comments (to make it look less messy ... or messier? :-)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-16_10:39:07 (mfranz)
/var/cvs/FlightGear-0.9/data/Aircraft/ufo/ufo-set.xml
/var/cvs/FlightGear-0.9/data/Aircraft/ufo/ufo.nas
- empty legend input field when no object is selected/available
- tweaks & cleanup
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-16_11:49:29 (mfranz)
/var/cvs/FlightGear-0.9/data/Aircraft/ufo/ufo.nas
make invisible input field less visible :-)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-16_17:24:32 (mfranz)
/var/cvs/FlightGear-0.9/data/materials.xml
add "runway boundary" and "ILS critical area boundary" glyph definitions
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-16_19:45:24 (mfranz)
/var/cvs/FlightGear-0.9/data/Scenery/Terrain/w130n30/w122n37/958416.stg
add taxiway signs to KRHV (for demonstrational purposes); There are some
missing, and others may be wrong.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-16_21:28:04 (mfranz)
/var/cvs/FlightGear-0.9/data/materials.xml
fix {start,stop}-frame for @L (Location) signs
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-16_22:05:59 (mfranz)
/var/cvs/FlightGear-0.9/data/Aircraft/ufo/ufo.nas
don't convert spaces to underscores for signs. It happens much to often
that they are added unintentionally -> just drop them
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-17_15:56:40 (curt)
/var/cvs/FlightGear-0.9/data/Input/Joysticks/SpeedLink/black-hawk-force.xml
Marc Pirrung:
I got a new joystick, a Speedlink Black Hawk (USB) with force feedback for
which I have written a setup xml file (see attachment) since with the default
setup, the rudder control didn't work.
Perhaps you could include it in the next version of Flightgear, such that
other users with the same joystick could immediately use it. The xml file
contains a description of the axis/button setup and should be self-explanatory.
I am using Windows XP but I guess the configuration should at least work on
all Windows platforms, no idea whether it works under Linux.
It would be great if one could get the vibration function to work (for
touchdown, running over uneven ground, plane stalling and the like) but I
frankly don't know how to do it. Has anybody already implemented force feedback?
Let me stress that Flightgear is a great sim and that I really enjoy it a lot!
You all are doing a great job!
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-19_17:21:21 (vmmeazza)
/var/cvs/FlightGear-0.9/data/AI/refueling_demo_1.xml
Add Air to Air TACAN. With this facility TACAN equipped aircraft can measure the range and bearing of TACAN equipped AI Aircraft. ATM there is only one assigned - callsign ESSO1 on TACAN channel 039X, but this can be easily expanded to include other c/s channel # pairs - just ask me if you want more.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-19_17:21:48 (vmmeazza)
/var/cvs/FlightGear-0.9/data/AI/FlightPlans/tanker_racetrack.xml
Add Air to Air TACAN. With this facility TACAN equipped aircraft can measure the range and bearing of TACAN equipped AI Aircraft. ATM there is only one assigned - callsign ESSO1 on TACAN channel 039X, but this can be easily expanded to include other c/s channel # pairs - just ask me if you want more.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-19_17:22:10 (vmmeazza)
/var/cvs/FlightGear-0.9/data/Navaids/carrier_nav.dat.gz
Add Air to Air TACAN. With this facility TACAN equipped aircraft can measure the range and bearing of TACAN equipped AI Aircraft. ATM there is only one assigned - callsign ESSO1 on TACAN channel 039X, but this can be easily expanded to include other c/s channel # pairs - just ask me if you want more.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-20_15:53:57 (mfranz)
/var/cvs/FlightGear-0.9/data/materials.xml
add a separate material entry for each sign's unlighted state. That's not
exactly how the material lib was designed for. Better would be selectable
sub-states within one material. But as long as only the signs need it, I'd
say we can live with that.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-20_17:16:52 (mfranz)
/var/cvs/FlightGear-0.9/data/Aircraft/Lightning/Models/lightning-f1a.ac
AJ MacLEOD: "add a refueling probe"
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-20_20:00:29 (mfranz)
/var/cvs/FlightGear-0.9/data/materials.xml
/var/cvs/FlightGear-0.9/data/Textures/Signs/Attic/empty.rgb
save some texture memory by setting a very small 8x8 texture. Otherwise
the matlib would use unknown.rgb, which is 256x256. And plib would AFAICS
load it 5 times, because it is too stupid to share the contents.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-20_20:17:49 (vmmeazza)
/var/cvs/FlightGear-0.9/data/Aircraft/tu154/tu154.xml
Bugfix: A slight adjustment to the YASim config to make the solution converge.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-20_20:29:55 (frohlich)
/var/cvs/FlightGear-0.9/data/Models/Geometry/Nimitz/nimitz.ac
Modified Files:
Tag: HEAD
./Models/Geometry/Nimitz/nimitz.ac: fix surface normals on the left
side. Fix some small holes in the deck. Fix some nonconvex deck
polygons.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-21_15:00:09 (mfranz)
/var/cvs/FlightGear-0.9/data/Textures/Signs/Attic/empty.rgb
now really empty. Kind of.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-21_19:49:44 (mfranz)
/var/cvs/FlightGear-0.9/data/Aircraft/ufo/ufo.nas
/var/cvs/FlightGear-0.9/data/Aircraft/ufo/Models/sign.ac
- make ufo import only static objects with a minimum of defined data
- turn off specular on the sign placeholder model
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-21_19:59:51 (mfranz)
/var/cvs/FlightGear-0.9/data/Aircraft/ufo/ufo.nas
whoops ... typo
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-22_06:15:06 (mfranz)
/var/cvs/FlightGear-0.9/data/Aircraft/Lightning/lightning-f1a.xml
/var/cvs/FlightGear-0.9/data/Aircraft/Lightning/lightning-set.xml
/var/cvs/FlightGear-0.9/data/Aircraft/Lightning/Models/lightning-model.xml
/var/cvs/FlightGear-0.9/data/Aircraft/Lightning/Sounds/Lightning-sound.xml
/var/cvs/FlightGear-0.9/data/Aircraft/Lightning/Sounds/motor.wav
/var/cvs/FlightGear-0.9/data/Aircraft/Lightning/Systems/instrumentation-fine.nas
/var/cvs/FlightGear-0.9/data/Aircraft/Lightning/Systems/lightning-controls.nas
/var/cvs/FlightGear-0.9/data/Aircraft/Lightning/Systems/lightning-electrical.nas
AJ MacLEOD:
"add seat height adjustment and other minor tweaks"
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-22_09:10:09 (mfranz)
/var/cvs/FlightGear-0.9/data/Models/Geometry/Nimitz/Models/red.rgb
512x512 -> 64x64
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-22_09:45:50 (mfranz)
/var/cvs/FlightGear-0.9/data/Textures/Signs/Attic/empty.rgb
now even smaller: 576 Bytes on disk, 64 bytes in memory
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-22_12:41:21 (ehofman)
/var/cvs/FlightGear-0.9/data/Models/Airport/shelter.ac
Update the dimensions and shape.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-22_12:41:44 (ehofman)
/var/cvs/FlightGear-0.9/data/Models/Geometry/sailboat.ac
Geometry update.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-22_13:40:58 (mfranz)
/var/cvs/FlightGear-0.9/data/Textures/Signs/Attic/empty.rgb
thanks to Erik's texture map I can now drop empty.rgb altogether and just
specify the same texture in the "foo.lighted" and "foo.unlighted" material
entry. This also allows to drop the state cloning and thereby solves the
most urgent apt_signs.cxx TODO. :-)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-22_13:41:04 (mfranz)
/var/cvs/FlightGear-0.9/data/materials.xml
thanks to Erik's texture map I can now drop empty.rgb altogether and just
specify the same texture in the "foo.lighted" and "foo.unlighted" material
entry. This also allows to drop the state cloning and thereby solves the
most urgent apt_signs.cxx TODO. :-)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-22_14:20:54 (mfranz)
/var/cvs/FlightGear-0.9/data/Scenery/Terrain/w130n30/w122n37/958416.stg
add two runway pointers
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-04-22_15:36:40 (mfranz)
/var/cvs/FlightGear-0.9/data/materials.xml
adjustment to the raised period to fight mipmapping artifacts
2f585eeea02e2c79d7b1d8c4963bae2d
|
