okopanja

We are having errors of 10s of meters here. There are 2 possible causes for this: - GPS precision (if true it would be worse than consumer devices) - Guidance law implementation Also note that the Angle feature does not work and that it appears that bomb mikes a rather short climb and dive, which in many case does not even seam necessary, otherwise for the non working angle ingress.

Geofizika 36T is on R-27T, Mayak-80 =>R-73

I think the plan is also to integrate nvidia control panel...

Field of regards vs field of view: As for targeting angle, I am also wondering. If you were correct FOV of 5x5 would allow only 62,5 FOR, so I do not thing this is the case, more likely this is maximal angle at which the seeker is able to capture and track the lock (likely the extreme angles are very likely to loose the lock, unless the missile itself turns). But this is just me guessing... There are also other definitions of target angle...

Can you please try the mission from @sylkhan? Clearly something is ODD, the precision is vastly different. The one I got before is the one of the dumb bombs.

If this was in ground attack mode, you have to wait for system to align. Wait 3-4 minutes before moving on take off

I tried Syria. I used my mod to enter coordinates and I made sure they are as accurate as possible. Made 3 runs: 1. Climbed to 30kft, launched, hit 2 out of 4. 2. Stayed level, launched, hit 1 out of 4. 3. Stayed level, launched, hit 1 out of 4. In all 3 cases the hitting errors were different. (e.g. not hitting/missing same target). This means that coordinates are not to be blamed. Furthermore the error is present both in latitude and longitude (mentioning this since the lower the latitude is, the greater the error would be with same precision in DD MM SS.s format). Observe the screenshot: error is great enough to miss a building. Clearly there is an issue here. On Caucasus: I am practically hitting the Leopards directly or within 1 meter from the edge. Mission I used: Growling Sidewinder, target at Tschinkvali.

I manage to hit 4 targets with 4 bombs in repeatable manner with both LS-6 250 and 500. However logic escapes me. I do not understand why I have to define profiles, while selecting explicitly pylon, and there later cycle the pylons while selecting proper pylon. @sylkhancan you post your mission? (which map do you use?)

Do not enable Dynamic Vibrance Yes, might be be good for faked spotting?

How do you capture coordinates? Decimal place in seconds matters a lot. I am hitting Leopards directly or by the very side.

I managed once to send 4 bombs on 4 different targets, but I must say logic escapes me. I did not find yet anything that works. So far I figure out that FC3 can get nav points from mission, but this sadly does not work in MP (commands get executed on server, but never transferred to client). However, I must say that I tried weird things but none could be used in a practical manner, the way it is possible with other modules. For the FC3 the only tip I can give you is to use LAND mode to select nearest airport and then switch e.g. ti A-A mode. The HSI will designate direction and distance to the airport.

Sun filter in Su-27 is difficult to see through. See it yourself. In addition you can see own uniform as reflection in HUD. MFD too reflective, and too good in sun. J-11 sun filter even more useless than before. Now with similar issues as Su-27

1. MT 2. I can do the track, I just have to do it manually, since DCS can not record the button presses done from my mod. 3. It's not strange, it's regular. I have a feeling that also it does not execute the ingress correctly Here is the video to demonstrate the issue.

I just tried myself with LS-6 250 and LS-6 500. 1. I defined 4 targets and entered them as PPs into UFCP. 2. I switched to A-G/SMS and defined first 4 profiles as PP with subsequent PPs 36,37,38,39 3. I cycled to 1st profile 4. I launched 1st 5. I cycled to 2nd profile 6. I launched 2nd 7. I cycled to 3rd profile 8. I launched 3rd 9. I cycled to 4th profile 10. I launched Results: LS-6 250: first two bombs hit designated targets, second two reverted to first target (despite being launched under profiles 3 and 4) LS-6 500: all 4 missiles went to the same target What am I missing here? In addition they do not ingress under default -45 degree angle.

I recorded my view:

just watched in the first pass and I can see what you mean: it felt as if it was showing the picture within the case. On observation: I am under impression that in previous version the POD did not move at all visually outside, while in this version I can see that it actually moves.

In last update I did not notice anything wrong, this is current version?

For me DLAA introduces some latency, when switching cockpit lights on/off. Might be better for others.

Found only 12 at pollin: https://www.pollin.de/p/drehschalter-cka1x12-26-mm-1x12-kontakte-420924

It was actually removed recently on October 19th 2023. with 2.9.0.46801 releases: https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.9.0.46801/

Is this still active thread?

I think you misunderstood me: Chuck is great! It filled the holes from official manual pretty good. However I was having second thoughts if this should be reported as JF-17 bug, and figured out it was more sensible to comment here.

Well, perhaps this is a point for updating the manual, but it appears that a number of A-G weapons in Jeff stopped working properly with 2.9. So maybe it is premature to update the manual. I wish in general that such technical decisions would be more clearly documented along the reasons.

If you carefully look into the Chuck's manual you can see that the target is tracked with radar in STT mode, the WMD7 is slaved to it with no actual lock. At some point this did work for sure the question is why it was removed? One answer could be that construction of WMD-7 prevents slewing it above the line of horizon (e.g. for targets on above own altitude). Still I see no physical reason why it could not be used for target that are below the line of the horizon. I was tempted to create a bug report, but have realized that this was likely removed intentionally. And yes, BRM-1 is very cool weapon, e.g. I actually was able to utilized it to target slow flying helicopters (below doppler notch) utilizing GMTI -> WMD7 -> BRM-1. In this case as soon as I locked it with WMD-7, GMTI was freed to search for other ground targets. GMTI presents some interesting options, including maddog-ing SD-10 at short range against helicopter.