arne bartels question about your tcas radar

[Guest ridgell]

i would like to overlay your radar on the gps map.i count 6 clicks from min to max range.how would i sync. the range to the gps range?by the way i do not seem to be able to change the brightnes

[Guest bartels]

Good question, I have no idea yet. There is the variable (@g:map_ZoomFactor) in the GPS in nautic miles and it displays fine on the GPS, but how does it relate exactly to the display? If it is 10nm range on the GPS and in the mode without the rose, you get 8.5 nm to the top of the screen and 11.5 nm to the bottom, to left and right 11,8nm. (I tuned a DME and moved the aircraft so, that the center of the DME symbol was on the GPS edge). So it appears that the vertical size of the GPS map equals 2*(@g:map_ZoomFactor) even if it isn't properly centered.At the moment it is a bit of a problem to add the trafficradar to the GPS, because you can't change the center of rotation of the traffic radar. Also the traffic radar assumes a square to write on, so it's a bit work to properly align the positions, or you simply wait a day or two until I implement a non-square surface and a changeable center of rotation.As for the brightness: the values are fixed to 0..255, please note that all C: variables are local to the gauge where it is implemented, if the brightness selctor is not part of the radar gauge use L: vars and write it to (L:...)

[n4gix 4,947]

Arne, here is the C equivalent to the FS9 GPS zoom scale:/* Initialize Map Variable Arrays Indexed via Zoom Level */SINT32 map_zoomvar = 12;char *map_zoomdistance[20] = {"500'", "1000'", "1500'", "2000'", "3500'", "1.0nm", "1.5nm", "2.0nm", "3.5nm", "5nm", "10nm", "15nm", "20nm", "35nm", "50nm", "100nm", "150nm", "200nm", "350nm", "500nm" } ;FLOAT64 map_zoomfactor[20] = { 0.082290,0.164582,0.246873,0.329164,0.576037,1.0,1.5,2.0,3.5,5,10,15,20,35,50,100,150,200,350,500 } ;

[Guest bartels]

So finally found it. I didn't need the Zoom setting steps, that's something readable from (@g:map_ZoomFactor). I needed to know how many pixel represent how many nautic miles. As I presumed the GPS Zoom factor is relative to the smaller side of the view window. Normally the screen's width is greater then the height, so the height of the view window reperesents 20nm if (@g:map_ZoomFactor) is 10. If the width is smaller then the height the width of the window is 20nm if @g:map_ZoomFactor) is 10. I thought this is fixed to the original aspect ratio in the , but it isn't. If you deform the GPS window, the display on the map screen and all the symbols aren't deformed like any other gauge (and the GPS rose BTW) would be. Strange.

[n4gix 4,947]

>I thought this is fixed to the original aspect ratio in the>, but it isn't. If you deform the GPS window, the>display on the map screen and all the symbols aren't deformed>like any other gauge (and the GPS rose BTW) would be.>Strange.The way it works was by deliberate design. All the scaling/drawing of the map is done based on the size of the client side's drawing surface. It's really a very clever bit of coding on ACES' part... ;)Thanks to the pioneering efforts of Alex Drawe and yourself, using the gps.dll is working quite nicely in C++/GDI+ now... :-beerchug

[Guest bartels]

I finally finished the TrafficRadarXML.dll version 2.0. I added some teasers. Now I have 40(!) Parameters to document, that might take some time. On the other hand, I think I incorporated almost any request that came up the last weeks.