Jump to content

falcon_120

Members
  • Posts

    2118
  • Joined

  • Last visited

Everything posted by falcon_120

  1. Hopefully one day we'll see this implemented, it is a very important part of RL defensive tactics and maneuvers, just like preventive flares which indeed work in DCS very effectively.
  2. In RL you have a STT reject that automatically switch to the next target, but as far as I know this logic is not currently implemented (in all auto acq modes after rejecting a target, the radar should avoid that same target for a period of time/radar cycles) For the time being you have 2 options I would say: 1- you could try the HMD I HAQ mode, that let you be a bit more selective with your target selecrion. You'll need to manually place the HAQ circle within the target you desire and avoiding the second target being within the same circle. 2-Other option is using the Aim9x without radar lock, just placing the seeker circle in one target , uncaging, shooting, then quickly look at the second target, uncage and shoot again, quite simple and effective. Enviado desde mi ELE-L29 mediante Tapatalk
  3. Sounds like a bug to me. They've probably not considered the expand function and the TDC is moving by its original radar coverage parameters of the non expanded view. I will test it today to see if I can reproduce on my setup EDIT: just tested myself, I don't see anything wrong, for me the TDC does not move too fast when in Exp mode, is perfectly usable. BTW my tdc is assigned as an axis to my virpil index TDC cursor
  4. But can the Su27 fighter to fighter data link receive info from more than 3 other planes? On a maybe not so relevant sidenote, a data link from the same time-frame in the Ka50 can only receive data from his 4 element package (3 other wingmen). I've maybe incorrectly assumed similar limitations for flankers/fulcrums datalinks from the 80s/90s. Enviado desde mi ELE-L29 mediante Tapatalk
  5. Exactly, as Harker said. You can hover with the TDC and select the TWS. Why they didn't make it to an physical button in the HOTAS like in other jets I would not understand. Apparently the real TDC in the throttle use a force sensing mechanism that lets you be really precise going for the different options, "PC-Mouse like". But I would never know unless one day i find a hornet parked in front of my house.... If you are not a realism freak you can always bind it to your HOTAS as I've done myself. BTW, I know that the hornet has this neat function of saving a set of parameters like range,HRP, bars to a certain weapon, which i use a lot, I wonder if in the latest SW OFP/lots you could for example do the same including the TWS mode, so for example you use the sparrow WCS as your normal RWS wide search mode but when you go WCS forward to select the AMRAAM you directly enter in TWS...
  6. As people correctly pointed out, it depends on the mission, A2A radar management, flir management, and dropping precise munition like jdam and lgb will virtually make no difference, you would do it in a SE the same or similar way to a viper/hornet, so it could be done by 1 pilot. The moment you need to manage the A2G HRM of the plane, you need a dedicated operator to handle that, it's too complex to allow enough remaining time to concentrate for real flying and combat. So in essence, true low level deep strike pre-gps era type of mission, indeed require a WSO. Also a WSO will always be better to help with the SA in any type of mission. Enviado desde mi ELE-L29 mediante Tapatalk
  7. this You Can, no one said is the efficient way of doing it versus 2 man crew. You can drive a rally car fine with one person, you just can't do it fast enough to win a rally without your copilot calling you the directions of the next turn and how sharp it is.... Enviado desde mi ELE-L29 mediante Tapatalk
  8. This is probably a moderator doing it's magic merging threads with similar topics [emoji848] Enviado desde mi ELE-L29 mediante Tapatalk
  9. Same here, at first thought it was my joystick not working well (that button at least), then realized it was actually a bug. Enviado desde mi ELE-L29 mediante Tapatalk
  10. Hello JZF, I was not able to prepare a video as i will be away from my computer more than i thought. Although i leave you here 2 YT tutorialssthat will help you understand what i described in my post: Setting up Sensor/RWR to show on the radar page (starts at 11:42): Using WACQ/Spot mode: I hope that helps
  11. There is a very easy way in the hornet, or at least one it works for me in difficult situations with the enemy close by. 1-In the central MFD open up the SA page 2-Click on sensors > make sure to highlight RWR, with this selected you will see the rough direction of the enemy in the top of the radar page even if you dont see it or your radar is silent. 3-Go TDC up long (>1.5 sg) to activate SPOT mode 4-Move your TDC to the general azimuth of the RWR indications of your radar and play with your radar elevation every 2 seconds until you find it. If you dont want to go SPOT mode you can just go 20/40 degree 6 BAR scan and do the same, biasing the search within the azimuth of the RWR nails. Is that clear? I can do a short video to show, when i'm back at home at the end of the weekend. Additional tip: If you suspect to be close to merge distance there are 2 modes that work wonderfull, 1st one is GUN ACQ in the direcction of the RWR contact and pitching up and down. 2nd one is WACQ autoacquisition and going TDC depress to be able to move your scan radar around. You will find anything within 10nm in a couple of seconds,
  12. I understand that in most cases this bug does not add anything real, very probable for modern planes like F16/F18 and in general modern Western/eastern RWR equipment. But on the other hand, in DCS all RWR, from all generations and from all planes basically detects always if you are being launched, ignoring some basic physics such as the Frequency at which they operate or simply because they could have higher sensitivity or malfunctions. Let me give you some example, we have a mirage F1 in DCS that was known to have problems detecting F14/phoenix during the Iran/Irak war, as a solution if a F14 was airborne they basically went home, later this was solved with new RWR for newer F1 versions. In DCS this is irrelevant, you will detect always if you are being detected/launched. This could apply to other old equipment like the SPO10 in the Mi24hind, Mig19 equipment with very restricted frequency bands as to detect everything as they do now. Take this just as a reflection or just a rambling that had we a more realistic EW sand box, people going cowboy style against SAMs networks would be frustrated for real. Enviado desde mi ELE-L29 mediante Tapatalk
  13. Well dcs is a Simulator, don't see the applicability of balance here. Also don't know why you mention 5th Gen fighter here since we don't have those in DCS. My comment applies to our 3rd and 4th Gen fighter we have in DCS. And I think is relevant for those people who are currently very frustrated for a temporal bug that ED is fixing as they have stated already, as it happens that this bug could actually be even quite realistic in some cases, is a good time to change frustration for enjoyment. This is not against wanting all bugs (not just this one) squashed asap. Enviado desde mi ELE-L29 mediante Tapatalk
  14. Obviously is frustrating and I also want it fixed, but on other hand is as real as it can get for certain planes with less advanced EW/RWR equipment. What I mean is, IRL you just not happily enter a SAM wez waiting for the launch warning to launch a harm and evade, you either stay completely out of it, you go with a dedicated EW plane escorting you or you go low. Even more, some modern Sam's like nasams, patriots, S300/400 don't provide a launch warning as they do (except this patch) in DCS, they have TWS launch modes that could be very dangerous. So myself at least, I'm approaching SAM defended zones as Ukrainian pilots are doing these days, considering once you are close you go low and scan for launches, and you stay just enough to lob a jdam, or a harm and get the hell out of it. It's been even fun instead of frustrating . Enviado desde mi ELE-L29 mediante Tapatalk
  15. Same here , reverb g2 Enviado desde mi ELE-L29 mediante Tapatalk
  16. Same here, no missile warning launches from SA2, hawks, SA10s for hornets or F16, but I think it affects for planes and SAMS Enviado desde mi ELE-L29 mediante Tapatalk
  17. I would like an option, preferably coming with the future data cartridge functionality for FF fighters, to draw lines, exclusion areas, cap areas to load them and be shown in the HSD (or equivalent depending on the plane). I would love something easy to use in multi-player and SP, where you could draw the lines via the or SP through the F10 menu using your mouse or a preset of figures (squares/rectangles/circles/lines ..) and load them to the mission computer for example through the radio menu when you are on the ground. This would make possible to see in the appropriate mdf pages important information like the front line, or simply the exclusion area you want to protect in your CAP mission. As far as I know this is realistic and a RL features of tactical situation displays like the SA page of the hornet or viper, but also true for the A10/F15/Av8.... Enviado desde mi ELE-L29 mediante Tapatalk
  18. So in short: -That the TOO mode in the hornet provides a TD box in the hud locating perfectly the enemy SAM is not realistic, at least not right away, period. This is something to improve by ED hopefully in the future -On the other hand, if the radar has been emetting for enough time, and the RWR/MSI combination has time to gather enough info to build a quiality track, is not that rare to think that calling up a HARM you can hand off this info to the missile. -This argument goes both ways, there are simplification of the same systems or very similar ones across the staple of ED modules all around, let me give you some examples: JDAMs need no align time in the A10C or AV8 but yes in F16/F18, F16 need to boresight maverick but no other modules needs to, F16/F18 can change weapon laser codes in the air while the JF17 needs to do so while in the ground (realistic), F16/F18/all FC3 rwr provides radar info perfectly and precise to 1 degree while it should not be like that (the f14 is the most credible implementation).... So a lot of work to do to lay a framework that homogenize systems across the board, a huge task that will take years over several iterations when time allows...
  19. Jojo i get your point and frustation, you want sources for the info provided, but the truth is there are no a lot of public data around. However i would say this, people that have worked with the hornet and superhornet, including not only personnel but also pilots, have repeteadly said that there is no coincidence the us navy does not use a HTS pod themselves (or an equivalent). In the case of the hornet, the whole MSI system, build tracks constantly with a level of confidence and precision, these tracks are build not only from the radar, but also from the FLIR, SPJ and the RWR. This is amazing, and it means that even when not emitting (radar off), the MSI system build tracks of enemy and ground units detected by the RWR, which as time passes improve confidence/precision of said tracks in the same way the HTS does (changes in angular precision, recevied mean power, etc...). For example in air to air mode, i've read you get a bearing only track if the sensor providing data is only the RWR, but paired with other hornets in the flight you can more or less triangulate the distance to the enemy, this is not enough to employ amraams silently, but could be enough to find the enemy using the FLIR, and from that moment ruse the radar just at the right time to launch the amraam and give the enemy planes virtually very time to react and gain SA. So in short, even this is not the answer you want, it is true that in the hornet the ASPJ/RWR/Mission computer via MSI are working together to provide tracks information to the pilot and to other weapons like the HARM. How exactly? Well i'm afraid this is unknown to us. On the other hand is not surprising to me that all the electronic living in the HTS pod in the vipers is something that can go (sort of) internally in a bigger plane like the superhornet, with more space and power available for the RWR gear.
  20. Ddcs (dynamic dcs), for sure the best server around in my opinion. It PvP with a dynamic Frontline and combined arms at its core. You only advance the front with cooperation from Fighter, chopters and ground forces controlled by a human. Also it has game economics, good weapons like amraam C or harms cost a lot of money which you only get back with kills or slinging, so you don't see people taking off with 12 cbu105 or 10 amraams C... Also the player base is quite skilled so every kill, even against ground targets feels like glory (its amazing how good all ground units like tanks and IR Sam's are when controlled by human and not sitting in bases like sitting ducks). Enviado desde mi ELE-L29 mediante Tapatalk
  21. same, it's a real pity if a bug like this doesn't get squashed up eventually. Enviado desde mi ELE-L29 mediante Tapatalk
  22. Exactly the same problem here, only with the harrier and using the TPOD. Reverb G2 user also. EDIT: i do use openxr toolkit and open composite but that has never been an issue in other modules even in 4 hours long sessions day in day out, I've only seen it with the harrier. I will update a track of the issue when happens again although normally is some minutes inside the mission after an attack run with the TPOD masked. Enviado desde mi ELE-L29 mediante Tapatalk
  23. Nealius is right in that you have simply turned your argument around. If we look at my OP post I think I was quite clearly expressing how the missile seems to turn too greatly against a high G orthogonal roll defense, specifically that. The answer to that was basically: "1-the missile is alright 2-we have a more modern version and 3-if anyone complain/ask is probably just a low skill floor that skew any assessment" Some post later turn out that in fact the missile is using a proportional navigation guidance that let him denies an orthogonal roll defense thank to leading perfectly the target) o_o Also we are not even sure of the version and G capabilities of the missile cough cough. Ofc i did not say is undefeatable (kinematic/out of NEZ and leading it to the ground works) but not what I was told is a known defense to the missile (orthogonal roll of more then 5g with chaff & jamming), which btw could be not effective IRL, my point here is simply that it does not make much sense that manueverability wise this SAM meets or exceeds the sheer maneuverability of a SA11/SA15. Ofc improved, more intelligent and more complex SAM Behavior would be a lovely addition to the game, better depicting this and other weapons. Enviado desde mi ELE-L29 mediante Tapatalk
  24. Fair enough, so i would add 2 considerations: Is the plan delivering a 1967 SA2 sam to better reflect that era? wink to the F4 The current one is for sure deadly, its better to treat it as a SA11/SA10 threat, and i'm not kidding, however shouldn't the chaff/ECM resistant be maybe revisitted? I have not be able to break a lock through Chaffing my whole expendables kit while jamming and doing high g turns, but obviusly this goes in the I FEEL category, i leave it there.
  25. So I was testing SAM evassion techniques against different SAMs today and i noticed how deadly the SA2 is. Obviusly is a potent SAM with great range, but i was under the impression that its susceptibility to chaff and a high-g barrel roll should do the trick, specially from a clean F16 on a 9g turn. Well... it turns out the SA2 hold its own incredibly well (as good even as a SA11), and from short to medium range the missile follows incredibly well and high g maneuver. Is that ok? In that other sim the SA2 can be defeated with a 4g turn, and sometime it just cant cope up with the initial turn towards the targets if its close... It probably something in the middle i guess
×
×
  • Create New...