VAS Project Forum

mattevans · 2009-06-18 21:07:09

My requests:

- Allow HDG change on autopilot to at pilot control rather than limited to 1-2 degrees per second (Airbus pilots can still turn their hdg dials slowly if they want)
- Sync altitude hold level back to (not from) X-plane (not just a GA request, should also allow for seamless handover from FMC to X-plane AP).
- Receive X-plane dataref inputs for ND mode (map, app, etc), range (10-640) and waypoints, airports, wx, etc
- Receive X-plane weather data and overlay onto ND
- Make ECAM screen more generic/single engine prop friendly

Peter Cole · 2009-09-16 13:11:24

Amen to the above. As a dedicated Mac user, vasFMC seems to be the only option for those of us wanting anything approximating a glass cockpit. vasFMC really is good, but would be even more awesome to be able to use in separate modules, not tied on the included autopilot &/or FMC.

I have a rather comprehensive set of GoFlight modules, but I can't use many of the functions, esp. the GoFlight Autopilot module, because vas FMC overrides the X-Plane A/P. I understand why, but it would be great if we had the option to not use the vasFMC autopilot & FMC - along with receiving X-plane dataref inputs for ND mode (map, app, etc), range (10-640) and waypoints, airports, wx, etc.

Basically, I'm very keen to see just really good glass cockpit instruments - so I can use my hardware with this great software along with X-Plane on my Mac/s. If the team was to develop such a system, I'd definitely donate, as I'd be a certain user! At the moment, the included A/P makes flying harder for me, so sadly I can't really use it.

Kind regards,

Peter C.

joerg.hermann · 2009-09-16 16:34:54

Peter, Matt,

I understand your grief.
If you take the time to read through the forum here, you will encounter numerous explanations, why we did it the way it is.
Contrary to our intention and program design most users seem to use the regular X-Plane panel on a single machine, single monitor setup. This is hard to understand, as we have the major screens, all knobs for interaction and are network capable from day 1 - why should X-Plane display anything else but scenery in a multi machine setup?

How to implement the pulling of a knob on a standard X-Plane AP panel?
How to do that in Go-Flight?
Without this vital information an automated flight a la Airbus is not possible, which is a goal of vasFMC.

Maybe we misunderstand our users.
Maybe all you want is an exterior PFD/ND and your are happy with the default X-Plane AP. This is the common denominator if we stick to standard datarefs:

No x737 interface, as Benedict uses non-standard datarefs.
No Peter Hager Airbus, as he uses non-standard datarefs.
No weather on external devices.
No real FMC, only the fictious internal one, no transitions etc.

Are these restrictions OK?
If this is all you want, in which setup do you use vasFMC then?

If you have the X-Plane AP panel visible on your (primary) monitor - where do you have the X-Plane PFD/ND? They surely react to the range knob.
And where (and what for) are the vasFMC PFD/ND displayed?

Weather on external devices is next to impossible with the current X-Plane. Our best rough guesses will seldom match what you see out of the window. A precise weather display requires significant changes with the sim/datarefs.

We do not know how many people out of the 3k+ d/l use vasFMC on a regular basis. Maybe its only a dozen? Maybe 1000?
Which sim?
Which A/C?
Single machine, single or multi monitor?
Multi machine, single or multi monitor?

It is our fault not to have a call home function telling us that. And without this knowledge it is difficult to decide which features benefit most of the users.

Regarding Matts ECAM request, I also would like to see support for 3 and 4 holers.
Whatever we do in this respect, someone will say: Naah, I want...
There is just no single solution for all users.

I have the impression that the majority of the requests we received lately are geared toward specific single user, one shot projects. Beeing a free time fun project we are reluctant to implement on a single user demand basis as we would end up in a hell of customized builds.

The bottom line is:
We are unsure what users REALLY want and HOW they use vasFMC.

Just tell us and how many users stand behind each option.

Best regards,
Joe T. Hermann

Last edited by joerg.hermann (2009-09-16 19:27:57)

Peter Cole · 2009-09-16 23:32:16

Hi Joe,

Thanks for taking the time to write a great response. I think your reasons for doing vasFMC the way you did are fine. I just think there's more opportunity out there, and vasFMC is in the right place to benefit from it.

There's no doubt a major issue with X-Plane, and the likes of UFMC and vasFMC make this obvious, is the default FMC. The default FMC is very simple. For casual flight simmers it's probably fine, but for enthusiasts it's too simple. Of course vasFMC was not written for casual simmers, so I understand why you've chosen to take the route you have. And then you need a better autopilot if you have a better FMC as the two go together. vasFMC makes sense, but I think it could be useful to another group of users if vasFMC does *less*.

You're right on Joe, I'd love to see an exterior PFD/ND (and ECAM for single and multi props and jets), that received X-plane dataref inputs for ND mode (map, app, etc), range (10-640) and waypoints, airports, wx, etc. I suspect this would be easier than the whole FMC/Autopilot integration anyway. vasFMC is by far the closest product I've ever seen for X-Plane to this ideal, and it would be fantastic!

What I hope for is for vasFMC to just offer some parts without necessarily having to take the whole (pretty much like you can achieve with Project Magenta for Windows). Now... I do like the vasFMC inbuilt FMC and autopilot, but I'd need to be able to interface with it, and the autopilot with external hardware (real life switches and buttons). Even though it's too simplistic, the X-Plane FMC does let us control it with custom keys/joystick buttons. Combined with a small LCD screen, this is a very useful set-up.

So, in a nutshell, what I really wish for is separate exterior PFD, ND and ECAM screens that just to their job well (by receiving X-Plane datarefs). It seems vasFMC is really close do already doing this, and I imagine just a little bit of work could take it there

joerg.hermann · 2010-03-11 23:19:40

Hi Peter,

to cook up an old thread, you stated: External PFD, ND, ECAM.
This leaves the FMGS/AP and the involved logic out of the game.
Which is the major effort and achievement of vasFMC - in our eyes.
Sounds a bit like buying a Ferrari and blocking gears 2 - 6 :-(

Joe T. Hermann

VAS Project Forum

Announcement

#1 2009-06-18 21:07:09

Making vasFMC more flexible in X-plane

#2 2009-09-16 13:11:24

Re: Making vasFMC more flexible in X-plane

#3 2009-09-16 16:34:54

Re: Making vasFMC more flexible in X-plane

#4 2009-09-16 23:32:16

Re: Making vasFMC more flexible in X-plane

#5 2010-03-11 23:19:40

Re: Making vasFMC more flexible in X-plane

Board footer