Havner

Could we please finally get this binding? Something akin to F-18 "throttle finger-lift", like F-16 "throttle lift" to get a momentary afterburner detent override. It's a simple fix. Pretty please.

Here is a little bit more modified file that doesn't break external canopy rendering. removes canopy shadows (as in taz1004 mod) removes canopy shades (as in taz1004 mod, like transparency == 0.0) removes the FRESHEN calculations (FresnelFactor, inScatterFactor) for in cockpit rendering glass.hlsl

Thank you for this remark, but I'd like to point at my original post, you know, in case you didn't notice.

Ok, got it fully. The taz1004 mod is still required plus a small additional change in the shader file described here. It seems to be related to some fresnel factor calculations that have been introduced in DCS at some point. There is still the older code with simple calculations. And it removes this effect completely. --- DCS/Bazar/shaders/model/functions/glass.hlsl 2023-03-10 23:24:10.010616200 +0100 +++ DCS.mods/Taz1004_ClearGlass_v2/Bazar/shaders/model/functions/glass.hlsl 2023-11-17 15:27:04.075284600 +0100 @@ -40,7 +40,7 @@ float4 colorMul : SV_TARGET1; }; -#define CALC_GLASS_FRESHEN 1 +#define CALC_GLASS_FRESHEN 0 #define CALC_GLASS_TRANSMITTANCE 0 //for the future #include "functions/shading.hlsl" Set CALC_GLASS_FRESHEN to 0, line 43. IMO there should be an in-game option for that.

Thanks for this, it's still not 100% but it's already MUCH better. I've set the "transparency" in line 101 to 0. Now I'll try with the canopy textures again and will play with the shader some more as there are some things that might help me still.

EDIT: I've marked Hotdognz post as a solution but to fix it completely see my following posts. Is there any way to get rid of those milky reflections? To make those 3 windows look the same as all the other, e.g. the side ones or the small CPG one? I know it might be realistic and whatever, I don't really care. I want to have fun with the bird and those constant reflections are really bothering me. They make the world look washed out too much to my liking. I've tried cleaning the cockpit glass textures and I've managed to do so, but it didn't help. It seems to be related to a reflective properties of a material and I don't know how to change that. Anyone? Some mod? Some setting? Some guideline/tips even for how to even approach changing the material properties of the glass. Would really appreciate it.

Tested in F-16. I get the effect of the command (persistent HUD close up on first press, back to normal on second), so the command gets triggered. But NumEnter does not revert back to proper FOV afterwards. I'll check on more modules later on. EDIT: Heh, indeed. I've tried ~5 more modules and it worked on every single one. But doesn't on F-16. Go figure

This doesn't work for me in 2.9. Num Enter doesn't restore proper FOV afterwards. It seems that a value around 20 degrees is added to the set one. What does work is switching seats in multi seat aircrafts. I don't have a workaround for single seaters though.

CasmoTV mentioned in one of his tutorials that fixed rockets option was added in later versions (probably Echo). He also suggested GND STOW as the only workaround now if you want fixed rockets.

By default they are only for the duration of the shortcut, but there are several ways to make them toggles (one possible with only the default shortcuts, but not really convenient, others require some keybinding edits). About default view points and editing snap view search on the forum, this topic is well described. For a quick view you can hit RALT+NUM0 (nothing will happen, but just do it) and then have a look in Saved Games/DCS/Config/View/SnapViews.lua. Index 13 is the default view point.

This is about the diamond symbol you see on the HDU, has nothing to do with setting B/S.

I made myself a special snap view for boresight. Yes, the default height is little bit higher than the boresight LOS but I guess pilots have different height as well. You can always customize snapviews and default camera views to your liking.

Thanks. AFAIR I was actually flying over the concrete there, so the misalignment got pretty big. I remember I had issues with replays long time ago. Seems they are still there

To all of you struggling. I've also been struggling to a point of frustration where I couldn't even hold the yaw in place while hovering without getting into oscillations. She's definitely the most difficult one of all the helis we have, but several hours of practice and definitely tameable. This is what I can do with her now. EDIT: LOL, I tried watching it myself and I crash on the replay while I did not when recording. Are replays still problematic in DCS? EDIT2: track removed, after last patch it's completely broken. Anyway, what I wanted to say is: don't give up. I also thought I won't be able to tame her. At some point it clicked and both slow precise flying/landing and fast with rapid accelerations and decelerations became possible. You just really have to anticipate her much more than any other heli out there. So more experience required, but still possible.

OP has said "PEDALS WITHOUT SPRINGS AND FFB" so you don't recenter them after trim. And that the curve doesn't follow then.

I know how you did it, but it's not what I'm talking about. With your setup press 'C' and then try to fire the gun. That's the issue. You can de-synchronize the state. Unless you used some LUA device::command I'm not aware of (and which I requested in the OP). EDIT: Using something like this for Mi-24 you cannot de-synchronize the state and this is what I requested. {down = weapon_commands.Pilot_RUV_FIRE_Cvr, cockpit_device_id = devices.WEAP_SYS, value_down = 1, name = _('Weapon Release Button Cover OPEN'), category = {_('Ins Cyclic Stick')}}, {down = weapon_commands.Pilot_RUV_FIRE_Cvr, cockpit_device_id = devices.WEAP_SYS, value_down = 0, name = _('Weapon Release Button Cover CLOSE'), category = {_('Ins Cyclic Stick')}}, Or doing a single DOWN/UP command that you could use for dual stage trigger like your use case.

I've flown some more and again, this seems to be a solution for the yaw channel. It's contrary to our muscle memory from russian helicopters. But push the pedal a little and see what she does. Don't compensate back for something that hasn't happened yet (but would in a russian helo) or just to stop the movement. This makes things slower and again I'm not sure I like it but with this mindset I don't have issues in keeping yaw direction in hover without oscillations.

+1 F-18 has such a binding (throttle finger-lift). It would be great to have it for F-16 as well. Not a toggle, but a momentary. To have the lock always enabled, but when a button is held you can move the throttle past the AB detent. There is a binding for: "Throttle cut-off release" which kinda sounds like it could be it, but it doesn't work. If that's not for this purpose I have no idea what this binding does.

There is no separate function/lua command/binding for gun select that can select up/down position separately. As the element is not even clickable I don't think a lua command for the device was ever created. Only iCommandPlaneModeCannon exists which is not enough to hold a 2 way switch (like trigger cover in virpil sticks) synchronized. Please add such a binding/command whatever. Same way it can be achieved on Mi-8 and Mi-24 for RS cover.

This actually helped a little. The yaw channel overcompensating was the sum of its work and me taking the rudder back (as we're used to from other helicopters). If you can restrain from doing that it behaves better. Not sure I like it, not sure it's supposed to be like that. I guess we'll have to wait and see what does change and what doesn't further down the Early Access line.

I have no issues with controlling all the other choppers in DCS, none at all with precise hovering and landing (extended stick, soft center, non-centering pedals with damper, etc). I do have some with Apache and what I've found out is that FCS yaw channel is overcompensating. It can be clearly seen on the autopilot overlay. Even micro rudder movements in hover cause huge FCS reaction in opposite direction. This can be mitigated by keeping the trim button pressed (disabling AP for the time being, Ka-50 style), but then you loose pitch/roll stabilization. What I've found out is that she is much easier to fly when you disable yaw and collective FCS channels. This gives warnings so I presume this is definitely not a normal mode of operation, but IMO there is something wrong otherwise, at least with the yaw channel. Unless there is something else I don't know about, or the way of flying with her requires something else. Anyway, meanwhile this is something that helped for me. EDIT: and yes, I know the difference with what AP does when you press the trim momentarily and when you hold it (the latter returns the AP compensations to the center slowly in span of few seconds). What I might not know are the procedures related with that.

Left/right engine cut-off valves are device.ENGINE_INTERFACE (4) buttons 3009 and 3010 respectively. Values 0.0 and 1.0. And they kinda seem to work. If you only use mouse or bindable keys you won't see the bug. The problem is that setting those lever to a specific value doesn't work the way it works for any other switch in Ka-50 and any other DCS module. Usually setting something to value 1 (or some other ON value) turns it on (and respective presses leave it on), setting it to 0 turns it off (and respective presses leave it off). Here, doesn't matter what value we set, the lever is always toggled. So set it to 1, it turns on, set it to 1 again and it turns off. Funny thing is, that values 0 and 1 properly set mouse clickable points (setting to 0 always leaves the clickable point down, setting to 1 always set it up). I do realize that this might not be treated as a bug because it cannot be reproduced without external software/hardware, but such things are crucial for cockpit builders, stream deck profiles and advanced switch bindings for switches that hold state. I've been doing such things for a long time and those levers/switches are the only ones that have this problem (and AFAIR it's there since DCS: Ka-50 1.0 standalone when I've been doing old TM profiles). Please, don't disregard it because of that. Run this code (on a cold plane), it will cause the levers to move up and down immediately, but it will leave the clickable mouse spots up. Clearly showing the bug. It should result in both levers being up and stay there. EDIT: There is a way to show this bug without any external help: get a hot plane turn off one of the cut-off levers (move it down with a click) run autostop sequence (LWIN + HOME) At the end you'll end up with the lever you moved down being in up position (despite the fact that Macro_sequencies.lua set it to 0) with a broken mouse click spot.

Just came here to submit such a request. Definitely +1. I'd also add the Electrical release control box (ESRB) to the list: And PKT panel: As a lower priority it would be nice to also remove the weapon control panels and circuit breakers from the left overhead panel to make a fully civilian version of the plane. But removing the before mentioned 3: the bombs control panel ESRB PKT panel would already be huge. Please, consider this.

I had the previous newsletter in mind (27.04.2018 ):

That's hardly a solution, merely a workaround. Still it doesn't solve the issue with Mercury pod. Try the training mission I mentioned.