Mud

Hmm odd. Maybe try running the updater as admin: Right click > More > Run as administrator (in Windows 10 at least)

Was DCS, or perhaps a DCS process running while trying to update? Easy way to rule that out is to restart your PC and try again. Br, Mud

Well, I just tried replicating the issue and I was not able to. Flew for about an hour with mostly staying in the 2000rpm range and boost around 0/+2. Coolant temperature stayed just shy of 50 degrees, and old pressure below 120.

Take it with a grain of salt, because I was not testing specifically and wasn't paying attention to what my settings were exactly. But I believe I was in that range. I will probably do a test later today with those settings to confirm.

Unfortunately, I believe it is, yes. I had the engine quit on me yesterday, flying at 10k feet (temp 15C in mission editor) at 2000rpm and 0/+2 boost. Seeing as they released some work on WW2 birds cooling in the last patch, I hope this will be sorted soon as well. Br, Mud

What I did notice myself is shaking during a cold start, once you start the engines. That started happening at the previous OB patch, not the latest one. I have not checked yet if it still does that now, nor did I see any other people report it. So I don't know if that is a normal "feature" or not. Br, Mud

Hey Pluton, What VR set are you using? It might also be helpful to let us know what CPU and GPU you have. Br, Mud

I do this, without TARGET, by modifying the default.lua file. {down = control_commands.ApPitchAlt_EXT, up = control_commands.ApPitchAlt_EXT, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = 1.0, value_up = -1.0, name = _('Autopilot PITCH Switch - ALT HOLD/AP OFF Mud'), category = {_('Special For Joystick'), _('Instrument Panel'), _('FLCS')}}, {down = control_commands.ApPitchAtt_EXT, up = control_commands.ApPitchAtt_EXT, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = -1.0, value_up = 1.0, name = _('Autopilot PITCH Switch - ATT HOLD/AP OFF Mud'), category = {_('Special For Joystick'), _('Instrument Panel'), _('FLCS')}}, }) I created it as a mod in OvGME so that I can enable it after an update without having to re-edit the file every time. The file is located in Mods\aircraft\F-16C\Input\F-16C\joystick Br, Mud

The tail wheel has to be roughly centered before it will lock again. So if you move forward straight, it should lock again.

Yeah, I sure hope so!

I have noticed the same yesterday (Valve Index). I have not had the time yet to check if it's related to bringing up the kneeboard or not, as there is/was another bug related to the kneeboard in VR.

I have it bound to my boat switch on the HOTAS Warthog so I don't have to keep pressing a button. So I guess any switch you may have on yours should work.

I got the Anton to just shy of 41.200 feet in a sustained climb. Was a bit surprised about that actually.

My pleasure. Credit to @scoobie who helped me with this some time ago. You can play around with the 0.5 number as you like to decrease or increase the increments I reckon.

Modify the following file: Mods\aircraft\P-47D-30\Input\P-47D-30\joystick\default.lua I did it myself as a mod which I enable and disable using ovgme. Look for the lines I added with "slow". I did only do my own for pitch and roll though. But it should be clear enough -- Port Wall - Trim Control Box ------------------------------------------------------------ -- Aileron Trim Wheel { pressed = device_commands.Button_2, cockpit_device_id = devices.CONTROLS, value_pressed = -1.0, name = _('Trim Aileron Right'), category = _('Flight Control')}, { pressed = device_commands.Button_2, cockpit_device_id = devices.CONTROLS, value_pressed = 1.0, name = _('Trim Aileron Left'), category = _('Flight Control')}, { pressed = device_commands.Button_2, cockpit_device_id = devices.CONTROLS, value_pressed = -0.5, name = _('Trim Aileron Right Slow'), category = _('Flight Control')}, { pressed = device_commands.Button_2, cockpit_device_id = devices.CONTROLS, value_pressed = 0.5, name = _('Trim Aileron Left Slow'), category = _('Flight Control')}, -- Elevator Trim Wheel { pressed = device_commands.Button_5, cockpit_device_id = devices.CONTROLS, value_pressed = -1.0, name = _('Trim Elevator Up'), category = _('Flight Control')}, { pressed = device_commands.Button_5, cockpit_device_id = devices.CONTROLS, value_pressed = 1.0, name = _('Trim Elevator Down'), category = _('Flight Control')}, { pressed = device_commands.Button_5, cockpit_device_id = devices.CONTROLS, value_pressed = -0.5, name = _('Trim Elevator Up Slow'), category = _('Flight Control')}, { pressed = device_commands.Button_5, cockpit_device_id = devices.CONTROLS, value_pressed = 0.5, name = _('Trim Elevator Down Slow'), category = _('Flight Control')}, -- Rudder Trim Wheel { pressed = device_commands.Button_8, cockpit_device_id = devices.CONTROLS, value_pressed = -1.0, name = _('Trim Rudder Left'), category = _('Flight Control')}, { pressed = device_commands.Button_8, cockpit_device_id = devices.CONTROLS, value_pressed = 1.0, name = _('Trim Rudder Right'), category = _('Flight Control')}, -- ---------------------------------------------------------------------------------------- Br, Mud

How would you do that in practice, @grafspee? Just trim nose up prior to starting your dive or?

Hahahaha, good one MstrCmdr! And good spirits by Das Feuer. I have seen people get upset for less

Correct, but then again I have no idea how easy or complex it would be for them to implement this. I would love for instance, to have the ability to do the same with Client slots on a server: Have the airplanes visible on the ramp, before a client actually occupies them.

You can set them to Uncontrolled to have them visible already, and add a trigger to the aircraft group to start them. Then have them start with a general trigger. I cannot check now, but at least that used to be the way I do it.

Love you folks and all the hard work you have put into this amazing mod! Best wishes to all of you and a genuine thank you!

I would also like to know if this is possible. Can switches be manipulated at mission start via a trigger? It's bothered me some time that the P-51D for instance always starts cold with the cockpit lights turned all the way up.

I think this is because when you're on the Mark point page, TMS up serves a different function (to drop a mark point). However I don't know how this works in the real Viper with the HAD being SOI at that moment.

Sounds fine to me. What exactly is wrong with it and makes it pathetic specifically?

What I quickly just did now: - Select steerpoint and my Mav was already looking there in PRE mode. - Switched to another steerpoint, Mav did not move. - TMS down: Mav seeker moves to new steerpoint - Switched back to target steerpoint > TMS down > Mav is looking there again - Fine tune, TMS up to lock and fire once within constraints. No need to uncage here it seems. Must be a left over thing I have from other aircraft / sim.

Did you uncage the missile? Gosh, it's been a while. Will do a flight now myself to check, in case no one else with a fresher memory drops in before