-
Posts
40 -
Joined
-
Last visited
-
Thanks for your answer. So, if the said « standard » can varies between aircraft, it doesn’t really exist. The problem is that people here are used to a certain standard of fidelity, and they consider that if this standard can't be reached with a certain aircraft... They'd rather not see resources allocated to the development of said aircraft, in favor of another aircraft that could reach the desired community standard. Anyway, yeah sure, we’ll always have the wallet vote. But seeing DCS losing it’s edge is not what we wanted.
- 607 replies
-
- 14
-
-
Hello Nineline. The question is not whether the aircraft meets the DCS standard or not. The question is whether the DCS standard has been lowered to make it possible to create this module. Because that's what the people complaining here don't want: to see the modeling standard lowered. And since the fidelity level between ED modules and third-party modules is already disparate, the -35 announcement is everything but reassuring.
- 607 replies
-
- 12
-
-
-
Wawar started following gun accuracy terrible , F-35A Announcement discussion mega thread. and The wobbly flight model
-
Considering the complexity (A/C moving in 3D, the gimballed gun, the recoil, etc) and the fact that these variables change every fraction of a second, I find that the gun does rather well in terms of grouping, and that on the contrary, the CEP is relatively low. However, the “point of impact” seems to be on the side. The rounds are well grouped, uniformly, but next to the target, not on it. (Clearly visible in the clip I recorded and posted above) Which made me wonder if it was correctly working. (The TSE seems to be compensating correctly, but not in the right spot) So I've got the answer to my question : TSE limitation. Thanks for the details and the quick reply. EDIT : Last question about the gun : In case of FCR gun targeting, is the TSE supposed to work?
-
Ok, thought that LMC was a criteria for TSE activation, thanks. So, constant lasing + target correctly stabilized in the scope = TSE is working and good accuracy? George is NOT using LMC, he is using the Autotracker + lasing while shooting. The target LOS is perfectly stable AND and the A/C perfectly stable. This should make the LMC work and put the rounds correctly to the target, without wind, since the TSE should compensate for the A/C movement. Does it seems normal to you, with the conditions described in my previous post, with a perfectly stable LOS and continuous lase (So, TSE in action), that : - target on the LEFT of the A/C : group of impact on the RIGHT of the target - target in the RIGHT of the A/C : group of impact on the LEFT of the target According to Bradmick, it's normal to "compensate" sometime, but I don't understand if we are supposed to compensate for the lack of performance of the TSE itself, or If we should adjust for the external factors like wind, etc. Currently with a perfectly stable A/C, in a sterile environment like DCS can provide (no wind, etc.), the rounds are well grouped, but OFF the target. It is supposed to be?
-
TADS yes. After verification with Bradmick on Discord it seems to be normal. The system is not « perfect », sometime the gunner has to make correction, even if the targeting is good. Another interesting point : apparently, George AI don’t use the LMC/TSE, so when George is operating the gun, there is not account of A/C movement. Which could explain why it is grouped, but off. Example of George AI grouping : https://streamable.com/okq8ql Sent from my iPhone using Tapatalk
-
Same issue. @Grennymaster : Like Dog explained, I don’t see a « dispersion » or a CEP issue, it’s just that the group of impacts is OFF target, to the right or the left. If I understand correctly, the TSE should compensate for the A/C movement, within margins. Another test : No wind, A/C height 1000ft AGL, target range 1000-1500m, 40KIAS; lasing a few seconds before the shoot to let the TSE make the calculation and lasing while shooting : - target on the LEFT of the A/C : group of impact on the RIGHT of the target - target in the RIGHT of the A/C : group of impact on the LEFT of the target The impacts are well grouped, good CEP. But the point of impact is OFF the target, left or right relative to the relative bearing of the target.
-
Wawar started following ASL wind correction incorrect?
-
Hi, Airstart jet, GBU10 loaded on the left CFT. At spawn, the LCFT seems not set up correctly in the pacs. Once the bombs have been manually set in the pacs, ASL for that specific station is bugged. Seems stuck in a corner of the hud, and the state "TREL" never appears. If I switch station, the ASL comes back on target and "TREL" appears on the hud. Track attached. GBU10 LCFT : GBU12 RCFT : ASL LCFT.trk
-
Thank you for the Klarification. Let’s hope Razbam is working on it, the current behavior makes the ASL not usable under certain wind conditions.
-
Any news about that ? Thanks. :-) Envoyé de mon iPhone en utilisant Tapatalk
-
Ok ! Thanks.
-
In this case of radar designation with AUTO release, shouldn't the radar switch to AGR mode during the last 15 seconds before the release? Like explained in the Baltic Dragon official manual, page 401 :
-
Hi, airstart jet, designation right on target. Without wind, the ASL is perfectly aligned on the target diamond. But with wind, the ASL is pointing towards the wind. The issue here is the ASL behaviour. The closer I am to the target, the more the ASL moves towards it. It is not "space stabilized". So, If I follow the ASL to the target, the plane will approach in a "curve" profile. Shouldn't the ASL be "fixed" in space, in this case to the right of the target, directly with the correct spacing? Track attached. ASL Drift With Wind.trk
-
Thank you for your answer. So you confirm that the AG Radar is not linked to any elevation database?
-
Hi, Airstart jet, patch map designation right on target. Target diamond on the HUD appears to be at the wrong elevation, under the ground. Track attached. null Radar Designate issue.trk
-
Yes, please. So important for cockpit users. Thanks ! Envoyé de mon iPhone en utilisant Tapatalk