fudabidu

As Ranma said: You turn the dial, hold the button, wait for the yellow light to extinguish, then release. That's the correct way of doing it.

There are two different versions of the Cougar throttle, so you wanna make sure to get the correct pot. Pictures here: https://forums.eagle.ru/showpost.php?p=2863739&postcount=130 Got mine from here and I'm very pleased (shipping from Ger): https://forums.eagle.ru/showthread.php?t=220916

Years ago I opened up an older Saitek stick because the trigger was acting strange. Inside I found switches identical to those used in computer mice. Grabbed an old mouse, spent 15 minutes soldering and the joystick was fixed. After 6 years my left mouse button would start double-clicking instead of single-clicking / holding. A friend of mine also had the same issue with his Logitec mouse. In both cases the exact same switches were used again. So, this behavior is exactly what I'd expect from a broken switch. Map the pickle button to something else and if it works fine there is your problem.

Forget about it. BS1 doesn't support stereoscopic rendering. There are tools that supposedly can turn every 3D game into stereoscopic 3D, but results vary from game to game. I tried several of those tools and none worked properly with BS1. If you're fine with loosing the 3D effect you could potentially still use it as a headtracker, but you'd most likely rely on external tools to get it to work. Enjoy the Harrier and maybe wait for the BS3 update next year.

Nope, all illumination bombs/rockets are broken since 2.5. They probably share the same illumination code which just doesn't work (properly) anymore. Could you upload the MIZ file so I can have a look at the ABRIS issue? Finally a reason to play around with the GNSS settings. :)

Illumination rockets have been broken for a very very very long time. Their light just doesn't show up on the Shkval at all. Has been reported ages ago and no attempt to fix it was made. The problem with your pipper comes from the Shkval giving you wrong range information. Similar thing happens in rain or dusk/dawn lighting. As soon as the laser stops firing range updates are calculated based on Shkval view angle and helicopter movement. Since the Shkval can't see anything it can't track the ground and the whole calculation goes off towards infinity. Just don't bother with the Shkval at night until illumination rockets work properly again. Maybe boresight mode works since it only uses the rangefinder, however I don't think it will. The ABRIS thing I've never encountered in 10 years of Ka-50. It uses satellite navigation and I remember you can get wrong information if one or more are masked by mountains. In this case you'd go to the GNSS page and filter out all satellites with bad connection. Details on that in the manual. Since I've never experienced anything like this I'm not sure this is even implemented properly, but I don't know what else it could be.

What about it? You point your nose at the target, both launchers will be (mostly) aligned and you shoot. The Vikhr can handle the few degrees. The original post talks about putting the Shkval and launcher in one line, which would require significant turning of the helicopter. A Vikhr fired at such angles might still work but it's gonna waste a lot of energy flying a large spiral after launch.

Got my TM Cougar replacement pots a couple of days ago. Replacing the stock sensors barely took 15 minutes. Calibration within the TM Control Panel worked perfectly. Shipping from the central EU was quick. Very friendly contact via EMail. So far I can only recommend MTW. Thank you guys for providing such a service! You just saved another Cougar.

The Vikhr has a spiral flight path and it doesn't like making turns. If you aim right with the right launcher active, the missile would attempt to make a very sharp left turn immediately, which it can't really do. It will go into a (wide) spiral and bleed off a lot of energy while trying to catch the beam. Near maximum range this could cause your missile to fall short or miss. Too far off target and the missile might just loose the laser completely and impact randomly, causing collateral damage. As I see it the launch cue ensures the missile has the best flight path possible and the laser offset is less of a concern.

Heading hold will retain some authority even with FD enabled, so you wanna use the trim to set the new heading. Also relative wind is gonna change during a turn, so you need to re-trim to account for that. Just use trimmer all the time until the helicopter basically flies smooth by itself. You almost won't notice the trimmer anymore once it becomes second nature. With a twist axis I'd strongly recommend using rudder trim. It's gonna be much easier on your wrist and you'll be able to take your hand off the stick once you're trimmed. Frederf is right about loosing rudder authority, but I never found it to be an issue.

3 months after release I found a boxed copy of BS in a supermarket: 10€ In 2016 I bought the full BS2 version during a Steam sale: 25€ I always felt bad because I made such a good deal, but now I know there are people making up for it. Thanks for supporting further development with money more than I do!

As Revelation said: the code for the LGBs can currently only be set in the mission editor. AFAIK there is no way to change the code from the cockpit in our particular F-16 variant. In the future they will certainly add an option to change the codes somehow while being parked on the ground.

Here: The NWS button has multiple functions, depending on what 'state' the plane is in. When the refueling door is opened it will act as a manual disconnect. There are 2 problems/bugs: 1. Currently the DCS Viper doesn't care about the 'state'. If you activate NWS on the ground for taxi you'll also operate the manual disconnect. 2. The state of the manual disconnect never resets. You press NWS just once and you're screwed. Just fixing #2 would solve the problem and it seems like an easy fix since the indicator lights are seemingly already reflecting the intended behavior.

Where did you get that "expanded data (RCR)" information from anyways?

According to a-source-that-can't-be-mentioned TMS left is used for IFF interrogation in all AA modes.

I can confirm: pressing NWS just once will cause you to disconnect immediately every time. Made several attempts trying to fix it somehow, but no luck. Today should be patch day, let's hope.

Have a look at the software that comes with your joystick. It might allow creating key sequences for subsequent button presses. I know old versions of the Saitek programing suite had such a feature. Not sure about TARGET, Logitech or anyone else. I'm using a TM Cougar with Foxy and there it just takes one line in the joystick profile to alternate between FOV keys: BTN T1 /T - /T = GlovePIE and AutoHotkey would be two 3rd party solutions I know off. GlovePIE has always been reliable for me, but AutoHotkey seems to be better documented.

"Easier to code" ... *cough* Right now the TGP is casting a ray of 8 mile length. Where it intersects with the terrain is where your laser spot will be. So there is already code in place to check where that intersect happens. It would be stupidly easy to add an exception to this piece of code: if it doesn't intersect with the terrain, there will be no laser spot (instead of a floating laser spot). Anyone who ever worked with IF, ELSEIF and ELSE could fix this in minutes.

That knob doesn't do anything in the current Ka-50 module. My best guess is it sets the contrast required for the Shkval to lock on to something. On a bright sunny day you'll have more contrast between a vehicle and its surroundings, and you wouldn't want the Shkval tracking some random spot on the terrain that just looks slightly different than the surrounding area. That's when you'd use the "sun" setting. With overcast the contrast will be less because there is no direct sunlight to reflect (even military vehicles are somewhat shiny in the sun). In this case you'd use a different setting that reduces the "contrast requirement" for locking onto a target.

Setting AP attitude/heading and hover point is done by releasing the trimmer, not pressing it. As far as I can tell the trim reset does the exact same as releasing the trimmer. Only difference being the cyclic being reset to its default position...obviously. It makes sense from a programing standpoint. You can reuse the trimmer code and instead of reading joystick input you use the default values. Nobody would use the reset in flight anyways, so doing it like this is perfectly acceptable. Speaking of which: why would you use it in flight unless you horribly screwed up and your chopper is going out of control already? Best case: you'd be commanding the AP to keep the helicopter level while the Ka-50 tends to violently pull up with neutral cyclic setting. The autopilot can't handle that kind of discrepancy and you'd be forced to instantly trim anyways. So, 99% of the time you won't need the reset function at all and if it screws up anything it would be fixed as soon as you'd use the trimmer again. Problem solved.

Wrong. It will also send your current attitude to the autopilot, just like releasing the trimmer does. Go into flight director mode, bank to one side, reset trim and observe how the FD bars on the HUD change angle.

The current Shkval acquisition logic is simply a hack: IF an object is under the cursor AND it's "in range" THEN you get a valid lock. The problem is the "in range" part: It's a fixed value of around 10-12km (estimated, not tested). Even before the sun starts setting this value will gradually decrease, even if the target is still fully illuminated. Rain and snow will do a similar thing. So even when flying through decent weather you could end up with acquisition ranges less than 7km. The Shkval video feed is also broken: doesn't show rain/snow, no shadows, illumination based on TOD instead of actual light conditions. There is nothing the community can do about that. ED needs to rewrite the Shkval so it tracks based on contrast and the video feed is accurate. Black Shark 3 better fixes this, but knowing ED it's probably not going to be part of the initial release.

The engines take longer to spool up in hot/cold climate + at high altitudes, but the auto-start uses fixed timings. The right fuel cutoff gets switched too early, the engine will not ignite and stick around 20% RPM. Just a slight variation in weather or altitude can cause this to occur, which explains why it can't be reproduced reliably. It has nothing to do with PG or any other maps. The only proper fix would be making the auto-start dynamic so the cutoff is only being engaged at 19% engine RPM. So, not really a bug. Just a shortcoming of the auto-start script.

Just did a 2 minute test on this: Using the trim reset will also send your current attitude to the autopilot (just like using the normal trim). This can be observed by engaging flight director, going into a turn and then resetting the trim. The "flight director bars" on the HUD will be at an angle. So, if you're sitting on the ground and use the reset, your flight controls will be in the default state. I'm 100% sure THIS is the intended use and nothing else, so there isn't any defect. But I have to ask: Why would you even need to reset your trim? In the Ka-50 you hold the trimmer, get to the desired heading/attitude and release. This is what you should be doing and unless you seriously messed up your trim there should never be a necessity to reset it. I haven't used the reset once in flight ever and I've been flying this thing for many years. If you depend on the trim reset you're doing it wrong and I wouldn't be surprised if that's related to your mystical auto-trimmer script.

I believe you're talking about the mission DUSK (Mission 11), where you end up at the Enguri dam? I've looked at the MIZ file and all you need to do is hit a trigger a few kilometers north of your IP. This will spawn a SEAD to destroy the Sa-8s below the dam and once those are down you'll get the clearance to attack. The trigger is placed slightly off, so follow the valley on the left side (there will be a road) and you should trigger it. There are also some buildings that need to be destroyed. Hitting the trigger will spawn in a strike flight to take care of those. I guess those buildings are what you've been missing to get a "mission complete"