LeCuvier

I happened to be in a mission today where the reflections are weak enough so they don't bother me, and some people may just not have been in daylight conditions where it's as bad as in my screenshot above. But at any rate, as @Art-J stated, there is no way by the laws of optics that there can be reflections of the instruments board on these glass surfaces.

I cannot reproduce what you describe.

Well, I don't fly in VR and I don't like to be frustrated. And maybe that's because I'm 76. My screenshot didn't capture the reflections well. Here is what it really looks like for me, captured with the Windows 10 snipping tool. I tried the same scenario in 2.7.7 stable release with the same graphics settings, and it has none of this.

How do the wheelbrake axes test in Windows? Can you post screen shots with the pedals not depressed and fully depressed?

All 3 trim axes work as expected here. Open Beta, Sim mode, no FFB.

Seems I'm the only one experiencing this problem. Or have people given up flying this aircraft? That's what I'll do if this doesn't get fixed. It's already handicapped by its poor dogfighting performance and it doesn't need any additional handicap.

Other train of thought: You are apparently trying to control pitch and roll with keyboard keys or pushbuttons rather than with a joystick. Question: do you have any game controller (throttle, pedals, joystick) that produces an analog (axis-like) signal connected to your computer? If NO, forget my post If YES, DCS World has probably created default bindings of these signals to pitch/roll/yaw/etc. In that case, the positions of these game controller signals override whatever you try to do with your key presses. You need to go into Options/Controls, select your aircraft (Sim/eal or Game mode), select the "Axis" category and clear any unwanted axis bindings.

I agree. It works fine here.

I went through several cycles, with the "loud cockpit afterburner sound" ticked and unticked, and I could not hear a significant difference in the sound when the supercharger kicks in. And I could not hear any difference when the supercharger went off. In my trials, it kicked in at slightly below 2,900 m altitude. In order to find out where it disengaged, I reduced altitude first to 2,700 m and speed to 400 km/h. When I went full throttle I still got 1.4 ata. At 2,600 and 400 km/h I got only 1.2 ata. So I guess the supercharger disengages somewhere between 2,700 and 2,600 m. That's a fairly large deadband and would help a bit to avoid overfrequent cycling. Anyway, the option "loud cockpit afterburner sound" doesn't seem to matter in this case. PS: Twice I changed that option during the mission (ESC/Options/Audio) and twice my screen went black (not immediately). The second time I had to kill Windows with the power switch. It could be a coincidence of course, but I haven't had any instability for many months. So going forward I'll keep my fingers off that tick box.

I have installed my TrackIR years ago, from what I remember you need to do some initial set-up in the TrackIR software. Have you done that? If yes, have you tried the actions suggested in the earlier posts?

I have no idea whether your programmable HID button doesn't work with the Hornet, but I created a command for a simple push button that generates the "eject" command 3 times if I push and release the button just once. I added the following line of code to the file "default.lua" in the folder "...\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick": {pressed = iCommandPlaneEject, down = iCommandPlaneEject, up = iCommandPlaneEject, name = _('Eject (push just once)'), category = _('Systems')}, ...and this creates the new command "Eject (push just once)" which you can bind to a simple push button. I added the same line of code into the "default.lua" of A-10C II, Bf-109K4 and F-16C (just for fun) and it worked there too.

I just took the Anton out in free flight to try something, and was shocked by the strong reflections especiall on the windscreen. Impossible to fight with this optical handicap. I tried the Dora just to be sure I don't have a general settings problem, but the Dora is fine.

You have obviously selected "Imperial" units under Options/Gameplay. So the info bar indicates IAS as190 kn (knots) while your cockpit instrument naturally indicates 380 km/h. That's all correct.

download and study the tutorial by Chuck Wagner! https://forums.eagle.ru/topic/181018-chucks-fa-18c-hornet-guide/#elControls_181045_menu

I have created Trim Preset commands for some fighters for a different reason: these tend to be trimmed badly nose-down when you start a mission airborn like in Instant Action, and by the time you have corrected the trim you're already under fire. My solution works only if the trim in question has an axis command. In these cases the solution is very simple: I create a pushbutton command that sets the respective trim axis to the desired value. Afterwards I change the trim using the POV hat on my stick. Obviously that solution will not work if you have bound your trim axis to an analog input device. For the Mosquito my Trim Preset command sets all 3 trim axes to desired values. This is done by adding this line to the file "default.lua" in the folder "...\DCS World OpenBeta\Mods\aircraft\MosquitoFBMkVI\Input\MosquitoFBMkVI\joystick": {cockpit_device_id = devices.CONTROLS, pressed = device_commands.Button_17, down = device_commands.Button_54, up = device_commands.Button_52, value_pressed = 0.38, value_down = 0.18, value_up = -0.1, name = _("Trim Preset Airborne"), category = _("Flight Control")}, If I wanted only to preset rudder and aileron, I would instead add this line: {cockpit_device_id = devices.CONTROLS, down = device_commands.Button_54, up = device_commands.Button_52, value_down = 0.18, value_up = -0.1, name = _("Trim Preset Rudder and Ailerons"), category = _("Flight Control")}, Unfortunately, not all planes have trim axes at all (the F-14 does), and some have just an axis for rudder trim. And the line of code of course is different for every aircraft. Not an optimal solution for you, but I wanted to mention it.

Are you referring to gunsight base and range? These value changes still work here.

In 2.7.9 we can export the HUD to a secondary monitor, but I cannot get it into a correct format. The lines and symbols seem shifted too high against the HUD shape, they are cut off at both sides and the lines are too thick. Has anybody managed to achieve a good display?

Have you checked your axis command bindings? What you describe is what will happen if some analog input device is bound to the axis "HMD OFF/BRT Knob", and you try to control the HMD with buttons bound to "HMD OFF/BRT Knob - CCW/Decrease" and "HMD OFF/BRT Knob - CW/Increase".

I presumed that these should work like normal pushbuttons that are spring-loaded to pop back out when you release them. So my first attempt was without the "up" but then the buttons would remain pressed and it was impossible to make them pop out. If they are supposed to latch in until you push them again, I'm not sure I can get that. Edit: The only solution I see would require two bindings per pushbutton. One with value_down = 1.0 and one with value_down = 0.0

The commands from my previous post can also be used with HOTAS devices, button boxes etc. To do that, the lines of code must be added into the file "default.lua" under "...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick". On these devices you can also use 3-position switches if you add these lines of code: {down = ecm_commands.PwrSw, up = ecm_commands.PwrSw, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.ECM_INTERFACE, name = _('ECM Power 2-Pos Switch OPR/STBY'), category = {_('ECM Pod')}}, -- combine to 3-position ECM Power switch {down = ecm_commands.PwrSw, up = ecm_commands.PwrSw, value_down = -1.0, value_up = 0.0, cockpit_device_id = devices.ECM_INTERFACE, name = _('ECM Power 2-Pos Switch OFF/STBY'), category = {_('ECM Pod')}}, -- combine to 3-position ECM Power switch {down = ecm_commands.XmitSw, up = ecm_commands.XmitSw, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.ECM_INTERFACE, name = _('ECM Xmit 2-Pos Switch Pos 1/2'), category = {_('ECM Pod')}}, -- combine to 3-position ECM Xmit switch {down = ecm_commands.XmitSw, up = ecm_commands.XmitSw, value_down = -1.0, value_up = 0.0, cockpit_device_id = devices.ECM_INTERFACE, name = _('ECM Xmit 2-Pos Switch Pos 3/2'), category = {_('ECM Pod')}}, -- combine to 3-position ECM Xmit switch And if you have a spare axis device you can use it for the ECM Dim command if you add this line of code: {action = ecm_commands.DimRotary, cockpit_device_id = devices.ECM_INTERFACE, name = _('ECM Dim Knob Axis'), category = {_('ECM Pod')}}, -- Tune to SLIDER, Invert, Saturation Y = 50 It must be added in the "axis" section near the end of the file. I recommend to insert it just below these lines: -- joystick axes join(res.axisCommands,{

Try these: {down = ecm_commands.ResetBtn, up = ecm_commands.ResetBtn, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.ECM_INTERFACE, name = _('ECM Reset Button'), category = {_('ECM Pod')}}, {down = ecm_commands.BitBtn, up = ecm_commands.BitBtn, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.ECM_INTERFACE, name = _('ECM Bit Button'), category = {_('ECM Pod')}}, {down = ecm_commands.OneBtn, up = ecm_commands.OneBtn, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.ECM_INTERFACE, name = _('ECM 1 Button'), category = {_('ECM Pod')}}, {down = ecm_commands.TwoBtn, up = ecm_commands.TwoBtn, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.ECM_INTERFACE, name = _('ECM 2 Button'), category = {_('ECM Pod')}}, {down = ecm_commands.ThreeBtn, up = ecm_commands.ThreeBtn, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.ECM_INTERFACE, name = _('ECM 3 Button'), category = {_('ECM Pod')}}, {down = ecm_commands.FourBtn, up = ecm_commands.FourBtn, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.ECM_INTERFACE, name = _('ECM 4 Button'), category = {_('ECM Pod')}}, {down = ecm_commands.FiveBtn, up = ecm_commands.FiveBtn, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.ECM_INTERFACE, name = _('ECM 5 Button'), category = {_('ECM Pod')}}, {down = ecm_commands.SixBtn, up = ecm_commands.SixBtn, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.ECM_INTERFACE, name = _('ECM 6 Button'), category = {_('ECM Pod')}}, {down = ecm_commands.FrmBtn, up = ecm_commands.FrmBtn, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.ECM_INTERFACE, name = _('ECM FRM Button'), category = {_('ECM Pod')}}, {down = ecm_commands.SplBtn, up = ecm_commands.SplBtn, value_down = 1.0, value_up = 0.0, cockpit_device_id = devices.ECM_INTERFACE, name = _('ECM SPL Button'), category = {_('ECM Pod')}}, These lines of code need to be added into the file "default.lua" under "...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\keyboard". I recommend you insert them near the top of the file, just below these lines (so they are easy to locate): local cockpit = folder.."../../../Cockpit/Scripts/" dofile(cockpit.."devices.lua") dofile(cockpit.."command_defs.lua") local res = external_profile("Config/Input/Aircrafts/common_keyboard_binding.lua") join(res.keyCommands,{ Use Notepad++ (or equivalent) for the editing! The 3-position switches require 3 bindings each; I have not found a way to create UP/DOWN commands. I have tested to verify that the buttons and switches move as expected. I'm not familiar with the functionality to expect. Good luck!

I find these new lines in the file "clickabledata.lua": -- ECM elements["PTR-ECM-TMB-OPR-455"] = default_3_position_tumb(_("ECM power switch"), devices.ECM_INTERFACE, ecm_commands.PwrSw, 455, false, anim_speed_default, false) elements["PTR-ECM-LVR-DIM-456"] = default_axis_limited_1_side(_("ECM DIM rotary knob"), devices.ECM_INTERFACE, ecm_commands.DimRotary, 456) elements["PTR-ECM-TMB-XMIT-457"] = default_3_position_tumb(_("ECM XMIT switch"), devices.ECM_INTERFACE, ecm_commands.XmitSw, 457, false, anim_speed_default, false) elements["PTR-ECM-BTN-RESET-458"] = default_button(_("ECM reset button"), devices.ECM_INTERFACE, ecm_commands.ResetBtn, 458) elements["PTR-ECM-BTN-BIT-459"] = default_button(_("ECM bit button"), devices.ECM_INTERFACE, ecm_commands.BitBtn, 459) elements["PTR-ECM-BTN-1-460"] = default_2_position_tumb(_("ECM 1 button"), devices.ECM_INTERFACE, ecm_commands.OneBtn, 460) elements["PTR-ECM-BTN-2-465"] = default_2_position_tumb(_("ECM 2 button"), devices.ECM_INTERFACE, ecm_commands.TwoBtn, 465) elements["PTR-ECM-BTN-3-470"] = default_2_position_tumb(_("ECM 3 button"), devices.ECM_INTERFACE, ecm_commands.ThreeBtn, 470) elements["PTR-ECM-BTN-4-475"] = default_2_position_tumb(_("ECM 4 button"), devices.ECM_INTERFACE, ecm_commands.FourBtn, 475) elements["PTR-ECM-BTN-5-480"] = default_2_position_tumb(_("ECM 5 button"), devices.ECM_INTERFACE, ecm_commands.FiveBtn, 480) elements["PTR-ECM-BTN-6-485"] = default_2_position_tumb(_("ECM 6 button"), devices.ECM_INTERFACE, ecm_commands.SixBtn, 485) elements["PTR-ECM-BTN-FRM-490"] = default_2_position_tumb(_("ECM FRM button"), devices.ECM_INTERFACE, ecm_commands.FrmBtn, 490) elements["PTR-ECM-BTN-SPL-495"] = default_2_position_tumb(_("ECM SPL button"), devices.ECM_INTERFACE, ecm_commands.SplBtn, 495) But in fact, the corresponding command bindings in "default.lua" have not been created. They need to be created in both "default.lua", under "joystick" and under "keyboard". That means, for now you can execute thes commands only per mouse click in the cockpit. Not a bug, probably just WIP. I'm fairly sure I can create these missing lines and post them. But are you willing to edit your "default.lua"?

@LowRider88: I'm still finding it very difficultto defeat the MiG-21 AI even at "Trained" level. Most of the time I can't even hit it and it crashes because it's out of fuel. And typically, I'm very close to do the same when I get there. Just now, I managed to hit it with 20mm HEI after 3:45 but it only crashed at 12:00 and although I got credit for the kill I'm sure that it was out of fuel. It did not try to fight me in a horizontal turning fight but kept manoeuvring in the vertical.

@LowRider88: I'm not an experienced F-5E pilot, and I'm trying to replicate what you say, dogfighting off-line against a "Trained" AI MiG-21bis. The first couple of rounds saw me going down burning. So I changed my tactics. I avoid pulling too much G so I stay close to 300 kts. The action starts at about 35000 ft altitude but the dance rapidly descends to very low altitude and after several circles I get into a good position, and I either get him with the guns or he just crashes. The difficult part is not to lose him or stall when he climbs like a rocket, which is what he does when his position gets critical. Questions: 1. I keep the flaps in "Auto". Is that ok? 2. I read about "manoeuvring flaps", but I find no command binding for that, no matter what spelling of "manoeuvring" I look for. Is there any?

Yes, that would suit me fine. I hate the thing, and I have removed it from all the missions that I have created or modified.