Guys, just wondering if it might be possible in a future release, to write the Vspeeds for given aircraft to the INI file for use as defaults. One can opt to select different checklists for specific aircraft, but not Vspeeds. Appreciate that speeds vary depending on takeoff weight, but simmers don't always tend to use different weights every time. It would be nice to define speeds once for a given aircraft and have them default for that plane.

E.G. example of possible added INI entry

 

[Dash8400]

V-speeds=119,119,120,etc,etc

 

Such method could also be used in the future for perhaps other aircraft specific parameters.

 

Any thoughts?

 

Stuart

I understand what you are trying to get at, but for the other simmers who actually like different weights ( Im taking this as a payware plane with a FMC/FMS)it wont be those speeds. The whole point of the FMC/FMS giving you takeoff speed is so you when to rotate at a correct speed than going to fast or to slow and wind up crashing at the end of the runway. On the other hand for the planes that dont have an FMC and are freeware, then yes this would be a good idea.

I appreciate some simmers like flying by the book, using different weights etc, but my suggestion would still allow this for those that wanted too. It was just to write back those entered Vspeeds and then default them in next time for that aircraft/type. If they are then subsequently changed, to fit fms weights, it would simply write those re-entered Vspeeds back to the INI as defaults again. Nothing would stop them being entered each time for specific weights as now.

 

Stuart

If its a FMC/FMS plane then i cannot see it working., but for the deafult and freeware it would be great. Also from a developer's view point , how would you code that into the plane, and display that.  

I think you misunderstand me. Multi Crew Experience does not interface with FMC/FMS, the Vspeeds are currently entered each time in MCE. If an FMC also requires them they would have to be entered there too.

 

Stuart

Hello Stuart.

 

I believe the MCE 1st officer reads the V ref from the monitor section of the GUI. The V speeds there are derived from the "ref" file for the respective aircraft. So you can either adjust each V ref speed from the GUI, before each flight, or alter the "ref" V speeds from the ref file for the aircraft, as a more permanent solution.

 

I just alter the GUI to the calculated V ref, since these vary with take off weight anyway. Since that's what is called out each take off.

 

Sorry if this is not what you meant. Its just what I do.

 

Regards.

David.

David,

Thanks for the advice. I had not realised that the Vref speeds were derived from an aircraft specific 'ref' file, I thought they simply defaulted from whatever was last entered in the gui, irrespective of the aircraft. I'll look into the ref file aspect.

Thanks for the clarification.

 

Stuart

David,

Thanks for the advice. I had not realised that the Vref speeds were derived from an aircraft specific 'ref' file, I thought they simply defaulted from whatever was last entered in the gui, irrespective of the aircraft. I'll look into the ref file aspect.

Thanks for the clarification.

 

Stuart

 

As David suggested, use the ref file to set your own Vspeeds which will end-up in the <Monitor> section in MCE UI anyway.

 

Be aware, with some aircraft like PMDG 737 NGX, Airbus A31X/A32X, Majestic Q400 and a few others, MCE will read the Vspeeds directly from the sim (whatever Vspeeds you input in FMC-CDU will be known to FO within a few seconds).

Thanks Gerald. Does that apply to the iFly737NG too?

 

Also Gerald, do you have any experience with MCE under Windows10, as I have just updated Windows but haven't tried MCE yet?

 

Stuart

Thanks Gerald. Does that apply to the iFly737NG too?

 

Also Gerald, do you have any experience with MCE under Windows10, as I have just updated Windows but haven't tried MCE yet?

 

Stuart

 

It has been tested with the Windows 10 public preview and found to be working as expected. Not yet with the release version, but can't see any major issue.

Do let us know if you find something. Thanks

 

Edit

 

Forgot to answer the other question.

 

Yes, FO should be able to be in synch with whatver Vspeeds you put in iFly 737 FMC-CDU. It could take up to 10 seconds to synch.