cefs

I did notice the other day that pressing the autopilot mode switch either up/down or both and then back to off I was able to lift off with a lot less forward motion, have not had time to confirm this behaviour, but give it a try.

Had that same error code when I had a problem when MSVCP120.dll went missing, check to see if you have the VS 2013 x64 redistributable installed, if not then download the vc_redistx64.exe (or something like that) for Visual Studio 2013.

Problem resolved, MSVCP120.dll is the redist for vs 2013, was thinking it was vs 2012, managed to download it and reinstall, no idea how it became uninstalled though, most curious.

MSVCP120.dll is missing Was flying ok earlier today, but for some reason the open beta v1.5 will no longer start. I have reinstalled but still get the same message at startup that MSVCP120.dll is missing. Have run vcredist_x64.exe and asked me to repair or uninstall, so repaired but still displays the same message. Any ideas.

No offence taken, each to their own. If anyone is going to download, you just fill out a short form, only need to supply a genuine email address, there are no checks for genuine student credentials or anything else.

Autodesk Inventor 3 year free student licence. Inventor Professional Free Download | Free Student Version

UART's are very unreliable in a bus topology without transceivers, there are a lot of reflections and the uart most probably wont have sufficient drive current to drive a number of receivers. Wifi is doable, but the overhead of decoding and encoding ethernet packets is the only downside. A low overhead protocal like Mifi might be better suited.

You should be able to use DirectInput yourself to grab what you need, only problem may be how sim sets the cooperative level, and you will need to decode the data sent. Have a look at this link also as another possible way, also has links to DirectInput API. http://www.codeproject.com/Articles/185522/Using-the-Raw-Input-API-to-Process-Joystick-Input

If you are having errors with rs485, could be down to bus and terminating resistor value or not using them altogether, for a short bus with only two devices then only one resistor should be ok, but any more evices then each end of the bus should be terminated, generally 120 ohm. Are you bit banging yourself or using an onboard uart, could be down to baud rate settings.

Will you then be running say a few at the top level in multi master mode and they will then feed each segment. Would be handy if the pro mini had two i2c ports.

The I2C spec. says a max of 400pf bus capacitance. Wire, solder joints, pcb traces and each device all add to the bus capacitance and you will have to select the correct pullup resistor values. The minimum pullup value I think is around 1.5k and the max for a 400pf bus is around 2k. At some point due to high capacitance the bus will just not be able to switch between high and low fast enough or even not at all. So playing aroung with the pullup values may be needed. One way around this may be to segment the network by using devices as hubs or repeaters, or better really would be to use rs485 or can.

I understand where you are coming from and there is no harm in asking, but I just cant see ED doing that, it would not be something that I would expect of them from experience of other sims. If the demand was there some one would be selling it already.

My point is that ED produce a flight sim, same as xplane and fsx, they are not really concerned with the pit building side of things, as you pointed out, that side of things such as project magenta are 3rd party efforts, its easy enough already to extract state data through lua scripting, why would ED make more work for themselves, its not necessary, they have already provided a convenient way to do it.

Not seen too many encoders with a 3mm shaft, grayhill do some reasonably priced rotary switches with adjustable stops with that size shaft, would have thought the originals would have been rotary switches, and if they were and its a matter of i/o pins then a port expander chip could solve that problem.

This is not a flight sim built for pit builders and I cant remember ever seeing anything like helios in any other sim. I would be very surprised to see anything more than we already have, and apart from texture exporting not working I think its good enough, there is a consistent interface to state data through lua, and its got to be the easiest sim to interface to, have a look at xplane and fsx/p3d.