tekwoj

Point track currently is unusable in some scenarios. Just had the following situation: approach suspected sam site, observe missile launch, find rough area, put area track, avoid missile. Everything is fine at this point. Now second approach, tgp kept the target properly, find the sam vehicle, track it. Took some time so there's a launch from SAM, avoid missile, come back on course, tgp has lost the track, is currently looking at some random point in field. Another problem that started showing up is tgp slave not working 80% of the time. That was in MP so I have no track files but I'll try to reproduce that.

It might try, but if it's not implemented properly it might swap to whatever just like it goes for the flares even tough it really shouldn't. Uncaging the seeker will let it track the target locked by the radar at angles further away from your nose. Best way to test it - set up a mission with a target, st up the binds, test locking at different angles.

Yes, if you search S8 it should take you to the correct bind, normally buttons Sx are stick, Tx are throttle. PL-5 is an IR missile, it will track whatever is hottest in front of it. Not sure if the IRCCM implementation in DCS allows anything more advanced. Do you uncage the PL-5 when you use it (T2 Press bind)?

I could reproduce it by just making a mission with air start and a few waypoints, just make sure the first waypoint is not directly south from spawn point. Can't really tell when it appeared as I don't pay attention to it that much

Right now they will point exactly to the waypoint if you fly to it exactly from the north. They should do that when you're exactly on the course line instead.

This is not tacan, tacan arrow looks like this --o-> But from what you've marked on the screenshot we can see that the plane thinks the next waypoint is north. I think there was a bug on another module recently where there was a mix-up in relative/absolute directions. Here the waypoint is 0 degrees from the plane heading but it gets interpreted as 0 degrees on the compass. Edit: I've tested it a bit and I think I figured out what's going on, the tadpole always shows as if the course line was from north instead from the previous waypoint.

Press switch weapon (S8) bind, should switch to sd-10.

I was able to lock ships but it was easier when I set target size to 45m.

Test different target size settings. They matter now. The settings in pdf posted earlier are not correct anymore.

If it's signed with a certificate that has expiration date that's not unheard of. It wouldn't be the first time that certificates weren't updated before expiration in the history of programming. And I don't think it does anything online, if it did the fix would be more complicated than moving system clock back.

Could it be to avoid other devs/modders from reusing or decompiling their dlls?

Currently we can't. This is temporary until they decide how to implement it.

Could we have a solution like in AJS-37 module where you can either load mission cartridge or F10 map cartridge? You switch it with a hotkey in the kneepad.

And if you want to learn specific weapon use, create the most basic mission with the targets you need and loadout you want to learn and take your time to practice.

Did some moving target bombing runs today. The loss of stabilization is so bad that it will cause loss of track and you're lucky if you hit anything moving with a gbu.

Nope, hot runway start almost always means you'll still change your loadout. If you do that while cartridge is out it gets updated automatically. So right now hotstart is like that: - rearm - plug in the cartridge - load data If it was your way it would be: - rearm - take the cartridge out - open the canopy - request a cartridge update - after update close the canopy - plug in the cartridge - load data

GB-6 does very inefficient maneuvers when set to impact at specific azimuth. Is this how it's supposed to turn - i.e. after it passes the line marked by the target point and the impact azimuth? gb-6-2.trk

Probably same for any other SAM. What is strange it's the only of the LS-6 series bomb that doesn't get shot down, LS-6 100 which is smaller and probably should have smaller signature gets tracked. ls6-500.trk ls6-100.trk ls6-250.trk

LD-10 has a tendency to go short when launched from lower altitudes in SP mode. Attached track with 1.5k feet and 4k feet. Even the hit that does damage falls slightly short. ld-10-sp.trk

It is, but WMD-7 is not exactly a modern, state of the art pod.

To be fair in case of rockets you would have to do a very sharp turn to put the target behind you before the rocket reaches it. With bombs it's a bit more visible because they are much slower.

I've used LS6-100. All hit dead on. The point is offset when looking at flat angle, which is normal. When you're passing above the locked target you see that it's locking exactly the point on the ground where the target stands. At what distance and altitude are you locking and launching? TBF I saw somewhere that the pod shouldn't be able to track objects above 6nm or so.

This makes it semi-useless to use for laser guided bombs as you'll almost always have the target behind you in the final phase, risking the bomb to hit away from target.

Sometimes WMD-7 loses target. I've had it happen on ships (Molniya) in IR, I've had it happen on ground targets in CCTV (attached track, 2nd and last targets). There's a problem with the track where it shows different targets getting hit each time. Originally the targets on which I've lost track was the 2nd and the last one. 2nd should be visible, usually it's the last 3 targets that get bugged. tgp bug.trk dcs.log

In other words the moment the pod has to look even slightly behind the image starts to shake. How to reproduce: 1. Lock area or point 2. Approach as if attacking 3. Turn away to avoid passing directly above the target It should be visible in at least one target in the attached track. Problem is from what I see each time I watch this track it shows me looking in different spots and some targets get destroyed others don't. tgp bug.trk