whamil77

Members
  • Content Count

    295
  • Joined

  • Last visited

Community Reputation

123 Excellent

7 Followers

About whamil77

  • Rank
    Member

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    No

Recent Profile Visitors

2,829 profile views
  1. I must have been brain dead when I replied to your post. I could have sworn I was in the 690B forum. Oh, well.....old age, I guess. I will take a look at the ITT at normal cruise. Just know that the data is largely extrapolated from the performance charts. There is no chart that tells what EGT/ITT is at any particular altitude or power setting. One can only extrapolate from where the engine becomes ITT limited. I am confident that ITT numbers are accurate at maximum continuous power. Below that, there is no printed data to go by.
  2. I have not done the ITT correction on this mod yet. The ITT here is the normal FSX/P3D programming. Before I can do a mod however, I will need actual data on how the ITT behaves in the -10 Turbo Commander. I don't have any of that data, so I'm dead in the water.
  3. whamil77

    Should I get the 690B?

    File in a PM for you.
  4. whamil77

    Should I get the 690B?

    So....I want be sure I get your intent.....Do you want to use my overall mod but also want to use the mouse for the landing lights? If that's the case I can fix you up quick.
  5. whamil77

    Should I get the 690B?

    Ed, If you revert back to the original code as suggested in Olivier's post, FSUIPC is not needed in any form for the landing lights. The "un-mod" takes you back to only using the mouse. If you want to use a hardware switch for the landing lights, FSUIPC is required however I do not know if an unregistered copy will suffice. I have always had the registered version.
  6. whamil77

    Request - Saab 340 Military - Sweeded / Argetina

    Wrong thread. A mod needs to move this to the SAAB 340 thread.
  7. I sent you an email with a link to various beacon effects to try.
  8. The only fix is to switch it out. It doesn't have to be a Carenado effect. Any beacon effect will do. There should at least be a generic effect in FSX/P3D. Just keep switching until you find one that works.
  9. All fixed.... Something in my computer. A reboot fixed everything...like they normally do.
  10. Bought latest IL2, Bodenplatte, my first foray into the IL-2 line. After taking my money it now says the download server can't be reached. Been trying for hours. Is 777 Studios a money scan or is it legit? I suppose I should have asked the question before the purchase.
  11. whamil77

    B200 Mod

    Thank you very much. But I have original Beechcraft manuals for every variation of each King Air. However, I am sorely lacking in information for the following: Cessna 421, Beech 18, Aero Commander 500S, PA31T Cheyenne II, PA42 Cheyenne III.
  12. Only to add.....many, if not most, King Air pilots delay advancing the props until AFTER touchdown due to the noise making passengers uncomfortable. Not terribly unsafe as long as torque limits are followed on a go around. Some turboprops have higher torque limits at reduced RPM.
  13. whamil77

    LH/RH Fluor Switches?

    I'm pretty sure it's florescent lighting. The cockpit lighting in Carenado aircraft is a normally a box of rocks so I wouldn't expect too much from it.
  14. whamil77

    690B Mods v3 .....

    The GTN750 popup is "Shift+8". Using FSUIPC simply assign a keystroke or a button/switch to "Shift+8".
  15. whamil77

    690B Mods v3 .....

    Using a text editor (Notepad, for example) open the file "Gauge_UPDATE_DIG_2.xml" Scroll down unitl you see this... <!-- For default VC landing light operation --> <!-- (L:ASD_690B_SWITCH_LANDING_LIGHT_RIGHT,number) 0 == (L:ASD_690B_SWITCH_LANDING_LIGHT_LEFT,number) 0 == and if{ (A:LIGHT LANDING,bool) 0 != if{ 1 (&gt;K:LANDING_LIGHTS_TOGGLE) } } els{ (A:LIGHT LANDING,bool) 0 == if{ 1 (&gt;K:LANDING_LIGHTS_TOGGLE) } } --> <!-- For assigning landing lights to FSUIPC landing lights switch --> (A:LIGHT LANDING,bool) 0 != if{ 1 (>L:ASD_690B_EXTEND) 1 (>L:ASD_690B_SWITCH_LANDING_LIGHT_RIGHT,number) 1 (>L:ASD_690B_SWITCH_LANDING_LIGHT_LEFT,number) (>K:LANDING_LIGHTS_ON) } (A:LIGHT LANDING,bool) 0 == if{ 0 (>L:ASD_690B_EXTEND) 0 (>L:ASD_690B_SWITCH_LANDING_LIGHT_RIGHT,number) 0 (>L:ASD_690B_SWITCH_LANDING_LIGHT_LEFT,number) (>K:LANDING_LIGHTS_OFF) } Change it to look like this.... <!-- For default VC landing light operation --> (L:ASD_690B_SWITCH_LANDING_LIGHT_RIGHT,number) 0 == (L:ASD_690B_SWITCH_LANDING_LIGHT_LEFT,number) 0 == and if{ (A:LIGHT LANDING,bool) 0 != if{ 1 (&gt;K:LANDING_LIGHTS_TOGGLE) } } els{ (A:LIGHT LANDING,bool) 0 == if{ 1 (&gt;K:LANDING_LIGHTS_TOGGLE) } } <!-- For assigning landing lights to FSUIPC landing lights switch --> <!-- (A:LIGHT LANDING,bool) 0 != if{ 1 (>L:ASD_690B_EXTEND) 1 (>L:ASD_690B_SWITCH_LANDING_LIGHT_RIGHT,number) 1 (>L:ASD_690B_SWITCH_LANDING_LIGHT_LEFT,number) (>K:LANDING_LIGHTS_ON) } (A:LIGHT LANDING,bool) 0 == if{ 0 (>L:ASD_690B_EXTEND) 0 (>L:ASD_690B_SWITCH_LANDING_LIGHT_RIGHT,number) 0 (>L:ASD_690B_SWITCH_LANDING_LIGHT_LEFT,number) (>K:LANDING_LIGHTS_OFF) } --> Save the file. That's it.