Taz1004

I have steering wheel pedal at my foot so I use rotary on my throttle as rudder. Good thing about using rotary is it works like rudder trim and don't have to apply constant input. Great for helos.

Yes, I pressed spacebar, he turned, I followed, then he kept turning. I'll fly again tonight.

After all the events, trying to refuel on the way back, tanker and I both turn south then tanker keeps turning. After two 360 turns, I just kept heading south and the tanker takes position to my right 0.3 miles behind. And if I turn, he turns, if I climb, he climbs, if I slow down, he slows down. I followed all the instructions and didn't request for fuel early. Tanker kept turning to be on my wing it seems.

I've made a mod for it until ED fixes it.

Updated 3/22/23 Makes canopy glass clear. Should apply to all modules but only tested on A10C-II, Hornet, A4E-C, Black Shark 3, and Viper. Adjustments: Last value of line 101 adjusts opacity. Default is 1 and 0 will be completely clear. Mod is preset to 0.2. Shadow on the glass is removed by default for better frame rate. If you want to restore the shadow, remove the comments (//) at beginning of line 88 and 89. Notes: This mod may also affect MFD and HUD glass if the module uses same material. Does not pass IC as of DCS 2.8.5 on 5/18/23 Install: Extract to DCS Main install path or use Mod manager. DOWNLOAD

Here's another view that showed it better. It's Weapons Qualification: Paveway single mission for Hornet. It's almost as if there's layer of dust on the canopy. Image switches between with canopy and without canopy.

I just think there's too much shadowing on canopy glass. Possibly because it's not transparent enough as @speed-of-heat said. DCS A10C II DCS Hornet Real Hornet. You can see where I circled the shadow doesn't carry into the glass. Below is full video. No where during the video, I see shadow on the canopy glass. Reflections, but not shadow.

It's always RGBA. You don't want to change the Alpha but RGB. You may want to re-download as I updated the file. ED changed the blending mode so the waypoints got darker too. Fixed.

There's separate section for Saitek. https://forum.dcs.world/forum/335-saitek/ It should be calibrated automatically by Windows but if it doesn't work, you can try https://support.logi.com/hc/en-us/articles/360023178974-Recalibrate-the-X-52-Pro-Flight-System-axes-RegEdit?msclkid=2507550ac64711ecbf187179937b8fef I don't use X52 Pro anymore but I recommend magnet mod.

I remember changing it in ME for BS2 before too.

That tab doesn't exist for BS2. Only for BS3. I believe you have to use ground crew comm menu to change it when you start the mission for BS2. If you're starting in the air... then IDK. BS3 BS2

I tried to get clarification on that data in the manual couple years ago but never got any answer. For example, if you lase for more than 10 seconds, does it count as 2 cycle? And interval between the series is 30 minutes, does it mean that cycle resets after 30 minutes? I tried that too and didn't do anything. As someone said above, laser in BS2 worked like it has finite use which you can stretch by turning it on and off. And cooling doesn't do anything.

Not talking about turn to target. Looks like you didn't even read that thread. There already is a thread about DL. For both BS3 and BS2. You just have to search. You're basically saying BS2 has only one bug, and BS3 has just two bugs. And everyone in bug section just don't know how to fly. I'm not even gonna try to argue with you.

You're saying Datalink issue is due to INS issue which is NEW bug. Yet this 2015 thread describes same issue. How is that possible if it's new?

OP listed most of the major ones. Datalink not working, Wingman refusing to fire... Most of the BS3 bugs reported, if you search, you'll find it in BS2 thread. Laser burning out is not a bug actually. Not being able to fix it was.

Only reason I bought this the day it came out was because it isn't worth $20. Majority of the bugs existed in BS2. Just ignored for years. What I understood in previous BS2 discussion is that INS worked until new Caucasus map was released. And was never updated. And it also affected Datalink and how AI wingmen behaved. I am hoping that ED will finally fix them with BS3 but I think they're just realizing what a mess it's in.

lua is mostly reverse engineering, backtracking, trial and error. It'd be nice to have SDK but will never going to happen. Goes against their business model. If someone creates better module than 3rd party developer for free for example.

Most of these suggestions are difficult to implement. Relatively speaking. I'd be happy with just the legs and torso option.

You're using A/A Airborn Target button. It sets the Vikhr to use proximity fuse. And simply turning off A/A button doesn't fix it. You have to RESET targeting. Now this part, I'm not sure if it's bug or not. You can test this on Shooting Range Caucasus Instant mission. Vikhrs wont work on T-55's with A/A button on. And this probably wasn't your main issue but it also looks like you're shooting through the power lines on some of the shots.

Happened to me a few times. But as you said, it's difficult to replicate so I don't bother reporting it since the response you'll get is to provide track.

This indeed was problem in BS2. If you search, you'll find same issue dating back to 2016. It's surprising that simply rearming fixes it. Because before with BS2, you had to break your helo and then repair for it to work again. That's actually improvement.

You can enter it in Google translate and click the speaker icon.

That still has not happened for A-10C-II so I wouldn't hold my breath.

I'm trying to use a button on NXT for push to talk in hold mode. For Voice Attack. But whenever I press any button on NXT, it immediately does press and release even when I'm holding the button down. This works with buttons on my other joysticks. Just not on NXT. I do have VKBDevCfg but I have no idea what I need to change.

I noticed it in Shooting Range - Syria. It's sunset but still too early for NVG. I opened up the map and it was set to Auto. So I'm assuming the issue is with the setting of Auto.