CallingBarranca

John, Thank you very much. I'll make these changes straight away. Best Regards, Daver

John, Thank you very much. I will try this straight away. Best Regards, Dave

I must first confess that I have recently realized that although I thought I was pretty good with using FSUIPC that I am merely a neophyte. The more I read, the more I understand how little I know. That said, I am trying to learn a bit more about the relationship between FSUIPC and SimConnect. I get that FSUIPC communicates to FS/P3D through SimConnect but I need a bit of help with the exact mechanics. I have multiple switches (buttons) that activate the PTT On/Off feature in FSUIPC. These are Control Yoke MIC switches, and ACP R/T switches. I can assign these to the PTT On/Off feature in FSUIPC without difficulty. But when I try to assign a PTT switch in the PilotEdge Client it only recognizes the Joystick button assignment not the other assignments in FSUIPC. Keith at PilotEdge has provided the SimConnect event names (PILOTEDGE.PTT_ON and PILOTEDGE.PTT_RELEASE) but I do not know how to access these from FSUIPC. Any help, or a pointer to any documentation on this would be greatly appreciated. Dave

Hi John, I believe I figured it out. The darn “Profile Specific” checkbox. Once I made my button presses Profile Specific the trim began working again. I figured it out when I saw that my yoke trim button inputs were being assigned to the JetMax TQ buttons for some reason. That has been another problem. Both the ACE Yoke and JetMax TQ seem to get confused when trying to assign buttons. Ex. I installed the PilotEdge Client and during the setup while attempting to configure the PTT button, the client would only recognize the JetMax TQ and not the ACE Yoke. So if you have any insight there based on the .ini, it would be greatly appreciated. Thanks, Dave

Hi John, Yes. I have controllers disabled in P3D. I suspect the issue may be due to running the JetMax Installer on the P3D computer. The installer asks you to calibrate the axis on the TQ and then write to the P3D/Modules/FSUIPC4.ini file. I was getting a write error for obvious reasons and renamed the FSUIPC6.ini file to FSUIPC4.ini so that the installer could write to it. I then renamed the file and ran P3D. Not sure of I even needed to do this as I was then assigning/calibrating axis in FSUIPC anyway. Also, when running the JetMax Installer the only way I could get it to recognize the JetMax TQ was to disconnect my ACE 737 Yoke until after calibration. So there may be an internal conflict somewhere. Anyway. I have attached the .log and .ini files and appreciate your taking the time to look them over. Thanks, Dave FSUIPC6.ini FSUIPC6.log

Hi John, Thanks for the prompt reply. After my post I reinstalled FSUIPC6 and did not check the “Add XML” option to see if using the .dll made any difference. It did not. I went back to the original “Trim Up,Trim Down” assignments and “Trim Up” seems to be getting me Reverse Thrust on Engine 1 as mentioned when using the Offset method. I’m away from the sim for the evening but will complete the tasks you requested and send you the files tomorrow. Cheers! Dave

Howdy, I have been using FSUIPC for many years and have never encountered this problem. I'm downright flummoxed. I own a JetMax 737 and recently upgraded to Prepar3Dv5. I was having some registry issues prior to upgrading to I started completely from scratch. Reloaded Win10, all drivers, etc. Then installed P3Dv5 and began setting up my network, Sim-Avionics, hardware, etc. Everything was going well until it came to assigning pitch trim to the trim switch on the yoke. I have always used the "Trim Up" and "Trim Down" options from the Drop Down Menu in FSUIPC and have never had any issues. But this time when I try to trim up it yaws violently to the left and nose down apparently does nothing. I tried using an Offset (53F4) that was recommended in the JetMax setup instructions but the same occurred. Most recently I tried using a Custom Control (65607, 65615) which apparently commands reverse thrust on Engine #1. Any help would be greatly appreciated. Thanks!

Hello Peter, Dave here. First time caller. First, Thank You so much for your wonderful applications. They have allowed me to take my flight simulation project to levels of realism that I could never have imagined. I am running a networked B747-400 setup using FSX and PM (All WinXP SP3). The setup is as follows: PC1= FSX Server: FSX, WideServer, USB flight controls attached. PC2= CDU: PM CDU Software, Flightdeck Solutions CDU attached PC3= PFD-ND: PM Boeing GC Software PC4= EICAS 1: PM GC Software, PM MCP Software, CPFlight 747 MCP attached. PC5= EICAS 2 (Lower): PM GC Software, PMSounds PC6= PMSystems I want to use the CDU "Shutdown all PCs" feature to shut all my software apps & computers down, so after reading the WidesFS Technical Documentation I did the following: WideServer.ini User Section: AutoShutdown=Yes Each WideClient.ini User Section: Run1=Application Name Run2=Application Name Close1=ApplicationName (if applicable) Close2=ApplicationName (if applicable) AutoShutdown=Yes So, I fire everything up, get FSX up and running, all clients online with software running. When I use the CDU "Shutdown all PCs" option...PC2 closes its PM software and shuts down. PC1 closes FSX and shuts down. PC6 closes PMSystems and shuts down. But the remaining PCs stay on with their PM software merrily chugging along. I am thinking that the problem is the Net Director file closing before the close/shutdown messages are sent across the network (it is on PC2) but I'm not sure. I would really appreciate your help with this. Thanks, Dave