Jump to content

Ross Carlson

Air Traffic Controllers
  • Content Count

  • Joined

  • Last visited

Recent Profile Visitors

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

  1. Somehow this thread escaped my attention last month, but I just noticed the notification bubble in the toolbar at top right. Anyway, better late than never. Thanks all for the kind words!
  2. The devs will be fixing the standalone client (and the new xpilot client) so that it works the same way as vPilot for PTT device detection. The Warthog (and the Rhino) has a different issue where sometimes it is constantly sending button presses, and this makes it so that you can't choose the button that you want for PTT because it always immediately detects the button that the driver is constantly pressing automatically. I will be releasing a fix for this in the next vPilot version. (Both the normal and the AFV versions.)
  3. I'll add B76F as a type code alias in the next vPilot update. If anyone connects using B76F as their code, it will change it to B762 (or whatever UPS uses) for the purpose of model matching.
  4. I believe he is asking how to direct VATSIM ATC audio to the speakers ... this is done in the pilot client settings, not in Windows sound settings.
  5. I received a few errors during calscream last night, one of which is the same as Rob just posted: [02:29:40] Failed to create aircraft AWE2953 using model "BVA_FAIB_A319CFM_AAL-AmericanUW". The model may be corrupt or missing. vPilot will try to create the aircraft with a different model. [02:29:41] Failed to create aircraft CPZ6057 using model "BVA_RAI_E75L_CPZ-Compass". The model may be corrupt or missing. vPilot will try to create the aircraft with a different model. [02:29:50] Failed to create aircraft AWE2953 using model "BVA_FAIB_A319CFM_AAL-AmericanSL". The model may be corrupt or
  6. Running the latest version, I've received some errors where vPilot tries to use the Robinson R22 to render a helicopter. The default R22 is not usable as AI, so it should be removed from the VMR file.
  7. I just promoted 2.1.11 to Stable, so now the beta and stable channels are the same. So you can keep your vPilot channel set to Stable if you want, and you'll now get 2.1.11 the next time you run it and perform the update.
  8. You are probably already aware of this, but that could be a matter of the static_cg_height value not being set correctly in the aircraft.cfg. vPilot uses that value (along with the height of the terrain at the aircraft's location) to ensure that the model is never rendered at an altitude that would put the wheels below ground. It could also be a glitch in the scenery but that's less likely. In any case, it's not an issue of scenery mismatch between the two users ... vPilot takes care of that as I described above.
  9. MR, can we touch base via email or phone/TS about the above? This should not be the case at all. You should be able to run multiple packages and set the priority for model matching, such that, e.g. vPilot will use BVAI's model matching rules first, then fall back to other packages. And it certainly should not cause vPilot to crash!
  10. It says on the 4.1 release page that they recommend just updating the client: "It is strongly recommended to only download and install the Client as there are only minor updates to content and scenery for this release." On that page they list the changes in each component so that you can decide what you need or don't need. The content and scenery changes do indeed look to be quite minimal for 4.1.
  11. That can be done by downloading the same data file that tools like VATSpy use.
  12. Anybody know what they mean by "online ATC integration" on the COMMS page?
  13. No, it does not. I plan to bring that feature back at some point to allow testing of custom rule sets and to help people find corrupt models that cause the sim to crash.