rlw9sr

Any suggestions for getting around a totally locked cockpit (no movable switches, buttons)-I’ve followed the complete install/reinstall method detailed on Discord-I’ve deleted the WASM directory in MSFS2020-Also I have auto-started the plugin, stopped it via the TM, and restarted it manually-still no joy-any help would be appreciated-thanks rw P.S. Only the default livery is used

Thank you--

Thanks for the suggestions--I am unable to upload the screenshots (from an URL)--FWIW I do see that the assigned has changed--I will create a new template before the next flight

Thanks--I will forward a screen shot shortly-What I mean is that I boot up the aircraft and AXOs--the aircraft profile has both axes (L,R Brakes, Rudder, Spoiler) and buttons. If I double click on the Axis Rudder Set (AXOs) it shows the Rudder Axis is assignment to the PFC Throttle Quadrant! I have to reassign (every time) to the WinWing Rudder (Orion)--I appreciate your help

I have a persistent problem. The rudder axis (Winwing Rudder pedals) switches axes with the throttle quadrant. There are no conflicts in the “profiles.” Every time I load the aircraft, I have to reassign the Rudder to the Winwing device. Any ideas as to why this is happening? Thanks P.S. The are also no assignments in fsuipc7.ini

Any suggestions as to how to stop the tutorial from running every time I open the app in the sim? Thanks

Could be but with all the other apps it seems to be OK. I've gone through all the security settings, permissions, allowed app settings, and still the same result--The only difference between the server computer (cockpit display) and this one (scenery display) is that this is a new Win 11 install--however I've validated the settings with those on the server computer--

I reinstalled and ran the APP (Admin permissions) and, unfortunately, the same results occurred. The log files contained the same error message --can't find ...simconnect.dll--Very strange! Any other suggestions would be appreciated--Thanks

Unable to Eliminate Simconnect Error I have installed and uninstalled several times the app. After the sim loads, the "Connection Status" always displays "RED" for a simconnect issue. I have checked the documentation and there is ony 1 Mobi.. module; the C++ 2015 redistribution is installed. I've also excluded the msfs2020 autofps folder/directory. The error log is-- 2024-07-05 15:52:17.621 [INF] ----------------------------------------------------------------------- 2024-07-05 15:52:17.634 [INF] [ App:InitLog ] MSFS2020_AutoFPS v0.4.2.16 started! Log Level: Debug Log File: ..\log\MSFS2020_AutoFPS.log 2024-07-05 15:52:17.637 [INF] [ App:InitSystray ] Creating SysTray Icon ... 2024-07-05 15:52:17.749 [INF] [ ServiceController:Run ] Service starting ... 2024-07-05 15:52:17.751 [INF] [ IPCManager:WaitForSimulator ] Simulator not started - waiting 30s between Retries 2024-07-05 15:53:47.784 [FTL] [ ServiceController:Run ] Critical Exception occured: MSFS2020_AutoFPS - Could not load file or assembly 'C:\Users\rlw9s\AppData\Roaming\MSFS2020_AutoFPS\bin\Microsoft.FlightSimulator.SimConnect.dll'. The specified module could not be found. --The offending .dll is present in the .bin directory--I appreciate your help--Thanks P.S. The app never closes following the shutdown of the sim!

This thread may help--

Understood--The AI roll "pointer' is offset from the vertical by 3'. The yoke is centered/level. Although the roll deflections are nominal, the yoke does NOT move (I have been using the first situation at KPDX). Thanks, Robert Willis

The AI in the DC6B is offset from the vertical by ~3'. The Cirrus yoke shows a red bar during roll calibration; the data for the roll ranges from -.9 to .9 which is similar to the other axes. Any suggestions as to why the AI is offset and the yoke apparent calibration problem? Is there a correlation? Thanks-- Robert

Hans and Rob--Thanks for the suggestions. I had checked the hardware with Prime95 and 3DMark. The flights are long-haul, e.g. YSSY-KSFO with the PMDG 7772. I suspect the G13 because of the previous Side by Side errors; I suppose it's conceivable that an abort command is somehow generated; I can't think of anything that doesn't leave some "footprint." I'll report back--Thanks again-- Robert

I continue to experience random, crashes of Prepar3D (v3.2.3.16769) to the desktop without error messages either in the Event Viewer, WhatIsHang, AppCrashViewer, or via fsuipc.log (Win 7 Prof). I have several devices including a PFC yoke and Throttle Quadrant, Saitek Rudder pedals, GF-ICCS, and a Logitech G13 which is programmed for cockpit and external views. The scenery includes UK2000, FlyTampa, and FSDT; ASN is used for the weather generation. I have examined the dll and exe.xml files and eliminated items one by one to no effect. Initially, I thought their may be a correlation with Side by Side errors msgs generated by the G13; that has been resolved through an update of x64 C++ packages. There's little to go on (as PMDG will affirm). Are there any suggestions or is this a restart from the beginning (reinstall the OS and Prepar3D)? Thanks-- Robert P.S. i7 4930k/16GB memory/GTX Titan X (v364.72)

After an OS reinstall (Win 7 Prof) and re-installation of Prepar3D v3.2.3.16769 (both on new SSDs), I continue to have Hook Errors relating to sim1.dll and visualfx.dll and, recently dwm.exe. There is no event log generated other than the fsuipc.log (v4.494p). The benchmark flight is with PMDG's 772 from YSSY (FlyTampa) to KSFO (FlightBeam). The "parameters" I have changed/varied include: 1) ASN enabled/disabled (via dll.xml) 2) regenerating the prepar3d.cfg 3) GoFlight ICCS enabled/disabled. All of these options produce the same results; at approximately 800 nm to T/D, the sim crashes. The CPU is a i7-4930k; the MB, P9X79 Pro. The GPU is GTX Titan X (v364.51). System temperatures are nominal. Any suggestions or comments would be most appreciated--Thanks, Robert P.S. I did receive an error pointing to the ai_player.dll even though there was no AI traffic enabled!