Jump to content

Frank Kopp

Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

Recent Profile Visitors

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

  1. I use MSFS2020 and tested this with the FlyByWire A320 and the Working Title CJ4 - both allow the input of .x20/.x70. Also I use the EFB2 from Aivlasoft which conveniently list all frequencies along a route. It also allows setting of frequencies into the sim via buttons. As EFB2 reads the published frequencies it can't set the correct frequency if the controller and the API do not provide the 3rd digit. See this ticket: Frequency differences on VATSIM - EFB v2 - Support forum - AivlaSoft Support Forum From my perspective as a user not knowing the history of older sims or client
  2. Thanks for closing the other post, Ross, Wasn't sure if that would have been another team when it comes to vPilot. According to you answer the root cause is the Controllers then - they should put in 3 digits, right? I just learned about the .025-steps - so this should only be an issue with .020 and .070 then, correct? But if a user doesn't now this and use tools like VatSpy to note down frequencies (without double checking in vPilot) it doesn't work. Maybe the simplest solution would be to have controllers input all 3 digits then? 🙂 Another solution would be to make
  3. Also raised this in the vPilot forum: Frequencies which are given with 2 digits but actually need 3 (eg. .220/.225) not working - vPilot - VATSIM Community
  4. Hi, there seem to be an issue with given frequencies and vPilot not "translating" them to the correct 3 digit frequencies and therefore no communication is possible without the 3rd digit. See this post: Frequency inaccuracies in VATSIM API - General - VATSIM Community Might this actually be a vPilot issue? Thanks
  5. Same at EDDB today - VatSpy also seems to use the faulty json data: vPilot shows and requires these frequencies: I'm using MSFS2020 with the Working title CJ4 and I had to tune up to the 3rd digit manually to hear the controller. I assume if the controllers use frequencies with 3 digits the API should provide all 3 digits, right?
  6. Just posted a new bug for this: When having VAT-Spy on a second monitor to the left in Windows 10 it records its position to VATSpyConfig.xml like this: <LastWindowLocation> <X>-1926</X> <Y>331</Y> </LastWindowLocation> If you close VAT-Spy and then try to reopen it like this it will freeze and not start. Removing the above section from VATSpyConfig.xml solves the issue and it starts perfectly on the right screen at x=0, Y=0 the next time. My assumption is that the <X>-1926</X> causes the issue.
  7. Just posted a new bug for this: When having VAT-Spy on a second monitor to the left in Windows 10 it records its position to VATSpyConfig.xml like this: <LastWindowLocation> <X>-1926</X> <Y>331</Y> </LastWindowLocation> If you close VAT-Spy and then try to reopen it like this it will freeze and not start. Removing the above section from VATSpyConfig.xml solves the issue and it starts perfectly on the right screen at x=0, Y=0 the next time. My assumption is that the <X>-1926</X> causes the issue.
  8. Try this: When having VAT-Spy on a second monitor to the left in Windows 10 it records its position to VATSpyConfig.xml like this: <LastWindowLocation> <X>-1926</X> <Y>331</Y> </LastWindowLocation> If you close VAT-Spy and then try to reopen it like this it will freeze and not start. Removing the above section from VATSpyConfig.xml solves the issue and it starts perfectly on the right screen at x=0, Y=0 the next time. My assumption is that the <X>-1926</X> causes the issue. Just created
  9. I have found the issue for this: When having VAT-Spy on a second monitor to the left in Windows 10 it records its position to VATSpyConfig.xml like this: <LastWindowLocation> <X>-1926</X> <Y>331</Y> </LastWindowLocation> If you close VAT-Spy and then try to reopen it like this it will freeze and not start. Removing the above section from VATSpyConfig.xml solves the issue and it starts perfectly on the right screen at x=0, Y=0 the next time. My assumption is that the <X>-1926</X> causes the issue.
×
×
  • Create New...