tekwoj

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

That's a weird observation about the shift. In other modules you have to manually shift the TGP to be on the vehicle's lower half (tracks). This is because otherwise TGP would look too far behind the target - it doesn't stop on the target when tracking, the line goes all the way to the ground. EDIT: I've ran some tests on 6 targets I hit all 6 with point track, dead on. Only issue I can see is you have to be really careful when passing the target. TGP starts shaking a little the moment target is slightly behind your 3-9 line, even if you pass properly while making a light turn. If you pass above or too close to the target that gets worse and you have a good chance missing the target. I have noticed a bug with the track file though - either it registered wrong where my tgp was looking or the AI in the track scattered to different positions (probably the latter). So in the track replay I hit only the first target.

FYI the target sizes in the pdf above are not up to date.

How to reproduce: - go to special options -> JF-17, set DL slew rate to 0.7, CM-802 control mode TRACTION - launch mission, launch AKG missile, switch screen to DL pod, make it SOI - take control of the missile, switch to NARROW field of view and use TDC to steer The missile doesn't respond to input. If you switch to WIDE field of view you'll be able to control the missile normally. If you quit the mission and set DL slew rate to 1 it works as expected. akg bug.trk