DaveSCUSA

Thanks, I did allow the trojan in the security. I have to disallow it now. I'll try it now.

PS - The confusing thing, I bet for many of us, is that I have the firewall and defender off (too many resources used). I scan at midnight. With all that off, Windows still killed it. ???

Thanks, can you put it at the top like the "Trial License" post? At least it will be seen as a person creates a new topic.

You were right and I was wrong. I found (not easy) your work around and I installed 7.4.11. Thanks. Perhaps you could put the work around in its own post.

Hello John, Like many, I receive a virus message with ver. 3.4. I have windows firewall and defender shut off. The router has a firewall that recognizes my IP address for a legitimate return of a request. My Chrome download still shows a virus with the download. Running Ver 3.4.12 on the server and Ver 3.4.11 on the client. I downloaded the 3.4 executable (FSUIPC7.exe) from the forum. I now receive the following error: 7914593 [ERROR]: **** The installed WASM version is 1.0.2 while the WAPI is expecting WASM version 1.0.3. Please update the WASM module as this may cause issues. Perhaps there isn't an issue with Windows Defender. I am running Windows 11 on my server and Windows 10 on my client and FSUIPC7 on both. The firewall and defender are off on both pcs. The message from the client is: 8729454 [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 1.0.4 (WASM version 1.0.3) using connection -1 VFSUIPC7.log FSUIPC7.log

PS Do all (A:, (K:, (L: entries require a >? Can your recommend a document that explains? I had a tutorial for syntax in FSX gauges, but can't find it. The XML there is fairly straightforward, but the RPN needed explanation which I had. Wonder why MSFS had to make it so difficult to understand

Thanks John, I used the wrong variable. Using ELEVATOR TRIM POSITION, radians instead to down -60 (-10°) to up 60 (10°). Perhaps I'll split the presets with a delay between. I realized after I said it that presets can't manipulate Input Events. Are you going to provide the C510 Input Events / Events you find to the public?

I want to increase/decrease the The elevator trim using the trim wheel on my Bravo. The switches dont seem to have much control thru the MSFS Controls with the wheel. I want to slow down the rate on the down and up switches. I read another post to increment/decremet the trim by 128 bips. I have tried to create two presets (dn & up). Would you please check the syntax for me. Thanks DA62_Elev_Trm_Dn#(A:Elevator Position, number) (>L:Elevator_Angle_Trim, number) (L:Elevator_Angle_Trim, number) 128 - -16383 Min (L:Elevator_Angle_Trim, number) (>A:Elevator Position, number) DA62_Elev_Trm_Up#(A:Elevator Position, number) (>L:Elevator_Angle_Trim, number) (L:Elevator_Angle_Trim, number) 128 + 16383 Max (L:Elevator_Angle_Trim, number) (>A:Elevator Position, number)

Thank you

Hello John, Though all your help, I have been able to get all keypresses for the DA62 to work. Thanks. I found the delay control ( 1152 ) you provide very helpful in controlling Keypresses when MSFS responds too quickly. Is there a Sim Variable that is set? I would like to use it in Presets if I find a command that may need it. Depends on the keypad timing. May I suggest a few items? 1. You would significantly increase the worth of FSUIPC7 for Alpha and Bravo users if you created a proprietary C510 set of presets to be offered in a paid version only. 2. To use the UI to set controls to buttons or keypresses may be enhance for users if the control search (one where the user enter the first few characters) returns the first entry at the top of the pick list. 3. Is there some way that upon start up that there could be a log option that could separate the InputEvent found and InputEvent parameter received lists from the log when a user request logging Input Events? Another words List On/Off. That way, when user debugging, the log is not too large. 4. Keypresses – Is there a way to turn on/off showing keyboard presses while continuing to show buttons & keys from other devices than the keyboard. I am realizing that most of the KEYDOWN and KEYUP entries in the log are keyboard usage to navigate around MSFS. These suggestions are to allow a user to use the log as a debugging tool while providing the ability to show all the data you need to debug FSUIPC. Thanks

Thanks John, You don't have to be so adamant. You have much more knowledge and intimacy with FSUIPC than most of your customers. If we ask dumb questions it's because we haven't a clue how simconnect works, where things are in the documentation or even most of the MSFS functionality. An example is how to read button/key log entries. If there is documentation, we can't find it. Thanks again.

Just asked for input of why there are KEYUP when I haven't pressed any keys.

Beacuse we may not understand or of continued confusion. I am confused why there are so many KEY entries with "136203 .. KeyUp received from FS but not programmed", especially with keypresses that are KEYUP with no key down. Or with keys that are not programmed in a profile. If there is a discussion on debugging (Advanced User guide) other than Lua, I've not found it. Thanks

Thanks John, You don't have to be so adamant. You have much more knowledge and intimacy with FSUIPC than most of your customers. If we ask dumb questions it's because we haven't a clue how simconnect works, where things are in the documentation or even most of the MSFS functionality. An example is how to read button/key log entries. If there is documentation, we can't find it. Cockspur C510 customers with Alpha and Bravo would be highly appreciative to know the bindings. Especially if FSUIPC was the only product to offer bindings. Thanks again.

John, You don't have to be so adamant. You have much more knowledge and intimacy with FSUIPC than most of your customers. If we ask dumb questions it's because we haven't a clue how simconnect works, where things are in the documentation or even most of the MSFS functionality. An example is how to read button/key log entries. If there is documentation, we can't find it. Thanks again.