fargo007

Sure, glad you are enjoying it! Put Russia in the blue coalition. The script is set up such that the friendlies are blue and the enemies are red, but which countries are which is still up to you if it matters. And of course you can add any aircraft with any skin. wherever you like. To move the zone where the TIC takes place, just move the big TIC rectangle zone, and all of the little round zones inside it to a different place, then move the map decorations to match if you like.

Here's one I posted in the general missions/campaigns thread. Really great for any attack helicopter but the Mi-24P shines in this role. I made both Syria and Caucasus versions. See the instructions, add your own aircraft as you like, and get out there and support the guys on the ground! Troops in Contact!

This is fixed for me by the latest update. Figured I would close it off on a happy note!

I just added a Caucasus version.

This is a really nice update all around for the Mi-24. Well done!

I suppose, but that would increase the size to add all new audio tracks and such. There's lots of stuff possible but I had to sort of "pick a horse, and ride it." What might be easier to do is to randomly spawn a group that's some distance away and have them advance. Sometimes they'll be there, sometimes they won't.

I had a similar issue after a card upgrade and the fix was removing saved games, and using a DDU driver removal utility to totally remove the nvidia drivers, and then reinstalling them. Copied back the config stuff I needed into the fresh Saved Games and I'm 100% whole again. Glad you got it sorted!

Yes, but that doesn't really fit the "we're under heavy fire and need help right now" scenario that I'm going for here. As it is now when a "heavy" group spawns, they do move/relocate to a notionally better position to fire from.

I got this fixed thanks to Thud over at VR4DCS. Fix was two part: Use DDU to completely remove the old driver. Nuke Saved Games and let it rebuild (after years, it was high time anyway).

Ryzen 5 5600, Nvidia 2080ti. Just switched from a 1080ti and I have high CPU frametime. In the area of 28 to 34. Wondering what I can check, reinstall, or go after to try and identify what the issue is. Any help is appreciated.

So far, but could easily be moved to another.

Thank you for that. Wilco!

The right ear of my HP Reverb G1 has a pretty bad short in it and I'm finding that I spend a lot of time tweaking, twisting and turning it. I have neither the courage to try and disassemble it, nor the skills to find and fix the issue. Has anyone added external audio/mic to it using the jack supplied, and if so what did you go with? The supplied headphones suck anyway.

I've only ever seen one person use these with any kind of proficiency. What I think would help is a mod that shows the trajectory of them, sort of like turning them into tracers.

I intentionally left this part for the end user to do. Sort of like I'm providing the engine and chassis, while you bring the wheels and pick the paint color. Just open it in the mission editor and add aircraft set up how you like them. Or put an aircraft carrier there with hornets 'n tomcats if that's what you dig.

Thank you! Really glad you are enjoying it. My intent was to make this as easily portable as possible from the beginning, so people could shape it according to their own needs, or build it into MP missions for their own squadrons.

To be clear, I'm never doing hover attacks. I trim out extremely stable and absolutely minimize any possible control inputs.

The initial radio stuff only goes to helicopters/planes in that specific grid.

Thanks, Not sure, probably IR strobe, glowstick on a string or something like that. None of which exist in DCS. As far as the script goes, they don't know daylight from dark, so they will still pop smoke. That's still visible though you don't see the color of course. Even lasing at night isn't an absolute answer because you can't tell which end is which. Flares might be an option.

Here's a short track illustrating the problem of Petrovich not being able to hit simple shots on vehicles in the open on flat ground. It portrays a 50% hit rate which is what can be expected usually by those having this problem. The trim button was held down for most if not all of the missile flight - taking the AP channels out of the equation. Track is a little to big to upload - link below: https://drive.google.com/file/d/1tXFZ35Y4UDJ9ln6OHm-p2GzU1m1XFmzy/view?usp=sharing ETA - it seems this track did not correctly record what occurred. Damn.

Version 2.0 is released with requested features. Keep the feedback coming. /F

Nice! No reason it shouldn't work with any other pieces of functionality. I sort of intended that mission creators could build this in if they wished to. You could also have a drone in the overhead and run the detection off that. Version 2 is coming, and will have the grid refs in the message, and also a spiffy BDA radio transmission when the enemy is all down.

LOL - I'll see what I can do. The grids are definitely possible, and in our internal version they are already there (displayed in text, not voiced). For the BDA, you can set the map how you like and see them. The default I used was fog of war, so if the friendlies see the enemy they'll be there. Shouldn't be difficult to schedule a once-execute function to detect the absence of enemy in prox to the friendlies, and have some "thanxbro" voice indicating they're all dead. Will look into it. ETA: Definitely gonna happen. Easier than I thought it would be.

That's the limiting factor, because you'd have to have pre-recorded voice for every possible circumstance. They did build some JTAC functionality right into DCS but that would be one hell of a wheel to re-invent. Having them rip off a five line and then shut up wouldn't be difficult though. Anything with a big possibility tree, back and forth interaction (like check in, game plan, etc) and supporting voice would be very hard to do.

It does seem that it could follow certain targets or possibly certain locations. With targets needed to be shot at 3,4 times to get a hit, it's hard to rule this out.... But as admiki says, since it only affects some, and as NeedzWD40 points out the misses are exclusively linear, it's clear that there's a detection of control inputs in the equation - likely "phantom" inputs that aren't actually there. And those are factored in (incorrectly) as "error" and are being imparted into the aiming process. I hope it gets identified, and fixed.