

LeCuvier
Members-
Posts
3513 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by LeCuvier
-
fixed Excessive reflections in the cockpit since 2.7.9 update.
LeCuvier replied to LeCuvier's topic in Bugs and Problems
no, there is no adjustment for reflections. -
No luck! I tried different values in the lines below, and the Heading didn't move at all. { pressed = ehsi_commands.LeftKnob, cockpit_device_id = devices.EHSI, value_pressed = -0.01, name = _('HDG Set Knob - CCW/Decrease'), category = {_('Instrument Panel')}}, { pressed = ehsi_commands.LeftKnob, cockpit_device_id = devices.EHSI, value_pressed = 0.01, name = _('HDG Set Knob - CW/Increase'), category = {_('Instrument Panel')}},
-
fixed Excessive reflections in the cockpit since 2.7.9 update.
LeCuvier replied to LeCuvier's topic in Bugs and Problems
@BIGNEWY Thanks! -
fixed Excessive reflections in the cockpit since 2.7.9 update.
LeCuvier replied to LeCuvier's topic in Bugs and Problems
I have found 4 .dds files that had a "modified" date of 23-DEC-2021. I do not understand these files although I have some experience with Photoshop and have been able a couple of times to reduce opacity of a HUD or so. But I took a gamble and replaced the 4 files with those from 2.7.7. stable release. And that works for me. There are still plenty of reflections especially in the free flight (Caucasus) mission, but I don't see the instrument board anymore. And in a dog fight mission it's back to what it was. The screen shot shows the 4 files I replaced. ED tried to fix what wasn't broken, and made it worse. -
fixed Excessive reflections in the cockpit since 2.7.9 update.
LeCuvier replied to LeCuvier's topic in Bugs and Problems
Correct. Makes the issue very visible, good test case! -
If my old eyes don'tplay me a trick, the knob placement is ok. It's just the label "Frequenzschalter" that's off to the left. And if you consider the circumstances under which these machines were produced, the label alignment was the least of their priorities.
-
fixed Excessive reflections in the cockpit since 2.7.9 update.
LeCuvier replied to LeCuvier's topic in Bugs and Problems
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. -
fixed Excessive reflections in the cockpit since 2.7.9 update.
LeCuvier replied to LeCuvier's topic in Bugs and Problems
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. -
TFRP toe brakes at 50% minimum when not depressed
LeCuvier replied to ChuckyChuck's topic in Controller Questions and Bugs
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.
-
fixed Excessive reflections in the cockpit since 2.7.9 update.
LeCuvier replied to LeCuvier's topic in Bugs and Problems
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 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.
-
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.
-
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".
-
Missing ECM keybinding in new release
LeCuvier replied to karpiyon's topic in Controller Questions and Bugs
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