Jump to content

TheBigTatanka

Members
  • Posts

    296
  • Joined

  • Last visited

Everything posted by TheBigTatanka

  1. If you've listened to some of the recent Russian BVR engagements.... The brevity is... Not there, lol. In USAF a missile not supported to at least husky is "trashed." Cheap shot and Husky are essentially the same thing, but one is internal comm, and one is external fight comm. Fox-3 with amplifying information is for training purposes, i.e. shot validation in the world of larping. It allows the range officer or the red air to evaluate the shot taken in real time and determine their own dead/alive status based on their own maneuvers or lack thereof. Not sure it would be helpful in a combat video game. That being said..... Internal AI comm of "pitbull" or "husky" or "trashed" would be helpful for the human player to build SA on how many bandits he can expect to have died on the last leaf. Better AI comm..... "Bandit Maneuver, north arm lead group, beam north" (not going to happen). Sent from my Pixel 3 XL using Tapatalk
  2. Nice to see it's planned! Hope this also includes pre and post launch AMRAAM Apole and M-pole info. Sent from my Pixel 3 XL using Tapatalk
  3. 4th gen radars build tracks with angular, range, and velocity info. If a contact enters the notch, the radar loses the velocity info, but continues to track the target in range and angles. It's not like in DCS where the contact just vanishes. Like others have said, If the signal to noise ratio is strong enough (which is a function of range in part), then you can track through the notch. Without the velocity info, what might be degraded is information related to closure, and thus when your missile is expected to impact -- but, you can still track and shoot guys in the notch. Thus, notching is for specific threats at specific situations. Sent from my Pixel 3 XL using Tapatalk
  4. +1. Was just reading about this and also wishing we had this in game. Sent from my Pixel 3 XL using Tapatalk
  5. Probably the unrestricted satnav option. If I recall, the red side has a later date where it's available, or it needs to be checked for western coalition jets to have datalink when on red side. Sent from my Pixel 3 XL using Tapatalk
  6. The radar shouldn't be notched as easily as it is in DCS. Perhaps at longer ranges, where the range return is weaker and it's relying more on velocity returns. If you read the description of the radar in the manual, it's building tracks with angular, range, and velocity information. If the contact falls into the filter for velocity, it's still tracked in range and angle. The radar goes into COAST mode and tries to resolve the velocity problem. You can still track and engage the contact in this mode (through the notch), you just don't get velocity data so you lose the active/pitbull cues. My reading of the manual, is that the radar shouldn't be affected by the notch unless the range returns are weak (small RCS or distant contact). There's also tools, like being able to adjust the radar gain in air to air mode so you can see smaller RCS contacts (or see them further) -- which we don't have in DCS. Sent from my Pixel 3 XL using Tapatalk
  7. I never flew the viper (i was a heavy guy), but i recently flew the DCS viper with a friend from pilot training who did fly vipers -- we were both gitty with how cool it was to be flying together again, this time virtually. For an entertainment product (not a professional trainer), ED has gotten a lot correct. Like... I've been very critical when things are not right (or as right as they could be) -- but I think they are doing a great job with this product. It's finally at the stage where most things are implemented and the gameplay is really good (If you know how to use stuff). I think the jet has suffered from being bare-bones for the first year of its release -- but it's now close to fully functional. Like.... If you want to go do SEAD / DEAD with a four ship and protect an entity based on timing in the MEZ.... You can do that. If you want to do BFM or BSA, you can do that with a variety of weapons. If you want to do CAS, you can punch in a coordinate or make a mark point from a variety of sources, fine-tune the target location in a TGP, datalink the location to your flight, and set a time on target and get speed cues to delivery simultaneous JDAM attacks. If you want to fly DCA -- you can now (finally) get radar contact at an expected range, verify targeting and sorting on the datalink, and execute a variety of flows. If you want to strike.... You can do JDAM attack, GBU-12 attack from self or buddy lase (you can laser spot search), you can use a GBU-24 to point and shoot a bomb to glide in under the weather. The jet is just super capable. If you want to go cruise around and do a cross country with Steerpoint navigation, you can get performance data to optimize your profile. I'm sure I'm forgetting things, but it's capable of every mission set the Viper can do, and it's fun to fly (after recent patches). Is there stuff left to improve and add? Yes -- especially related to pre and post launch AMRAAM stuff, some radar symbology, radar gain levels in air to air, boresight launch mechanics, datalink network setup, and TDOA for the HTS pod -- but it's all achievable with what DCS has proven they can do. Again -- keep up the good work. Thanks for bringing this jet to life. It's cool. Sent from my Pixel 3 XL using Tapatalk
  8. I know there's still some WIP stuff with the radar and the AMRAAM symbology -- but i just want to encourage and thank the development team working on the F-16. This is quickly becoming the F-16 of our flight sim dreams. I never would have imagined 15 years ago that we could have something like this in a game. Keep up the good work. It's close to being at as high a level of an entertainment sim as you can get. I'll probably start piling on with some missing features or weirdly implemented things -- but I'm really enjoying the F-16, and so are my buddies. Thanks. Sent from my Pixel 3 XL using Tapatalk
  9. Probably related to this bug, if you lock a contact co-altitude at a range of ~40nm, and continue to climb in your commit, the radar will lose lock when you get ~10k above the bandit, and they vanish from the FCR until you get much closer. It's awesome that the lock range vs detection range took a step towards realism, but the look-down modeling is either borked or WIP. I think as others have noted, it doesn't seem to actually model the interference of mainlobe and sidelobe clutter (or the tools to combat that interference); and instead applies a generic formula. As others have said, look-down penalty should, in most cases, only be a problem when the fighter is at low altitude. I've also been told that the look-down problem would manifest itself more like extra contacts appearing on the radar -- which is why you wait for two target histories before trying to lock (as a technique). Of course, ED isn't interested in second hand accounts. Sent from my Pixel 3 XL using Tapatalk
  10. I have copies of several F-16 squadron standards documents, and it varies squadron to squadron. I've also had F-16 guys tell me how they've gotten yelled at in debrief for not having the lights set per the standards when in the arming area. Sent from my Pixel 3 XL using Tapatalk
  11. What Fusropotato wrote matches with what I've been told by several fighter guys: that by narrowing the beam, you are getting many more returns back (because the radar is hitting the target that much more) and you can see and lock things much much further away than you would normally be able to. One example had to do with being able to lock a tanker at much further than normal detection range when commanding an STT lock at the bullseye location and elevation provided by AWACS. Another example had to do with being able to hold a lock on a contact at a further range than you would normally be able to detect it -- for example, let's say you can normally see a fighter at 50nm and lock it there -- you might be able to hold the lock on that fighter contact out to 70nm because the radar has concentrated its energy. The same applies for narrowing the scan. I need to do some testing and make some tracks, but i get the sense that it's not working like this when you spotlight aircraft with TMS up long. I can't seem to detect contacts where i have datalink tracks by using spotlight at any range beyond what i would normally get a hit at on a 30 azimuth and 4 bar scan. Sent from my Pixel 3 XL using Tapatalk
  12. I can appreciate that at high angles like that it's going to seek that 1G and may need to pitch for it, until AOA logic takes over (at 15 deg AOA I believe); but it would be weird if the jet couldn't hold level flight hands off at one G, which is what we have in DCS now. I don't know, I've never flown a viper, it would just be maddening to pilot such a craft. Sent from my Pixel 3 XL using Tapatalk
  13. We're not talking about the loft of the missile, we're talking about manually assisting that loft by pitching up pre-launch. The F-16 should have a cue on the DLZ to indicate that optimal manual loft-assist. Sent from my Pixel 3 XL using Tapatalk
  14. Why can't the jet maintain 1 G and stay pointed where you point the nose? The FBW aircraft that I fly is capable of that. A FBW system that can't maintain level flight doesn't pass the common sense test. Sent from my Pixel 3 XL using Tapatalk
  15. There's a lot of variables.... But quick and dirty paveway III for DCS... If above 20k feet, release level. Set your release angle to zero. Have 350+ knots indicated, drop in the LAR. One technique is to drop on a spot a little beyond the target, and then shift laser onto the target to give the bomb more energy (steeper). Delayed lase of the last 15 seconds has been working well with PWIII. This is for a static target. Releasing from below 15K, and in greater than a 15 degree dive, the bomb is in "point and shoot" mode. Make sure your release angle is set to negative 30-45 degrees (affects the LAR). Roll-in like you are dive bombing, and point your HUD at the target area. In the LAR and with 350+ knots, release the bomb in the dive. Time of fall will be short, so be ready for the laser. You have given the bomb enough energy here that continuous lase works well. This works for static or moving targets, and self or buddy lasing. It's my preferred way to employ paveway III -- Point and Shoot. Lastly, releasing below 15K and level.... Bomb will pop up and fly level until it sees the target. When you lase, and how you lase, and when you release has too many variables and the jet won't give you good cues in the cockpit (since the bomb doesn't talk to the jet). A guy who used these IRL told me that for this scenario, they just get in the sim and try different things until they have an attack profile that works with the particular target. So.... For low level paveway III attacks from level, you just have to try different things until you have a system that works. I haven't found one particular attack i like yet. You seem to get too close to self lase at those speeds.... So I think it would require a wingman in wedge or arcing the target and buddy lasing. Sent from my Pixel 3 XL using Tapatalk
  16. As pitchy / mushy as the jet got with the last two updates, it's not a bad idea. Sent from my Pixel 3 XL using Tapatalk
  17. 340 knots is really fast for AR if we're talking indicated. 310 or 315 is standard for boom receivers from the 135. I agree though, it is a lot more pitchy (even at correct speeds for AR), and the boom operator doesn't plug as well as he did before. The planes that receive via probe usually refuel at 270 or 275 indicated. A-10s are painfully slow and i don't want to relive those memories of dragging them across the ocean. You can calculate your TAS (for the mission editor) by taking 1/2 of your flight level and adding it to desired indicated speed. For example, if you want to refuel at 300 knots and 20k feet (Flight level 200), you take half of 200 (100) and add it to 300. Your TAS to enter into the mission editor is 400 knots. That's not perfect, but good enough to get you within a few knots. I'll try refueling at the unrealistic speed of 275 and see if that's more stable. Sent from my Pixel 3 XL using Tapatalk
  18. Air data computers are only accurate above a certain speed. Sent from my Pixel 3 XL using Tapatalk
  19. That +10 degree limit is for the release limits of the jet's LAR calculations. The pubs state that the F-16 doesn't support greater than a 10 degree nose high release on the GBU-24 in the modes we currently have. If you want to loft GBU-24s (which should be a lot of fun), i think we have to wait for the implementation of manual release mode. And then it will be up to us to figure out at what range, speed, and angle to release the bomb for optimal flight path, and when to start lasing. Until then, I'm pretty happy with how closely the bomb is matching what it should do based on the publically available info out there. Point and shoot mode has been a lot of fun -- I'm always imputing +10 degrees into the control page to give myself the largest LAR window, and rolling in from about 5nm to the target to give myself a ~20 degree dive angle. Lasing the last 15-20 seconds works good too. Sent from my Pixel 3 XL using Tapatalk
  20. Also, don't forget to cursor zero your new Steerpoint once you are on it. Sent from my Pixel 3 XL using Tapatalk
  21. Aspect does matter for detection with Doppler, because it's not just your closure rate to the target that makes it stand out, but the difference in the closure rate to the target and the ground. The radar knows your own jet's ground speed, and it's comparing that with the returns it gets back from both the ground and the target. A hot return with 400 knots closure is going to stand out more than a cold return with 400 knots closure, because it's a lot more if a difference vs the background terrain returns. Sent from my Pixel 3 XL using Tapatalk
  22. I'm not sure I understand your method, but if HSD is SOI, you're going to send out your Steerpoint only. If you have TGP as SOI, you will send out the coordinates for whatever your TGP is looking at. We've done this a lot and it works great. Sent from my Pixel 3 XL using Tapatalk
  23. As the OP said, terrain textures to low is the ticket. 40 frames solid in VR, where i was only getting 10fps with terrain textures on high. The tool-tip says that "terrain textures" controls the quality of "terrain objects" which i think means the textures on the buildings, not the ground. Sent from my Pixel 3 XL using Tapatalk
  24. Got it sorted -- I have to eat crow on this one -- no bug here. The contact I was shooting at (what I use for testing purposes) is a MiG-29S. He must have turned on his jammer as I was shooting. I didn't have pre-launch jamming indications, and by 25nm I must have been at a burn-through range. In my previous 7 tests, I didn't notice the jamming chevrons through the datalink symbols, but I did on these subsequent tests. So, as expected, the missile is not lofting when it is HOJ. There's no bug -- I apologize for jumping to conclusions. Thanks to all the testers who double checked this today, appreciate your work. Apologies.
  25. Marlan, that's very possible. I've only been getting locks around 28nm because of the look-down penalty, so my go-to tactic has been a short skate from 25nm from the crank. No loft there, so it's not very viable anymore. I'll test more after SA map finishes downloading.
×
×
  • Create New...