Blackbird Sims / Milviz Forum Archive

To get quick to the point. The work they have to go thru for all the numerous add-ons is insane. So with this in mind if you try the gns430-530 setup with some narly VC visual problems, as did I it was a bit disappointing. BUT they have the NEW realityXP language and I have the older ones from a few years back with WAAS. I made the popups into the RXP units but used the Milviz 430-530 VC plates stay as they are. The lighting does not get messed up nor any visuals. The interior of the units however will NOT be the Milviz but the RXP units. ONE SETBACK IS ALL CONTROLS HAVE TO BE DONE IN THE POPUPS. The whole reason for this alter is to keep a nice looking VC without any visual problems. IF YOU HAVE THE NEWER RXP UNITS ALTER ACCORDINGLY where I have my units in the PANEL.CFG. OK, first OPEN the "panel" folder. Then open PanelConfigs. MAKE A COPY OF PANELCONFIGS FIRST for a fallback. I have FSX so the WX panel does not work. If you have the proper P3D open it and you can do this to the WX panel. Now open MV-GNS430_430_Panel.cfg. or the MV-GNS430_430_WX_Panel.cfg for those who can run the weather radar. When you open Milviz MVAMS and select configuration and select DEFAULT or DEFAULT WX this panel will load up. IF YOU WANT TO KEEP THE ORIGINAL default and default WX make copys.
The newer rxpGNS's I believe have crossfill but the cool thing I like with the older ones is in the manuals there is a click spot on the 430 and 530 units which make that unit the active. So on this Milviz 310 the HSI switches between 1 and 2 vor. If a flight plan is put in the 530 and a different one in the 430 by turning on gps on that unit with it activated you can jump back and forth between units. I always check Auto CRS in the GNS configuration for the 430 and 530. The HSI then sets itself to the GPS course automatically and hitting the CLICK SPOTS with GNS turned on, on both units with different flight plans you can see the HSI quickly set the course. If this sounds a bit confusing the information is there just read it several times with testing. All changes have notes after the gauge.

// This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com
// Built Tuesday, February 13, 2018 at 15:56 FSPS Build:22767

// GNS530_GNS430

[Window Titles]
Window00=Main Panel
Window01=Throttle
Window02=C310 Prelight
Window03=FBS_GNS430_2d--leave this, it is the original Milviz
Window04=FBS_GNS530_1d--leave this, it is the original Milviz


[VIEWS]
VIEW_FORWARD_WINDOWS=MAIN_PANEL,THROTTLE_PANEL,GPS_PANEL

VIEW_FORWARD_DIR=10.000, 0.000, 0.000



//--------------------------------------------------------
[Window00]
Background_color=0,0,0
size_mm=1680,1050
window_size_ratio=1.000
position=7
visible=1
ident=0
window_size= 1.000, 1.000
window_pos= 0.000, 0.000



//--------------------------------------------------------
[Window01]
Background_color=0,0,0
size_mm=296,547
window_size_ratio=1.000
position=8
visible=0
ident=10030
window_size= 0.176, 0.514
window_pos= 0.834, 0.486
zorder=2

gauge00=C310_XMLGauges!C310_ThrottleQuad, 0,0,286,547


//--------------------------------------------------------
[Window02]
Background_color=0,0,0
size_mm=500,243
window_size_ratio=1.000
position=0
visible=0
ident=70
window_size= 0.400, 0.324
window_pos= 0.000, 0.040

gauge00=C310_XMLGauges!C310_Preflight, 0,0,500,243


//--------------------------------------------------------
[Window03]
Background_color=0,0,0
size_mm=937,390
window_size_ratio=1.000
position=7
visible=0
ident=15531
window_size= 0.340, 0.260
window_pos= 0.660, 0.728
zorder=99

gauge00=RXPGNS!GNS430, 0,0,937,390--this is to the older rxpgns purchases
//gauge00=rxpGNS2!GNS_430_2, 0, 0,937,390--this is what Milviz has which MUST be the newer purchases
;so put to slashes before the first one and remove them from the second for newer units


//--------------------------------------------------------
[Window04]
Background_color=0,0,0
size_mm=937,685
window_size_ratio=1.000
position=7
visible=0
ident=15531
window_size= 0.340, 0.421
window_pos= 0.660, 0.320
zorder=99

gauge00=RXPGNS!GNS530, 0,0,937,685--this is to the older rxpgns purchases
//gauge00=rxpGNS2!GNS_530_1, 0, 0,937,685--this is what Milviz has which MUST be the newer purchases
;so put to slashes before the first one and remove them from the second for newer units



//--------------------------------------------------------
[Vcockpit01]
file=C310_VC_01.bmp
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$C310_VC_01

gauge00=MV3DSound!MV3DS, 0,0,1,1,SimObjects\\Airplanes\\MV_C310R\\panel\\C310R_Sounds#25
gauge01=C310_XMLGauges!KR 87 ADF, 0,715,640,134
gauge02=C310_XMLGauges!C310_DME, 649,32,300,150
gauge03=MilVizC310!EDM700_L, 663,200,339,339
gauge04=MilVizC310!EDM700_R, 662,547,339,339
gauge05=C310_XMLGauges!C310_Logic, 693,11,1,1
gauge06=KAP140_HSI!MV_KAP140Servos, 0,0,1,1
gauge07=KAP140_HSI!MV_KAP140Display, 0,852,640,163
gauge08=RXPGNS!GNS430, 0,451,640,262
//gauge08=RXPGNS!GNS430, 0,451,640,262--this is what Milviz has which MUST be the newer purchases
gauge09=RXPGNS!GNS530, 0,0,640,448
//gauge09=rxpGNS2!GNS_530_1, 0,0,640,448--this is what Milviz has which MUST be the newer purchases
gauge10=Console!console_MV_530_430, 0,0,1,1--THIS MUST STAY AS IT IS THE MILVIZ PLATES or VC VISUALS
gauge11=TrueGlass!Core,0,0,1,1
;so put to slashes before the first one and remove them from the second for newer units


//--------------------------------------------------------
[Vcockpit02]
file=C310_VC_02.bmp
size_mm=512,512
visible=0
pixel_size=1024,512
texture=$C310_VC_02

gauge00=C310_XMLGauges!FBS_GTX330, 0,0,512,135


//--------------------------------------------------------
[Vcockpit03]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_1

gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller, 0,0,1024,1024,0


//--------------------------------------------------------
[Vcockpit04]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_2

gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller, 0,0,1024,1024,1


//--------------------------------------------------------
[Vcockpit05]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_3

gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller, 0,0,1024,1024,2


//--------------------------------------------------------
[Vcockpit06]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_4

gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller, 0,0,1024,1024,3


//--------------------------------------------------------
[Vcockpit07]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_5

gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller, 0,0,1024,1024,4


//--------------------------------------------------------
[Vcockpit08]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_6

gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller, 0,0,1024,1024,5


//--------------------------------------------------------
[Vcockpit09]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_7

gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller, 0,0,1024,1024,6


//--------------------------------------------------------
[Vcockpit10]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_8

gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller, 0,0,1024,1024,7


//--------------------------------------------------------
[Vcockpit11]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_9

gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller, 0,0,1024,1024,8


//--------------------------------------------------------
[Vcockpit12]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_10

gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller, 0,0,1024,1024,9


//--------------------------------------------------------
[Vcockpit13]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_11

gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller, 0,0,1024,1024,10


//--------------------------------------------------------
[Vcockpit14]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_12

gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller, 0,0,1024,1024,11


//--------------------------------------------------------
[Vcockpit15]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_13

gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller, 0,0,1024,1024,12


//--------------------------------------------------------
[Vcockpit16]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_14

gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller, 0,0,1024,1024,13


//--------------------------------------------------------
[Vcockpit17]
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$VCNL_15

gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller, 0,0,1024,1024,14

//--------------------------------------------------------
[Vcockpit18]
background_color=0,0,0
size_mm=2048,2048
pixel_size=2048,2048
texture=$Int_TG_0

texture00=TG_0, 0,0,2048,2048

//--------------------------------------------------------
[Vcockpit19]
background_color=0,0,0
size_mm=2048,2048
pixel_size=2048,2048
texture=$Int_TG_1

texture00=TG_1, 0,0,2048,2048


[Color]
Day=255,255,255
Night=85,85,85
Luminous=140,140,140

[Default View]
X=0
Y=0
SIZE_X=8192
SIZE_Y=3384

A small correction on the top of the panel.cfg. I thought I had changed this but in rechecking I had left the Milviz Default settings. I will tell you about how FANTASTIC this aircraft is and the incredible navigation possibilities with the rxp gns 430 and 530 with the Milviz HSI toggle switch, below the configuration

[Window Titles]
Window00=Main Panel
Window01=Throttle
Window02=C310 Prelight
Window03=Reality XP GNS Unit 1 (managed)
Window04=Reality XP GNS Unit 2 (managed)

I did a test flight out of KFHR. My example shows, lets say you are in IFR conditions and have no ground visuals at all. I set up a GPS flight plan to 0S9 Jefferson, on the rxp530. Now on the 430 you can set up an alternate plan. Also on the 430 on Nav 2 dial in 117.2 Pen Cove which is close by. Always keep the heading bug close to the track you are going in case you need to play around with the GNS units. On taking off I set the HSI to VOR 1, the 530 unit active. I had the 530 active with the click spot I talked about that is in the GNS manuals.The 530 CDI was on GPS. If I wanted to check where CVV 117.2 is in my route from the gns430, Autopilot to HDG then HSI to 2. Now my HSI will be able to dial in the radial to 117.2 WHILE following my track on my heading as to keep to 530 flight plan. Next scenario On this heading Clickspot on 430 and it becomes the active on HSI 1. You can now DIRECT TO 1st point on 430 flight plan. Many Many scenarios with HSI 1 and 2 GNS530 and GNS430 with the ability to be able to quickly change to active. Also GPS on the CDI on the 530 while NAV on the CDI on the 430 or vice versus. I do all my work on a second monitor with the GNS popups all the time and only use the VC gns units while flying and not fideling on the popups.
I am using FSX WITHOUT acceleration. Windows 8.1 16GB with a GTX680. CH Throttle, Ch Yoke, Elite Avionics Panel, Saitek TPM and Saitek Cessna Trim Wheel, original Microsoft Sidewinder forcefeedback Stick, Backup Saitek Multi panel. A 27" main monitor and 17" second monitor. THIS PLANE IS A KEEPER the sounds are incredible and Bernt Stolle did the flight dynamics. INCREDIBLE.

First, thank you for the detailed report. I do however have a few observations to make...

1. Why are you editing the MV_GNS530_430_Panel.cfg file? There are four config files specific for the RXP units in the ..\PanelConfigs folder.

2. You should be editing one of the RXP_xxx panel.cfg files instead

3. We provide a MV_WX.dll* that will work with FSX, so why aren't you using it? You are handicapping yourself by not trying it out.

You are entirely correct about the incredible amount of effort required for this aircraft. With five different sim versions to support, there is a total of 40 separate panel.cfg files to keep organized and chaos free. P3Dv3 and v4 require different gauges, and the panel.cfg files have to be amended accordingly.

*NB: This version of the WX Radar will only work with Milviz products, but it is included as a bonus for our customers.

I have been trying to keep my woes out of affecting anything or anybody else, but I think I need to share a possible reason for the oversite. I have been treated for years at the V.A. for uncurable cancer. Recently they put me on a Chemo I take at home everynight. After 1 month which is now it put massive ulcers and other sores in my mouth. I JUST was taken off it and am trying to heal. That said,,,,,,,probably the pain is making it more hard then I thought. I read the manual several times over etc... I appreciate the response and apologize if I did any harm etc.... sure did not mean to.. Sorry, I will be doing all reading AGAIN and AGAIN till I have all your points understood. Thanks

I did FIRST change the RXP_530_430_panel.cfg. When I choose it in the Milviz MVAM , turned on FSX, the VC had where the buttons etc.. on the GNS panels showing thru in holes. Tried many times. Thinking now because the language being used in the configurations was for the NEW units I had to alter with the OLDER language of rxp. The units I purchased are ????? ten years old with the upgrades. I never got past the unbearable site in the VC of what was happening, thus the idea to keep the original Milviz VC "plates" with ONLY the rpxGNS!GNS showing thru on the glass part. It worked! I will start from scratch again and check everything again. I do think I am correct that the entries are different from mine. EXAMPLE:

[Window04]
size_mm=100,100
window_pos=0.617188,0.707940
window_size=0.382812,0.292060
visible=1
always_visible=0
zorder=99
background_color=0,0,0
ident=15432
gauge00=rxpGNS2!GNS_430_2, 0, 0,100,100------this guage will never work with my units. It would have to be gauge00=rxpGNS!GNS430, 0, 0,100,100.
I did change ALL these to my units both the 530 and the 430 with bad results. BUT I will recheck EVERYTHING again. Thanks
I will post a picture of the result

Don't feel bad. I think Bill's questions were more curiosity than condemnatory

Oh, absolutely it was more curiosity than anything else. To be honest, I'd forgotten about the "older RXP GNS" gauges as I haven't had them working in ages, nor will they work with P3Dv4 either, so that's why I've set it up for the "new RXP GNS" gauges.

Because RXP did not supply the scripts needed for the modeldef.xml file, I had to use a "gauge overlay" for the buttons and knobs. Since the "old" and the "new" versions have the same size and form factor, using the two panel.cfg files I made for them should work just fine, and allow you to control the units from the VC. Simply substitute the gauge names in those two .cfg files, and leave the sizes and positions the same.

BTW, the VA has been very good to me with regards to my diabetes. Thankfully I don't have anything else wrong so far. I'll keep your needs in my prayers dear (new) friend!

I posted a reply but it disappeared?? Starting over. I tried uploading 2 pictures BMP's but they were rejected. First one shows the problem which the overlay does not work with the older unit .....perhaps. The second shows my alteration which does work but ,,,,is it necessary????

The second problem is with FSX running then chosing the Milviz C310R I get this message
Error
MV_Wx.dll incompatible with this simulator

I was NOT surprised as when I had FIRST read this before purchasing I assumed the WX would NOT work with FSX

Milviz 310R Redux
Enchanced and upgraded
included REX/Milviz WXR weather radar
(P3D latest versions ONLY)

Lastly... your concerns are overwhelming,,yes I am crying. Mostly out of joy. I have two autistic grand sons who at this VERY HOUR are probably moving back in with me and my wife. VERY difficult as we did this for 2 years till I was to sick. My option is I have to quit all chemo so I can raise them. Doesn't make sense but dozens of ALL options have been exhausted. Thank you so much God Bless

You are running FSX Acceleration correct?

If whatever you've done works for you, then there's no reason to do anything different! Leave it alone and just go flying...

There's certainly no harm done, and your suggested 'solution' just may be what someone else needs as well.

BTW, the installer program should have installed a version of the MV_WX.dll that works with whatever sim version you have installed.

GAUGE OVERLAY. that has to be it. I did not know how to explain the picture but that is it exactly. Everything would work BUT the overlay did NOT coverup and that is what is showing thru. Now we are on the same page. So it would have to be ANOTHER!!!!! fix to make yet ANOTHER older gns to work... I totally agree the developers are making the money at $50 a unit and SHOULD provide all the labor and work to get them into aircraft created by somebody else. You do the work, they make the money. I have been a General Contractor since the 70's and understand business. This is quite lob-sided. Carenado choose only 2 gps units to install and seem to do ok but it does stop anyone else from another choice. I stuck with the original rxp GNS 430 and 530 and bought the Flight 1 GTN750 BEFORE rxp came out with there GTN750. It was a bit confusing when flight1 popped up after years of rxp having the gns units. Thanks Keith

Regarding the WX:

JonathanBleeker wrote:You are running FSX Acceleration correct?

Supported Platforms:
• Microsoft Flight Simulator X, Service Pack
2(SP2)
(Note: Service Pack 2 is required, aircraft may not
function correctly with Service Pack 1 or earlier.
The Acceleration expansion pack is fully supported
but not required.)
• Microsoft Flight Simulator X, Steam Edition
• Lockheed Martin Prepar3D, version 2
• Lockheed Martin Prepar3D, version 3
• Lockheed Martin Prepar3D, version 4
(Note: Our product is tested with and designed to
operate in the most recent updates to Prepar3D;
this includes all hotfixes available at date of release.
For compatibility with any future updates
and hotfixes, please register for and visit our product
forums. Compatibility with future versions of Prepar3D is not implied no included.........this is from a section of the manual. I think it is the same in the Beaver

I just put this here so if anyone is curious this is from the Manual. NO to the question. I am back because I was going to clarify just that. I have just FSX sp1 and sp2. When the beaver came out only the manual said FSX sp1 and sp2 not the page that sells the aircraft. I took a chance on the beaver and the only thing that does not work is the VOR and ADF knobs on my Elite avionics and the Mag once it is moved to 1, 2 and both it cannot be turned to off or used for a mag check. On your more then awesome B55 EVERYTHING works. I have windows 8.1 and expected some difficulty with pidly things. I am COMPLETELY satisfied with the B55, Beaver and the C310R. I fly all of them often. NOTE: I own every A2a aircraft and most all of the Alabeo, Carenado aircraft which is over 50 and these 3 get plenty of hours on them. I think the C310R might pull slightly ahead of the B55. Thanks, Keith

To answer the question about which flight simulation platform. NO, I do not have acceleration. I bought FSX Deluxe Edition from a Best Buy store I think, in 2003?? I purchased the Beaver with the same expectation that somethings MAY not work. On the main page were the Beaver and the C310R are sold it does NOT list FSX sp1 with sp2. But in both manuals it does. I read both manuals before purchasing and was hoping it would work GOOD ENOUGH. Which I does. I have windows 8.1. With the Beaver the only thing that does not work is the VOR and ADF knobs being controlled by my Elite Avionics , and the Mags do not work properly. Once from a cold start moving to mag1, mag2 and both it will not go back to off or be able to do a mag check. The B55 which is MORE then what I had expected it to be, EVERYTHING on it functions with the ELite avionics. Everything works perfect.
I just sunk $400 into a processor and $600 dollars into a GTX680 in my 4 year old computer so I would NOT have to go thru Months of redoing everything. Flight simulation IS GOING TO GO TO 64BIT and everything else quickly is going to become obsolete. My computer works perfect with FSX now and that is what counts. With my age and cancer I wanted to FLY fsx instead of 90% work on computers and little flying. I am SURE that my system WILL be just an FSX memorial but will satisfy all my needs. If FSX was never considered again for any type of upgrades. I would spend no less then $3500 on a new computer to make P3D4 and the X-Plane 11 work, plus the unforeseen %50 increase of computer complexity needed as soon as a new computer is purchased. Always the story. I have purchased 25 computers so far.
One company is now selling aircraft and scenery with ONLY P3D4 in mind on some of there newer items. I would think this will be the norm. Thanks Keith

Tinian wrote:Supported Platforms:
• Microsoft Flight Simulator X, Service Pack 2(SP2)

Ah, that explains why the WX won't load. The installer contains these specific versions only: