Nerdwing

Speaking of Stingers... are any of you folks able to confirm that their CM-sensitivity (and that for most IR missiles) is set way too high during the beta? Or are they genuinely this susceptible to flares?

I strongly doubt that :P It feels much more like a bug than intentionally removing realism elements in such a way. That sort of goes against what DCS's intentions are anyways

Understood. Hopefully this is just a beta quirk, I'd hate to try and fly with all IR being so ineffective. I mean I'd love to ~FLY~, but hate to play, if that makes sense :P

That isnt really related to the topic though :P

Not every mission has an A-10C assigned though :P Plus, there's the AH-64D's use in CA as a support asset and such.

Hello there! I apologize in advance if I'm missing something, but I came to a weird conclusion earlier and decided to report it as a bug since it sort of fits the criteria. I made a little CA mission with an AH-64D engaging T90's at standoff range. The Apache, armed with its AGM-114K's, would only engage at 5km. This is, I assume, due to it not using the radar at all to engage targets with that variant. Instead, it has to use the conventional laser designation as per the rest of the family, I assume? However, upon looking through the game files to try and find an explanation, I came to realize the AGM-114L doesnt have any entry in the db_weapons_data.lua file! This means that the missile apparently cant be assigned to any aircraft, it would appear. As a result, the AN/APG-78 radar and its ~8km range are pretty much useless it'd seem :( The Apache closes to within 5km of the enemy T90's, and risks eating a Refleks to the face as a result. Is the Longbow Hellfire simply not complete/ready for implementation on the AI AH-64D? Or was it accidentally removed at some point?

I'm also noticing some generally bizarre behavior in regards to all helicopter DM's. I had an Mi26 eat THREE Roland missiles last night that I fired at it from a rear aspect. Today, I had an Mi8 eat two OSA Sam's. This is in addition to small things like helicopter shrugging off direct hits from MANPADS, like the OP has mentioned. I wonder if something was changed in the warhead coding, or helicopters as a whole? They are taking alot more damage than I remember, as well as ignoring the effects of full-blown engine fires (fired a ZSU23/4 at a Hip's engine, set the right one ablaze. Stopped shooting and watched it flee for 10 minutes using time acceleration, engine a full-on inferno. It climbed/descended with no difficulty over mountains and generally seemed unbothered by the giant fire that had consumed the engine!) And good lord, the CM rejection rate (or lack there-of) for Stingers is absolutely abysmal. Are these what the 92C variants were really like? I can imagine the A being this bad, but damn!

Heya :) The first (High Voltage/Emission Toggle" toggles the unit's radar. "Feed Slot 1" and "Feed Slot 2" are for weapons like the RARDEN, where you change between HE and AP rounds on the fly. It also lets you change between AP and HE on most IFV's chainguns.

I'd love to have ships prioritize incoming threats/AShm's in order of danger presented to engage those closest with a higher degree of effort than those further away. Also, the SM-2 on the Ticonderoga shouldnt use the exact same stats in terms of Engagement time/Reload time as that of the Oliver Hazard Perry, to the best of my knowledge. Plus, the Aegis system is only modeled with two-targeting channels rather than the six it should have :(

Man, those FIM-92's cant reject a flare worth a damn :P Plus the Stinger guy has no texture. He's all orange with error text! But that aside (its a beta after all), MANPADs are fun as heck. The tank combat now is actually very enjoyable too. And Im in love with the Gepard SPAAG with its laser range-finder >:D

The spoof-rate for the FIM-92C seems to be remarkably high as well, in my experience. I'm literally looking at 90% in the 1.28 beta for a flare to properly trick my MANPAD in front and rear aspect shots. Isnt the FIM-92C supposed to have a degree of countermeasures-resistance?

Agreed in full, that'd be a massive boost to CA's playability.

I recently had to replace my computer's hard drive after a failure, and am in the process of reinstalling programs. I have reinstalled DCS World 1.2.4 and the appropriate A10C module, but when asked to verify by entering a serial number, I realize that I've nothing listed. I can only assume this is due to my original purchase being through Steam. I'm unable to launch the DCS World's missions currently as I'm asked for a key once more. Do I have to re-download the Steam install, get the key, then CnP it into my DCS World's activation prompt? Or is there some other way to recover it that I'm unaware of?

Hello there. I've been playing DCS World and the A10 module for awhile now, but as of recently its outright refused to launch when requested. I used the appropriate shortcut and all, but to no avail. Here is my me.log file's contents: This and the auto-update log are the only ones visible in my Logs folder. If there's any other information I can provide to fix this conundrum, then I'd be happy to oblige. The game will flash the command-line/DOS screen briefly then just stops, leaving me at the desktop. I dont even make it so far as the game's title sccreen.

Hasnt the M1A2 always had this problem in DCS? Even in LOMAC2 they would routinely lose to T55's via frontal hits. Its hitbox is wrong or something, because its performance has been quite wrong for as long as I can remember. I imagine it developed some quirk when it was brought over to the DCS engine. Oddly, in LOMAC 1 it had the opposite problem and would routinely trump the T80U in missions it was featured in.

Lovely patch so far :) Really enjoying it!

*Made user Nerdwing realize his Logitech Extreme 3D is too old and not registering movement correctly :(

You've gone from a great poster to horribly confused in a single topic. You're a hero.

Absolutely nothing :) It works fine, was just curious if there was an alternative. I'm just now getting to use the TGP to designate an SPI for the Maverick to slew to, thats a fantastic feature! Its great to be able to lob them from so far outside the Maverick's seeker range without having to desperately try and pick up on a unit's signature with slewing.

Yep, it works like a charm! This has helped a ton. Is there any way to slew the cursor faster aside from manually setting the speed via the Stat page for the TGP, and the (forgot the name, but its the same concept) for Mavericks?

Thank you kindly, sir! Thats going to be a huge help. Since I've a cruddy old Logitech Extreme the whole Chinahat thing is counter-intuitive to me since despite my Track IR, I'm instinctively trying to use the hat on my stick to pan camera until I get used to the new setup. :P Will check the keybinding as soon as able!

Hello there :) After I've designated or attempted to designate (or even just look at honestly) a target with the targetting pod or the maverick's camera, the point remains designated to the best of the pod's ability even if I break off. This means that I have to take ages to reset the designator to the default position again manually, and try and guide it back into my FoV for use again. Is there any way to automatically initiate some sort of "reset" for the maverick and targeting pod's cameras? Just something to default it to its 12 o'clock position would be spectacular.

I sure as heck wouldnt. In fact, I wouldnt wish such a game on my worst enemy. It'd be cruel and unusual in the extreme!

Oh, rest assured Im playing it exclusively with Sim Avionics now :)

Logitech 3d Pro is my stick, picked it up about two years ago at Best Buy. The rudder is a bit twitchy on it, even when idle, but I figure some Deadzone can make up for that flaw. I'll take a look into setting it up tonight :)