Jump to content

Eirik Sletteberg

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. We should be able to build WebRTC-based voice servers, with legacy conversion on the server side between the old voice codec and the new one. That would also let us build web-based clients, running directly in the browser. It's also possible to use WebRTC standalone, so existing clients could use the standalone WebRTC library to connect to the voice servers. In that case, all the people logged in with "new" clients would have good audio, those with "old" clients would have bad audio, and those with "new" clients would receive bad audio from those with "old" clients. I was going to try to
  2. What about dedicating one day every week, possibly on a smaller area/airport, as "beginner friendly", where pilots and/or controllers are allowed to make more mistakes than what would be expected at other airports, at other times? (Or staffing two airports to enable simple A->B flight plans for beginners) It could also lower the barrier to entry for beginners. Some people who are genuinely interested in learning how to fly properly on VATSIM may be intimidated by the prospect of getting yelled at for doing things wrong, or ruining the fun for others.
  3. Also, why not JavaScript? I'm currently experimenting with building a web-based ATC client.
  4. The only good source of docomeentation for SCT files I could find, was this one from VRC: http://www1.metacraft.com/VRC/docs/doc.php?page=appendix_g However, when I open some SCT files meant for EuroScope, the [sTAR] sections are quite different than what VRC's docomeentation says it should be. Here are two examples: [STAR] ; ; ENAT, Alta ; ;ENAT RWY 11 - BADIX 1Q ENAT STARS RWY 11 BADIX BADIX EKTOX EKTOX ;ENAT RWY 11 - ORVAK 1Q ORVAK ORVAK RIXIB RIXIB ;ENAT RWY 11 - UDSAM 1Q UDSAM UDSAM EKTOX EKTOX ENGM STARS RWY 01 PMS RANGE N059.39.15.947 E010.16.01.883 N059.42.20
  5. That's a very nice app you have there! I've now moved my GeoJSON data from D3 into OpenLayers (I can post a demo later), which gives support for zooming and panning, much better and more performant. I considered using electron, but that would defeat both goals; being able to run straight in the browser, and being cross platform (given you run the .dll which is Windows only. But I suppose it's possible to cross-compile VVL to MacOS/Linux)
  6. Proof of concept (UI). This loads the Norwegian sector file from VATSIM Scandinavia, p[Mod - Happy Thoughts]s it to JSON, converts it into the GeoJSON format, and renders it with D3. (Very slow though, unoptimized) ~400 lines of code so far (plus D3)
  7. No, it's not made public yet. It's only a proof of concept; it logs in to an FSD server, interprets the protocol (or a subset of it anyhow) and forwards it to the browser (in JSON format), where it is console.log-ed. It's all written in JavaScript/Node.js. I suppose I could share it on GitHub privately for people who are specially interested.
  8. I really want to build a JavaScript API, to be able to write web-based VATSIM clients. The FSD part would be implemented with WebSockets; a client talking to a proxy that talks to the FSD server. (I have a working proof of concept, except it only speaks plain FSD, while VATSIM uses a modified FSD protocol) One of the main challenges is voice messaging integration - I'm thinking of using a WebRTC gateway, to be able to connect to voice servers from the browser. I really need the help of a C/C++ developer (preferably somebody who has worked with VVL before?) to be able to bridge the gap betwe
  • Create New...