Jump to content

Neil Farrington

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Neil Farrington

  • Birthday March 17
  1. Hi Raihan, Are you copying the key with the '-----BEGIN PUBLIC KEY-----' and '-----END PUBLIC KEY-----' sections? You should make sure you include these parts when saving the key.
  2. VATS.IM is a URL shortening service for VATSIM and its members, and is now available to the public for general use at https://vats.im/. The service has been in use by VATSIM UK since 2014, providing shorter URLs that allow easy and memorable access to resources such as docomeents and charts, and a way of providing pilots with simple links in an Air Traffic Controller's ATIS or controller information block. Due to the development work required to broaden the service's access, VATS.IM has been restricted to only VATSIM UK for the longest time. However, with the appropriate infrastructure
  3. This is the same issue as viewtopic.php?f=134&t=76302 - unfortunately, the demo SSO environment isn't available at the moment, which means when the JSON response is received, it doesn't have the correct format. Currently, the demo environment simply returns "DB1001B", however when functioning properly, it should return something like: {"request":{"result":"success","message":""},"user":{"id":"1104841","name_first":"Neil","name_last":"Farrington","rating":{"id":"4","short":"S3","long":"Student 3","GRP":"TMA Controller"},"pilot_rating":{"rating":"1","1":{"id":1,"short":"P1","long":"On
  4. Agreed on all counts... we're literally saying the same thing. I wasn't at all suggesting it would be a solution people would use, since it would be so inaccurate - it's a stepping stone to the end goal, for a small project, for a new programmer.
  5. Absolutely - I suggested custom distances because of that fact, so they're at least more attuned to a realistic value. With the max allowed APP range of 150 and the max CTR range of a whopping 600, the vis range itself would be wildly inaccurate. I'm definitely not saying it's a great solution, or even a good one, just that for a personal project for a new programmer, where motivation can waver, especially in the face of such complexity, it's a very simple solution to allow a milestone to be reached, which can then be developed to the necessary complexity.
  6. If I recall correctly, the coordinates listed for controllers in the data files are the centre of their primary visibility range (you might want to double-check this, though). Using this data, you could warn a user when they are n miles from the visibility centre of an online controller (e.g. 150 for CTR positions and 60 for APP positions) Knowing how lengthy projects (particularly the complexity headache of trying to define all of the constantly changing airspace sectors) can drag on and all motivation to complete them be completely lost, this would be a significant stepping stone and som
  7. Thanks for that - I've gone ahead and merged it
  8. Hi Zach, The only recent issue we encountered was with OSTicket v1.10, where we had to implement the following change: https://github.com/VATSIM-UK/Helpdesk/commit/345c27fd37d938c6fe47b0ffbc3e3776f0f11b9c As per Kieran's request, if that doesn't help, could you please provide a little more detail on the issue?
  9. It looks like the issue is only present over HTTPS. Since HSTS is enabled, if you've previously visited the site via HTTPS in that browser (if the browser supports HSTS), you'll be forced to use HTTPS even when attempting to connect to the HTTP version.
  10. I've done a fair amount of late night controlling in the past, and given that I am the only position online, I often get pilots from airports a number of miles away calling me up, and very occasionally, a new pilot who ends up keying up on frequency and continuously transmitting. While I try and help them fix whatever problems they're having, I tend to reduce my vis range away from the aerodrome they're at, so that they drop of my frequency, and I don't get a 4AM earache. Given that they do drop off my frequency after the vis range updates, this is my basis for audio being connected to the vi
  11. Not at all, your English is perfect, it's just not the easiest of topics to explain. No, there are no separate ranges for scope and radio - they're both related to the set visibility range on the client. As Bremen Radar is a CTR position, they can often have a high vis range of 300nm+, and of course, some controllers also overextend. The distance between Bremen and Modlin is 400nm-450nm, so really, all it would take is a 400nm vis range for the positions to overlap, on top of any additional range added by the pilot client. The next time it happens, you could do a little investigati
  12. Hi Adam - your wording is a little confusing, but I essentially understand what you're asking. Skip to the bottom for a brief summary, as I've made things even more complicated. In Euroscope (and any other controller client), the range that you set in the connect dialog is a set radius, for example 400nm. The range set on that slider is generally referred to as the vis(ibility) range, and is directly related to the visibility point that is set. The visibility range is the radius extending outwards from the visibility point. Primarily, this means that the controller sees live, active tr
  13. It appears as though there are a number of different causes for the connection dropping between FSX and Windows 8, the power configurations being just one of them - I myself tried this solution before and the connection still kept being dropped. My way around it has been to use FSUIPC to map all of the controls, and disable the controllers in FSX itself. It's a pain to set up, but once everything is setup and configured, FSUIPC takes care of everything, and it actually provides much more flexibility for changing any controls in the future.
  14. Changing the values may alter the physics slightly, although I honestly don't know - as mentioned before, you can simply set these to weird/extreme values to test if the physics change. Everything is reversible, remember. The values given are in relation to a central reference point, and will be highly different depending on the aircraft. There's no way of knowing where they need to go without using some form of software, which will help you visualise the aircraft and the recorded values. That's really all I can bring to the table on this discussion - I know what's wrong, but I can't p
  15. Thrust lines? Not quite sure what you mean there - it may be a confusion with terminology: On reading your first post again, I believe you may be mixing up contrails (which you are referring to as thrust lines?), which trail behind the engines, to the wingtip vortices, which appear behind the wingtips. You'll need to clarify whether we're talking about contrails, or wingtip vortices, as you mentioned both. Changing the engine position will most likely start messing with the physics, although simply testing it out with extreme values would confirm this. Given that engine positions are usua
  • Create New...