EagleOne49

Success! Thank you so much!

Well I got it working in one aircraft (Just Flight) but lost mouse scroll wheel capability. I also received the following error message in the log: rxpGtnSim.dll.log: 18/06/30 16:02:52.004 13920 - ] # rxpGtnSim64.dll version 2.5.2.0 18/06/30 16:02:52.004 13920 INFO ] 18/06/30 16:07:04.112 13920 WARN ] A component version required by the application conflicts with another component version already active., code: 000036b8 18/06/30 16:07:04.120 13920 WARN ] rxpGtnSim32.dll v2.5.1.0 (32bits), v2.5.2.0 (64bits) 18/06/30 16:07:04.352 08712 INFO ] 18/06/30 16:12:37.390 11060 INFO ] 18/06/30 16:14:14.810 06424 INFO ] Please advise.

Opened P3Dv4.2 this AM. In the process of booting up, Chase Plane did a quick download to my computer. Issues have been solved. Thanks.

I tried reinstalling ChasePlane using the VFXCentral app. I received this lengthy error message: Installation Error: System.IO.IOException: The process cannot access the file 'F:\Program Files (x86)\OldProp Solutions Inc\ChasePlane\ChasePlane.exe' because it is being used by another process. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.File.InternalWriteAllBytes(String path, Byte[] bytes, Boolean checkHost) at System.IO.File.WriteAllBytes(String path, Byte[] bytes) at a.ah.A(Boolean ) at VFXCentral.MainWindow.A(Object , DoWorkEventArgs ) at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e) at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument) Please help!

Update: I uninstalled Chase Plane using VFX Central. Back in the cockpit, hat switch 1 is disabled. P3D>Controls>Joystick>View>Pan correctly shows hat switch 1, but I have to pan/tilt. So, I have a dead simulator until you provide assistance. Pease advise.

I recently uninstalled and reinstalled the Prepar3d v4.2 Client (only). Now, ChasePlane does not auto-launch when starting P3Dv4.2. Furthermore, I can no longer manually launch ChasePlane. Double-clicking on the ChasePlane.exe file does nothing. Please help.

In mid-May 2018, I purchased RealityXP GTN750 for X-Plane 11 (Windows10). It never installed properly after multiple attempts. The GTN750 did appear in 3D cockpits but with blank screens (battery/avionics on), across multiple vendors (Just Flight, Carenado, etc.) I became so frustrated, I just removed the rxpGTN folder from the X-Plane 11 plugin folder. Recent videos showing the Reality XP GTN750 in use rekindled my interest in getting it installed properly. My first step was uninstalling it from Windows10 using the Windows10 uninstaller. I then manually uninstalled various Reality XP folders in Windows10 & X-Plane 11. I started the original (May 2018) setup app and was prompted that an up update was available. I updated it successfully, receiving the file: "rxpGTN-750-XPL.exe," dated 6/1/2018. The following error message was received shortly after starting the executable: C:\Program Files (x86)\Reality XP\GTN Simulation\X-Plane\Reality XP GTN User's Manual (XPlane).pdf An error occurred while trying to replace the existing file: DeleteFile failed; code 5 Access is denied. Click Retry to try again, Ignore to skip this file (not recommended), or Abort to cancel installation. It sounds like I should not have uninstalled the original files. I feel like I've dug myself into a pretty deep hole. Please provide assistance so that I can get out of the hole I created and successfully install this product, once and for all. Thanks in advance.

No error message(s). The sim freezes. After ~5 seconds, P3D crashes. I'll move to support forums. Thanks.

Just updated to v3.180330. Thank you for the fixes! Unfortunately, in both versions, the aircraft brings my P3Dv4.2 to its knees (CTD). I have a beefy (4.6 GHz) Jetline Systems machine with an nVidia GeForce 1080. I have backed off P3D sliders which gives me a few more minutes of air time, but still CTD. Any suggestions or assistance would be appreciated.

Thanks for the updated info re: 1.7, OneWhoKnocks53! I'll need to rattle PC Aviator's cage...

Sorry, SkipperMac. My error. I was cutting/pasting - never a good idea. But, yes, it is in the executable file title for the Flysimware Cessa 441. So, go to your download folder and open the folder entitled "Flysimware_CESSNA_441_FSX--P3D." Then open the folder with the same name and you'll find 4 files: the executable file (application), and 3 text documents. If you expand the width of the file name column, you will expose the entire executable file name: "Flysimware_441_CONQUEST_II_FSX--P3D_REV1.6", or whichever version you own. And to clarify my latest comment in this thread re: the exterior sounds of the C441, I meant to say in the latest version Rev1.6, not Rev1.7 which does not exist for the C441, at least for now. Hope that helps. Sorry for the confusion.

The *.exe file/folder shows the version number in the title: "Flysimware_MITSUBISHI_MU-2B-60_FSX--P3D_Rev1.7". The exterior sound issue that redbarron79 introduced in this thread and that I discussed is still present in Rev1.7 at startup, but seems to "clear up" during climb out and cruise. ?????

redbarron79: Great! I understand v1.6 is now out at the Flysimware store and it is supposed to address some sound issues among other things. I don't know if it is available at other retail outlets yet.

OK. I have a workaround... First, the exterior sound file in question (xTPE331b) and can be found in the sound folder here: FSX or P3D>SimObjects>Airplanes>FLYSIM Cessna 441>sound. Find & play the sound file, and if it sounds OK to you, go no further. For those of you that would like an alternative, open the SOUND.cfg file in the same sound folder. Using a text editor, scroll down to the grouping with the heading: [x6902]. Change the next line to: filename=xTPE331a. Now, scroll down to the grouping with the heading: [x441b]. Change the next line to: filename=xTPE331a. Save the CFG file and you are good to go. Now, if Joe or others with Flysimware, say that the sound file xTPE331b is an accurate exterior sound for engine 2, then you can always go back to that sound flie.

I just purchased the C441 at PC Aviator yesterday and am having the same poor exterior sound issues. And, like you, it's driving me nuts! It sounds like a stock FSX C172 sound. The interior sound set rocks! There's a good YouTube video by Storm KILM that has excellent exterior sounds for the 441. I wonder if we have an older version... https://www.youtube.com/watch?v=mcdrbfvfpSg. Any help from Flysimware would be much appreciated!

I got it. It had been so long since I had really configured FSX, I had forgotten that I had to set the resolution for all 3 monitors in the FSX>Settings>Customize>Device (ATI Radeon HD 4800 Series.0, ATI Radeon HD 4800 Series.1 and ATI Radeon HD 4800 Series.2). Now, if I can just get my reinstall activated, I'm back in business. For some reason, the online activation is not functioning... Thanks for your help, Bob. Much appreciated.

Thanks, Bob, for the timely response. I first tried deleting any reference to DISPLAY.Device and restarted FSX. No change. I then deleted the fsx.cfg file and letting FSX rebuild the file. When FSX started you could see it sampling the screen resolutions (flickering screens), but then came up with the incorrect screen resolution. I rechecked the "new" fsx.cfg file and the same DISPLAY.Device data was there. Any other suggestions? Thanks again. Ted

Greetings from a noobie to AVSIM. I've been a MS FlightSim enthusiast going back to the first edition when 3D scenery was "stick outlines". I have been successfully running FSX Acceleration with 3 displays, using 2 ATI Radeon HD4850s for 4 years. I started with three 20" monitors (1440x900x32) with no resolution recognition problems. I then upgraded the center monitor to a 23" monitor (1920x1080x32), and FSX was able to keep track of the two different screen resolutions. Most recently, I replaced the two 20" (outboard) monitors with two 23" monitor (1920x1080x32), matching the center monitor. I also upgraded my GPU with a Radeon 6950 2GB and successfully operated FSX in eyefinity (5760x1080x32), although with very poor frame rates. I decided to test things out and went back to the two Radeon 4850s, using the three 23" monitors. To my amazement, FSX held onto the center 23" monitor resolution, but downsized the resolution of my outboard 23" monitors to 1440x900x32, the 20" display state prior to the monitor/GPU upgrade. I uninstalled/reinstalled FSX Acceleration, keeping only my flight records thinking that would solve the problem. Sadly, I'm still experiencing the same issues. My guess is that FSX held on to the "old" resolution setup through the uninstall/reinstall process. Any help would be appreciated. Thanks. Ted