April 2, 201313 yr The Milviz RealityXP panel has been around for quite some time.Is it the same panel cfg I gave to Bert 22Dec2012 (post # 30 and #31 here)?:http://forum.avsim.net/topic/393504-b55-gps-knobs/ Best Regards, Vaughan Martell PP-ASEL KDTW
April 2, 201313 yr Vaughan, Thank you. I was not aware of that thread here at Avsim and I am now totally incensed at Milviz. If you re-read that thread here, then follow the link above I provided to my recent thread on the Milviz site you will see that a) Milviz promised both here and there that they would post a correction on their site but failed to do so; and that they never acknowledged the discussion here (with solution) in my inquiries on their site. c) they also did not follow Bert's suggestion that they update their package with corrections. I purchased the B55 some 20+ days later and spent hours of repeated attempts with their instructions, pushed onward in that by insistence on their site by one of their team members that the faulty instructions were correct, despite the Milviz acknowledgement here on Dec 21 or 22 that new instructions were to be posted on their site. Clearly they already knew of the problem but did not acknowledge that to me. Another user was going through the same drill on their site last week, and now yet another here this week. What a shame! Thank you for the work you did and what you provided to Bert. He passed it on to me after I inquired of him after my failures. Highest regards, Frank Frank Patton Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener. Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126 "I will never put my name on a product that does not have in it the best that is in me." - John Deere
April 2, 201313 yr Author Commercial Member Well - again, I appreciate all those from this community that have offered advice and tried to help. I fear I have muddied things up a bit by stating my intended use of the free radio panel. I should have never mentioned RXP. The issue is present regardless of the intended use; one could just as easy be perplexed by it if they were intending on putting in a couple of Bendix King radios in the free panel, and leaving the Milviz GPS units in the 3d panel. I initially thought the issue might be as simple as removing some mesh in a model, however I see that they have some fancy coding going on: Not only is the free radio toggle switch placing a panel over top of the original 3d panel (I believe the 3d faces for the ADF and the AP units are always there), but then they've tried to accommodate our RXP requests by enabling / disabling 3d panels for their units and the RXP units. The bug must be in that coding somewhere; he knob that I've posted a picture of simply isn't behaving properly. I kind of feel perplexed and conflicted here - I appreciate the attempts at RXP integration on the part of Milviz, I understand that there is no support for the RXP units, I also believe that this bug is a direct result of their attempt to try and accommodate a common and loud community request... but at the same time I'm kind of peeved that because of the association with RXP, this bug gets filed under a 'no support provided for RXP units' category, when it affects all users, even those who would not be using RXP at all, but wish to use the free radio panel for other purposes. I will be registering on the Milviz forums and reporting this bug there, but I will be refraining from mentioning RXP, since it is unrelated from a user perspective, as well as seeming to be a sore spot. Jim Stewart Milviz Person.
April 2, 201313 yr Jimmy, Try using these file contents as a test and see if the 3D knob is still there. You can comment out the RXP lines in VC03 and VC04 and see what presents itself then. The folks at Milviz I believe intended that toggle switch to control whether you get VC03 and VC04 -or- VC05 and VC06. What I believe I found was multiple instances of the GTX330, and that their own GNS430 and GNS530 in VC05 were still affecting the panel presented on the other side of the toggle switch. If you read my annotated message in that GNS 530 topic on the Milviz site you will see my comments in red and blue indicating the exceptions. Hope that helps you with your intended use. [Vcockpit01] file=C310_VC_01.bmp size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$C310_VC_01 gauge00=MilVizC310!MilVizC310_XMLSound, 657,4,17,16 gauge01=B55_XMLGauges!FBS_KAP140, 0,767,640,163 gauge02=B55_XMLGauges!FBS_KR 87 ADF, 0,630,640,134 gauge03=B55_XMLGauges!B55_DME, 649,32,300,150 gauge04=B55_XMLGauges!B55_Preflight, 0,0,1,1 //-------------------------------------------------------- [Vcockpit02] file=C310_VC_02.bmp size_mm=512,512 visible=0 pixel_size=1024,1024 texture=$C310_VC_02 gauge00=B55_XMLGauges!FBS_GTX330, 0,376,512,136 //-------------------------------------------------------- [Vcockpit03] Background_color=0,0,0 size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$C310_VC_03 gauge00=rxpGNS!GNS430_2, 0,10,1024,433 //-------------------------------------------------------- [Vcockpit04] Background_color=0,0,0 size_mm=512,512 visible=0 pixel_size=1024,1024 texture=$C310_VC_04 gauge00=rxpGNS!GNS530, 0,8,512,384 [Vcockpit05] file=C310_VC_01_FR.bmp size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$C310_VC_05 gauge00=MilVizC310!MilVizC310_XMLSound, 657,4,17,16 gauge01=B55_XMLGauges!BK_AudioPanel, 0,0,640,128 //-------------------------------------------------------- [Vcockpit06] file=C310_VC_02_FR.bmp size_mm=512,512 visible=0 pixel_size=1024,1024 texture=$C310_VC_06 gauge00=B55_XMLGauges!FBS_KAP140, 0,106,512,131 gauge01=B55_XMLGauges!FBS_KR 87 ADF, 0,0,512,106 Frank Patton Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener. Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126 "I will never put my name on a product that does not have in it the best that is in me." - John Deere
April 2, 201313 yr Jim's post mentioned .. this is not RealityXp related. The knob is visible .. in the blank panel. Replacement gauges can try to hide it. Best Regards, Vaughan Martell PP-ASEL KDTW
April 2, 201313 yr https://www.dropbox.com/s/vz83r7owq2anzgz/Beech_Baron_55_I.zip?m The above is a link to a revised model, the knobs visibility tag has been in theory rectified to vanish when its supposed to, back up the original .mdl's and insert in both the B55 & E version. This should this take care of the issue , upon confirmation it will be bundled up for distribution. Best CJ
April 2, 201313 yr Nice to see a fix posted! I tested it with my RXP retrofit.. This works nicely for the Freeradio model - less so for the 3d model (where the black post was less noticeable, so the fix is less important..). Bert
April 2, 201313 yr Tried it some more - and I am quite happy to fly with the Freeradio panel exclusively.. Thanks for the fix! :rolleyes: Follow-on question.. Is there a way to select the Freeradio panel as the default, so I do not have to flip the switch to select it? Bert
April 2, 201313 yr I have not downloaded the fix yet. So, just to verify. Are these double knobs the 3D fix? Best Regards, Vaughan Martell PP-ASEL KDTW
April 2, 201313 yr @@Bert Pieke > If you dont mind adding a gauge to the panel .cfg there is a way of having the Free Panel there on startup , place the cabfile here in your panel folders and add the line > gaugeXX=Freepanel_ON!Freepanel_ON, 2,2,1,1 like in [Vcockpit01] below . Download [Vcockpit01]file=C310_VC_01.bmpsize_mm=1024,1024visible=0pixel_size=1024,1024texture=$C310_VC_01 gauge00=MilVizC310!MilVizC310_XMLSound, 657,4,17,16gauge01=B55_XMLGauges!FBS_GNS430_2, 0,367,640,262gauge02=B55_XMLGauges!FBS_KAP140, 0,767,640,163gauge03=B55_XMLGauges!FBS_KR 87 ADF, 0,630,640,134gauge04=B55_XMLGauges!B55_DME, 649,32,300,150gauge05=B55_XMLGauges!B55_Preflight, 0,0,1,1gauge06=Freepanel_ON!Freepanel_ON, 2,2,1,1 @ vonmar > try the mdl and verify with your setup , there will be a compilation of the completed solution and your help in pinning down all the variables is appreciated.
April 2, 201313 yr Author Commercial Member That's great!! I appreciate the fix very much - and also the gauge posting that loads the free radio panel on start-up! I'll test it out either when I get home tonight, or perhaps later this afternoon through the magic of VNC. :lol: The irony is that I *just* received my Milviz forum login and was about to post about the bug there! Jim Stewart Milviz Person.
April 2, 201313 yr The irony is greater than you know, my time available for forum diving is limited, I became an Avsim Staffer years back when i was making freeware aircraft and scenery and dont frequently visit other forums, so its quite possible it would not have come to my attention anyway . Thanks for the help Best CJ
April 2, 201313 yr @@Bert Pieke > If you dont mind adding a gauge to the panel .cfg there is a way of having the Free Panel there on startup , place the cabfile here in your panel folders and add the line > gaugeXX=Freepanel_ON!Freepanel_ON, 2,2,1,1 like in [Vcockpit01] below . Hi Chuck, Thanks for that! Now I'm a happy camper.. B) If you are going to publish this little gauge, you might consider changing it to allow the switch to operate after the initial startup. <Gauge Name="Freepanel_ON" Version="1.1"> <Element> <Select> <Value> (L:ControlInit,bool) 1 != if{ 1 (>L:CJ1_PressAuto,bool) 1 (>L:ControlInit,bool) } </Value> </Select> </Element> </Gauge> Bert
April 2, 201313 yr I have not downloaded the fix yet. So, just to verify. Are these double knobs the 3D fix? I would say, that the the Freeradio fix, which works, has an undesired side effect on the 3d panel, as you can see in the picture. I've now switched to the Freeradio panel so that is not an issue for me.. Bert
Create an account or sign in to comment