Hardware support
-
I'd really like to see this, as well.
-
Any info regarding display export of FMS appreciated
-
We don't natively support any external FMS hardware at this time; however, software such as SPAD.neXt can be used to control buttons via Lvars.
We do recognise that FMS hardware has become more accessible to larger parts of the community in recent years, and supporting that hardware in our products is something that we have logged on our internal feature request trackers for evaluation.
Mark - Just Flight
-
That's great to hear. I hope this feature makes it onto the implementation roadmap. Affordable CDUs are no longer niche products among the audience interested in this aircraft, but quite common.
@esaahonen Agreed. More and more people will be asking for this -- and just binding the buttons isn't very satisfying compared to utilizing the entire unit.
-
S storemaster referenced this topic
-
I'm going to hold off buying this until full functionality with hardware CDU is added. It's been something that has frustrated me with the RJ Professional and I hardly fly it currently as it's the only 3rd party aircraft I own that doesn't have this functionality. I consider it a must have feature now.
-
We don't natively support any external FMS hardware at this time; however, software such as SPAD.neXt can be used to control buttons via Lvars.
We do recognise that FMS hardware has become more accessible to larger parts of the community in recent years, and supporting that hardware in our products is something that we have logged on our internal feature request trackers for evaluation.
Mark - Just Flight
@Mark That's good to hear.
Would you be able to make the screen data available, for 3rd party tools to be abe to display them on the MCDU?
Text and formatting instructions would be necessary, so it could just be a single read-only var, or a a var per line, containing text.
If you'd like, I can forward you the spec of MobiFlight driver input, though of course community can build a translation layer as long as you are able to export the output.
-
There is a post here on how to get the display variables with SPAD.Next - it will need a little conversion to other tools however the variables will remain the same:
https://community.justflight.com/post/51540
-
There is a post here on how to get the display variables with SPAD.Next - it will need a little conversion to other tools however the variables will remain the same:
https://community.justflight.com/post/51540
@ScotchMist correct me if I'm wrong. I'm a spad user also. We could always code our MCP type devices to display. The problem is with the MCDU/CDU displays. That's the one we are unable to use on all just flight aircraft.
-
You're correct in regards the MCDU however there was FCU mention earlier so thought I'd cross reference as that post slips down the list very quickly...
-
I was really hoping that the F100 would have it considering it has a reasonably modern FMS. This was already requested for the RJ and I can understand that with that plane already released it was not going to be developed, but for the Fokker it would be really nice to get. With a couple of hundred Australian Dollars for a Winwing FMS it’s definitely not just for the cockpit builder and even planes like the CRJ support it even though they are not considered top tear. Anyway, I am not sure what is involved, but I am sure you can sort it out if it would get the focus and priority on the list. In the end if people spend a lot of money for hardware, they will check what planes can support it especially with so many great addons coming to the community
-
M Mark referenced this topic
-
So, not sure if this is of use, but the first Mobiflight profile for Winctrl hardware has been released on flightsim.to:
https://flightsim.to/addon/111120/mobiflight-winctrl-fcu-efis-throttle-profile-for-justflight-fokker-70-100
Also, they're asking in the Winctrl dc for feedback re them adding support for the Fokkers:
Maybe jump in there and let them know you want it:
https://discord.com/channels/1444993890355511326/1521266758462210069
-
There is no problem at all with hardware. We have tools like Spad.Next, Mobiflight, Axis and Ohs, etc to make it work. All we need is that developers make the variables and data available for configuration - which sadly Just Flight has not yet fully implemented.
-
For anyone interested, I created a profile for the new WinCtrl TCAS in Spad Next (as of right now, you'll need to enter the Beta channel in Spad Next to use it) Snippet 17363.
The display was quite a challenge to get right.
https://youtu.be/eonsUzKxeZk?si=ErZZtOhq7z1gy3Aq
@storemaster said in Hardware support:
is there already existing or planned hardware support (i.e. winctrl) for FCU
I also created a WinCtrl FCU profile. Snippet for that one is: 17282