riojax

Great job! Thanks a lot for your work on weapons, is awesome. ;)

As seen on the latest Wags video, the A-10C II APKWS rockets supports lasing and seems to have some erratic movement like the vikhr, also the warhead seems to be more powerful than the BRM90 one. Is it possible to review that to have a proper guiding and warhead damage?

Wow Mustang. Awesome work! I hope that ED will integrate these shaders on DCS.

Please, open a new thread to discuss about it, this is about a seeker and guidance bug. Thank you.

No, the battery was on parameters: Flying time: * CHAFF bug: 61 seconds. * NOCHAFF bug: 63 seconds. Also you reminded me that the real SD-10 battery time is 120 seconds, this also must to be raised in DCS. SD10-TACVIEW.zip

# Seeker problem The seeker is too vulnerable to old chaff, as you can see it turns out Unrealistically when a long time ago someone throw chaff at a distance of 5.700ft, at this distance the ARH radar can get the plane using pure pulse (no doppler here, by that a notch is a no-sense) and never will turn out from the center to a old hot point near the sensor border*, that in RL it will be too dissipated to do a response. *) Also in this case the chaff was out of the seeker cone before turning to it. Attached: [sd10-bug_chaff.trk] [sD10-CHAFF1.PNG] [sD10-CHAFF2.PNG] # Guidance problem The pure pursuit guidance fail to get the final point, also the missing missile fuse don't help. Attached: [sd10-bug_nochaff.trk] [sD10-NOCHAFF1.PNG] [sD10-NOCHAFF2.PNG] sd10-bug_chaff.trk sd10-bug_nochaff.trk

I use this hidden nvidia page: https://www.nvidia.com/Download/Find.aspx?lang=en-us Also, I recommend select Studio Drivers on "Recommended/Beta", Standard on "Windows Driver Type" and install the 442.92 version, for me is the best nvidia driver at date. This is the direct link if you want: https://www.nvidia.com/download/driverResults.aspx/159678/en-us

Thank you, and sorry if I was too rude, but I did think that on my last video all was crystal clear. My fault. This is easy explainable by an UUA indicator error, if it's wrong your G will be wrong too. About the video, I will expose my findings: I know that it's a 23UB. this means a very different airframe than the 21Bis, but it have the same DUA-3 and UUA-1 sensors and indicators. As you can see on the attached image, this is the exact moment that the nose wheel lose ground contact. On this, the UUA-1 measure only can be pure instrumental AoA and in this exact position the airframe differences are almost unmeasurable, also you can see that the difference is almost the third part, by that we can only conclude that the instrument is returning a bad measure. I hope that this ends the FM vs UUA-1 measuring error dispute, also thank you for your time, dedication and reading. P.S. If anyone finds a 21bis takeoff showing the UUA-1 it will be greatly appreciated.

The current CLmax is correct, and about the UUA the bug isn't the FM, is only the indicator as I did show on a RL video. Please, review your data with the possibility of a bad UUA indicator and don't spread FUD. About the "we are still able to extract too much performance" statement, this is simply a lie, the stall point is exactly the same on alpha and G values to the real tables, anyway if you want to rely on the UUA indicator, as I said before, the current output is wrong, don't use it.

Wow, IMHO this cockpit is a lot better than the default. Please, can you post the URL?

SD-10 was borked time ago. It had a lot drama at time but now seems that only few people is asking for a fix and always without any developer response. In my squadron a lot people was burned with this and now nobody fly the JF-17.

The AIM-120 is working well.

Still present in 2.5.6.52196

Still present in 2.5.6.52196

NOT A BUG

I tested it on default 20ºC 29.92inHg and on 29.49inHg (in this air pressure the steerpoint is perfect target centered) and on both the bomb was too inaccurate. About the CCIP bug is only on retarded bombs, not on normal Mk-82.

CCIP Delayed Release huge inaccuracy (280ft) The CCIP on Delayed Release bombing mode is highly inaccurate. All tests was made without wind, at 43ºC and 29.32inHg. This can be related to the CCRP bug: https://forums.eagle.ru/showthread.php?t=279283 F16_BUG_DTOS_01: The bomb goes short 280ft. F16_BUG_DELAY_01.trk

As you can see in the attached track and screenshots the steerpoint is off from the objective. Modifying the mission air pressure it will move. All tests was made on 43ºC. F16_CCIP_BUG_01-2992.png: The diamond is forwards. 2992inHg. F16_CCIP_BUG_02-2932.png: The diamond is backwards. 2932inHg. F16_CCIP_BUG_03-2949.png: The diamond is centered. 2949inHg. F16_BUG_CCIP_02-1.trk

CCIP huge inaccuracy using retarded bombs (325ft) The CCIP accuracy using normal Mk-82 bombs seems ok as you can see in the attached "F16_NOBUG_CCIP_01.trk" but using retarded bombs it goes too far from the objective. All tests was made without wind, at 43ºC and 29.32inHg. F16_BUG_CCIP_02: Mk-82 AIR F16_BUG_CCIP_03: Mk-82 Snake-eye P.S. Also I noted a steerpoint hud representation bug related to the air pressure that opened on other thread. F16_BUG_CCIP_02.trk F16_BUG_CCIP_03.trk

The CCRP bombing mode is highly inaccurate. All tests was made without wind, at 43ºC and 29.32inHg. F16_BUG_CCRP_04: Using BDU-33 F16_BUG_CCRP_05: Using Mk-82 F16_BUG_CCRP_06: Using Mk-84 F16_BUG_CCRP_07: Using GBU-12 (without lasing) As you can see the nearest bomb impacted at 500ft, and the bomb type seems to affect slightly the result. F16_BUG_CCRP_04.trk F16_BUG_CCRP_05.trk F16_BUG_CCRP_06.trk F16_BUG_CCRP_07.trk

Yep, but probably this bug is low level enough to be present on other TGP implementation, also the CZ missing is hurting this a lot more.

Hello, In some situations your steerpoints will corrupted, in this thread I attach three bug related to CCRP only. F16_BUG_CCRP_01: When you put the TGP to Standby the steerpoint will set some nonsense coordinates. F16_BUG_CCRP_02: With TGP OFF when you do barrels or be very near to ground the steerpoint will rotate changing a bit the original point. (can be related to this bug report) F16_BUG_CCRP_03: In RL when the TGP point/area is masked (plane or terrain) it will put on INS mode with latest good point and not modifying the steerpoint, but currently in DCS it will change the steerpoint coordinates like if the laser is measuring distances. Regards. F16_BUG_CCRP_01.trk F16_BUG_CCRP_02.trk F16_BUG_CCRP_03.trk

Nice video, by the engine sound seems that lights are on NORM before the engine start and once get the generator on line the lights goes on.

Wow M3, The MiG-21 FM is now a lot better! You nailed the CLmax graph and the stall point. Congrats. Edit: Also I want to say you that the current MiG-21 FM is probably the best on all DCS modules.

I used emergency to empty the O2 tank and ejected the canopy.