Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

pkofman

Members
  • Joined

  • Last visited

Everything posted by pkofman

  1. First issue . can someone help with this issue. i have the black castle baron and bonanza in msfs 2024 ,, i also have the tdsgtn 750 full up to date and it is in gauge mode, firstly i dont know how to get it as a stand lone on these particular planes , is it possible? i dont see a switch on the ipad or anywhere else or natively ? Second issue and this one is really odd !! i have two computers each set up almost exactly the same and the graphics card in both is a 4080 Critical questions; on one machine when i click right alt - mouse click the gtn , i get a + sign and upon clicking the gtn will pop out as a new ui and i can move it to another screen on the other machine no matter what i do it will not pop out, the + sign appears but upon clicking it never pops out and it wont generate the new ui to provide a stand alone gtn , this is important because i find it hard to read in the gauge mode. Note that on both machines picking any native guage will pop out with the right alt -+ function so that works but not on the tdsgtn 750 can anyone provide some thoughts or input on this, ive chased this for a while , i cant figure it out, maybe someone here has a thought? Peter
  2. In fsx there was a key rate function that allowed one to change the key rate on the joystick. It was in the control settings when selecting a command with a key press. Is this even available in the ms2020. I want to speed up the key press rate. Thank you. Let me know. Peter
  3. Thank you i sort did the same,, I use the main hat to pan as left right up down, but I'm trying to get the left hat ( my 2nd one ) to emulate the eyepoint movement of the old fsx. I don't think that is possible, thank you for the suggestion, very frustrating, most things were working well in 2020, but others are a struggle pete
  4. hey thanks for this , but it is not what i need , i think i know most of what you are suggesting but what i want to do ( im using 2020) is to assign the move eyepoint command up, dn,, left and right to my second hat switch on the x52.. the older versions had a eyepoint selection and when assigned to the 2nd hat switch provided smooth panning. the key idea about this is so that and the panel would move in all directions, similar to if the pilot raised or lowered his seat or looked rightt or left with the ability to raise or lower the panel.. having an infinite amount not incrementally allows allot of view flexibility, this was available in all fsx versions and p3d., i dont think you can acheive this in 2020 or 2024.. but i might be missing something because it just does not seem there is a command or function that allows this @btacon thanak you for the video
  5. I tried all of this related to smoothing the movement of the eyepoint on the 2nd hat, but it did not work. i can move the eyepoint via the "translate " but it moves an incremental amount, I can't seem to get the eyepoint to move up/down left/right using the upper hat .also it is interesting in that I can't find the translate up and down command in the control search assignment settings .. any other thoughts would be appreciated
  6. Thank you guys. So I’ll experiment but my goal is to just be able to adjust the eye point infinitely as I’m flying and adjusting the sight picture onthe high hat. Sometimes the cockpit view is just too high to get a view over the windscreen. Some of the adjusts are very small and continuous as the glideslope changes. I’m mostly talking about the plane I fly in real life the mooney ovation and the Carenado model is great for practice approaches etc but the sight picture is never just quite right. As I mentioned previously this was much easier for some reason in fax and p3d. Thank you for your advice
  7. i recently got back to msfs2020 , compared to older version i have a problem that i know you guys can answer I want my 2nd hat switch to simply , smoothly and infinitley pan up and down in the cockpit . i want to assign move up and move down left and right but not incrementally, i simply like to move it to whatever i wish,, this seems to be a preset increment when i set it up with "translate or other commands," i have the main hat switch set up to look around but that is not what i want to do with the second and the up and down keyboard buttons are not infinite Im trying to set up the second hat swith on the x52 to be able to move the cockpit smoothly as per the old fsx and p3d to any cockpit adjustment In the older versions this command was "move eyepoint " or something similar any assistance or point me to the correct command would be appreciated, maybe it is not possbile in this sim thank you all peter
  8. I bought this monitor a while ago and tried it with fsx se and p3d v3 and basically gave up Recently , I bought a 980ti and thought i would give it a try again so i installed it on the card and changed up my non hd monitor ( asus pb278q ) for this the hd monitor ( asus pb287q-4k hd) My experience on the hd 4k monitor is very bad! colours are washed out in both fsx and p3d max resolution and it is incredibly difficult to read the menus , ( fonts too tiny and not clear )in fsx and p3d as they are just much too small Im sure there is tons of experience here with suggestions in both fsx-se and p3d v3 platforms... Questions: Is it possible to get great resolution with this HD card and monitor in fsx -se ( i gave on fsx legacy/boxed version long ago ) and p3d v3 Is it possible to make the menus within the sim on 4k readable. They are just much too tiny and the fonts are not clear Thank you in advance for your thoughts and assistance Peter
  9. How do i use the aircraft browser for p3d or steam I'm trying to get the 530 into some of the aircraft that minstar says will install into by default. two things happen i see aircraft listed but that is about all i can do also i have been getting a runtime error The only plane i have been able to install into so far is the a2a 182 p3d and steam fsx nothing else trying to get it into the carenado m20j in both sims Did i miss the manual or instructions I know i can add things manually but evidently i should be able to install automatically to same planes Pete
  10. Here is what i did to test things based on some of your ideas. I removed both the 980 and 980 ti cards and thoroughly cleaned the and the slot then reseated them. they appears clean to me and very little dust in the case I have three monitors i put two on the 980ti and one on the 980 ( hdmi) I check the bios fan profile My cpu has a corsair h link so it would not make noise Checked to ensure that all fans on the cards were working im running p3d-v3 at a little more than mid range graphic specs but pretty high rez. ( test was with a non stock 182t from carenado) I removed the latest nvidia driver and went back one version. I have msi afterburner. Now flying mid level specs on p3d and fsx-se i have temps pretty solidly in the in th high 70's with appears manageable.. Maybe one of you may be able to determine why things were so loud but i played with way too many variables to really put my finger on one culprit.. I think given the temps im seeing that i should be ok I was trying to avoid an expensive meltdown. Thanks for the ideas. Pete :smile:
  11. I tried cleaning things up but honestly the temps are still pretty high...Maybe it has always been like this and i just did not notice in the past ... Maybe with fsx-se and p3d v3 the temps will be in the 70's , any other thoughts and experience would be appreciated. Pete
  12. hmm?? good point.. ill check the dust and reseat them.... the 980ti is msi the 980 is asus I run two monitors on the ti one on the 980 at idle ( meaning no program basically working ) the 980ti msi is 49c the 980 is 48c p3d really ramp it up quickly Peter
  13. I just noticed that my 980ti is running in the high 70's with p3d v3. med settings I have a 980 and a 980ti card If i run either steam and /or p3d on med setting the cards start to run really hot. windows 10 x64 I have been at this for years and I for some reason I'm having this problem now. I have the most current drivers I'm curious as to what others are experience with respect to the issue I have 2 monitors on the 980TI and one on the 980 My temps are mid 70's fans running very loud onthe cards any thoughts. never had temps this high any thoughts.. Peter
  14. Ed Thanks you for the clarification , your description of my expectaion was 100 correct expectation "I think you're taking the term 'fly LPV approaches' and applying that as if it's an autopilot. It is not an autopilot, it's a navigation unit. It provides guidance, but does not actually control anything. It can not drive the sim's built-in glideslope needle without a hack. That's not going to happen. Since it doesn't drive the built-in needle value, then the built-in autopilot can't fly the glidepath." Your clarification is perfect and in fact I did do something correctly as the mindstar gauge is in the plane as i do get the needle indication. Thank you and thanks for helping me to understand the limitations. Regards Pete
  15. Hey ED... correct me if im wrong but i thought that i read somewhere that one of the features of the mindstar gps 4/5 series was that it would fly lpv approaches with certain aircraft and give a gs indication ... Now maybe i misunderstood and that is fine... I will simply use it for lnav and lnav +v .. I am simply working to understand the functionality . I also understand that this functionality only would work in certain aircraft... Regardless i like the product... and thanks again... Pete
  16. So i have been busy working away on LVP approaches. Seems to me that even with an updated database and minstar 172 i cannot get the 172 to follow the glideslope on a LVP . I would expect the aircraft to follow the GS down after the FAF and gs intercept. In my case i get the gps was approach. ( lap ) . set the a/p to APP and ensure the approach is activated. Every time i try this the plane blows through the gs and never follows the gs down to DA . ( I've tried it both ways with alt enabled and disabled ). Any thoughts (btw I'm doing this on the mindstar texture 172) in fsx pete
  17. Hi Ed BTW. in case i did not say it earlier . really appreciate your help with this... Il try this Pete
  18. MPI_CDIGauge.gau yes is it is in this folder G:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Gauges Pete
  19. I probably did create that panel and your gps unit shows up when i select the gps from the menu.. ..Maybe i should just reinstall your product into fsx again and the MPI_CDIGaige will reinstall I dont mind doing this as long as i don't have to reauthorize because i have no authorization left . Peter
  20. I think you want my 172 panel.cfg content thanks for having a look Here it is // Panel Configuration file // Cessna 172sp // Copyright (c) 2001-2003 Microsoft Corporation. All rights reserved. [Window Titles] Window00=Main Panel Window01=Radio Stack Window02=GPS_PANEL Window03=IFR Panel Window04=Landing View Window05=Mini Panel Window06=Reality XP GNS 430 WAAS - RXP_CONFIG_TOOL - DO NOT CHANGE Window08=Reality XP GNS GMAGTX - RXP_CONFIG_TOOL - DO NOT CHANGE Window09=Reality XP DropStack [Window00] file_1024=cessna_172_background.bmp file_1024_night=cessna_172_background_night.bmp size_mm=640 position=7 visible=1 no_luminous=1 ident=MAIN_PANEL zorder=0 windowsize_ratio=1.000 window_pos=0.0,0.0 window_size=1.000,1.000 view_window_rect=0,0,8192,4000 gauge00=Cessna!Altimeter, 346,167, 79, 79 gauge01=Cessna!Annunciator, 517,159, 62, 15 gauge02=Cessna!Avionics Switch, 288,426, 37, 47 gauge03=Cessna!Flaps, 467,415, 48, 64 gauge04=Cessna!Fuel_Selector, 556,415, 82, 62 gauge05=Cessna!Heading_Indicator, 264,247, 81, 81 gauge06=Cessna!Master_Alt_Bat, 121,425, 40, 45 gauge07=Cessna!Nav_GPS_Annunciator, 582,162, 12, 11 gauge08=Cessna!Nav GPS Switch, 594,162, 12, 11 gauge09=Cessna!OMI_Lights, 609,158 gauge10=Cessna!Pitch_Trim, 528,416, 21, 36 gauge11=Cessna!Starter, 71,422, 47, 52 gauge12=Cessna!Turn_Indicator, 185,247, 78, 78 gauge13=Cessna!Vertical_Speed, 346,247, 79, 79 gauge14=Cessna!Vacuum_Ampermeter, 122,334, 58, 58 gauge15=Cessna172!Airspeed, 185,167, 78, 78 gauge16=Cessna172!Alt_Static_Air, 339,453, 37, 27 gauge17=Cessna172!Clock, 122,193, 58, 58 gauge18=Cessna172!EGT_Fuel_Flow, 122,271, 58, 58 gauge19=Cessna172!Fuel, 61,270, 58, 58 gauge20=Cessna172!Fuel_Shutoff, 517,453, 36, 28 gauge21=Cessna172!Panel_Lights_Switch, 342,418, 30, 34 gauge22=Cessna172!Tachometer, 347,329, 78, 78 gauge23=Cessna172!Thrust_Controls, 375,425, 81, 55 gauge24=Cessna182s!Oil_Press_Temp, 62,334, 58, 58 gauge25=Cessna182s!Switches, 163,440,121, 41 gauge26=CessnaWAlpha!ADF_Alpha, 431,329, 79, 79 gauge27=CessnaWAlpha!Attitude_Alpha, 266,167, 78, 78 gauge28=CessnaWAlpha!VOR2_Alpha, 431,247, 79, 79 gauge29=CessnaWAlpha!VOR1_Alpha, 431,167, 79, 79 gauge30=CessnaWAlpha!Whiskey_Compass_Alpha, 499, 98, 35, 23 gauge41=SimIcons!Kneeboard Icon, 66,255 gauge42=SimIcons!ATC Icon, 78,255 gauge43=SimIcons!Map Icon, 90,255 gauge44=SimIcons!GPS Icon, 102,255 gauge45=SimIcons1024!IFR Icon, 114,255, 12, 12 gauge46=SimIcons1024!Landing Icon, 126,255, 12, 12 gauge47=Bendix_King_Radio!Bendix-King Radio Audio, 519,177,120, 24 gauge48=Bendix_King_Radio!Bendix-King Radio Nav-Comm 1, 519,200,120, 41 gauge49=Bendix_King_Radio!Bendix-King Radio Nav-Comm 2, 519,240,120, 42 gauge50=Bendix_King_Radio!Bendix-King Radio ADF, 519,281,120, 32 gauge51=Bendix_King_Radio!Bendix-King Radio DME, 519,313,120, 30 gauge52=Bendix_King_Radio!Bendix-King Radio Xpndr, 519,343,120, 34 gauge53=Bendix_King_Radio!Bendix-King Radio AP, 519,377,121, 34 gauge54=n_number_plaque!n_number_plaque, 210,387,65,19 //-------------------------------------------------------- [Window02] size_mm=456,520 window_size=0.5 position=8 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=GPS_PANEL gauge00=MPI_GNS!GNS530, 0, 0, 456, 331, 1:1:225 gauge01=MPI_GNS!GNS430, 0, 331, 456, 189, 2:1:225 //-------------------------------------------------------- [Window03] file_1024=cessna_172_ifr_background.bmp file_1024_night=cessna_172_ifr_background_night.bmp size_mm=640 position=7 visible=0 ident=MAIN_PANEL_ALT1 no_luminous=1 zorder=1 view_window_rect=0,0,8192,1200 gauge00=Cessna!Altimeter, 279, 91,100, 99 gauge01=Cessna!Annunciator, 493, 81, 79, 20 gauge02=Cessna!Avionics Switch, 210,411, 40, 59 gauge03=Cessna!Flaps, 430,399, 61, 78 gauge04=Cessna!Fuel_Selector, 540,400, 98, 79 gauge05=Cessna!Heading_Indicator, 179,191,100, 99 gauge06=Cessna!Master_Alt_Bat, 2,414, 45, 55 gauge07=Cessna!Nav_GPS_Annunciator, 574, 84, 16, 15 gauge08=Cessna!Nav GPS Switch, 589, 86, 13, 11 gauge09=Cessna!OMI_Lights, 609, 83, 31, 15 gauge10=Cessna!Pitch_Trim, 504,400, 24, 46 gauge11=Cessna!Turn_Indicator, 78,189,100,100 gauge12=Cessna!Vertical_Speed, 280,191,100,100 gauge13=Cessna!Vacuum_Ampermeter, 158,298, 73, 75 gauge14=Cessna172!Airspeed, 79, 90, 98, 97 gauge15=Cessna172!Alt_Static_Air, 271,449, 44, 30 gauge16=Cessna172!Clock, 1,122, 73, 72 gauge17=Cessna172!EGT_Fuel_Flow, 1,299, 73, 73 gauge18=Cessna172!Fuel, 1,220, 74, 72 gauge19=Cessna172!Fuel_Shutoff, 494,445, 43, 34 gauge20=Cessna172!Tachometer, 282,293, 98, 95 gauge21=Cessna172!Thrust_Controls, 321,414,102, 64 gauge22=Cessna172!Panel_Lights_Switch, 273,402, 38, 41 gauge23=Cessna182s!Oil_Press_Temp, 80,300, 73, 72 gauge24=Cessna182s!Switches, 51,429,151, 51 gauge25=CessnaWAlpha!ADF_Alpha, 387,292,100,100 gauge26=CessnaWAlpha!Attitude_Alpha, 179, 90,100, 99 gauge27=CessnaWAlpha!VOR1_Alpha, 385, 91,100,100 gauge28=CessnaWAlpha!VOR2_Alpha, 385,190,100,100 gauge29=CessnaWAlpha!Whiskey_Compass_Alpha, 471, 3, 43, 30 gauge30=SimIcons!Kneeboard Icon, 37,379, 12, 12 gauge31=SimIcons!ATC Icon, 51,379, 12, 12 gauge32=SimIcons!Map Icon, 65,379, 12, 12 gauge33=SimIcons!GPS Icon, 79,379, 12, 12 gauge34=SimIcons1024!VFR Icon, 93,379, 12, 12 gauge35=SimIcons1024!Landing Icon, 107,379, 12, 12 gauge36=Bendix_King_Radio!Bendix-King Radio Audio, 496,102,143,27 gauge37=Bendix_King_Radio!Bendix-King Radio Nav-Comm 1, 496,129,143,52 gauge38=Bendix_King_Radio!Bendix-King Radio Nav-Comm 2, 496,181,143,56 gauge39=Bendix_King_Radio!Bendix-King Radio ADF, 496,236,143,35 gauge40=Bendix_King_Radio!Bendix-King Radio DME, 496,271,143,37 gauge41=Bendix_King_Radio!Bendix-King Radio Xpndr, 496,308,143,43 gauge42=Bendix_King_Radio!Bendix-King Radio AP, 496,351,143,43 [Window04] file_1024=cessna_172_landing_background.bmp file_1024_night=cessna_172_landing_background_night.bmp size_mm=640 visible=0 no_luminous=1 ident=MAIN_PANEL_ALT2 windowsize_ratio=1.000 position=7 zorder=2 view_window_rect=0,0,8192,4900 gauge00=Cessna!Altimeter, 346,167, 79, 79 gauge01=Cessna!Annunciator, 517,159, 62, 15 gauge02=Cessna!Avionics Switch, 288,426, 37, 47 gauge03=Cessna!Flaps, 467,415, 48, 64 gauge04=Cessna!Fuel_Selector, 556,415, 82, 62 gauge05=Cessna!Heading_Indicator, 264,247, 81, 81 gauge06=Cessna!Master_Alt_Bat, 121,425, 40, 45 gauge07=Cessna!Nav_GPS_Annunciator, 582,162, 12, 11 gauge08=Cessna!Nav GPS Switch, 595,162, 10, 10 gauge09=Cessna!OMI_Lights, 609,158 gauge10=Cessna!Pitch_Trim, 528,416, 21, 36 gauge11=Cessna!Starter, 71,422, 47, 52 gauge12=Cessna!Turn_Indicator, 185,247, 78, 78 gauge13=Cessna!Vertical_Speed, 346,247, 79, 79 gauge14=Cessna!Vacuum_Ampermeter, 122,334, 58, 58 gauge15=Cessna172!Airspeed, 185,167, 78, 78 gauge16=Cessna172!Alt_Static_Air, 339,453, 37, 27 gauge17=Cessna172!Clock, 122,193, 58, 58 gauge18=Cessna172!EGT_Fuel_Flow, 122,271, 58, 58 gauge19=Cessna172!Fuel, 61,270, 58, 58 gauge20=Cessna172!Fuel_Shutoff, 517,453, 36, 28 gauge21=Cessna172!Panel_Lights_Switch, 342,418, 30, 34 gauge22=Cessna172!Tachometer, 347,329, 78, 78 gauge23=Cessna172!Thrust_Controls, 375,425, 81, 55 gauge24=Cessna182s!Oil_Press_Temp, 62,334, 58, 58 gauge25=Cessna182s!Switches, 163,440,121, 41 gauge26=CessnaWAlpha!ADF_Alpha, 431,329, 79, 79 gauge27=CessnaWAlpha!Attitude_Alpha, 266,167, 78, 78 gauge28=CessnaWAlpha!VOR1_Alpha, 431,167, 79, 79 gauge29=CessnaWAlpha!VOR2_Alpha, 431,247, 79, 79 gauge30=CessnaWAlpha!Whiskey_Compass_Alpha, 499, 98, 35, 24 gauge31=SimIcons!Kneeboard Icon, 66,255 gauge32=SimIcons!ATC Icon, 78,255 gauge33=SimIcons!Map Icon, 90,255 gauge34=SimIcons!GPS Icon, 102,255 gauge35=SimIcons1024!VFR Icon, 114,255, 12, 12 gauge36=SimIcons1024!IFR Icon, 126,255, 12, 12 gauge37=Bendix_King_Radio!Bendix-King Radio Audio, 519,177,120, 24 gauge38=Bendix_King_Radio!Bendix-King Radio Nav-Comm 1, 519,200,120, 41 gauge39=Bendix_King_Radio!Bendix-King Radio Nav-Comm 2, 519,240,120, 42 gauge40=Bendix_King_Radio!Bendix-King Radio ADF, 519,281,120, 32 gauge41=Bendix_King_Radio!Bendix-King Radio DME, 519,313,120, 30 gauge42=Bendix_King_Radio!Bendix-King Radio Xpndr, 519,343,120, 34 gauge43=Bendix_King_Radio!Bendix-King Radio AP, 519,377,121, 34 gauge44=n_number_plaque!n_number_plaque, 210,387,65,19 [Window01] BACKGROUND_COLOR=2,2,2 size_mm=156,308 position=8 visible=0 ident=RADIO_STACK_PANEL zorder=3 gauge00=Bendix_King_Radio!Bendix-King Radio Audio, 0, 0,156,31 gauge01=Bendix_King_Radio!Bendix-King Radio Nav-Comm 1, 0, 29,156,59 gauge02=Bendix_King_Radio!Bendix-King Radio Nav-Comm 2, 0, 86,156,59 gauge03=Bendix_King_Radio!Bendix-King Radio ADF, 0,142,156,41 gauge04=Bendix_King_Radio!Bendix-King Radio DME, 0,180,156,41 gauge05=Bendix_King_Radio!Bendix-King Radio Xpndr, 0,217,156,49 gauge06=Bendix_King_Radio!Bendix-King Radio AP, 0,262,156,48 windowsize_ratio=1.000 window_pos=0.756,0.358 window_size=0.243,0.641 [Window02] size_mm=456,378 window_size=0.5 position=8 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=GPS_PANEL zorder=4 gauge00=fs9gps!gps_500, 0,0 [Window05] position=7 size_mm=631,100 child_3d=1 background_color=0,0,0 no_luminous=1 ident=MINIPANEL gauge00=Cessna172!Airspeed, 0, 1 gauge01=Cessna!Turn_Indicator, 102, 0 gauge02=CessnaWAlpha!Attitude_Alpha, 207, 0 gauge03=Cessna!Heading_Indicator, 312, 0 gauge04=Cessna!Altimeter, 417, 0 gauge05=Cessna!Vertical_Speed, 531, 0 [VCockpit01] size_mm=512,512 pixel_size=512,512 texture=$C172s_1 background_color=0,0,0 gauge00=Cessna!Nav_GPS_Annunciator, 69,457, 20, 19 gauge01=Cessna!VOR1, 259, 1,140,140 gauge02=Cessna!Nav GPS Switch, 45,456, 20, 21 gauge03=Cessna!ADF, 259,283,145,145 gauge04=Cessna172!EGT_Fuel_Flow, 400,109,107,107 gauge05=Cessna172!Fuel, 400, 1,107,107 gauge06=Cessna182s!Oil_Press_Temp, 405,325,107,107 gauge07=Cessna!OMI_Lights, 0,456, 44, 24 gauge08=Cessna!Vacuum_Ampermeter, 405,217,107,107 gauge09=Cessna!Annunciator, 0,481, 99, 25 gauge10=Cessna172!Whiskey_Compass, 100,456, 56, 39 gauge11=Cessna182s!VOR2, 259,142,140,140 gauge12=Bendix_King_Radio!Bendix-King Radio Audio, 0, 0, 258, 50 gauge13=Bendix_King_Radio!Bendix-King Radio Nav-Comm 1, 0, 51,258, 95 gauge14=Bendix_King_Radio!Bendix-King Radio Nav-Comm 2, 0,147,258, 95 gauge15=Bendix_King_Radio!Bendix-King Radio ADF, 0,243,258, 66 gauge16=Bendix_King_Radio!Bendix-King Radio DME, 0,310,258, 66 gauge17=Bendix_King_Radio!Bendix-King Radio Xpndr, 0,377,258, 78 gauge18=n_number_plaque!n_number_plaque, 188,468,89,25 [VCockpit02] size_mm=512,512 pixel_size=512,512 texture=$C172s_2 background_color=0,0,0 gauge00=Cessna!Heading_Indicator, 0, 0,163,162 gauge01=Cessna!Turn_Indicator, 164, 0,158,158 gauge02=Bell_206B!Attitude, 323, 0,158,158 gauge03=Cessna!Altimeter, 0,163,158,156 gauge04=Cessna172!Airspeed, 164,159,155,155 gauge05=Cessna!Vertical_Speed, 323,159,156,157 gauge06=Bendix_King_Radio!Bendix-King Radio AP, 0,321,258, 77 gauge07=Cessna172!Tachometer, 260,318,143,143 gauge08=Cessna172!Clock, 0,400, 86, 86 gauge09=Cessna!Flaps, 88,400, 78,105 [Views] VIEW_FORWARD_DIR= 8.0, 0.0, 0.0 [Color] Day=255,255,255 Night=255,255,255 Luminous=201,64,64 [Window06] window_pos=0.609375,0.000000 window_size=0.390625,0.291667 visible=1 ident=15431 zorder=99 gauge00=rxpGNS!GNS430,0,0,100,100 [Window08] window_pos=0.609375,0.587500 window_size=0.390625,0.412500 visible=0 ident=15327 zorder=99 gauge00=rxpGNS!GMA340,0,0,100,33.670033 gauge01=rxpGNS!GTX327,0,33.670033,100,44.107744 gauge02=Bendix_King_Radio!Bendix-King Radio ADF,0,77.777777,50,22.222222 gauge03=Bendix_King_Radio!Bendix-King Radio AP,50,77.777777,50,22.222222 [Window09] position=0 window_size=0.062500,0.041667 visible=1 ident=15000 zorder=100 gauge00=rxpDrop!Stack,0,0,100,100
  21. what i mean is that i tried the microsoft 172 ... thats what i mean by stock.. I was able to use the a2a 182 but no lpv , its the only a2a plane i own the a2a 182 im using is not g1000 and i successfuly installed the 530 into it. just no verical guidance Ill keep working on it...
  22. Tried an lpv into rochester Kroc on the a2a.. 182 and stock ms 172.. (rnav 07 )approach with mindstar and data updates and im still not getting vertical guidance.... ( lpv )....using the 530 Can someone else try that approach and let me know if they are picking up Vertical ... I have horizontal... or ..... Can someone suggest a combo of plane and specific approach that give them lpv and ill give it a shot to see if i have things set up properly Pete
  23. Mike i might be wrong but i think he means http://www.a2asimulations.com/ Pete
  24. I am trying to get the c-182t g1000 to work as designed. I understand that many of the features of the unit are not modelled . I am just not sure if my problems stem from the item not being modelled or I'm making mistakes For instance when i select an approach ( assume rnav) i am able to select the approach and then activate it. But i am then unable to get rid of the flight plan window on the mfd. Hitting the FLP or CLR button will not take me back to the main screen. Normally and in real life i could hold the C key and it would take you back to the default screen. Further lets say you are flying an approach and want to go to a fix direct in the approach. You normally can hit "direct" then scroll to the waypoint and hit enter and you can truncate the approach similar to how atc might send you to a specific point on an approach. On the g1000 in the sim i can scroll to a fix but when i hit "ENT" nothing happens, it won't send me direct and i cant complete the task. Typically i get stuck at this point ( or frustrated) !! lastly there is just no way to back up and get rid of the flight plan screen on the mfd, It seems as though once i bring it up it just stays on top of the map Maybe this is some of the missing functionality our perhaps I'm making a mistake . I fly a g1000 in real life and this all seems a bit odd... Thoughts Pete
  25. thank you.... i own the 182 ill check it out... much appreciated,,, Pete

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.