ncngrr

I've concluded that my earlier suspicion is correct. I put the -90, -45, and straight ahead on one camera facing -45. That works. I put the +45 and +90 on a second camera facing +45. That works too. I still have some tweaking to get it perfect, but it's close now.

I have no joystick. Is there an easy way to see all assignments across all devices? I can check for yaw being assigned to multiple devices causing conflict…

I do not have turning control using my pedals while taxiing on the ground. Thanks.

Five (5) monitors spanning 180 for outside views and 2 PCs. The center monitor (straight ahead) is for the MSFS 2020 server (i7-4790K, RTX-2080 GPU). The other four (4) monitors are for the remaining (-90, -45, +45, +90 degrees) outside views (i7-9700K, RTX-3080Ti GPU). The LAN seems to handle the data traffic just fine (PCs using Ethernet cables through a managed switch). The problem is the inability to setup the displays for all four monitors oriented in their correct orientations. I understand Wideview manual to say i need to edit the camera.cfg on the client PC for [CAMERADEFINITION.0], which I did for the +45 degree view. That seems to work fine, as does the +90 degree view. The problem is with the two left (-45 and -90 degrees) views. The -45 is almost okay but the -90 is nowhere close. I'm guessing the problem stems from trying to get a -90 degree view from a "camera" pointing 45 degrees to the right. Yes? Is there a viable solution to this problem, with 2 PCs? Thanks. Scott

Thanks for the reply! Unless I'm missing something, I seem to be able to assign only one function to an axis at a time (which seems correct to me anyway). I tried both default settings (XPlane recognizes the rudder pedals) and I tried manually assigning the yaw function. Yaw is the correct function for rudder pedals... right?!?

Virtual-Fly rudder pedals have no effect on C172 nosewheel steering while on the ground. Pedals do produce yaw effect while plane is in the air. I'm new to X-Plane, so I'm confident i've done something wrong. I enabled the XP-11 Data Output and verified the rudder inputs (per the troubleshooting article); of course, I expected that to work just fine since the plane behaves correctly to pedal inputs while airborne. Thoughts? Thanks.

Did you resolve this? I just bought X-Plane yesterday and have the same problem. Autopilot is off. Elevator trim automatically stays at full nose-down no matter my attempts to change it. C-172 plane un-flyable.

Have you looked at FSFlyingSchool Pro by FS Inventions? Does anyone have experience with their product… it seems to support what you’re after, as well as many other things… Scott

I'll do that! Thanks again!

1. Downloaded/installed/registered msstdfmt.dll in both C:\Windows\System32 and C:\Windows\SysWOW64 folders. It took a bit of learning how to register .dll files, especially as an Administrator a. I entered "run as administrator" in the search box at lower left corner of screen and received an "Administrator Command Prompt" dialog with "C:\Windows\system32>" prompt where I entered regsvr32 "C:\Windows\System32\msstdfmt.dll" b. Windows returned a dialog indicating my command was successful. 2. Now when I start RCv4, I get the home screen; entered a flight plan (*.pln), and instead of getting the error dialog, fields within RCv4 populate with what appears to be helpful information. 3. I suspect it works now (or at least this is progress). I now need to read the operator manual so see what to do next! Thanks, Ray. Scott

Okay. I checked the P3Dv4\Modules and still see FSUIPC6 in it... I sent you a PM with e-mail address. Thank you. Scott

Okay. Thank you.

Win10, P3Dv4.5 on non - C drive Here's the install process: 0. Uninstalled FSUIPC 6.1.8; installed FSUIPC 6.1.9 (per Ray's instruction) 1. Ran installer as Administrator to an "S" drive; accepted license agreement 2. Selected "FS X Full - RC v4.3, FSUIPC, Chatter, Pilot and Controllers in the Components dialog 3. Allowed Radar Contact Start Menu Folder with shortcuts; reviewed all of my selected options 4. Watched as [apparently thousands of] files were installed over several minutes 5. Watched as installer installed FSUIPC 4.x 6. Received dialog "Looking in registry for FSX install path: .... 7. FSUIPC4 dialog: "User identified path: "F:\P3Dv4" Checking version of FSX.EXE: ... Version 4.5.14.34698 (Need at least 10.0.60905.0) !! WARNING !! This version of FSX is later than any known by this FSUIPC4. There may be problems. Please check for a later version of FSUIPC4! 8. Launched RCv4.3; input registration key with RCv4 Encrypt app 9. Launched RCv4.3 again, this time getting to the "Main" menu screen 10. Clicked on "FS200x Flight Plan (*.pln) button, selected flight plan that I created using the P3D Flight Planner 11. Received Radar Contact dialog, "Run-time error '713': Class not registered. You need the following file to be installed on your machine. MSSTDFMT.DLL. 12. Clicked OK; RCv4 CTD

Will do. Currently running paid version of 6.1.8 from March 22; 6.1.9 will fix things?

I saw DeltaAir's topic from 2020; was going to reply there, but saw Ray's message to start a new post, so here goes. RCv4 says I should point to the FSX.exe file, which I don't/didn't have. I tried two strategies: 1) saved copy of P3Dv4.exe as fsx.exe; RCv4 indicated that the FSUIPC version isn't compatible with that version of fsx.exe... and 2) created a .txt file, renamed it fsx.exe; RCv4 said it couldn't retrieve version information from it. I'll return to searching for answers within this forum, but, I wanted to get something going in the meantime. Thanks. Scott