I wrote > Sent: 02 July 2007 13:15 > To: 'FlightGear developers discussions' > Subject: Re: [Flightgear-devel] [ANN] OSG - Improved Weather Radar > > > Csaba Halász > > > Sent: 01 July 2007 21:12 > > To: FlightGear developers discussions > > Subject: Re: [Flightgear-devel] [ANN] OSG - Improved Weather Radar > > > > > > Hello! > > > > Here is a new version of my radar patch. > > *** This is still for OSG only *** > > > > Theoretically the ai.diff & wxradar.diff can be applied > > without the others to get data display on the wxradar. > > *Note: I have temporarily changed the texture size to 512. > > For a 1:1 mapping this will have to be dynamic later. Any > objections? > > > > Included is a preliminary osgfont.diff that can optionally be > > applied to osg (duh). Having done that you can change the #if > > 0 in wxradar.cxx:844 and specify a truetype font in > > /instrumentation/radar/display-controls/font (I use > > VeraMono.ttf) to get nicer looking output. The ATC is > > currently nicest in 1024x768. > > > > Still on the TODO list: make more stuff configurable > > (colors), add highlight support, show taxiway designations, > > fix ATC panel bugs, support different resolutions, etc... > > > > You can get the package from > > http://w3.enternet.hu/jester/fgfs/atc-20070701.tgz [116kB] > > > > Let me know if I have broken something. > > > > You certainly have! > > That patch seem to apply cleanly here and compiles under > MSVC8, but wxradar.diff breaks the KC-135, but we knew about > that and it's readily fixable (already done and tested here). > > The new texture seems to break the whole display - it doesn't > rotate correctly, and I seem to get 2 displays. Reverting to > the one in cvs fixes it. > > There are no symbols that I can see - just 2 very small dots > which are hardly visible. > > No runways - big disappointment - should there be? > > The aircraft number selector works in the wrong sense, and > goes between 0-1, even when there are more ac on the radar > > The range selector appears to have no effect. Increments of > 1nm? Most radars I'm familiar with have steps which double > the range at each step 5, 10, 20 or 4, 8, i6, 32 are the ones > I'm most used to. > > Great text!!! Well done > > No callsigns from the Traffic Manager stuff - did we break that? > > I would think that we could get wxradar.diff into cvs, but > unless I applied the patch incorrectly (possible), the rest > needs a bit more work. > >
It helps if you put the new texture in the right place, it was the old one which broke everything. Now it works much better! I can now see symbols and the runways, and range now works. Apart from that all the above remarks still apply, with the addition that the tower position is marked with the own ac symbol - that is now selectable: <heading-marker type="bool">false</heading-marker> Display runway up? or something? Most radar displays are North up AFAIK ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
