Korber

Members
  • Content Count

    54
  • Joined

  • Last visited

Community Reputation

4 Neutral

Flight Sim Profile

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

Profile Information

  • Gender
    Male

Recent Profile Visitors

998 profile views
  1. Korber

    card declined

    777 where are you from?
  2. Korber

    RealAir Piston Duke V2 & Weather Radar

    Yes, it can be done, but I unfortunately can not help as I do not have the RXP gauges. Read the original thread from the start, maybe someone has found the way
  3. Korber

    RealAir Duke B60 WX Radar

    See here:
  4. There is a very good free alternative in case you have MS Excel (post 2007 version) https://library.avsim.net/esearch.php?CatID=fsxutil&DLID=188491
  5. Use the FSX registry repair tool from Flight1: http://www.flight1.com/view.asp?page=library and try again to install the duke.
  6. Korber

    What was your best purchase 2016?

    -ActiveSky 16 -SteveFX FSX Cloud shadows
  7. Korber

    RealAir Piston Duke V2 & Weather Radar

    This is how to install radar to RAS Duke V2 without realityXP gps gauges. It is a bit complex as the gps panels of the duke are part of the 3d model. This makes any gauge installed over the gps panels to loose all or some of the click spots, so a popup gauge must be installed in order to control the vc gauge. Ensure that you did a backup before you edit any file. Here we go: Open the .../RealAir Duke B60 v2/panel/config folder and edit the options.xml file with a text editor, change the 0 entry below from 0 to 20: <Element> <Select> <Value>(G:Var1) 0 == if{ 20 (>L:dukeRadioConfig,number) }</Value> </Select> </Element> This will change the panel configuration to 2 GPS units for Rxp gps. Replace the default gps with the gns530 from the freeware Douglas C117v2 by Manfred Jahn, (You can download the C117 from the simouthouse library) 1)copy FS9Garmin530_Basler.cab from the c117 panel folder and paste to the duke panel folder 2)edit the duke panel cfg as follows: ----------------------------------------------------------------- [Window Titles] Window00=Main Panel Window01=GPS Window02=WXR [Window00] file=2D_Help.bmp size_mm=1024, 95 position=6 BACKGROUND_COLOR=0,0,0 visible=1 ident=MAIN_PANEL [Window01] Background_color=0,0,0 size_mm=500,366 position=7 visible=0 ident=210 window_size= 0.385, 0.385 window_pos= 0.243, 0.280 gauge00=FS9Garmin530_Basler!GNS530_nc1, 0,0 [Window02] Background_color=16,16,16 size_mm=100,150 position=2 visible=1 ident= window_size= 0.098, 2.105 window_pos= 0.050, 0.650 zorder=4 gauge00=RolasnRadar!oRadGauge, 0,0,100,150,sweep|beam|icing|nogps --------------------------------------------------------------------------- [VCockpit01] - - - gauge19=FS9Garmin530_Basler!GNS530_nc1, 2,655,504,364 //gauge19=fs9gps!RAS_gps_500, 1, 607, 502, 416 gauge20=RolasnRadar!ORadGauge, 617,740,305,180,sweep|beam|icing|nogps //gauge20=RASDuke!Blank, 0, 0, 1, 1 Full controls: -GPS through the GPS popup (SHIFT+2) -Radar on/off/test and gain with vc clickspots, all controls with popup (SHIFT+3)
  8. Korber

    Setting the parking brake in a B737

    After setting the parking brake and releasing the pedals, they return about an inch back, That inch is what you need to press to release the parking brake.
  9. Korber

    Weather Gauge for JS4100

    The click spots are on the vc radar screen, use the mouse wheel to turn on and adjust gain, tilt and range. You dont have to pop up the 2d gauge. With 2 entries in the panel cfg (for 2d and vc) only the vc works and displays weather, the 2d popup is just a gray panel where only the click spots work.
  10. Korber

    Weather Gauge for JS4100

    Have you installed VC++2013 runtime libraries x86? (see p.1 of the installation pdf)
  11. Korber

    Weather Gauge for JS4100

    Download "rolasnradar-v10.zip" from the library. You will find instructions in the readme how to install it in the J41.
  12. This is how to install radar to RAS Duke V2 without realityXP gps gauges. It is a bit complex as the gps panels of the duke are part of the 3d model. This makes any gauge installed over the gps panels to loose all or some of the click spots, so a popup gauge must be installed in order to control the vc gauge. Ensure that you did a backup before you edit any file. Here we go: 1.Open the .../RealAir Duke B60 v2/panel/config folder and edit the options.xml file with a text editor, change the 0 entry below from 0 to 20: <Element> <Select> <Value>(G:Var1) 0 == if{ 20 (>L:dukeRadioConfig,number) }</Value> </Select> </Element> This will change the panel configuration to 2 GPS units for Rxp gps. Radar gauge installs over rh gps the usual way, but now we have more problems: -there is no nav/com freq select panel, -default gps cannot set nav/com freq, must be replaced or install a popup nav/com panel -default gps popup is not synchronized with the vc gps, that means what you choose to display on the popup gps it is not displayed on the vc.(default vc gps cannot be controlled by the 3d switches as these are set for the RealityXP GPS) -the nav/gps switch is missing Solution:Replace the default gps with the gns530 from the freeware Douglas C117v2 by Manfred Jahn, (You can download the C117 from the simouthouse library) 1)copy FS9Garmin530_Basler.cab from the c117 panel folder and paste to the duke panel folder 2)edit the duke panel cfg as follows: ----------------------------------------------------------------- [Window Titles] Window00=Main Panel Window01=GPS Window02=WXR [Window00] file=2D_Help.bmp size_mm=1024, 95 position=6 BACKGROUND_COLOR=0,0,0 visible=1 ident=MAIN_PANEL [Window01] size_mm=500,366 window_size= 0.385, 0.385 window_pos=0.243, 0.280 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=210 gauge00=FS9Garmin530_Basler!GNS530_nc1, 0,0 [Window02] size_mm=100,150 position=2 visible=1 Window_pos=0.05,0.65 zorder=4 background_color=16,16,16 gauge00=RolasnRadar!oRadGauge, 0,0,100,150, sweep|beam|icing|nogps --------------------------------------------------------------------------- [VCockpit01] - - - gauge19=FS9Garmin530_Basler!GNS530_nc1, 20, 660, 470, 350 //gauge19=fs9gps!RAS_gps_500, 1, 607, 502, 416 gauge20=RolasnRadar!ORadGauge, 617, 740, 305, 180, sweep|beam|icing|nogps //gauge20=RASDuke!Blank, 0, 0, 1, 1 3)Set a key in fsx for "Nav1/GPS toggle". The result: Controls: -GPS and nav/com freq through the GPS popup (SHIFT+2) -Radar on/off/test and gain with vc clickspots, all controls with popup (SHIFT+3) -Nav/GPS toggle with assigned key
  13. Korber

    WING-BODY OVERHEAT can we go?

    If warning light does not extinguish by closing the isolation valve and the engines/apu bleed valves (engines/APU operating), that means it is an indication and not a real air leak problem. Real or indicating you can dispatch, but with serious operating limitations: -Airplane is not operated in known or forecast icing conditions -Limit altitude to FL 250 26.2 Fire Protection-MMEL 26-12 Wing-Body Overheat Detector System (Left) Except for ER operations, may be inoperative provided: a. Right pack and engine bleed is used for pressurization only. b. Use of APU is prohibited except for engine start. c. Isolation valve and left engine bleed valve remain closed for all operations except engine start. d. Airplane is not operated in known or forecast icing conditions. MAINTENANCE NOTE Refer to DDG item 21-01-01 (M) procedure, as applicable, for information when the left pack is not used. OPERATIONS (O)* 1. Refer to DDG Item 21-01-01 (O) procedure for information when the left pack is not used. 2. Except for engine start, do not use the APU for pneumatic air supply and/or electrical power. 3. After engine start, make sure that: A. ISOLATION VALVE switch is set to CLOSE B. APU switch is set to OFF C. L PACK switch is set to OFF D. R PACK set as desired. 4. Do not dispatch into known icing or forecast icing conditions. 26-13 Wing-Body Overheat Detector System (Right) Except for ER operations, may be inoperative provided: a. Left pack and left engine or APU bleed air is used for pressurization only. b. Isolation valve and right engine bleed valve remain closed for all operations except engine start. c. Airplane is not operated in known or forecast icing conditions. MAINTENANCE NOTE Refer to DDG item 21-01-01 (M) procedure, as applicable, for information when the right pack is not used. OPERATIONS (O)* 1. Refer to DDG Item 21-01-01 (O) procedure for information when the right pack is not used. 2. After engine start, make sure that: A. ISOLATION VALVE is set to CLOSE. B. R PACK switch is set to OFF C. L PACK as desired. 3. Do not dispatch into known icing or forecast icing conditions. For -300/-400/-500/-600/-700/-800/-900: 4. Increased air flow will occur when flaps are extended (takeoff and landing) if the APU is used instead of engine bleed to supply bleed air to the left pack. 5. With the L PACK switch in AUTO, the pack operates in the high flow mode. 6. Do not set the L PACK to HIGH for takeoff and landing with the engine bleed on. 7. Do not use APU bleed air at altitudes above 17,000 feet. *OPERATIONS (O) 1. When dispatching with one operating pack supplied by engine bleed air on takeoff: A. Determine V1(MCG) based on engine bleed for packs OFF. B. Determine takeoff performance based on packs AUTO. 2. Limit altitude to FL 250. 3. ER operations are not allowed. 4. For galley 4B food cart chiller installed, use only one chiller inflight. 5. Set R RECIRC FAN switch to OFF. 6. Set the PACK switch for the inoperative pack to HIGH. 7. Position the ISOLATION VALVE switch to CLOSE. 8. For increased air flow when the flaps are extended (takeoff and landing), use the APU to supply bleed air to the operating pack. A. Right pack inoperative 1) Do the Supplementary Procedure - Air Systems “No Engine Bleed Takeoff and Landing” (Refer to the Flight Crew Operations Manual). NOTE: Keep the ISOLATION VALVE switch in the CLOSE position. B. Left pack inoperative - PRIOR to takeoff or landing 1) Engine No. 1 BLEED air switch to OFF 2) R PACK switch to AUTO 3) L PACK switch to OFF 4) ISOLATION VALVE switch to OPEN 5) Engine No. 2 BLEED air switch to OFF 6) APU BLEED air switch to ON. C. Left pack inoperative - AFTER takeoff or landing 1) APU BLEED air switch to OFF 2) Engine No. 2 BLEED air switch to ON 3) ISOLATION VALVE switch to CLOSE 4) Engine No. 1 BLEED air switch to ON. 21-01
  14. You should comment out the rxpW gauge (//), in your "VC section 2" to have Rols radar appear in your VC, try these changes: // VC SECTION 2 /////////////////////////////////////////////////////// [VCockpit02] size_mm=512,512 pixel_size=512,512 texture=$GaugeTwo background_color=0,0,0 gauge00=j41!pmdg_j41_rmu_1, 0, 0, 197, 250 gauge01=j41!pmdg_j41_rmu_2, 197, 0, 197, 250 gauge02=PMDG_BAe_JS4100_3!GNSXLS, 1, 254, 256, 204 gauge03=j41!pmdg_j41_alt_pic, 448, 0, 64, 254 //gauge04=rxpWX500!RDR, 266, 264, 236, 166 gauge04=RolasnRadar!oRadGauge, 532, 528, 472, 331, sweep|icing gauge05=j41!pmdg_j41fms_pu_open, 460,229,27,17
  15. In Manfred Jahn's C-47 the mouseover adjustments work. As they should work with every panel designed with the "classic" way where a gauge is projected on a "VC texture". With complex panels and gauges where there is a 3D "object" instead of VC texture or a combination of the two, the mouse over does not work. Instead the object "screen" is coded to "toggle GPS". Even the buttons may be the same as 3D, so they dont work either and you can't do any adjustment to the radar, buttons or mouse over.