Page 1 of 6

New Feature Requests

Posted: Mon Sep 26, 2016 4:22 pm
by Peter
Major Features:
  • Drone formation aircraft. AI aircraft can be added to your formation flight.

Minor Features (Priority Order):
  • P3D Add-On folders,
  • Allow take over of recorded aircraft during flight.
  • Synchronize system failures.
  • Aircraft collision detection and engine damage. Damage on recorded aircraft, AI/physics takes over.
  • Flight route and remarks.
  • Nicknames saved in recordings.
  • Copy date/time.
  • Glider tow rope physics.
  • Spot view control from aircraft list.
  • Display nearest airport for each aircraft.
  • List of nearest airports with distance, bearing and elevation.
  • Share flight plans between pilots.
  • Highlight bad network connections.
  • An option to allow network pause. So everyone in the session pauses at the same time.
  • Keyboard support for some features, e.g. Follow.
  • Visual indicator of relative positions.
  • Custom animations. C130.

Worth Further Consideration:
  • Persisant/distributed information storage. For example, offline data for users' aircraft last position.
  • Post-flight formation analysis tool.
  • FS9 support, via FSUIPC.
  • MacOS and Raspberry PI (target ARM).
  • RESTful, ACARS interaction. Web details and mapping capability.

  • Extend radar range. Version 1.1.16
  • Elevation correction for different scenery. Version 1.1.7
  • Shared cockpit: Battery, GPS, Pitot, bug, OBI, pump, prop sync, Right Master ALT, r/a trim, right selector. Version 1.1.7
  • Minimize to System Tray. Version 1.1.6
  • Different model scans for each simulator connected. Stop warnings if running on a server. Version 1.1.6
  • Add filter to substitution windows. Version 1.1.6
  • Default substitution for each type role. Version 1.1.6
  • Auto substitution. Version 1.1.6
  • French translation. Version 1.1.5
  • Command line launch for Windows servers. Version 1.1.2
  • Hub network. Version 1.1.0
  • A way to bookmark the current session. Version 1.1.0
  • Option to ignore certain aircraft in the list. Version 1.0.14
  • Radar support. Version 1.0.13
  • Choose specific folders to scan for models. Version 1.0.13
  • Resize Aircraft window. Version 1.0.12
  • Recorder Toolbar. Open a window for managing recording and playing. Track-bar controlled. Include visual markers for points of interest.
  • Allow host name entry as well as IP address. Version 1.0.11
  • Option to save log files from the Monitor window. Version 1.0.7
  • Show closest airfield. Version 1.0.7
  • Get weather data from other pilots. Version 1.0.3
  • Show distance, bearing and tracking data in aircraft list. Version 1.0.3
  • Re-position behind other aircraft. Version 1.0.3
  • A user-friendly list to choose other clients and hub IP addresses. Version 1.0.0
  • Enable squawk code. Version 1.0.0

Re: New Feature List

Posted: Wed Oct 05, 2016 6:25 pm
by MartinCANCoast
Any thought about MacOS Support? I have a couple of pilots on my VA that use X-Plane on MacOS who would love to fly multiplayer. They'd most likely also be willing to act as Beta Testers.

Re: New Feature List

Posted: Wed Oct 05, 2016 8:34 pm
by Peter
MartinCANCoast wrote:Any thought about MacOS Support? I have a couple of pilots on my VA that use X-Plane on MacOS who would love to fly multiplayer. They'd most likely also be willing to act as Beta Testers.

Hi Martin, that's an interesting question. I just had a very brief look online and there does appear to be a way to run .NET applications on MacOS. So, basically if I can get X-Plane support into JoinFS, there may be a relatively easy way to get it running on MacOS. I shall look into this further.


Re: New Feature List

Posted: Wed Oct 05, 2016 9:35 pm
by MartinCANCoast
Thank you Peter. Lots of grumbling out there about windows 10, so a MacOS client might be a good thing.

Re: New Feature List

Posted: Mon Oct 10, 2016 2:39 am
by Grumpy
Hi, Pete, I was introduced to this clever little doodad and its sooo cool!!

At first look, So simple, even I can make it work!!

    Will it run on a Raspberry PI3?
    Does it need anything really Microsoft stupid?
    Can we have a dropdown box for the JOIN IP list with a text window tied to it alongside to put meaningful names?

seeing as it is NOT tied to any flight sim, a Raspberry Pi makes it so cheap to run and it could just sit there.



Re: New Feature List

Posted: Mon Oct 10, 2016 8:28 am
by Peter
Grumpy wrote:
    Will it run on a Raspberry PI3?
    Does it need anything really Microsoft stupid?
    Can we have a dropdown box for the JOIN IP list with a text window tied to it alongside to put meaningful names?

Hi Bob,

Great ideas. I was also thinking about some sort of drop down box and text names the other day. I'll add it to the new feature list.

I've also had requests for MacOS. While porting to other systems usually requires a lot of work, JoinFS is developed with .NET and I believe it may be possible to do a .NET port to linux so that it would work on the Raspberry Pi. I need to investigate this further. It won't be a high priority just yet, but it is something that I would also like to see happen.


Re: New Feature List

Posted: Mon Oct 10, 2016 9:37 pm
by bunoire14
Hi Peter,

Ive just been fired your link for a pal in a VA. Firstly ive been out of the "Cockpit" for some time now but thank you for finally filling the huge gap in flightsim MP! Might even tempt me back ;)

Secondly... I was wondering two things, firstly is there a Linux version available or in the Works.... especially if your working on a MacOS version... mainly for the Node mode i guess. Idea being it could be dropped onto a Cloud VM and run as a background process to host the larger scale sessions.

Thirdly... Do you have any plans to throw any data out of the system that could be access or optionally pushed to another service? I am rewriting the unnamed VAs website and will be designing it around a RESTful API so that I can consume and provide useful information to the pilots. Originally I was thinking to use it to allow for ACARS interaction with the website (amongst some other funcky ideas i had) but I was wondering if your software may be able to fire out variables to a configured API endpoint to track say number of users on the session? Callsigns? Locations? Flight time? fuel? weather?... even COOLEr if you could consume requests back in.... say ChangeWeather("ThunderStorm") ;) LOL

Any pointers would be great. Once again fantastic work.


Re: New Feature List

Posted: Mon Oct 10, 2016 9:59 pm
by Peter
Hi Olly,

If you've been tempted back to the cockpit then I must say this little project must be working.

Well, I'm certainly considering MacOS and linux at this stage. They haven't quite made it onto the 'new feature list' yet as I need to investigate it a bit more. All I can say is that if .NET applications can be ported relatively easily to other platforms then it's on.

Your last point sounds very interesting. I haven't considered this at all so far, but it does sound rather good. It will be a nice way to advertise your own JoinFS node via a website. There might even be a way to include a user-friendly way of adding the server address to their JoinFS client without having to mess around with IP addresses. I shall investigate further.


Best regards,

Re: New Feature List

Posted: Mon Oct 10, 2016 10:28 pm
by bunoire14
Hi Peter,

Im happy to help with any testing from an external API type approach. Just let me know. I could have something rigged up in fairly short order just to play with. Obviously there are probably more important things on the feature list first though ;)

Immediate use case that comes to mind for VA's may go like this (and forgive me... having never actually used the software myself... yet... this may be inaccurate)

1. User Loads flight in FSX (For Arguments Sake) and Sets their Aircraft Identifier/Callsign in Game to some reference issued by the VA thats unique to that Pilot.
2. User connects to a joinFS session.
3. JoinFS Session has a API endpoint configured including API auth key.
4. JoinFS logs time user spent on the session???? (No idea if this comes out of the box)
5. Once the user disconnects from the session a PUT request is fired off to the API and it logs a flight on the VA Database against that pilot/aircraft along with associated stats and times, which then allows the Developer to manipulate, play, display analyze the data as needed.

So in essence the Pilot has to just ensure one thing is configured in the simulator (This unique reference) and everything else is done for them......... Sys Admins or hosts need to insert and API end point and auth key into their JoinFS software and Voila. Integrated ACARS without messing about installing other applications and minimizing windows to start and stop them etc.

Also being able to push information back the way could, as you say, create a much easier configuration for the user. Insert API Key and Endpoint... initial request is fired off for "Configuration Info" from the VA's API and it returns the IP address and any password for the session? I guess this means also if the IP address changes or the password changes.. its automatically pushed out to the software?

Would need to keep an eye on FPS though I guess.... not sure what this sort of extra traffic would do to the experience in flight.

Just a thought ;)

Let me know if you want any help on this front. happy to assist!

Re: New Feature List

Posted: Thu Oct 13, 2016 3:53 pm
by karl
I see that you have shared cockpit on the feature list.

I recently had a conversation with the coders at a start up called TFDI. I asked them about the limit of two users in one model (aircraft, boat, etc...). I think the example that I provided how this wasn't a hard limit was TacPack (TP). In TP the server can place a carrier model into the sim. Other users land on that model and that model can move around the virtual world. Back in the 90's a program called Air Warrior allowed 8 users on bombers which could fly through that virtual world.

After an initial pessimistic response they got a bit more interested. In the next day or two the sent me a message saying that the feature had been enabled with 2 pilots being able to share control of their aircraft but no real limit of the number of people connected to it in the role of passengers per se. I'm sure they used a third party method like Majestic uses to create the connection between the users.

Just a thought for your future consideration.