Search the Community

Make the speed and sensitivity of TDC/sensor cursors for the F-16 and the F-18, independently tunable? i.e. In the Hornet, if the curve and saturation isn't tuned way down, the sensor cursor is nearly impossible to control with precision in A2A. But, when a curve is used and the saturation cut down to try and correct the erratic movement. That then makes slewing Mavs or the TGP painfully slow. It's the same way with the antenna elevation/TGP zoom

Is it just my pc or does it seem like dcs aircraft just kinda float through the sky instead of haulin ass like 3-600 knots should feel like. My Build.... Asus Rog Strix hero viii w/wifi • Ryzen 9 5900X, AIO cooled • Asus Rog Strix RTX 2080 08G Gaming Triple Gpu • 4x8gb Adata 3600Mhz Ram • 250gb Adata M.2. Both vr and monitor

Is it just my pc or does it seem like dcs aircraft just kinda float through the sky instead of haulin ass like 3-600 knots should feel like. My PC Build..... Asus Rog Strix hero viii w/wifi • Ryzen 9 5900X, AIO cooled • Asus Rog Strix RTX 2080 08G Gaming Triple Gpu • 4x8gb Adata 3600Mhz Ram • 250gb Adata M.2. Both vr and monitor

All charts are sourced from SFI AJ 37 del 3, 1979 print. Test flights were flown in ISA, using weights as close as possible to those described for each loadout (remembering that the AJS is somewhat heavier than the AJ), either start weight or flight weight depending on what the chart in question described. LEVEL ACCELERATION Tests were run at 0km, 6km, and 11km in ISA conditions only. Each test included two runs (one by myself, one by Airhunter) with clean config/rent FPL. In addition, I ran a second set of 0km tests with a group 3 loadout (4x ARAK + XT), and 6km tests with a group 4 loadout (4x SB + XT). Two tests were run at 11km with the loadout stipulated in the manual, one by myself and one by Airhunter. Airhunter provided me with tacview files and graphs which I then charted against the manual (obviously only for the clean config 0km and 6km tests, and the 11km test). On my own end I forgot to save tacviews, but did save trackfiles, which are attached as well. The results show what I'd found myself: At sea level, mil thrust is maybe a touch slow to accelerate to M 0.9 but is still relatively close, and zone 3 is tuned almost on the dot. Zone 1 and 2 show discrepancies, particularly zone 1, although they aren't very large at this altitude. Excuse the rather unscientific graphs, but unfortunately just overlaying the ones from tacview wasn't really workable and I'm working with what I've got here: At 6km alt, mil thrust gradually diverges from the chart, ending up a little slower than expected. Zone 1 and 2 show large discrepancies. Zone 1 follows zone 2's curve, zone 2 follows zone 3's curve, and zone 3 is doing something else entirely. At 11km alt, only zone 3 was tested. The results were very far off the expectation: according to the chart, level acceleration from M 0.9 to M 1.6 should take about 5 minutes and 45 seconds. In the sim, this was achieved in just one minute (!), while acceleration from M 0.9 to M ~1.63 (as far as the line is drawn) should take about 7 minutes and 15 seconds, while in DCS it took 1 minute and 15 seconds. This is a very large discrepancy even compared to the aircraft's own charts, but also compared to acceleration profiles of other aircraft known to have phenomenal performance in this area (F-104, MiG-23, MiG-29). Something is clearly causing an issue here but I don't know what. Big thanks to Æck for spotting this one during a MP session and bringing it to light - I wouldn't have thought to test it otherwise. Finally for now, THRUST/DRAG EQUILIBRIUM SPEEDS AT SEA LEVEL This has been something I've been meaning to report for a while, but invariably by the time I got trackfiles, DCS would update and break them. As a result I'll just post the results of my testing now and drum up the trackfiles when I get time. Please note that this is separate to, but was compounded by, the now-fixed drag issues with Sidewinder launch rails. Each test was run using the circled loadout group from the AJ 37 loadout tables - so rent FPL was clean, group 1 was KA-24-XT-24-KB, group 2 was KA-24-XT-blank-04, group 3 was RA-RA-XT-RA-RA, group 4 was SB-SB-XT-SB-SB. All loadouts except group 4 (bombs) reach thrust/drag equilibrium above the intercept of MAX ZON 3 lines and thrust/drag lines, some significantly so. Group 4 is slightly slower than expected, the clean airframe flies beyond even SAAB's estimate for a world speed record using a stripped and polished modified aircraft, groups 1 and 2 are beyond the aircraft's Vne and fall off the chart, and group 3 (which should be the slowest according to the chart - just barely subsonic, likely due to the rocket pods generating enormous amounts of transonic drag compared to anything else tested) is sitting slightly above the aircraft's Vne. It seems drag values need looking at. I don't have trackfiles handy for these tests (the ones I did have are now several DCS patches old), but I do have tacviews for them. I can get tracks again if necessary. I haven't checked climb performance yet, but hopefully there won't be anything to add for that. OWN TRACKFILES.zip Tacviews from Airhunter.zip drag tests.zip

Hi everyone, The ARA Santa Fe is current capable of achieving 29 knots in the mission editor. As the ARA Santa Fe is a Balao-class (Guppy II - North Atlantic/Northern Sail) it should have the following performance characteristics (note that wiki gives performance figures for the Balao-class as built): Diesels: Surfaced: 18 knots Submerged (snorkelling): 6 knots (though C:MO says 12 knots) Electric motors: Surfaced: 10 knots Submerged: 16 knots

Hi everyone, For some time the AN/SPS-48E NTU (RADAR on the rear of the superstructure) has had a rather excessive rotation speed; currently, it rotates at about 4× the speed that it should (~60 rpm / 360°/s or a rotation period of 1 s as opposed to 15 rpm / 90°/s or a rotation period of 4 s). Tarawa_SPS-48E_rot_speed.trk

Hallo, ich habe mal eine Frage zum aufschalten eines anderen Flugzeuges per Radar im BVR Luftkampf was dabei Natürlich erheblich zur SA beiträgt. Wenn ich z.B in einer F16 oder FA18 usw. in einer Höhe von 30Kft fliege, höher oder tiefer und der Gegner auch in etwa die selbe Höhe hat und wir z.B eine Entfernung von 50NM haben, warum kann ich mich dann manchmal nicht aufschalten im TWS,RWS und der Gegner schon obwohl beide sich nicht in der Notch befinden sondern beide genau auf Kollisionskurs aufeinander zufliegen. Wo liegt beim Radar der Zusammenhang zwischen der Fluggeschwindigkeit des Bandits und was kann man tun um wieder in der Lage zu sein ihn zu aufzuschalten ? Vielen Dank ich freue mich auf eure Antworten !

Just trying to figure out the behavior of the radar. There seems to be a random change in radar sweep speed while flying. The only thing I can think of is some kind of overheat behavior? Specifically, I'll be scanning the area infront of my at full 60 degrees while flying. I'll get a contact, fly towards it until I'm within locking range, and lock. Obvious shenanigans results as they evade and I try to maintain lock. After firing a missile/maneuvering to get gun solution, returning back to 60 degree scan results in a much slower radar sweep. The time for one sweep almost seems twice as long as it took before locking/fighting. Idk if I'm losing my mind, as its not consistent. I'd love to know if this is modeled behavior and, if so, is there a way to get the radar to sweep fast again(either letting it cool down for a bit or reseting).