Jump to content

toilet2000

Members
  • Posts

    408
  • Joined

  • Last visited

Everything posted by toilet2000

  1. The Ka-50 is a prototype, there never was a single production variant of the Ka-50, as they were basically test beds for the autopilot system and other stuff that would be put in the Ka-52. Not a single Ka-50 was the same, and all got different test configurations over their life. That's why there are certain liberties with the Ka-50: the real aircraft doesn't have a specific configuration or version with specific features. The F-16CM Block 50 in ANG/USAF does have specific capabilities and configurations/software versions.
  2. Belsimtek (BST) is and always was Eagle Dynamics. They branched out a part of their team to test the 3rd party workflow, forming the Belsimtek team. When the API got much more mature and more 3rd parties got in, they moved the team back into the core team, hence the "merger".
  3. I mean, the original poster gave his source: NFM-000. So yeah we have evidence that it should be.
  4. Yes, the FLIR (or targeting pod) is a donor to the MSI picture, at least IRL and not currently in DCS. Trackfiles when MSI is enabled should include tracks purely given by the FLIR or even datalink, but it is not currently the case. We can "see" datalink tracks but they don't behave like tracks (ie selectable and L&S-able).
  5. The original YF-16 was first presented as a day air superiority fighter in the LWF competition, but the ACF competition that made it so popular both for the USAF and internationally was intended to produce a multi-role fighter/bomber to supplement the F-15. So from the get go, even before the production started, the F-16 was designed as a multirole aircraft. The first YF-16 (which isn't an F-16) was a pure ASF, not the F-16.
  6. I'm not talking about the original F/A-18A/B, as these didn't have MSI to begin with. I'm talking about the upgrades made to the Hornet to replace the F-14 in the fleet defense mission when talks about removing it from service started. That's especially why I chose the word evolved when talking about the Hornet.
  7. IPD is a variable set per person, and by default it is obtained by DCS via the VR API of your headset. The calibration procedure of your VR headset is done to obtain this, but you can measure it yourself using a mirror, an app or by asking your optician. This isn’t something that you ask others, this is something that is very specific to you and your facial dimension. IPD represents the baseline of the stereoscopic system that is your eyes, and as you know, the distance between your eyes depends on your own measurements, not anyone else’s.
  8. With proper MSI, the Hornet should indeed be a beast for SA. It's a generally slow aircraft that accelerates slowly but has great nose authority, so the F-16 is generally the winner in a dogfight. As for missile slinging and BVR, don't forget that the Hornet evolved to replace the Tomcat in the fleet defense and AS role, and thus a lot of goodies have been implemented to help it do so, especially MSI. The F-16 on the other hand was first designed as a cheap fighter-bomber for export (like the F-5A) and evolved into a mainline fighter-bomber/specialized SEAD aircraft afterward. The USAF has several other and better aircraft for the air superiority role, such as the F-15 and the F-22. It's radar (even though it has unrealistic range currently in DCS) is smaller and less capable than the APG-73 of the Hornet, so definitely it most likely is less capable in BVR compared to the Hornet. The F-15 is another story though, as the version we have in DCS is both extremely simplified and much, much older. IIRC it's similar to an early 1980's F-15, so non of the fancy sensor fusion and datalink avionics. Therefore the comparison in DCS isn't very relevant.
  9. I'm pretty sure I had this discussion with @Santi871 and he has documentation that points toward this. But honestly, just based on pure educated guesses and logic, just the name of it definitely gives you enough details to know this: Multi Sensor Integration. Currently, there's no "integration", just a bunch of sensor doing their separate things. There's a lot of SMEs who have hinted at this too.
  10. Check if your Radar Elevation axis is not bound to something you don't want it too. It sounds like the radar is scanning at the lowest or highest angle. (check the elevation carret on the left side of the radar)
  11. No, not at all. SEA mode is not GMT. GMT requires moving targets. SEA mode is optimized to filter out non-return areas typical of bodies of water and put synthetic bricks over the resulting returns. Otherwise there wouldn't be any difference between the SEA mode and the GMT mode. This is very well described in available documentation online for the APG-65.
  12. Santi is the same guy that helps Wags with some info on the Hornet for example. He is not with Razbam, same goes for Chicken. They're both completely independent from Razbam.
  13. To begin with, ChickenSim. Also, I know Santi has good sources on that and discussed the issue on Razbam's Discord channel. Those are two very good sources.
  14. Really hope this is going to get fixed. It makes no sense and several SMEs chimed in to confirm this isn't the correct behavior.
  15. This isn't conjecture. This is info that is found in public documentation, including a Master Thesis made on the inherent limits of the LITENING targeting pod for weapon delivery and accuracy that state the limited resolution available at full zoom. According to said document, the "usable" digital zoom is general zoom level 5.0, above that you lose too much details. This has absolutely nothing to do with DDI/MPCD resolution. Honestly, this isn't something very hard to Google, and before completely throwing out someone's valid point, I'd suggest you do a bit of research. And btw, it's Rafale (as in gust, translated), not Rafael (a person's name).
  16. Just landed yesterday with a 21 loaded with 3 R-60s and 1800L of fuel and it was smooth like butter, no need for AB. And this is a somewhat heavy loadout to land with. I think most of the issues come from flying the -21 like other planes in DCS on landing, ie dropping full flaps and gear and trying to fly in that configuration. Landing flaps should be used a bit like those on warbirds: you put them out when you're about to land and need to drop speed.
  17. If you have the stereo parser/fustrum culling option enabled in autoexec.cfg, try disabling it. It solved the issue for me.
  18. The LITENING zoom as said previously is WAY over modeled. In reality it's a digital zoom with integration (making it a bit better than pure digital zoom) when using zoom levels. Max full-resolution zoom should be Narrow FOV at Zoom 1.0. On top of that, the LITENING AT actually has a better narrow FOV compared to the ATFLIR according to docs I could find. I think it's 1x1 deg FOV vs 1.5x1.5 deg FOV.
  19. There was a placeholder implementation, but for now a long time it’s actually not been available at all. The screen stays black, plus they never implemented the targeting/SPI designation system for the EXP modes anyway. It just wasn’t functional.
  20. Honestly, this is all 100% a matter of subjectivity and preferences. My favorite weapons and those I always go back to are the Walleyes and SLAMs.
  21. Because deploying the latest and greatest weapons isn't the only fun to have in DCS. Exactly like flying cold war/early jets, there's a lot of fun in flying older 1980s Hornet scenarios. As for the Walleyes I, they were the ones mostly used on the Hornet during ODS, so for a cool ODS strike scenario, they'd be pretty neat.
  22. 10 or 20 means the TERNAV can't update but the error is estimated to be small. Are you flying over flat terrain or water? TERNAV continuous updates requires some terrain elevation to make automatic fix. As for your question, yes this was solved in a subsequent patch.
  23. You seem to be using a very old version of DCS. Update to the latest stable version or open beta. The DDI Format you're getting is back from when the AG radar was unimplemented.
  24. I haven't been able to see the captain bars to designate an FTT target in the AG MAP EXP radar modes. Only the INS designation cursor can be shown by depressing the TDC, but the captain bars are not shown on the display. Pretty sure this is a bug, because the captain bars should be able to be used to select the OSB labels (HOTAS shortcuts) and the TAC-000 manual from the AV-8B (very similar radar, the APG-65, just older than our -73) says that a FTT designation can be made in expanded modes. I'll try and post a track whenever I have the time. Thanks
  25. Doppler Beam Sharpening still requires a certain radial speed to resolve the distance, so both DBS and SAR (which uses DBS btw) have a dead zone in front of the aircraft. See more info: https://www.radartutorial.eu/20.airborne/ab05.en.html
×
×
  • Create New...