tekwoj

I watched the track, 3 rockets hit, 4th one misses cause it's launched too close and it can't turn hard enough to hit the target (but it really tried so don't be angry at it). Here's the video If on your end it looks different, do you have mods installed?

What goes wrong in this track file is that right after you launch the first rocket you turn on LSS mode. This prevents lasing. You can verify this by replaying it, and right after the launch, beforee LSS is turned on do ESC -> take control. Then do nothing, the rocket will hit. So to sum up procedure for BRM: Master arm on, A-G mode selected, BRM selected in SMS page Fuze set to EFUZE TGP on TGP in AREA track or POINT track launch on HUD cue You shouldn't have to mess with anything on tgp related to laser. LSS is only when you want to find buddy lased target. LSR is for when you want to manually laser targets which shouldn't be needed in 95% of situations.

I think that's an intake cover to reduce drag and avoid engine spinning with just airflow? Now they are supersonic all the way. They get the initial boost of extra 600kts on engine activation, then gradually slow down to 600+ kts of TS. I think this topic may have to be moved to weapon bugs section https://forum.dcs.world/forum/540-weapon-bugs/ @uboats ?

No. By default it's in auto mode, if you click the button it will turn on manual lasing. This will be indicated by the LSR being in border and a count down timer in the middle of MFD display (time to laser burnout). LSS is laser search - the pod will look for laser signal from other source (when buddy lasing) Make a quick mission in mission editor. One target, hot start plane. Fly the mission, fire a rocket, wait until impact, exit the mission. Save the track file. Upload it here and we should be able to help you.

This is not mentioned anywhere so I assume it's a bug. When trying to designate target using the HUD the maximum range is 10nm. How to reproduce: - Load in a mission - Select HUD as active sensor - Move cursor using TDC. Try pressing TDC when pointing at ground at different ranges.

Is this a bug or is it normal that you can only designate target within 10nm using the HUD as SOI? I have a feeling you used to be able to designate targets further than that, but I'm not sure. I tried to look through the manual for more information but haven't found anything.

I've also just had a session where if I did an area or point track once by tgp, I would no more be able to slave tgp to waypoints. It's as if I was unable to undesignate the tgp target. Slaving still worked fine if I designated target by radar.

That's crazy, this is not at all what I see in your track file, the GB6 explodes above targets and destroys them all before the GBU12 hits. Here's how it looks on my side I saw in the logs that you have a good deal of mods installed, my first guess would be at least one of them is interfering.

Yeah, your track file for me works fine, so I wonder what's up. Maybe try replaying that track file, see if it's still bad, if yes record a video and put in on youtube?

I watched the replay and: LD-10: - the active one: lofts and reaches the target zone, but hits between 2 units, try with a single one in case it was issue with seeker unable to pick a target. - the passive one: it doesn't loft and simply doesn't have the range to reach the target zone, passive and sp launches need to be from high altitude or you have to loft "manually" by angling up. GB6: - everything seems to work fine? Flies to target, opens above and destroys everything in the area correctly. Both GB6 and LS6 have minimal and maximal range and might not reach target if launched outside of those. GB-12: - hits the designated target One note, if you set up your weapons ahead, you may want to use weapon pages rather than click the wpn button and switch the weapon on page. To do this use the A/S1 button (1st in top row) on SMS MFD. Then select page you want to configure. Whatever you set up on page will be remembered on that page. (you set up GB6 PP mode that was later back to TOO) TGP LSR now pretty much works in auto mode all the time. The laser turns on automatically few seconds before impact. You can press the LSR MFD button to turn it on manually. You'll se LS and timer counting down on the tgp screen.

From playing with the replay, you might be able to avoid it for the moment if you drop the first bomb from the right wing, but that's annoying to have to remember that every time.

I'm sorry Flappie, but some of the bugs have been reported quite a while ago, and if we compare other modules' patchnotes, JF-17 does look neglected.

As in the title. It's getting tiring to have to traverse all weapon pages to turn on the fuzes or LD-10 modes just in case I use the swap weapons button more than once.

Just to make sure, cdlp was active and you were in A-G mode?

Tested it and they track fine. They start actual tracking at around 5miles. Here's the screenshot showing different signatures: small , large, medium

That pdf is not up to date. Also the Viggen's RB-15 is currently bugged, so it would help to see the track. Might be the same bug.

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.