Jump to content

McCallaway

Members
  • Posts

    33
  • Joined

  • Last visited

Personal Information

  • Location
    Paris

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. SO far we have observed the issue with: => F-14A ; F-14B ; F-15C ; Mirage 2000C ; MiG-29S ; Mirage F1BE ; Mirage F1CE ; Mirage F1EE ; SU-25T ; SU-33 ; A-10C II Strangely, the F/A-18C doesn't seem affected. Other airframes not tested.
  2. If an aircraft group has a callsign with a flight number on multiple digits, interactions with AI ATC/AWACS/Tankers wont work correctly, or at all. Not necessarily a big deal, though in some cases this seems to cause problems to activate a tanker or get info from an AWACS. For example: With test aircraft is an F-14B plopped in a empty mission, cold at the ramp in Anapa. Test procedure is to plug external power, turn on the radio on 250 (Anapa frequency) and requesting startup. Results are as follow: Callsign Enfield-9-1 => message out is spoken as Enfield-9-1 => Anapa answers with audio Callsign Enfield-10-1 => message out Enfield-1-1 => Anapa answers with audio Callsign Enfield-19-1 => message out Enfield-9-1 => Anapa answers with audio Callsign Enfield-20-1 => message out Uzi-1-1 => Anapa answers with audio Callsign Enfield-50-1 => message out Ford-1-1 => Anapa answers with audio Callsign Enfield-75-1 => message out Pontiac-5-1 => Anapa answers with audio Callsign Enfield-79-1 => message out Pontiac-9-1 => Anapa answers with audio Callsigns with flight number over 80 (tested with Enfield-80-1, Enfield-81-1, Enfield-99-1, Enfield-100-1, Enfield-101-1) => there is no message out ==> Anapa responds with no audio (only text is shown). It's in this last case that some users reported inability to interact with a tanker.
  3. Do note that this seems to happen much more in multiplayer (when connected to a remote server) than in solo (or even with a self-hosted mission).
  4. Thanks bal2o, I did tinker with that a bit and it's indeed a way to do it. I would still love to have integrated MIDS in the Voice Chat, but we'll see
  5. Is there a reason why and do we know if there are plans to implement these MIDS someday ? (I have a feeling that has to do with these radios not using explicit radio frequencies like the other ones) This new voice chat looks amazing but I like using a MIDS for inflight coms and we used to do it with SRS. I will miss them.
  6. A future release of Skynet IADS will get back to using setAI for HARM defence. This will greatly reduce the impacts of this DCS issue. Still hoping this will get acknowledge by ED. Also note that even though this thread was move in the F/A-18 section, it seems to be a more general problem with the HARM. The same problem can be encountered in the F-16 at least.
  7. Thanks I very well know that. That's precisely what I meant by "They won't ever show as [S] on the HARM TOO". The point is : these EWR have nothing to do with the issue I am pointing at here. Please just ignore them. @BIGNEWY if you didn't see tracks have been provided as requested.
  8. These are two additional EWR not the Flat Face used for testing. They won't ever show as [S] on the HARM TOO. Anyway the tracks attached above were done with a simplified mission with only the SA2 and no EWR.
  9. Please find attached two tracks and the mission used. Again please realize that the problem is only present in multiplayer, and when connected to a distant server - not in solo and not on a self-hosted server. First track is demonstrating the issue (radar turned off with enableEmission(false)) Second track is for control : same mission file, but in this test the radar is turned off with setAi(false) instead. Here is what is happening : SA2 is ahead 50 nm and on the rough location of WP1. Just the default DCS template dropped in the editor. First track - setEmission(false) - HARMs kill the Flat Face - We can see the [S] on the HARM TOO page (LMFD) and the RWR (RMFD) as is expected. - Trigger enableEmission(false) on the group. - [S] comes off the RWR but stays on the HARM TOO (indefinitely). - Launch 2*HARM in PB on WP1 (SA2 location) with 122. - HARMs track and kills the Flat Face. Second track - setAi(false) - HARMs miss the Flat Face - We can see the [S] on the HARM TOO page (LMFD) and the RWR (RMFD) as is expected. - Trigger setAi(false) on the group. - [S] comes off the RWR and the HARM TOO. - Launch 2*HARM in PB on WP1 (SA2 location) with 122. - Both HARMs miss. TestEnableEmission.miz TestEnableEmission-20230104-114128_emissionoff.trk TestEnableEmission-20230104-114701_aioff.trk
  10. Ok wilco. In the meantime here is a screenshot with a search radar showing on the HARM display and not on the RWR. It was done back in november.
  11. Hello, bumping my own report here because I think it is quite an important thing to know. HARM defense in Skynet IADS is not doing *anything at all* in multiplayer because of this. HARMs will always kill radars even when they are supposed to be turned off.
  12. Hello, This happens only in multiplayer, when connecting to a server. NOT in solo or on a local server. - F/A-18C, 60 Nm hot on an SA-2 site, FL350, M0.8. The S from the P19 radar shows on the RWR, and on the HARM TOO page. - SA-2 site is turned of using enableEmission(false) - S disappears from the RWR, but stays on the HARM TOO page (indefinitely) - If fired the HARM will track the P19 I'm not sure if it is a bug but it sure looks like it. At least, I don't see any good reason why it should be different between solo and multi. Is there a reason in real life why the HARM seeker should "see" radars that the RWR won't ?
  13. Thanks for the share I will give it a try. Can you explain why you said the altimeter is "QNH 31.1inHg" ? It seems in fact to be an standard 2992 at least in the NM version, but I don't understand why you would put something as high as 3110. I think the F18 altimeter cant even go above 3100.
  14. Oscillation problem seems to be a bug in DCS when the A-10 is not loaded with any payload. I added a TGP and a pair of Aim9 in the armament menu at the start of the mission, and it corrected the oscillation. Do not forget to activate the emergency brakes, and try not to lock the wheels !
  15. Came to this thread trying to understand what I was missing in BFT-10, ended up finding on my own. Here it is : 1- Waypoint coordinates (lat/long) are given in min/sec, and should be converted to min/dec before entering in the CDU. This one seems not to be a big problem, I guess the trigger zones are big enough to account for the variation, but it can be a factor. 2- Offset from bullseye seems to be given in geographic heading, and must be converted in magnetic before entering in the CDU (so 030° geo is ~024° mag @ Batumi). I wonder if this is on purpose of if maybe magnetic declination was not in DCS at some time ? Also (3) About the violent aileron movement in manual reversion, seems to be a DCS bug when the A-10 is not loaded. Adding a TGP and a pair of cap AIM9 corrected the problem for me. Hope it can help someone along the way.
×
×
  • Create New...