Taz1004

Not sure if it's bug or the way it is but I find the radar to be much more reliable if I use 10' Azimuth. I actually don't see the need to use 30' or 60' in most cases since datalink is tracking them and I just need my radar to point and lock.

That's A10C cockpit. This mod is for A10C-II.

I and many others have been complaining about Saitek/Logitech profiler. I'd like to take back everything I've said about it after using VKB DevCfg. It's not profiler but it re-programs its firmware. Meaning you have to re-program everytime you want to use different profile for different plane. Plus its UI is horrendous. I suggest leaving it default and use DCS in-game profile as suggested by others. Of course this means no advanced macro functions or assign to keystroke that doesn't exist as mappable in DCS. You can use Vjoy and Joystick Gremlin as profiler but I find them to be buggy as well. Controller itself is well made minus couple design flaws. But the software, expect the worst.

This makes manual mode completely pointless. Will need to keep it on Semi all the time and dispense flares manually.

YES! +1 A10C-II, any missions in the mountain is guaranteed to kill wingman.

Hmm... that should have nothing to do with shimmering. It basically doesn't render what's behind you. It doesn't change how they're rendered. It's performance feature. I haven't seen improvement from it for last couple updates however so I stopped using it.

You have to go into Campaign builder, open the campaign, and see the progression path. If two missions are assigned to same range, then it's randomly chosen between the two.

Is that how it is in real A10C? Switching programs is now Long command. And it switches one at a time. Will take forever to switch even from A to D. I mapped the rocker switch on CMSP instead but can't imagine how the real pilot can use manual mode with the long command.

You talking about A10C? Or A10C-II? For A10C-II you can just use my cockpit mod which has reflection removed. And is IC safe. https://www.digitalcombatsimulator.com/en/files/3313706/

Updated to V9 Gun Smoke: Larger, thicker, and longer gun smoke. Will likely affect all guns. (IC Safe) If you want to tweak the gun smoke further, I included comments in: \Bazar\shaders\ParticleSystem2\gunSmoke.fx Search for Taz1004. Smoke Texture: Softened the texture to remove blotchy spots in the smoke. And removed repeated patterns in the mask. (Single Player Version Only)

Isn't there slight delay between the actual launch and the sound? I keep thinking it didn't fire because I don't hear the sound immediately. And press the launch twice. Maybe it'll take time getting used to.

The new missile sound... Opinions? Still unsure if rockets and Mavericks would sound the same.

Barthek Caucasus My Tree Dark Low Standard VR Shader mod with parts of Mustang's tonemap adjustment merged. And of course Better Smoke Those are the only visual mods.

I think there's update scheduled today so I'll release new version after checking for compatibility. But will include comment in the file for further adjustment. @flanker1 I'm not sure what you mean. My used mods? Or do you mean list everything that's modded in this mod?

In the original file, the two groups were set to same speed and separated by some space. So if one tried to pass the other in that setting, that'd be a bug too. And as for AI running into mountains, it still happens with lighter load. I think it just helps. Just lost all wingmen to the mountains in mission 11.

Yes. Is that too long? Seems about right based on 1:02 of the video above. Default Longer

Syria may be heavy in content but Ugra did very good job optimizing textures. Syria vfsTextures is only 1.8GB compared to Caucasus 4GB. They don't have any 32bit normal maps or oversized bark textures like ED.

20% Larger with 50% more opacity.

Knew I forgot something. You wanted it bigger? By how much. Below is 2x. Default 2x But in my opinion, default seems more accurate.

Yea, looks like Dunx is correct. Bottom right corner SteamVR overlay should show your headset and controller icons. It doesn't seem to be detecting it.

Just FYI on AI's running into mountain issues. I'm sure there are many reasons AI does stupid things and this is just from testing in 3 missions so far. But in this campaign, I think it's because they're too heavy. I reduced their payload weight from 98% to 90% and they seem to be doing better. They haven't ran into mountain once since I reduced the load. Before, at least one was guaranteed to crash. I still think it is a bug with the AI however. A10C is perfectly capable and maneuverable at 98% weight. Ace skill level pilot should not run into mountains.

They're originally set up to cross the bridge in order. Set to same speed, second unit a bit further back. First unit gets stuck and backs up the second unit. I moved them across the bridge in that screenshot.

I just moved the units across the bridge as starting point and that seemed to solve the issue so looks like map issue. I'm pretty much playing each mission 2-3 times because of the bugs. And now I'm running into my AI wingmen running into mountains. With this campaign giving extra points for bringing wingmen back alive, this bug also sucks. Really frustrated.

Options - Gameplay - Tooltips

Mission 8 of Operation Piercing Fury for A10C-II. Georgian ground forces stuck at the bridge. Not sure if this is AI issue or the map issue. It's frustrating to lose hours of progress because of these bugs. And I'm running into so many.