Recommended Posts

Original implementation indeed, thanks for posting :smile:

Takes a good pair of glasses for sure!

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Re statement on previous page of this thread, where is v3.2 available from... as doing a search in the Avsim library on Rolands name, only brings up a download option for "Weather Radar VC & pop-up Gauge V 1.0"

Share this post


Link to post
Share on other sites

Thanks for clarification of that... if I had read all 26 pages, I'd probably have picked up on that.

Share this post


Link to post
Share on other sites

Hi,
Thank you, Roland, for this excellent gauge. Finally I have found the perfect replacement for the Alabeo Aztec stormscope that doesn't seem to work in P3Dv3.x.
The image shows some panel textures which are part of a repaint I have made for the Aztec.

 

https://drive.google.com/open?id=1XgpGOwZabgZksYyprNPD8BC5Wt0LtA2SNA
 

[Vcockpit02]
//gauge03=Radar_Aztec_F_250!Radar,       0,  0, 290, 291
gauge03=RolASNRadar!ORadGauge,  32,24,240,203,sweep|starton|icing

Regards.

Share this post


Link to post
Share on other sites

I assume that the gauge will not work with Active Sky 16 or will it?

Share this post


Link to post
Share on other sites

I have no idea ... until someone get the API documentation if any.

If the API is the same and the interface DLL also, there is a good chance.

 

But I saw somewhere that they are going to deliver a radar gauge with AS16 so I'm afraid the interface will disappear for 3rd party gauges.

 

Is AS16 a replacement of ASN? Not sure to understand the new HiFi product line.

 

Also I'm still waiting the API enhancement to add the vertical profile view in my gauge. My ticket has been accepted a long time ago (almost 1 year), but still nothing in the last SP5  :nea: 

Share this post


Link to post
Share on other sites

Yes, AS16 is the new version of ASN. The linkage to the radar in the PMDG aircraft is continued in AS16, so maybe the new app isn't all that different from ASN.

 

ASCA is a new companion product that adds cloud textures that change dynamically while the sim is running.

Share this post


Link to post
Share on other sites

If the PMDG radar is ok, mine should work as well. Both use the same API from ASN.

So tha't good news!

 

Can ASCA work with ASN, or do we need to move to AS16?

Share this post


Link to post
Share on other sites

According to the limited information provided so far by Hifi, ASCA works with any weather injector, but the dynamic textures only work with AS16.

Share this post


Link to post
Share on other sites

ASCA Integration for Real-Time Texture Dynamics

AS16 works with any texture/graphics add-ons (including default graphics), but when combined with ASCA, real-time texture dynamics and automatic wx-influenced selections are enabled

Share this post


Link to post
Share on other sites

Hello

Integration in the Aero commander 500S from Carenado

 

[Vcockpit01]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=513,513
texture=$Panel_1
//gauge00=GPS530_3D_A500S!GPS_530,    0,  0, 512, 372
gauge00=RolasnRadar!oRadGauge,   90, 27, 365, 275, starton|sweep|beam|icing
gauge01=CARA500S!ToggleCAR530,     64,0, 256, 32
 
fsx_2016_06_15_11_12_11.jpg

Share this post


Link to post
Share on other sites

Hi Roland, all,

Yes, the API remains and even extended further but is fully backward compatible.  All developers, please feel free to contact us for pre-release integration testing builds (support.hifitechinc.com).  We're very close now.

Share this post


Link to post
Share on other sites

Thanks a lot Damian, very good news :)

 

@Cool: nice integration, thanks for your feedback!

Share this post


Link to post
Share on other sites

Great gauge Roland.  Put it in the Just Flight DC-8-21 and seems to work great.  Have not flown yet but testing on the ground.

 

Below is my Panel.cfg for the aircraft if anyone else wants to do:

 

[Vcockpit11]

Background_color=0,0,0

size_mm=1024,1024

visible=1

pixel_size=1024,1024

texture=$AH_WXR

 

//gauge00=dc8_WRxradar!wrxradar,  123,84,769,769

gauge00=RolasnRadar!ORadGauge,  200,140,675,650, sweep|beam|icing|starton

 

Had to fuss with the size and placement for quite awhile to get it to fit.  Of course the knobs on the Just Flight dummy radar don't work but all the hot spots on Roland's Radar work as designed.

 

Thanks again Roland.


Put gauge in the Captain Sim 707-300 per post #357 from Warbirds.  Fits and displays fine but can not make any adjustments to the range, tilt, gain, mode.  No hot spots on the gauge and the Captain Sim knobs do nothing to this gauge.

 

Any ideas how to get the hot spots to work?

 

Thanks,

Share this post


Link to post
Share on other sites

Hello,

For carenado (alabeo) PA31 Chieftain 350:

 

 

[Vcockpit03]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=512,512
texture=$Panel_3
 
//gauge00=EX500_PA31350!EX500_config,       0,  0,   1,  1
gauge00=RolasnRadar!ORadGauge,70,70,370,251, sweep|beam|icing
//gauge01=EX500_PA31350!EX500,           0,  0, 513,409
//gauge02=EX500_PA31350!EX500_Update,       0,  0,   1,  1
gauge03=PA31350!Toggle10020,         0,  0, 513, 32
 
 
 
 
 

Share this post


Link to post
Share on other sites

Thanks Roland for your awesome free gauge!

 

I thought I'd post what I worked out for the Quality Wings Avro/146:

 

If you want the gauge to appear within the dummy GPS shell in the VC:

gaugexx=RolasnRadar!ORadGauge,470,513,298,215, sweep|beam|icing|starton

And if you want to use the shell that Roland supplied with the gauge you do this:

gaugexx=RolasnRadar!ShellRadGauge, 442,482,395,327, sweep|beam|icing|starton

I have found that I have to have the Fwd Console and Aft Console lights (on the pedestal) turned ON for the controls to work for either configuration.


 

Share this post


Link to post
Share on other sites

Capt. Sim L1011

 

w2_zpswoz593le.jpg

 

[VCockpit24]

size_mm=2048,2048

pixel_size=2048,2048

texture=$_24_T

background_color=0,0,0

//gauge00=l112.wxr!wr_display, 1430, 0, 618, 463

gauge00=RolasnRadar!ORadGauge, 1440, 14, 618, 463, sweep|beam|starton

Hi Paul.  Thanks for the info on putting the gauge in the CS L1011 and the 707 and 727!

 

For some reason, the mouse-over spots are not working for me in either the L1011 or the 707.  They work fine in the 727 (all variants, -100, -100F, -200, -200F).   The radar itself is fine in the L1011 and 707, just doesn't  seem to be a way to turn on/off or adjust.

 

Can you confirm if the clickspots work for you in the L1011 and 707?

Share this post


Link to post
Share on other sites

This works fine in the CaptainSim 737 too.

 

 

[Window06]
size_mm=500,500
zorder=4
gauge00=RolasnRadar!ShellRadGauge, 0,0,,, sweep|beam|icing|nogps


[VCockpit11]
size_mm=1024,1024
pixel_size=1024,1024
texture=$WXSP
background_color=0,0,0
//gauge00=Captain_Sim.x737.wxr!wr_display, 0, 500, 305, 225
gauge00=RolasnRadar!ORadGauge, 0,500,305,225, sweep|beam|icing

 

Vic

Share this post


Link to post
Share on other sites

milviz freeware p38 vc

 

p38_rxp.jpg

 

[Vcockpit05]
file=C310_VC_01_FR.bmp 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$C310_VC_05
 
//gauge00=B55_XMLGauges!FBS_GNS430_2,  0,707,640,262
gauge01=Milviz_Sound!FBGS_XMLSound,  0,0,1,1,SimObjects\\Airplanes\\MilViz P38 Lightning\\panel.Restored\\Milviz_Sounds#19
//gauge02=B55_XMLGauges!BK_AudioPanel,  0,0,640,128
gauge03=rxpGNS!GNS530,  0,0,640,468
//gauge04=B55_XMLGauges!FBS_GTX330,  0,571,640,136
gauge04=RolasnRadar!ShellRadGauge, 0,470,640,480, sweep|beam|icing 
 
besides above, the milviz default gps should be commented out if using the rxp gns530.  a small panel state gauge can be added to automatically select this panel setup, i'll need to upload it to sim outhouse. 

Share this post


Link to post
Share on other sites

I'm very happy to confirm that my radar gauge is working well with Active Sky 2016 :)

 

Thanks to HiFi to keep the API alive!

  • Upvote 1

Share this post


Link to post
Share on other sites

This is how to install radar to RAS Duke V2 without realityXP gps gauges. It is a bit complex as the gps panels of the duke are part of the 3d model. This makes any gauge installed over the gps panels to loose all or some of the click spots, so a popup gauge must be installed in order to control the vc gauge.

Ensure that you did a backup before you edit any file.

 

Here we go:

1.Open the .../RealAir Duke B60 v2/panel/config folder and edit the options.xml file with a text editor, change the 0 entry below from 0 to 20:

 

<Element>
        <Select>
            <Value>(G:Var1) 0 == if{
20 (>L:dukeRadioConfig,number) }</Value>
        </Select>
    </Element>  

 

This will change the panel configuration to 2 GPS units for Rxp gps.

 

Radar gauge installs over rh gps the usual way, but now we have more problems:

-there is no nav/com freq select panel,

-default gps cannot set nav/com freq, must be replaced or install a popup nav/com panel

-default gps popup is not synchronized with the vc gps, that means what you choose to display on the popup gps it is not displayed on the vc.(default vc gps cannot be controlled by the 3d switches as these are set for the RealityXP GPS)

-the nav/gps switch is missing

 

 

Solution:Replace the default gps with the gns530 from the freeware Douglas C117v2 by Manfred Jahn, (You can download the C117 from the simouthouse library)

 

 

1)copy FS9Garmin530_Basler.cab from the c117 panel folder and paste to the duke panel folder

2)edit the duke panel cfg as follows:

-----------------------------------------------------------------

[Window Titles]
Window00=Main Panel
Window01=GPS
Window02=WXR


[Window00]
file=2D_Help.bmp
size_mm=1024, 95
position=6
BACKGROUND_COLOR=0,0,0
visible=1
ident=MAIN_PANEL

[Window01]
size_mm=500,366    
window_size= 0.385, 0.385                        
window_pos=0.243, 0.280                                                                                     
BACKGROUND_COLOR=0,0,0
VISIBLE=0
ident=210

gauge00=FS9Garmin530_Basler!GNS530_nc1, 0,0

    
[Window02]
size_mm=100,150
position=2
visible=1
Window_pos=0.05,0.65
zorder=4
background_color=16,16,16
gauge00=RolasnRadar!oRadGauge, 0,0,100,150, sweep|beam|icing|nogps

 

---------------------------------------------------------------------------

[VCockpit01]

-

-

-
gauge19=FS9Garmin530_Basler!GNS530_nc1, 20, 660, 470, 350

//gauge19=fs9gps!RAS_gps_500, 1, 607, 502, 416
gauge20=RolasnRadar!ORadGauge, 617, 740, 305, 180, sweep|beam|icing|nogps
//gauge20=RASDuke!Blank, 0, 0, 1, 1

 

 

3)Set a key in fsx for "Nav1/GPS toggle".

 

The result:

42793128.f1c7a711.640.jpg?r2

 

 

Controls:

-GPS and nav/com freq through the GPS popup (SHIFT+2)

-Radar on/off/test and gain with vc clickspots, all controls with popup (SHIFT+3)

-Nav/GPS toggle with assigned key

Share this post


Link to post
Share on other sites

Wow, the most complex integration I've seen so far!

Congratulation

I'm quite surprised it works as the ASN/AS16 API can not normally handles 2 simultaneous clients, the VC + Popup.

 

Is the popup display correct?

  • Upvote 1

Share this post


Link to post
Share on other sites

I did the original RA tduke v1 wxr integration with rxp gps and it requires 2d pop up to use all 4 click spots. The 2d gauge display becomes all gray but click spots work to operate wx gauge in 3D panel.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now