Hardcard

@Ferchu1976 The viper's radar takes its sweet time to build tracks, also, TMS right doesn't always do what it's supposed to. I've found that reducing the azimuth setting to 1 (narrow search) speeds up the process. Also, if you're having trouble building tracks in TWS, switch to RWS first, then back to TWS when you have a track.

The problem is that he often fails to get a lock on targets that are beyond visual range too. I do GCI regularly in MP and I've lost count of how many times Jester has gotten my tomcat teammates in real trouble (often killed). The following is a rather common chain of events in MP: The tomcat carries fat phoenixes and a powerful radar for a reason... if it can't consistently get locks and fire beyond 20nm (the very things it was designed to do, which enemy fighters are able to do), it becomes kind of useless.

201 doesn't seem to work for Roland ADS.

This has also happened to another user today, so I can confirm it's not just a strange bug on my end. We were both playing Blueflag Persian Gulf server, he got a CTD when guiding the walleye during the very final stage, right before it hit.

That's terrible news, then. Sounds like you need a team of MP testers. If I were you, I'd ask the community for volunteers, I'm sure many would answer the call (I can ask people who regularly fly tomcat in MP). I would gladly perform tests and gather data for you, but I don't own the tomcat module (since I won't pay such a high price for a module that doesn't work as it's supposed to in MP)

Report this in the bug section and provide a track. I've also experienced these problems, but my tracks are corrupted

Last week I got killed by one of these viggen meme mavs... it was fun, tbh, but I agree that this ridiculous exploit needs to be fixed.

@reece146 How many times do I have to tell you guys to include the mission file and dcs.log in your reports? :cry: Yes, like you said, SWAPR isn't meant to support people's mods (unless the modder has managed to make the mod assets work just like DCS assets). That said, I can still look into it and see whether the problem is easy to fix (or fixable at all).

Multiplayer, Blueflag PG server. I replaced my A/G loadout (including Datalink pod + walleyes) for A/A loadout (amraams, sidewinders and fuel tank). Note that I did this using custom loadout profiles created by myself in ME (and then modifying them a bit in the rearming interface). After spending my amraams (most of which didn't track... but that's an issue for a separate thread) and dropping the fuel tank, my stores page looked like this (no DL pod equipped, as you can see): Yet the DL Pod feed (static) showed up on the left DDI every time I left A/A mode (when switching to either A/G or no master mode): I don't think the dcs.log will provide any answers, but here it is anyway: https://drive.google.com/file/d/11P7zyxxYIQX-ebfldqZ-xbb0NeTN03j9/view?usp=sharing Track is corrupted, so I don't see any point in providing it.

Blueflag PG, join blue team. They desperately need viggen pilots to deal with red ships.

It has happened to me twice already. I get an access violation and CTD when guiding walleyes right before they hit. dcs.log

Jester consistently fails to get locks on nose bandits (precisely called by AWACS / GCI), he also has a tendency to switch between TWS modes before phoenixes go pitbull (causing them to go dumb), etc. As a consequence, tomcats have become virtually useless without a RIO... Jester / TWS need urgent fixing. Also, please implement a TWS menu for Jester, so pilot can command it to switch between tracks (and can also prevent him from doing stupid stuff on his own)

Will probably need to rinse and repeat many times, since GBU-31s and GBU-38s are quite inaccurate in windy missions. @Nuggit Walleyes don't get intercepted, can be dropped from 25+nm (provided you fly high and fast), can be remotely guided on the way down using the DL pod and pack a pretty powerful punch. However, if you're dealing with SA-10 sites, you'll need to fly low instead.

Sure, all those things you mentioned SHOULD ideally be like that... but in practice they aren't. Good luck performing a "by the book" engagement in a server where bandits pop in and out of scope and half of the friendlies aren't even on comms. Also, TWS autolocking known friendlies is simply unacceptable, no matter how people try to spin it. I'm not talking about furballs, I'm talking about TWS autolocking friendlies almost outside of radar cone, when the bandits are on the opposite side of the cone (or right ahead)... it's ridiculous and any systems engineer worth his/her salt would take steps to prevent such behaviour. Anyway, I always check before shooting, so it's not me you should be worried about... it's the many other players who aren't nearly as cautious... Sure, it's on them, but their amraams will be coming for you nonetheless... wouldn't you rather have a system where TWS didn't autolock? I totally would.

TWS autolock is a pretty bad idea for several reasons: - Increases the chance of blue on blue Imagine that you have an enemy contact ahead, as well as some friendlies around (within radar cone). Those friendly contacts are provided by AWACS, you don't IFF because you already know they're friendlies (you also have comms confirmation or whatever) and also because that bandit is about to fox, so there's no time to lose. But just when you're about to fox, bandit fades and TWS autolocks one of the friendlies that you didn't IFF (because there was no need to)... by the time you realize what's going on, it's too late. - Tends to autolock bandits you're not interested in - It's annoying af

Hornet is surprisingly lightweight, 1GB should be enough (liveries are the heaviest part, tbh)

In my case, I was also unable to connect when flying the hornet... until I decided to try something that has always worked for me with other planes: Set Y and X stick curves to 40+ and reduce deadzone. After doing this, I was able to make the fine adjustments required to connect (and stay connected) to the basket. As for speed, I use the hornet's Auto Throttle Control. It's not as good as the Su-33's, since it can't be tweaked, but it's better than nothing :D

Por si acaso, podrías exportar tus llaves de registro de LockOn / FC en un archivo reg. Ya no me acuerdo de la ruta exacta de las llaves de registro para LockOn / FC, tendrás que buscar en viejos posts para encontrar referencias. Una vez hecho eso, instala FC en el nuevo ordenador y usa las llaves de registro que has exportado del viejo ordenador. Si esto falla, siempre puedes abrir ticket de soporte, a ver que te dice ED: https://www.digitalcombatsimulator.com/en/support/faq/1115/ No hace falta que te diga que FC es prehistórico y que no tiene demasiado sentido que sigas usándolo teniendo DCS World y FC3. Saludos y suerte.

@draconus Nope, I had told Jester to search 100nm. Regardless, TWS Auto decided to start with a contact at 170+ nm that I couldn't even see on HSD, since the scale was set to 100nm. This happened in the worst possible moment, ofc, when I finally had the enemy AWACS within 50nm (right ahead) and my launch window was closing (due to SA-10 in the area)... gotta love Jester ;) As for the bogeys ahead, brackets were on top, so they were definitely radar contacts, not DL contacts. (I watched the TacView track afterwards, those were a couple of vipers and a jeff, like I said in my previous comment). @solidGad I think he understood just fine, but he seemed more interested in patronizing me than in investigating the issue. It's ok, no hard feelings.

I've encountered a different problem today... gbu-12s just wouldn't release (whether in CCIP or Auto, didn't make a difference). Master arm was on, efuze inst, mfuze off, correct laser code, target designated with TPOD... freaking bombs just wouldn't drop. I tried it with trigger, with weapon release buttons (even holding them for a few seconds)...nada Does the mfuze need to be set now? I'm pulling my hair, trying to figure out what I missed... laser mavs worked just fine... This has happened to other people in the server I was playing... is this a new bug or something?

@majapahit Those lock drop problems you're describing sound like you're using 2 bars instead of 4 bars. Alternatively, could it be that you're using interleaved PRF setting instead of high? (Every time it switches to "Med", you lose lock) I don't know, I haven't experienced such issues in MP for a while now (except for the radar auto locking contacts, which might be normal behaviour? I ignore it, tbh.)

Reset the TPOD (set switch to off and then back to on).

I mean... any hornet pilot who does that deserves to be splashed :lol: That's why I prefer to face them in the F-15C, it brings balance to the force :D (at least speed wise) Thanks for running the tests and putting the numbers together! :thumbup: Beats fulcrum, flanker and mirage hands down, if you ask me. Awesome datalink / SA page + proper TWS + amraams > No DL / Barebones DL + Barebones TWS requiring STT lock + Fox1s / Inferior fox3s Sure, hornet is inferior when compared to tomcat (like the rest, let's be honest), JF-17 (only because SD10 is superior to amraam atm), eagle and viper (in terms of speed only) As for the "atrocious lock behaviour", I don't know what you mean, exactly. Hornet's radar does require some extra steps to get going, but once it's set, it's quite effective. Sure, it needs to be set to "Auto" in order to retain locks as you move around and it'll bug contacts automatically (often friendlies), just need to get used to it.

There's something funny going on with JDAMs. Sometimes they overshoot, other times they fall short (even when firing within zone) and other times they simply fail to destroy the target (despite the fuze being set to INST and the 400+kg of high explosive, in the case of GBU-31).

I'd check the airbase object description (or the database), perhaps the length of the runway(s) is listed there. Like pmiceli said, if runway length is displayed in the F10 map, it means it's stored somewhere... just need to figure out where and whether it's accessible via scripting.