fudabidu

TARGET is still a simple and permanent solution for everybody who doesn't want to deal with LUA files (which probably reset after each update as well). How exactly does that Matrix board work? Does it require any software in the background to work?

Uhm ... if the FOV issue can't be solved without editing some LUA file I have one simple question: Why is the Ka-50 using a different camera than any other aircraft in the first place? The camera is a fundamental feature and it makes no sense to me why it should be different. Hooray for spaghetti code -.-

https://ts.thrustmaster.com/download/accessories/pc/hotas/software/TARGET/TARGET_User_Manual_ENG.pdf TARGET manual, page 39ff Map the ALT and ATT hold to your switch as PRESS events. Then map AP OFF to both switch positions as RELEASE events. Flipping up/down will engage AP, returning to center will disengage it.

It is indeed depressing. With 12 years it's the oldest full fidelity module and it still feels like early access. Datalink still bugs out sometimes, saving points through HMS is bugged, Shkval is a sad hack (possibly taken from the FC3 Su-25T), campaigns still haven't been officially updated for 2.5 Caucasus (...) and just recently the A-10C II update partially broke the Vikhrs. I love the Ka-50, but I can't recommend it anymore, because it's getting almost no love from the devs. Maybe BS3 is supposed to address all the issues, but brand new modules seem to have priority.

You probably want MadDog's Deployment patch. Caucasus changed with the 2.5 update years ago and ED still hasn't bothered testing/updating the campaign missions. https://www.digitalcombatsimulator.com/en/files/3308753/ If the AI can't see the target it will fly straight towards it, ignoring all threats along the way. Not only is AI stupid like this, it's also totally blind sometimes. You really have to babysit your wingman. Don't let your wingman attack anything before you've taken down all air defenses. It's at least going to increase his chances of survival. If he gets too close to the targets order him to rejoin. Instead of using "attack my target" send him a datalink point and order "engage datalink targets by type". If you've send him the position of a BTR he should focus on that type of vehicle. "Engage datalink targets" will order him to engage everything in the vicinity. This will at least lower his chances of going suicidal, since he isn't focused on one specific target. You can also send him an ingress point, so he will start his attack from this location. Useful if you think he has (read: should have) a better view from somewhere else. You can at least use him for scouting somewhat reliably, but just don't send him too far. If the target is 10km away, only send him 6km. I find it really sad that we still have to deal with poor AI 12 years after the original BS release.

Picked the mission "Shooting Range", autostarted, took off, trimmed for forward flight, went to the toilet, came back and everything was fine. There was a minor pitch oscillation (about 2° total), but that seems to be expected in windy conditions. Something has to be different on your end and because you didn't provide ANY information all we can do is play guessing games. Can you reliably reproduce the issue in singleplayer? If so, please provide a track.

If the target is outside the Shkval limits, you can't get range information, so a turret wouldn't be a significant advantage. That's what I was trying to say

IIRC there were concerns about increased drag caused by the tall rotor assembly, so the gear was made retractable (leaving no space for a turret, but less drag) and the cannon was moved to the side (less drag than a turret). Recoil will always have an effect on your aim unless the cannon is perfectly in line with the center of mass. You can either design a ridiculous looking helicopter (in the 1980s!), find ways to compensate for it or your gun will just spray all over the place. If you've watched videos about Soviet helicopters you'll have noticed they prefer running attacks and if this was the doctrine at the time the Ka-50 layout makes perfect sense. The cannon is mounted as close to the center of mass as possible to minimize the effect recoil has, airflow and autopilot will stabilize the helicopter significantly and the limited cannon traverse compensates for any remaining deviation. It's not like you could make use of a turret in the Ka-50 anyways. The Shkval can only look 30° to both sides. Using only the HMS would make the gun inaccurate due to the lack of range information and you'd loose almost all your situational awareness. So, assuming running attacks where the doctrine, I'd call it "Soviet genius". It gets the job done very well without any extras. The Mi-28 still has to deal with the same kind of problems, especially if you start turning the turret, but the solutions stay largely the same. In the end it's not a huge difference to the Ka-50.

In my experience the MAVs can't track beyond 8 miles (read from WPN page). TMS UP will switch between 'wide cross' and no cross, but the MAV won't track and launch will be inhibited. You don't, because this doesn't exist! You either put the TGP into area track or you ground stabilize the MAV. Which one is it? This forum is confusing enough already. I've had a stuck MAV exactly once and TMS down on the WPN page fixed it, so I'm assuming ground stabilize is part of the issue. TGP handoff is commanding the MAV to slave, but the MAV wants to stay ground stabilized. Reach gimbal limits and the MAV will just look anywhere.

Selective Jettison (S-J) on the SMS page. It (partially) overrides every other master mode, so JETT is displayed on the HUD instead.

I'm curious, did that fix your issue?

By now there seems to be a new post about a borked TGP and/or MAV every day. I suspect these issues come from the temporary A2G logic we have to deal with right now. The correct logic should be known to the devs, so what's the status on the implementation? Newy or any other mod, we know you read this, just ask the developer responsible what his feelings are about it and post it here. I'm not asking about a release date, just an update on the progress. In that context it would be good to know about the 7-MARK page as well for obvious reasons (if you know the aircraft already). The error reports are not going to get much more useful over time, there is no point in maintaining placeholder code and we don't need things like JDAMs if the SOI still glitches out regularly. We have enough toys for now and we'd like to employ them properly. Thank you very much in advance. In the mean time, for everybody running into TGP / SOI issues: 1. do not panic and do not press random buttons 2. make sure you have at least one valid waypoint near your target and select it. create one if necessary 3. select the appropriate delivery mode (CCRP or PRE) 4. make TGP the SOI 5. command 'Cursor Zero' (when in doubt: TMS aft a lot) 6. TMS right for AREA track So far this procedure has fixed my TGP/SOI every time. - NOT tested with mixed loadouts. The MAVs always reset into VIS mode when you switch weapons, so that might screw things up in a different way. - If you exit A2G mode without commanding Cursor Zero your waypoints appear to be messed up. Command CZ in A2G to fix it. This is not supposed to be a support thread. If you have a problem, post it in the right section. Thanks.

@10:45 Handoff works Watch the range on the WPN page. It's "8". This appears to be the max tracking range for IR MAVs in good conditions. If the MAV seeker is out of range the handoff won't complete.

The MIDS knob seems to be the easiest to forget, because of its position in the cockpit. I certainly kept forgetting about it when I picked up the F-16. That's why I mention it. You're either forgetting something, your checklist is wrong/incomplete or you're running into a bug I haven't seen before. A track file would help.

Can't watch the track, because Nevada. Try using TMS RIGHT to get into AREA mode first.

On the ICP go to the TCN page. If it says OFF it's the MIDS knob.

Just one waypoint seems to alleviate some problems with the TGP and MAV PRE. Contact the host of that server and tell him to add a single waypoint on the spawn airfield for each F-16.

Before you exit A2G mode command CZ to clear the offset. If you don't the offset will go crazy and your cues will all be off.

Reminds me how LJDAMs couldn't be done, because of some engine limitation. Guess enough people were complaining about that, but not the MPRS. I'm so sick of this half arsed implementation, but that appears to be more and more standard in DCS.

If you ever spawn with no waypoints you should have a serious talk with the mission's creator. The TGP had problems with no waypoints from the start and still has. It's baffling how many server owners/mission creators haven't figured that out yet. A single waypoint on the airfield would 'fix' several A2G issues and it's just 1 extra click in the mission editor.

Did you not even read my post completely or what's your problem? I'm disagreeing with the statement that this ALWAYS happens and provided an example where it worked perfectly (handoff aside). Wanna know what's useless? Calling it luck instead of investigating the circumstances. Maybe now we can start talking about mods, maps, location, daytime, weather ... you know; USEFUL information. I find it hard to believe that I managed to fire 20 MAVs without a hitch and without any prior practice just because of pure luck.

Around 30 seconds into the track file I saw the vertical scan bar "having a seizure". It looked like a 1.5 bar scan, which doesn't make any sense to me in RWS. This didn't even last a second and the FCR returned to a normal 4 bar scan. Latest OB. No mods. Whatever your problem is, it doesn't show up for me in the track replay. I know what a 4 bar should look like and I counted every single bar from start to finish. It's just during that brief period where I see an anomaly.

I strongly disagree. The other day I launched about 20 MAVs at targets around Beirut airport and all of them correlated perfectly. Handoff didn't always work (possible IR MAV range limitation), but correlating did. Same plane, no respawns. There is an issue with MAVs sticking to random objects, but it's not an issue I'd call consistent.

Syria, mid day, CAVOK, no track because MP In those conditions my 65Ds were unable to track anything beyond ~8 miles (range as seen on the WPN page). TMS up on the WPN page didn't work either. I think the A-10C has to deal with a similar range limitation. Once within 8 miles the handoff would complete just fine, so I assume it's just an issue with the IR MAV's tracking range. Maybe the missile performs better during night time, when there should be more contrast between hot targets and cold terrain. EO sensors like the Shkval have their tracking range artificially reduced, based on TOD and weather. There is no visual feedback, but it happens. Wouldn't be surprised if a similar thing happened to IR sensors, just kinda in reverse.

Watched it 4 times now and all I see is a normal 4 bar scan. Only exception is around the 30 second mark, when the TDC gets towards the bottom left corner. The elevation twitches briefly and returns to 4 bar. If this state was permanent on your end I don't know why we're seeing different things, unless of course the TRK system is as unreliable as it has always been.