Jump to content

Ross Carlson

VATSIM Developer
  • Content Count

    4699
  • Joined

  • Last visited

  • Days Won

    2

Ross Carlson last won the day on July 16

Ross Carlson had the most liked content!

Community Reputation

31 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Now try opening the debug window on the remote with the ".debug" command. Press the PTT on the host. Does the remote see the PTT events coming over the network?
  2. On the host, open the debug window, and press the PTT button. Does the debug window show messages indicating that the button press was detected?
  3. Maurizio, I encourage you to abandon that old, outdated method for remote PTT. You simply do not need it anymore, so why bother trying to get it working again? Sure, it's frustrating when something stops working and you don't know why, but if you don't need it anymore, why waste time on it?
  4. I don't know why your previous method stopped working. All I know is that you don't need FSUIPC and WideFS to have vPilot recognize a yoke button press. That PDF you found is from years ago before vPilot supported the remote/host split setup. There is a lot of old outdated information on the internet, and you found a piece of it. :D I will remove that PDF from the server so it doesn't confuse anyone else. All you need to do is follow the current instructions for configuring PTT and you should be fine.
  5. Right, the remote cannot detect a button press on a different computer. Using FSUIPC to convert the button press into a key press and send it via WideFS to the remote, that is not the same thing as the remote detecting the button press. The thing is, you don't need any of that. You can just configure the host to detect the button press, and you're done. No need for FSUIPC or WideFS. As for why your radios are inactive, that's a completely separate issue that I have not addressed yet. I have only addressed your PTT issue.
  6. Are you saying that you are trying to configure PTT on the remote, and it's not recognizing the button press on the host? If that's what you're saying, then that is exactly what should be happening. The remote copy of vPilot cannot possibly detect a button press on a different computer. However, if you are saying that you have configured the PTT on the host, but then when you press the PTT, the transmit light does not light up on the remote, then that's a different issue. Let me know which of these two things is actually the case.
  7. Then you should be able to just configure the yoke button as PTT on the host. You don't need to do anything with PTT on the remote.
  8. I'm confused ... is your yoke plugged into the host or the remote?
  9. Does vPilot recognize the yoke button directly without having to use FSUIPC?
  10. vPilot never turns off mode C ... it only turns it on when airborne if you have that option checked. Perhaps there is some other add-on messing with it?
  11. If it keeps telling you that you need .NET Framework 4.7.2, even after you install .NET Framework 4.7.2, then the installation of the framework must be failing in some way.
  12. As long as the model set is installed into P3D properly, then vPilot will recognize it. You don't have to tell vPilot where you installed models. It discovers your models by scanning your P3D configuration.
  13. No, vPilot is heavily dependent on SimConnect, which didn't exist until FSX. You may be thinking of VRC, which worked with FS2004 for tower view. That was possible thanks to Joel giving me the relevant code from Squawkbox. I could not use that same code in vPilot because vPilot is developed on a different platform than VRC and Squawkbox. (.NET Framework versus C++)
  14. Hi Garry, I'm sure you don't think that VATSIM is blissfully unaware of the new sim or uninterested in getting users of the new sim flying on VATSIM as soon as possible. :D I suggest you sit tight and wait for the official word.
×
×
  • Create New...