Jump to content

Kondor77

Members
  • Posts

    88
  • Joined

  • Last visited

Posts posted by Kondor77

  1. The TACAN stops transmitting/goes silent when aircraft is more than 30/40nm away.

    This happens in the 14 and 18. Oddly enough this is not the case for the free Forrestal carrier. This only affects any SCs in your mission. Bug is only reproducible in MP. 

  2. As an aside, and currently kind of a DCS-ism if you lose track on a target before missile is commanded active and want to try to rescue the shot - STT the target (if you know the target has a jammer that will be activated in self protect mode). The missile A or C will turn to HoJ. But in another DCS-ism the target aircraft will get an RWR warning of an active shot out on them. The jammer would obviously need to remain on the entire time for the missile to guide. 

  3. Hi again,

    I had some time to revisit this and take screenshots this time. Simple air start in position to HRM the AB. 

    Sinai Map (currently functional) Bir Hasanah Airfield

    Sinai_Bir_Hasanah.png

    Marianas Map (Currently FUBAR) Saipan

    Marianas_SaipanAB.png

    Marianas_SaipanAB2.png

     

    nullMarianas_SaipanF10.pngnull

    As we can see, it's defining the entire airfield area as 'water'. Perfectly matching the F10 map in the 3rd picture. This to me looks to be a mesh issue with some maps, and how the A2G radar does its mapping. For example, here's the same issue on the South Atlantic Map for Mount Pleasant. 

    South Atlantic Map (FUBAR) Mount Pleasant

    SA_MP_HRM_10.png

    SA_MP_HRM_4.png

    SA_MP_F10.png

    If you'd like me to attach the .miz files or .trks I can do so, but this is so easily reproduced that I didn't bother to save either. 

  4. 58 minutes ago, norman99 said:

    Whilst not the exact same problem, AG radar issues are not just limited to the F-15E. I just took an EXP3 map of Tonopha in the Hornet, and it was crystal clear (as much as the F-18 gets anyway), try that at Anderson and it’s just a blurry, faded, shadow of an image.

    At least for the Marianas, it’s been like that since release. I’m actually surprised it’s not a more discussed issue, as it really needs to be solved.

    Good to know! It definitely is some sort of map mesh issue, which then depends on how individual modules have their A2G radar modeled. Hopefully a dev somewhere can chime in...

    • Like 1
  5. Hey all, 

    Spent a good amount of time last night testing on all the maps currently in game. If you try to HRM an airfield, it will come up as a featureless body of water (sometimes the hangars pop up - but the rest of the airfield complex will just be black, no runway lines, etc). Currently this is a bug on the following maps:

    • Marianas
    • Normandy
    • Channel
    • South Atlantic

    HRM currently works as it should on the following maps:

    • Caucasus
    • PG
    • Syria
    • Sinai
    • Nevada

    Pretty easy to replicate, all testing was done offline in an empty mission on air start F15Es. Seems to be an issue with how these maps are built with how the A2G radar draws the picture.

    For example, I tried the broken maps with the F16 A2G radar (knowing full well it's limitations compared to the 15), but the airfields at least still showed up. 

    • Like 2
  6. On 10/31/2023 at 10:07 AM, ChaosRifle said:

    Capture.JPG

    where? its not in the list on the mission editor beacons list at all, which means its not in there at all.

     

    I apologize for the late response, but your snark certainly didn't help. 

     

    image.png

  7. 35 minutes ago, ChaosRifle said:

    yes. particularly 71X is problematic. I have also noticed basically all stations drift as you fly (only about 100m usually, only visible if you enable map underlay), but the 71X freq will drift up to like 50nm off target.

    Because there is a 71X already on the map as a tacan. You'll have to use a different tacan. 

  8. Can confirm. This has been a longstanding MP bug. The worst part is the only way to 'fix' it is to totally close out of the game and restart DCS. At which point you're just praying you don't get hit with it again. 

    I have found an interesting workaround, BUT it's not 100%. When choosing a slot, chose another carrier plane - in this case a Hornet (I know). Spawn in. Despawn, select the 14 and you're good to go. I've gotten into the habit of doing this if I see even just 1 player on the carrier deck when I want to spawn. As mentioned, this problem is more consistently reproduced with the SC. The Forrestal/Free Stennis suffer from this, but not nearly at the same rate as the SC (shocker). 

    • Like 1
  9. Yes, unfortunately the long forgotten and abandoned SC is still quite buggy. 

    You've run into one of the more annoying ones, that when there are more than 4xAI 'active' on the deck it is likely that they will not take off and get stuck at some point prior to launch. The easiest way to get around it, is to space out their spawn time. I've found that 2-3 minutes per flight of 4 works out best. Alternatively you can start some already 'hot' on the catapults when the mission starts, and others to spawn in cold. 

    • Like 2
  10. 4 hours ago, QuiGon said:

    It really depends on the type of SAM. Against the SA-5 the jammer can reduce the launch range from ~63nm to ~18nm (flying at 30.000 ft at 350 kts)! That's a huge difference!

    Interesting. Has that been tweaked recently? I haven't experienced that kind of reduction in range. I'll have to test it out later, thanks!

  11. From experience the jammer does not have a huge impact on SAMs, especially modern ones where their WEZ is smaller than burn through distance (~29nm). It might buy you several seconds from like an SA-10 max range, but that's it.

    Where IMO it shines - in its current state (correct or not) is in A2A BVR engagements. The jammer will prevent long range TWS shots - which is nice especially if you are against a non-jamming target. If the parameters are good for a long range 54 shot (both very high, with high closure - to maintain track) you can shoot and hit your target before you reach burn through. Additionally you can STT lock a jamming target, and manually loft your 54 - since it will not loft on it's own on a jamming target. All of this is also possible with the 54A, with the C it's easier since it's not reliant on keeping track until missile gets the go active command from the radar. 

×
×
  • Create New...