December 12, 201213 yr Bram, I switched from RealityXp Garmins to MilViz default Garmins to see your problem. All works ok with Ezdok. Try this: FSX running, Cessna cold and dark flight loaded ... (no saved flights). Now select B55 and load it. Options, settings,display, ... check show cockpit tool tips and clk OK. B55 start engines, avionics on. VC view is showing now (default view). L-clk on the lower half of the Garmin 530 screen (flight plan area) to bring up the 2D gauges (or select via View menu) in the VC view. Load a MSFS flight plan for testing. It should have at least 8 waypoints for testing here. L-clk the Garmins FPL button. The flight plan will show up in Garmin. L-clk the right center knob to make the first field in the flight plan start blinking. If it is not blinking stop here ... there is a problem. Move your mouse to the right outer knob and see your mouse change to a + or - (change page group/move cursor) tool tip. If you do not see this stop here ... there is a problem. Go to the (+). Hover your mouse on the (+). Now you have a Hand mouse cursor with a (+), (change page group/move cursor) tool tip. If you do not see this stop here ... there is a problem. Now L-clk that (+). You should be moving down waypoints in your flight plan. Again. You should be moving down waypoints in your flight plan. Now move your mouse wheel away from you one notch at a time. You should be moving down waypoints in your flight plan. If you do not see this stop here ... there is a problem. Now move your mouse wheel toward you one notch at a time. You should be moving up waypoints in your flight plan. If you do not see this stop here ... there is a problem. Move your mouse cursor to the lower half of the 530's screen where the flight plan waypoint are listed and hover it there. Popup/Toggle GN530 Tool tip shown up. If you do not see this stop here ... there is a problem. L-Clk. Now you are back to the VC screen. Get your Garmin 530 view (I used Ezdok in this case. L-clk the right center knob to make the cursor field in the flight plan stop blinking. L-clk the right center knob to make the cursor field in the flight plan start blinking. If it is not blinking stop here ... there is a problem. Now move your mouse cursor (a hand) to the top area (anywhere) of the outer knob an hover it (hold it still) . There are no + or -'s here. Move the scroll wheel away from you to move the blinking cursor to the next waypoint or toward you to move to the previous waypoint. Did it work? Best Regards, Vaughan Martell PP-ASEL KDTW
December 12, 201213 yr Bram, I also did a quick video. I had to remove the RealityXP Garmins for this test. I would like to know if your screen(s) are the same and works the same as shown in the video. Best Regards, Vaughan Martell PP-ASEL KDTW
December 12, 201213 yr Author Still no luck. I quickly filmed a video showing what I'm doing. Whenever the cursor is hovering over the knob, I'm scrolling (except of course, in the area of the 2D panel that displays the + and - signs). http://www.youtube.com/watch?v=N6Yb1vSqKJU -Bram Osterhout
December 12, 201213 yr Ok, I wish you had stayed on the flight plan page. The idea is not to be at the first entry of the waypoint page .. rather in the middle so we can see the cursor go up/down one at a time ... In my previous post I wanted you to check the 2D view mouse scroll ... which I left out of my video. To verify the scroll wheel was working on the Garmin knob in this view: Now L-clk that (+). You should be moving down waypoints in your flight plan. Again. You should be moving down waypoints in your flight plan. Now move your mouse wheel away from you one notch at a time. You should be moving down waypoints in your flight plan. If you do not see this stop here ... there is a problem. Now move your mouse wheel toward you one notch at a time. You should be moving up waypoints in your flight plan. If you do not see this stop here ... there is a problem. Best Regards, Vaughan Martell PP-ASEL KDTW
December 12, 201213 yr Author I actually did check the scroll wheel in the 2D panel (although I see I forgot to mention it). In the part in the video where I go to the DirectTo page, I'm actually scrolling in the 2D panel to change the letter and cursor position; so I can confirm that the scrolling does indeed work in the 2D panel, but not not for whatever reason in the VC. And like I've said, the left knob works fine in the VC--no problem there. -Bram Osterhout
December 12, 201213 yr Well, If you want to do it again .. use the starting vc view I had ... so I can see the proportion of the default 2D Garmin stack against the main panel. Leave the cursor on a middle flight plan waypoint after moving Up/Down with the wheel ... then go to the VC view and scroll the waypoint again. Looking for a clue here .. we both need to be doing the same moves. Best Regards, Vaughan Martell PP-ASEL KDTW
December 13, 201213 yr Author I'll film another video with narration if I have some time this weekend. However, in the meantime, do you have any idea as to why the left knob works, but not the right? I can't seem to imagine that there's some strange trick to operating the right knob that doesn't apply to the left knob. I've tried using it in scenarios where I know that it should function, because it does on the 2D panel, but no matter what angle I approach it from, it just doesn't operate. Thanks! -Bram Osterhout
December 13, 201213 yr Moderator Check the Milviz forum for a panel.cfg file that will solve your problem. I suspect that for some reason you don't have the correct panel.cfg file... http://milviz.com/forum/viewtopic.php?f=59&t=2681#p25000 Fr. Bill AOPA Member: 07141481 AARP Member: 3209010556 Avsim Board of Directors | Avsim Forums Moderator
December 14, 201213 yr Author Thanks so much! That did the trick--works perfectly now! -Bram Osterhout
December 14, 201213 yr Bram, It would be nice to know which bad lines in the file caused the problem. Best Regards, Vaughan Martell PP-ASEL KDTW
December 14, 201213 yr Moderator Bram, It would be nice to know which bad lines in the file caused the problem. The latest installer has the corrected panel.cfg file. The major change lies in this section. There is a version of the GNS530 and 430 which contains the control code for the 3d knobs, and is invoked by adding the letter "d" to the gauge name: //-------------------------------------------------------- [Window01] Background_color=0,0,0 size_mm=1280,650 window_size_ratio=1.000 position=2 visible=0 ident=GPS_PANEL window_size= 0.710, 0.552 window_pos= 0.290, 0.480 gauge00=B55_XMLGauges!FBS_KR 87 ADF, 640,268,640,134 gauge01=B55_XMLGauges!FBS_KAP140, 640,402,640,163 gauge02=B55_XMLGauges!FBS_GTX330, 0,468,640,170 gauge03=B55_XMLGauges!FBS_GNS430_2d, 640,0,640,268 gauge04=B55_XMLGauges!FBS_GNS530_1d, 0,0,640,468 I have v5.120830, which I believe is the latest version, and I'm only using it as-is I just noticed this today. That is an old version. The current version is MilViz_B55_v5.120901 The only difference is the revised panel.cfg file, so now that it's working there's no point in downloading the entire installer again! Fr. Bill AOPA Member: 07141481 AARP Member: 3209010556 Avsim Board of Directors | Avsim Forums Moderator
December 14, 201213 yr "gauge03=B55_XMLGauges!FBS_GNS430_2d, 640,0,640,268 gauge04=B55_XMLGauges!FBS_GNS530_1d, 0,0,640,468" Thanks for the follow up ... I do now recall .. I had wrote about it once long time ago but figured it was way gone .. history / purged sort of thing. Glad all is well now. Best Regards, Vaughan Martell PP-ASEL KDTW
December 22, 201213 yr OK - I've also got version 120830 - purchased yesterday. I've tried to add the letter "d" in those two places - without success... How do I get to the "latest version"? Bert
December 22, 201213 yr Commercial Member He's talking about the cfg. That's an old one. The installer is the correct one. You can get it off of the forums tmrw. I will ask Bill to put it up. Please contact oisin at milviz dot com for forum registration information. Please provide proof of purchase if you want support. Also, include the username you wish to have.
December 22, 201213 yr Bert, //I am sure you will love this Baron. //The "d's" were the problem .. remove the red. //I originally got the setup info from a post by : tttocs (Scott) //This is my current panel // This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com // Built Sunday, June 24, 2012 at 17:41 FSPS Build:21603 [Window Titles] Window00=B55 Preflight Window01=GPS Window02=Reality XP GNS 530 WAAS - RXP_CONFIG_TOOL - DO NOT CHANGE Window03=Reality XP GNS 430 WAAS - RXP_CONFIG_TOOL - DO NOT CHANGE [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=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=B55_XMLGauges!B55_Preflight, 0,0,500,243 //-------------------------------------------------------- [Window01] Background_color=0,0,0 size_mm=1280,650 window_size_ratio=1.000 position=2 visible=0 ident=GPS_PANEL window_size= 0.710, 0.552 window_pos= 0.290, 0.480 gauge00=rxpGNS!GNS530, 0,0,640,468 gauge01=B55_XMLGauges!FBS_KR 87 ADF, 640,268,640,134 gauge02=rxpGNS!GNS430, 640,0,640,268 gauge03=B55_XMLGauges!FBS_KAP140, 640,402,640,163 gauge04=B55_XMLGauges!FBS_GTX330, 0,468,640,170 //-------------------------------------------------------- [Window02] window_pos=0.7070305,0.000000 window_size=0.2929695,0.3375 visible=1 ident=15531 zorder=99 gauge00=rxpGNS!GNS530,0,0,100,100 //-------------------------------------------------------- [Window03] window_pos=0.686667,0.526882 window_size=0.312500,0.210000 visible=1 ident=15431 zorder=99 gauge00=rxpGNS!GNS430,0,0,100,100 //-------------------------------------------------------- [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, 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 Day=255,255,255 Night=85,85,85 Luminous=140,140,140 [Default View] X=0 Y=0 SIZE_X=8192 SIZE_Y=3384 //////////////////////////////////////////////////////////// //And just for info .. the rxpgns.ini: ////////////////////////////////////////////////////////////// [GNS430] Popup=15431 AutoPilotMode=2 Radios=1 LinkCdiKey=On AutoCdiMode=0 AutoApproach=Off LinkVor=1 LcdStyle=Off AutoWidth=500 AutoHeight=210 Trainer= NoKeyClick=Off DisableRxTx=Off AutoPowerOn=Off AutoRadiosOff=On GndSpdFromDeltaLatLon=Off AutoCourse=On LinkObs=On ShadinFuel=On RadioSyncMode=Full Brightness=-1.000000 CrossFill=On TCAD=Off FuelType=0 Taws=On TawsVolume=60 TAWS_ALRT_TYPE_NEG_CLIMB_RATE=0 TAWS_ALRT_TYPE_IMMINENT_OBST_IMPACT_CAUT=0 TAWS_ALRT_TYPE_REDUCED_OBST_CLEARANCE_CAUT=0 TAWS_ALRT_TYPE_IMMINENT_TERR_IMPACT_CAUT=0 TAWS_ALRT_TYPE_REDUCED_TERR_CLEARANCE_CAUT=0 TAWS_ALRT_TYPE_IMMINENT_OBST_IMPACT_WRNG=0 TAWS_ALRT_TYPE_REDUCED_OBST_CLEARANCE_WRNG=0 TAWS_ALRT_TYPE_IMMINENT_TERR_IMPACT_WRNG=0 TAWS_ALRT_TYPE_REDUCED_TERR_CLEARANCE_WRNG=0 CPU=0 HardwareDevice=Off HardwareIdx=0 [GNS530] Popup=15531 AutoPilotMode=2 Radios=1 LinkCdiKey=On AutoCdiMode=0 AutoApproach=Off LinkVor=1 LcdStyle=Off AutoWidth=500 AutoHeight=360 Trainer= NoKeyClick=Off DisableRxTx=Off AutoPowerOn=Off AutoRadiosOff=On GndSpdFromDeltaLatLon=Off AutoCourse=On LinkObs=On ShadinFuel=On RadioSyncMode=Full Brightness=-1.000000 CrossFill=On TCAD=On FuelType=0 Taws=On TawsVolume=60 TAWS_ALRT_TYPE_NEG_CLIMB_RATE=0 TAWS_ALRT_TYPE_IMMINENT_OBST_IMPACT_CAUT=0 TAWS_ALRT_TYPE_REDUCED_OBST_CLEARANCE_CAUT=0 TAWS_ALRT_TYPE_IMMINENT_TERR_IMPACT_CAUT=0 TAWS_ALRT_TYPE_REDUCED_TERR_CLEARANCE_CAUT=0 TAWS_ALRT_TYPE_IMMINENT_OBST_IMPACT_WRNG=0 TAWS_ALRT_TYPE_REDUCED_OBST_CLEARANCE_WRNG=0 TAWS_ALRT_TYPE_IMMINENT_TERR_IMPACT_WRNG=0 TAWS_ALRT_TYPE_REDUCED_TERR_CLEARANCE_WRNG=0 CPU=0 HardwareDevice=Off HardwareIdx=0 [sETTINGS] Dimmer=Off SimpleMouse=Off Keyonfocus=On /////////////////////// //Rxpstack.ini //////////////////////// [DropStack] Icon00=Reality XP GNS 530 WAAS Unit 1 Icon01=Reality XP GNS 430 WAAS Unit 2 Icon02=Reality XP GNS GMAGTX [icon00] file=GNS530 ident=15531 name=RXP_CONFIG_TOOL - DO NOT CHANGE [icon01] file=GNS430 ident=15432 name=RXP_CONFIG_TOOL - DO NOT CHANGE Best Regards, Vaughan Martell PP-ASEL KDTW
Create an account or sign in to comment