sparkz-nz

@Insonia you, Sir, are a saviour! Took me a while to figure out what the deviceID needed to be (simply 0) and then it worked a charm. I hadn't realised all those data points were accessible in that way so thanks a mil!

I am building a motor driven cyclic to provide variable centering torque and trim position, and one of the key goals is to have the stick follow the co-pilot stick when the co-pilot is flying (either when 'autopilot' or in multiplayer) - in the real Huey the two sticks are mechanically linked so the always follow each other, and linking them in the game means that way when you take back control the stick is already in the right place. However I have not been able to find any exportable data for the stick position. (This may be specific to the Huey, I'm not sure, but I imagine the it should probably be common to all aircraft) The list_cockpit_params() lua function returns BASE_SENSOR_STICK_PITCH_POS and BASE_SENSOR_STICK_ROLL_POS, but it is just a reflection of the pilot stick input - when in 'autopilot' it continues emitting the pilot stick input position (ie. my joystick position), not the copilot stick position that is actually controlling the aircraft. When you show the control positions overlay, it is the position of the white copilot diamond I want, not the one that moves with my own stick. This data is obviously there somewhere as it is used to display on the controls overlay and also used to animate the cyclic position when in 'autopilot' mode - the question is, is it accessible from a lua script? Any ideas, anyone?

Thanks MAXsenna - that suggestion enabled me to track it down to the Bell-47 module I had installed a while back - shame because thats a great little bare bones chopper and its probably as close as we're going to get to a Korean war era heli for a while. Never mind, at least my Huey addiction can be sated again

On just some missions (eg instant action->caucus->oil rig landing, mission->elbrus rescue) the cockpit instruments have this weird light overlay which makes them almost impossible to use. Most of the other missions seem okay. This is just basic UH-1H setup on a decent pc with 4070Ti graphics. Not sure if this has only just started being like this, or if I only just noticed it because I've not flown those missions before. I'm hoping this is a bug with the mission rather than the Huey, but seems odd and I would like to fix it if possible. (Actually I'm pretty sure I've flown the oil rig landing before and did not get this problem) Any ideas?

Awesome thanks guys for your help!

No I had not heard of that - sounds like just what I need - thanks for the tip! Did a quick search on the forums and lots of mentions but no links - could you point me in the right direction to get a copy? Thanks

Add command line option --options <filename> which allows selecting the options file used at startup. Why? I would like to be able to start the sim with subtly different options depending on what I want to do. An obvious one is VR or flatscreen - yes, there is the --force_disable_VR option, but I also want to change the use_mouse setting, and maybe some of the graphics settings. Depending on the module I want to fly I often want to change the IPD. Would be super nice if I could make some options file variations and some shortcuts that select the different options files. I dont mind hand-editing options files, or making changes in the UI and then renaming copies of the files. And while we're here, how about other cli options for say --config_input_path which would allow selecting a different folder for the input settings. Then I could have different UI Layer setups for if I'm flying VR or flat, or some modules where I want to map a button that is used in the UI layer already, and so on. Should be a fairly simple change I would have thought, and adds a world of flexibility. And if this ever does happen, maybe document the other cli options available too?