OrtegaS

Hello, Thanks, Steve

The sim (Milviz F15E) before chase plane worked fine. Installing chase plane locked up the whole sim-mostly chase plane refused to work at all. Thru trial an error (long process trying to figure out what addon might be in conflict) I found that disabling the F15 Tool module allowed the two to work together, but without full functionality. Disabling chase plane fixed the problem also. Didn't mean chase plane was not the issue either. Selecting the experimental option in chase plane solved this. Thank you.

Chase plane has an issues with this A/C. Specifically with the load out tool for the F15E. Chase Plane locks up FSX Steam, P3Dv34, and P3d v4.2. The only way to make it work is to go to DLL.XML and disable the milvizpack. ie <Launch.Addon> <Name>MILVIZPACK</Name> <Disabled>True</Disabled> <ManualLoad>False</ManualLoad> <Path>Modules\MILVIZ\Milviz_pack.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> The A/C then works with no lock ups, but then you no longer have access to the load out tool. Is there a work around or up coming fix? Thank you. Steve

Works now! :-) Thank you for the update...... Steve

Ver actually 11.11r2. Setting up Dir To function....enabling NAV mode only seems to act as a wing leveler...Never follows path

Hello. Thank you for the reply's. Yes i have tried everything enabled in the settings to various settings. I am using the latest non beta ver of Xplane 11......ver ..11.10. Steve

Any ideas?

Hello, OK...I have a fresh install of Xplane 11. Absolutely nothing else installed, except for RXP GNS 530. No addon's no plugins. I tried the C172 and the BE58. Both act similarly. The GNS530 itself seems to do what i ask of it, but engaging NAV mode only acts as a wing leveler etc. I don't even have an AV/Firewall installed right now so that cant be interfering (went to a new HD). It worked with those two default A/C in the past. So something must have changed since. I was sure going to a new HD, which I needed to do, with a fresh install of everything would help. Thanks, Steve

After installing the latest ver 2.3.9 the RXP GNS530 no longer seems to react to any autopilot input ie Nav mode, Apch mode. etc. I was having trouble with the Airfoil labs C172 that no one else seems to be having, but now this issue has grown to where there seems to be no interaction with the device and the airplane in any A/C including the default. Where as before the update at least the default A/C would work. I do have the GNS530 set as the master with all options enabled. Win 10 64bit and the latest non beta Xplane 11 update. Thanks, Steved

Hello, I still seem to be encountering issues with the initiation of the GS portion of the KAP140 autopilot. As soon as the GNS 530 switches from TERM mode to LPV mode I engage the APR autopilot function button on the autopilot switching from NAV mode to Apch mode. This should be coupled, but GS is not displayed on the autopilot hence i have to use Vert speed to fly the descent. Laterally there does not seem to be an issue. I cannot determine if its a RXP issue, Airfoil labs issue, or User error . Also the KN62A....should it not read the DME from the GNS530 as default, master NAV device? It does show DME from NAV 2 (radio stack)? It would be a great help to know if there are any other Airfoil C172 XP users who are encountering this pblm or even if not. Thanks, Steve I will paste this post in the Airfoil forum at Xplane.org

Hello, Thank you for your response. "It is possible this aircraft uses a custom autopilot which is not 'recognizing' the overridden input provided by the RXP GNS. Testing the same approach with a default aircraft and the same GNS settings should help determining if the settings, or the aircraft, are the culprits." This seems to be the case. Thank you for you prompt reply. Steve

Hello, Thank you for the release of this fine tool for Xplane. I am currently flying the Airfoil Labs C172. Conducting an instrument appch- type LPV- shows the lateral and vertical deviation bars in the appropriate VOR gauge. I have the RXP GNS 530 setup to automatically tune/connect the GPS to the VOR indicator, connect GPS to autopilot, connect CDI mode to NAV/GPS, as well as RXP GNS 530 as master. With the autopilot engaged and while in Nav mode, the A/C flies as predicted. Once the GNS switches from TERM mode to LPV mode I activate the apch mode on the C172 autopilot. The C172 continues to follow the lateral deviation indicator but does not follow the vertical deviation. Is this correct in this A/C? Is this a feature of the RXP GNS that should work, but is A/C specific depending on its capabilities? Also, shouldn't the VOR gauge automatically set the correct heading or is this also A/C specific. Thank you very much, Steve

I installed chase plane. Start up FSX steam and chase plane initializes and starts up. With FSX running I click anywhere on the chase plane box and the whole program whites out and crashes without fail. Ive reinstalled just to check...same result. It is v03.21 beta. I would have at least thought I would have been able to run the program. Any ideas? Thanks Steve Note: cant include an attachment so here is the log. Sorry. ------------------------------------------------------------------------------------------------------ --------------- ChasePlane Report by ortega.steve@gmail.com on 7/4/2017 5:26:59 PM UTC --------------- ------------------------------------------------------------------------------------------------------ Version: 0.3.21 PLV: 0.3.21 OS: Microsoft Windows 10 Pro .NET: 4.6 RC or later Running Sim: fsx 10.0.62615.0 Supported Current aircraft: No aircraft Current aircraft cfg: No aircraft CFG ---------------------------------------------------- --------------- Installed Simulators --------------- ---------------------------------------------------- FSX:SE "F:\Entertainment\Steam\steamapps\common\FSX" P3Dv4 "F:\Simulations\Prepar3D v4" ------------------------------------------- --------------- Preferences --------------- ------------------------------------------- experimental_version = False ui_refresh_ms = 500 ui_anim_duration = 0.4 view_sel_anim_in_ms = 0.2 view_sel_anim_out_ms = 0.1 view_sel_delay = 300 minimize_taskbar = True x_to_minimize = False turb_pause_ms = 1 always_on_top = False debug_show = False vas_show = True vas_warning = True vas_remaining = True vas_warning_treshold = 400 turb_wind_amplitude = 1 startup_glob_enable = True app_auto_launch = True mouse_middle_view_switcher = True mouse_disable_on_gauges = True mouse_unhooked = False mouse_right_cam_look = False mouse_right_cam_zoom = False mouse_middle_cam_look = True mouse_middle_cam_zoom = False mouse_middle_pan_hide_exp1 = False mouse_middle_pan_hide_exp2 = False pause_turbs_on_mousemove = False pause_turbs_on_mousescroll = True pause_turbs_in_slew = True doors_enabled = False mode_cinematic_ctrl_speed = 1 mode_cinematic_ctrl_inertia = 3 mode_cinematic_duration = 30 mode_cinematic_distance = 1 mode_cinematic_delay = 10 mode_cinematic_vas_protection = True mode_cinematic_zoom = 0 boostFactor = 5 hdr_override = False hdr_brightness = 1 hdr_bloom = 1 hdr_saturation = 1 binoculars = 30 joystick_default_dead_zone = 100 user_statistics = True auto_cpu_afinity = False cpu_afinity = 1111 show_whats_new = True enable_advanced = True enable_trackir = True trackir_reset = True translucent_window = False invert_x_trackAircraft = False invert_y_trackAircraft = False user_defaults = recorder_max_s = 480 recorder_playback_start_s = 60 disableInputs = False drop_object_1 = Flour_bomb drop_object_2 = Propane_Tank_sm drop_object_3 = Discovery Spaceshuttle ----------------------------------------------------------- --------------- Cameras.cfg file for FSX:SE --------------- ----------------------------------------------------------- CFG created on 5/19/2017 3:48:13 AM UTC CFG modified on 7/4/2017 4:46:45 PM UTC [CameraDefinition.012] Title=On-Board(ChasePlane) HotKeySelect=1 [CameraDefinition.013] Title=Outside(ChasePlane) HotKeySelect=6 [CameraDefinition.014] Title=Static(ChasePlane) HotKeySelect=5 [CameraDefinition.015] Title=Gimbal(ChasePlane) HotKeySelect=8 [CameraDefinition.001] Title=Cockpit HotKeySelect=2 //[CameraDefinition.002] //Title=VirtualCockpit //HotKeySelect=1 [CameraDefinition.003] Title=Spot [CameraDefinition.004] Title=LockedSpot HotKeySelect=3 [CameraDefinition.005] Title=FlyBy [CameraDefinition.006] Title=Top-Down HotKeySelect=4 [CameraDefinition.007] Title=NearestTower NoSortTitle=True [CameraDefinition.008] Title=FacilitiesTower [CameraDefinition.009] Title=FacilitiesRunway [CameraDefinition.010] Title=AIPlanes [CameraDefinition.011] Title=MultiplayerPlanes ---------------------------------------------------------- --------------- Cameras.cfg file for P3Dv4 --------------- ---------------------------------------------------------- CFG created on 7/2/2017 5:01:53 PM UTC CFG modified on 7/4/2017 4:46:45 PM UTC [CameraDefinition.023] Title=On-Board(ChasePlane) HotKeySelect=1 [CameraDefinition.024] Title=Outside(ChasePlane) HotKeySelect=6 [CameraDefinition.025] Title=Static(ChasePlane) HotKeySelect=5 [CameraDefinition.026] Title=Gimbal(ChasePlane) HotKeySelect=8 [CameraDefinition.001] Title=Cockpit HotKeySelect=2 //[CameraDefinition.002] //Title=VirtualCockpit //HotKeySelect=1 [CameraDefinition.003] Title=Spot [CameraDefinition.004] Title=LockedSpot HotKeySelect=3 [CameraDefinition.005] Title=FlyBy [CameraDefinition.006] Title=Top-Down HotKeySelect=4 [CameraDefinition.007] Title=NearestTower NoSortTitle=True [CameraDefinition.008] Title=FacilitiesTower [CameraDefinition.009] Title=FacilitiesRunway [CameraDefinition.010] Title=AIPlanes [CameraDefinition.011] Title=MultiplayerPlanes [CameraDefinition.012] Title=IR(WhiteHot) [CameraDefinition.013] Title=IR(BlackHot) [CameraDefinition.014] Title=NVG(WhiteHot) [CameraDefinition.015] Title=NVG(BlackHot) [CameraDefinition.016] Title=Weapons [CameraDefinition.017] Title=Static [CameraDefinition.018] Title=RadarCamera [CameraDefinition.019] Title=VRCockpit [CameraDefinition.020] Title=VRVirtualCockpit [CameraDefinition.021] Title=DISEntities [CameraDefinition.022] Title=VirtualCockpitOnly -------------------------------------------------- --------------- PRESET ASSIGNMENTS --------------- -------------------------------------------------- {} --------------------------------------------------- --------------- CONTROL ASSIGNMENTS --------------- --------------------------------------------------- {} --------------------------------------------- --------------- END OF REPORT --------------- --------------------------------------------- ---------------------------------------------- --------------- CONSOLE OUTPUT --------------- ---------------------------------------------- App Started v0.3.21 Beta Couldn't get remote UriHandler object. P3Dv4 is installed in F:\Simulations\Prepar3D v4 FSX:SE is installed in F:\Entertainment\Steam\steamapps\common\FSX Will load GoogleAnalyticsDotNet Assembly Will load Newtonsoft Assembly Will load Mouse Hook Assembly Will load SlimDX Assembly Will load SimConnect Assembly Assemblies loaded Is Beta: False Login success! Setting Window Position Window Position Set to 8, 912 Getting Janet Janet Aquired Starting the Bridge server Bridge server started Starting Bridge Bridge Started Request sent to server for cam presets Request sent to server for aircraft presets Getting Preferences from server Sleep Mode True Gradual Release Enabled Autolaunch Install for FSX:SE: success Autolaunch Install for P3Dv4: success Initializing Keyboard Keyboard Initialized Initializing Mouse Keyboard Mouse Starting Timer Started Timer Response received from server for cam presets Removing Orphans Response received from server for aircraft presets Checking Cameras.cfg file for sim: FSX:SE in C:\Users\steve\AppData\Roaming\Microsoft\FSX\ Checking Cameras.cfg file for sim: P3Dv4 in C:\Users\steve\AppData\Roaming\Lockheed Martin\Prepar3D v4\ Joystick Detection Mode Disabled Getting Running Simulator Getting Running Simulator Attempting to connect to FSX's SimConnect Setup SimConnect Definitions and Events Initializing Recording Session Recording Session Initialized SimConnect Connected UI Connected to FSX isSupported%true%cb;10906510 No Active sim or SimConnect is already Connected Saving to server in 2461ms Generating Joystick list Adding: 92aeee90-071e-11e6-8001-444553540000 Name: Throttle - HOTAS Warthog Trying to create Thread for: 92aeee90-071e-11e6-8001-444553540000 Name: Throttle - HOTAS Warthog Trying to start Thread for: 92aeee90-071e-11e6-8001-444553540000 Name: Throttle - HOTAS Warthog Adding: c3bea8c0-5ee6-11e6-8002-444553540000 Name: P880 Trying to create Thread for: c3bea8c0-5ee6-11e6-8002-444553540000 Name: P880 Trying to start Thread for: c3bea8c0-5ee6-11e6-8002-444553540000 Name: P880 Adding: 8efcab50-0676-11e6-8004-444553540000 Name: Mad Catz Pro Flight Combat Rudder Pedals Trying to create Thread for: 8efcab50-0676-11e6-8004-444553540000 Name: Mad Catz Pro Flight Combat Rudder Pedals Trying to start Thread for: 8efcab50-0676-11e6-8004-444553540000 Name: Mad Catz Pro Flight Combat Rudder Pedals Adding: 92af8ad0-071e-11e6-8002-444553540000 Name: Joystick - HOTAS Warthog Trying to create Thread for: 92af8ad0-071e-11e6-8002-444553540000 Name: Joystick - HOTAS Warthog Trying to start Thread for: 92af8ad0-071e-11e6-8002-444553540000 Name: Joystick - HOTAS Warthog Button clicked btn_nav_settings tutorial_focusArea Saving Preferences to server Button clicked btn_report isSupported%true%cb;24185674 ----------------------------------------------------- --------------- BRIDGE CONSOLE OUTPUT --------------- ----------------------------------------------------- "Init Connecting to the Bridge server Connected to the Bridge server as client Bridge received message: setProc-32,fsx,10.0.62615.0 CP Version 0.3.21 Bridge received message: isSupported-fsx-10.0.62615.0-cb;10906510 Bridge received message: isSupported-fsx-10.0.62615.0-cb;24185674 "

Ok. Thank you for the reply. Steve

Hello, I uninstalled the beta ver since i removed P3D and reinstalled ver 5.10.1. Have been using steam all along. Now all of my camera profiles do not show up in the camera mgmt section. In the installation folder it appears they are all still there. How do I get Opus to recognize them again? Thanks. Steve

This seemed to work .......sort of. undocking and sliding the window to another monitor, resizing and right clicking all work fine. But, if you drag that window back to your original FSX screen no matter you seem to do you get the dreaded waiting donut cursor and FSX eventually freezes. Thank you. Steve I have also downloaded the guide. Thanks EDIT .....OK! From the second monitor just don't slide back over to the FSX monitor. Undock from the second and it returns to the original and continues to work. To slide back over to the second monitor undock again and it returns. Problem solved. Thanks for product. I am enjoying it.

Hello, I am using ver 3.3 with a triple monitor setup. When i create a 2d popup item, such as pop up FMC, then undock the window to slide to another monitor, I experience a drastic FPS drop to anywhere from 1-5 fps then mouse icon turns to donut and FSX SE becomes unstable and flyable. I read somewhere DX 10 fixer does not support multi monitors. Is this what is meant? Thanks Steve

Thanks....I just tried that......didn't help me. I even tried a different browser. This is the error page i get: ForbiddenYou don't have permission to access /rex-game-studios-m-415.html on this server. Apache/2.4.7 (Ubuntu) Server at www.fspilotshop.com Port 80

I went on today to buy the Majestic Q800 PRO for 60.00. Logged on, put it in my cart and went to pay for it. As soon as i did.......FORBIDDEN! In my opinion the price is too good....hence forbidden.

Done.

Still no change. The gauge information is the same as that shown in my first post: The gauge MPI_CDIGauge.gau file in my FSX (non steam) shows 11/24/2014 10:30AM 10,904kb.

Removed the 5th parameter. No change.

Thank you...... If I do this: [Window03] size_mm=100,100 position=7 visible=0 ident=225 window_pos= 0.000, 0.000 Background_color=0,0,0 gauge00=MPI_CDIGauge!GI106A, 0,0,100,100,1:1:225 //gauge00=MPI_CDIGauge!KI525, 0,0,100,100,1:1:225 Then I am able to call up a 2d popup panel as shown here on the bottom left.... If I do this: [Window03] size_mm=100,100 position=7 visible=0 ident=225 window_pos= 0.000, 0.000 Background_color=0,0,0 gauge00=MPI_CDIGauge!KI209, 0,0,100,100,1:1:225 //gauge00=MPI_CDIGauge!KI525, 0,0,100,100,1:1:225 I can get the KI209 to come up also as shown here: But with my panel.cfg as shown in post 9 I can not get the KI525 to do the same. Thanks.

// RealAir Legacy 2012 [Window Titles] Window00=Main Window01=Mindstar GNS Window02=Blank //Window03=Mindstar GI106A Window03=Mindstar KI525 [VIEWS] VIEW_FORWARD_DIR=0.000, 0.000, 0.000 //-------------------------------------------------------- [Window00] size_mm=1024,1024 position=0 BACKGROUND_COLOR=0,0,0 visible=0 ident=15552 //-------------------------------------------------------- [Window01] //window_pos=0.739583,0.000000 //window_size=0.260417,0.300000 //visible=0 //ident=15531 //zorder=99 //gauge00=rxpGNS!GNS530,0,0,100,100 size_mm=456,520 window_size=0.5 position=8 BACKGROUND_COLOR=0,0,0 VISIBLE=0 ident=11013 gauge00=MPI_GNS!GNS530, 0, 0, 456, 331, 1:2:11013 gauge01=MPI_GNS!GNS430, 0, 331, 456, 189, 2:1:11013 //-------------------------------------------------------- [Window02] size_mm=1,1 position=0 visible=0 ident=15600 BACKGROUND_COLOR=0,0,0 gauge00=RASLegacy!Blank, 0, 0, 1, 1 //-------------------------------------------------------- [Window03] size_mm=100,100 position=7 visible=0 ident=225 window_pos= 0.000, 0.000 Background_color=0,0,0 //gauge00=MPI_CDIGauge!GI106A, 0,0,100,100,1:1:225 gauge00=MPI_CDIGauge!KI525, 0,0,100,100,1:1:225 //-------------------------------------------------------- [VCockpit01] size_mm=1024,1024 pixel_size=1024,1024 texture=$RASLegacy_CFG background_color=1,1,1 gauge01=Config!Options, 1020, 1023, 1, 1 gauge02=Config!RealView, 1021, 1023, 1, 1 gauge03=RASLegacy!InitVars, 1022, 1023, 1, 1 gauge04=RASLegacy!1hzCode, 1023, 1023, 1, 1 gauge05=RASLegacy!2hzCode, 1024, 1023, 1, 1 gauge06=RASLegacy!18hzCode, 1025, 1023, 1, 1 gauge08=RASLegacy!NavCom1, 1, 2, 509, 61 gauge09=RASLegacy!NavCom2, 1, 64, 509, 61 gauge10=RASLegacy!ADF, 4, 127, 332, 49 gauge11=RASLegacy!Xpndr, 7, 243, 305, 57 gauge12=RASLegacy!Autopilot, 5, 177, 292, 62 gauge13=RASLegacy!DME, 4, 305, 256, 46 gauge14=RASLegacy!VM1000C, 579, 0, 445, 446 gauge15=RASLegacy!Annunciator, 0, 379, 453, 68 gauge16=RASLegacy!AOA_Pro, 347, 204, 106, 63 gauge18=RASLegacy!Master_Warn, 346, 271, 108, 107 // =============================================================================== // IMPORTANT - 'gauge19'. 'gauge20, 'gauge22', and 'gauge23' BELOW CAN BE OVERWRITTEN // BY THE CONFIG PANEL. PLEASE KEEP THIS IN MIND WHEN MANUALLY EDITING THIS FILE // IF YOU WANT TO CHANGE THE GPS ENTRIES AND DON'T WANT THEM OVERWRITTEN IN ANY // CIRCUMSTANCE THEN CHANGE THE GAUGE NUMBERS. EG - CHANGE 'gauge 19' TO 'gauge22' // =============================================================================== //gauge19=rxpGNS!GNS530, 1, 660, 504, 364 gauge24=MPI_GNS!GNS530, 1, 657, 504, 353, 1:1:-1 gauge20=RASLegacy!Blank, 0, 0, 1, 1 gauge21=Config!AdfDip, 1019, 1023, 1, 1 gauge22=RASLegacy_Sound!Sound, 1,1,2,2,./SimObjects/Airplanes/RealAir Legacy/Panel/Sound/RASLegacy_Sound.ini gauge23=RASLegacy!Sound_Manager, 1,1,3,3 [Default View] X=0 Y=0 SIZE_X=8192 SIZE_Y=3500 [Color] Day=255,255,255 Night=255,255,255 Luminous=201,64,64