Just getting around to finally setting up the avionics as I want - and in the free radio panel, the right hand knob from the 3d GNS430 is showing up. I haven't seen any other posts with this issue, which is odd.

 

My version is MilViz_B55_v5.120830.

 

I really want to use the free radio panel, since I only own a single RXP unit and would prefer to set that up in the same manner as my F33A.

Jim, since no one else has jumped in...

 

I don't use the free radio panel as I use both RXP 430 and 530 in the 3D panel so I can't directly answer your question, but other users have posted panel.cfg files to use a single RXP in the B55.  This gives you 3D, plus your RXP.

 

Scott

other users have posted panel.cfg files to use a single RXP in the B55. This gives you 3D, plus your RXP.

 

Thanks Scott - right now, that's how I've been using it, alongside the Milviz unit.  However, my RXP unit is the 430, which means that it's placement isn't ideal.  I'd much prefer to put it in the 2d free radio panel up higher, and then put a radio below.  The lack of 3d doesn't really bother me, since that's how I currently use it in most other planes.

 

For the Milviz admins / reps, I've attached a screenshot showing my issue:

 

 

 

(edit)

 

I should also mention that the knob is also visible in the 3d panel, with the Milviz 430 commented out and the RXP 430 in place - it's just not as obtrusive, since the RXP knob mostly covers it up. 

If memory serves the milviz parts will display if an instance of the gauge itself is in the panel.cfg, 

 

 

It may be that changing the 500 series milviz unit for the default gps will cause that bit to vanish, another option is a second RXP unit , even their WX kit would line up nicely on the 3d background.   

 

It may be that changing the 500 series milviz unit for the default gps will cause that bit to vanish, another option is a second RXP unit , even their WX kit would line up nicely on the 3d background.

 

I do very much appreciate the suggestion, but having just tried exactly that, no luck.  The bit of mesh still shows. 

 

I do realize that I am the type of person that fixates on small details, but for me this mars what is otherwise a flawless plane, and I do hope it can be fixed.

This has been reported to Milviz quite a while ago (go to the Milviz support forum for details) and they have not decided to fix it.

 

Their response was along the lines of... "we do not have RXP GNS gauges, so it is a user problem..."

 

Their response was along the lines of... "we do not have RXP GNS gauges, so it is a user problem..."

 

Which I would perfectly understand if it was in any way related to RXP gauges.  I fully understand their position on support for RXP integration.

 

However, whatever I'm wishing to use the free radio panel for is largely irrelevant.  The problem would remain even if I was just putting in the stock MS radios.  The issue of a bit of mesh / knob showing on a panel that is supposed to be blank and advertised as such is what I would like to be addressed.

 

I wasn't able to find anything on the support forum related to this, but perhaps I didn't dig far enough.  I haven't registered there, as I hate having too many registrations scattered around + I was under the impression that this was an official support forum.  If I'm wrong, then someone please let me know.. I'll register over there asap and report the issue there.

 

I do appreciate the members of this community trying to help though! 

 

Their response was along the lines of... "we do not have RXP GNS gauges, so it is a user problem..."

 

While Milviz' support for RXP integration in the B55 was always a bit, er... distant, in fairness they did end up doing a very good job of getting it to work (even if it's not perfect), and I appreciate that I can have them in the 3D panel. I hope they can continue offering such things in the future in, oh say, the MU2? <hint, hint>

 

Jim's issue seems to be something entirely different and a legitimate flaw in the free radio panel.

 

Scott

If you would like to see it changed, you'll have to go to the official support forum, I believe..

 

wasn't able to find anything on the support forum related to this, but perhaps I didn't dig far enough.  I haven't registered there, as I hate having too many registrations scattered around + I was under the impression that this was an official support forum.  If I'm wrong, then someone please let me know.. I'll register over there asap and report the issue there.

Looking into it i note the part is visibility coded too , if you comment out the instances of FBS_KAP140 in  [Vcockpit01]  and [Vcockpit04] that parts going to vanish .

 

You will be able to position the free panel assembly as wanted in theory , and assign another unit to replace the KAP140

 

Best CJ

 

Looking into it i note the part is visibility coded too , if you comment out the instances of FBS_KAP140 in [Vcockpit01] and [Vcockpit04] that parts going to vanish .

 

Thanks so much for your attempt to help.  I just checked, and commenting out the KAP140 didn't help.  In fact, just to be on the safe side, I then commented out anything and everything, and that bit still shows up, in both the 3d panel and the free radio panel.

 

When I get home tonight, I'm planning on doing a re-install from a fresh download to remove the possibility of a bad install, then I'll register on the Milviz forums and take this issue up there.

 

Interestingly enough, the P38 (which I treated myself to yesterday - hey, if my kids can have Easter candy, so can I!) uses the exact same mechanism for the radio stack, and it works perfectly fine - no out of place knobs there!

Thats an indication we are using different cfg's , there were a few in the baron to use and as the one i have in service is possibly not the same as yours it would be an idea to cut and paste the vc sections 1 to 6  ( not 7 ) from the P38 and see if that fixes it .

I have posted a solution to this last week on the Milviz site.  Completed Milviz Projects.  B55 Support Forum. Topioc titled GNS 530.  I will withhold comment on the tone you may sense from reading the entire thread.  Please reach your own conclusions.

 

http://www.milviz.com/forum/viewtopic.php?f=59&t=2890

 

I believe the following link is to a pinned topic providing corrected sections of the panel.cfg file for this.  The published instructions in the Milviz package are in error and this provides corrections.  Milviz advised me, as you will clearly read in the thread referenced above, that they would not be correcting their package.

 

http://www.milviz.com/forum/viewtopic.php?f=59&t=2897

 

I would ask all interested or concerned parties to do whatever necessary to educate developers that the reason we seek to integrate 3rd party add-ons of the quality like the GPS units from RXP are not due to dissatisfaction for the effort they put into their own products, but instead the additional functionality of superior add-ons, and in the case of RXP GPS units the NAV database updates that enrich our experience, skills, and enjoyment.  I for one am totally enjoying all of the added RNAV/GPS approaches provided by the Garmin updates that are functional in the RXP units.

No need for re-install.. Milviz have acknowledged the "flaw", but not produced a fix..

 

When I get home tonight, I'm planning on doing a re-install from a fresh download to remove the possibility of a bad install, then I'll register on the Milviz forums and take this issue up there.

 

No need for re-install.. Milviz have acknowledged the "flaw", but not produced a fix..

 

Bert,

Thanks for the help you provided for me a couple of weeks ago.  I did a side by side comparison of the VCxx sections in the Milviz RXP integration instructions and the file you sent me.  I identified some errors in the Milviz instructions and advised them.  There is now a pinned topic there in regard to this.  See the second link in my previous message this evening in this topic here.  The first link in my message points to a topic where I discussed the specifics of the errata.

 

Frank