Jump to content

KiloJuliett

Members
  • Content Count

    472
  • Joined

  • Last visited

1 Follower

Profile Information

  • Gender
    Male

Recent Profile Visitors

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

  1. Exactly the issue I tried to explain. While center is actually using the correct/raw frequency, vPilot puts a 5 there when the 25 kHz channel spacing requires it. But this is just a vPilot thing. And it seems vPilot also requires you to use the adapted frequency to connect it back to the original channel, which is technically without the 5. I thought vPilot would also accept the actual/correct frequency (ending with the 0), but maybe this is not the case for the MFS client. I'll check with my setup for P3D and let you know.
  2. What simulator do you use? I seems then you are able to fool the VATSIM pilot client and bypass the correction logic. Technically seen, there are no actual .xx5 frequencies on VATSIM. It's all just made to look alike. See here the extracts from the AFV configuration. This is what the controllers use when connecting on these positions.
  3. It's basically VATSIM still living in the 25 kHz times. Back then, there was no need for 3 decimals and you were fine with 2. Old simulators also still have this kind of display. So it would show 129.42 or 119.72. You could only tune that and a RL equipment would know that 129.425 is the frequency to be tuned. So the precision basically doesn't need a 3rd decimal. And this is exactly what VATSIM askes it's facility engineers to consider and enter data only up to a precision of 2 decimals, which basically means that the 3rd decimal always is a 0. Not all facility engineers though work according
  4. A revision of the same data cycle is usually only issued if there was an issue with the package in question. This seems not to be the case for the EFB 2.0 one, so everything is fine. E.g. for my FSLabs Airbus, also no second revision of the cycle 2102 has been issued.
  5. Looks like a priority issue of the different EFB windows. Did you hover over the EFB symbol in the task list and then select every of the EFB windows after each other to check whether this brings the ATC Ribbon on top of the main window?
  6. The Update of the EFB DB needs to be done via the DbBuilder. Refer to Manual 4 Database, ยง2.4.
  7. This is the location where you will see the call sign if a SimBrief ICAO flight plan has been correctly imported.
  8. Virtual Airlines usually are a hobby as well, so this is not contradicting. I'm not aware of any other discounts nor of the conditions, under which Virtual Airlines share such a discount code.
  9. I've created a pull request to change the VATspy file accordingly. Once it has been approved, APP should show up correctly for RKSI.
  10. Is your scenery also using the same frequency? The problem usually not the navdata, but the scenery that still uses old data. And if they don't match, you get the "outdated" message.
  11. To make vPilot changing frequencies, use the command ".com1 [FREQUENCY]". I don't know if the sync between vPilot and MSFS works. But I think it should. Then you can simply change the frequencies in your aircraft and vPilot will detect this change.
  12. But a snapshot target wouldn't have a vector, would it?
  13. Urs, isn't the filtering only relevant for the snapshot data? The target on the screenshot however looks like a live one, which shouldn't be there after all, as the network client shouldn't return your own connection as an AI target again. And then, the flightplan call sign shown on the right bar of EFB seems to be the same as the call sign shown on the map.
×
×
  • Create New...