Jump to content

Hardcard

Members
  • Posts

    1080
  • Joined

  • Last visited

Everything posted by Hardcard

  1. @IronMike Just to be clear, the main reason I'm asking for more micromanagement is because Jester, as it is now, needs babysitting. I'd love to be able to just focus on piloting, knowing that I have a competent AI RIO who seldom lets me down (or gets me killed), but this is not the case with Jester atm. I'm all for Jester being more competent, so if that's what you guys at HB are aiming for, by all means, go for it. Here's a list of urgent stuff Jester needs to learn, imho: - Sort bandits using common sense (ask the pilot to pick the targets if needed). For example, if there's a hot bandit right ahead, close, and another one way in the back and to the side, don't ever prioritize the latter until the former is sorted. Another example, if you have two bandits at the same distance and bearing, but one is low and beaming / cold and the other is high and hot, prioritize the latter (or at least ask the pilot to choose) - Use narrower sweeps when the bandit's BRA is known. For instance, keeping the 40º + 8 bar setting in RWS when we already have BRA / DL contact (given by AWACS, GCI, etc.) is dumb and sometimes results in Jester not being able to find the bandit in time (TWS isn't an option when bandits are notching or just out of PAL range) - Disable the MLC filter when the bandit notches and tell the pilot to drop below the bandit accordingly. In the server I normally play, notching is a given, we can't afford Jester not knowing how to deal with notching bandits - Change the aspect settings (nose, beam, tail) as bandits maneuver - IFF properly and don't miss any IFF calls - Use Pulse / Pulse Doppler search modes when we know there's a bandit ahead but we can't pick it up in RWS or TWS I'm pretty sure I've missed some other stuff that has made me wish to pull a Goose on Jester sometimes As for the "why don't you do RIO if you want it so badly" attitude, the short answer is that I can't do RIO 99% of the time, so that's definitely not a solution.
  2. There are no players willing to do RIO 99% of the time, I can't join the RIO seat without a human pilot either, so I'm stuck with Jester whether I like it or not. This isn't something I choose, it's simply how things are.
  3. In a sim where the rest of modern fighters allow players to properly control radar elevation , azimuth scan + bars, primary target, IFF, etc., tomcat shouldn't be any less (when flying without a human RIO). Those controls exist in the RIO seat, we should be able to tell Jester to do essential stuff like setting the desired azimuth scan + bars, cycle TWS targets, perform IFF interrogations, etc. Jester AI will never be as good as a human RIO, so the easiest and less painful thing Heatblur could do is to provide the required RIO bindings to pilots, so they can micromanage radar functionality (just like they do in their hornets, vipers, jeffs, etc.). Unrealistic? Idk, seems like pilots should be able to tell RIOs what they need, specially when they're messing up, besides, aren't we tired of Jester issues and the threads they generate? I'm pretty sure Jester is a pita to develop, seems like an unnecessary torture for devs and players alike. Making all relevant RIO bindings available to pilots seems like the path of least resistance to solve the most glaring Jester problems. As for deciding which RIO bindings should be made available to pilots, the rule of thumb I'd propose is the following: "If hornet pilots can control this, tomcat pilots should too" (of course, always within AWG-9 limitations, tomcat pilots shouldn't be able to do stuff that RIOs and the AW-9 can't do)
  4. @thornx I think this issue is already reported internally (it also affects FC3 aircraft, not just the tomcat). Check this thread
  5. Bug: AWACS "Declare" option missing Can I reproduce it 100%: yes How to reproduce/ description: -Step1: Get an STT lock -Step2: Access AWACS comms menu -Result: "Declare" option is missing (no AWACS IFF available, so we have to rely on Jester for IFF... ) DCS Version: OpenBeta 2.7.8.16140
  6. Could we just have ALL Jester wheel commands added to the bindings list (under Jester AI)? Jester wheel changing dynamically is kind of a nightmare for voice command users like myself. Also, I second everything @mattag08 said above.
  7. @Beirut If you can't figure it out, try VoiceMacro, it's free, it has no profile / macro limit and it works quite well (as long as your mic is configured properly and you make command tests before alt tabbing back to DCS) Here's the tomcat B profile I'm currently using (40 commands so far), you can import it: Tomcat B.xml PS: You'll need to modify some of the commands in that profile, since they rely on custom bindings I made (under Jester AI). Also, the six communication commands at the bottom of the list use the "ç" key ( OEM_2 (? /) ), which your keyboard might not have... they're pretty specific to the server I usually fly in, so you can just ignore / delete them.
  8. @Home Fries Are all commands in the Jester wheel included in that plugin? I'm using VoiceMacro here and I'm pretty happy with it, the only real problem I'm encountering is what you mentioned about the dynamic Jester wheel, which changes depending of whether your radar is on / off, whether you have an STT lock, etc. I was about to start a thread asking HB to duplicate ALL Jester wheel commands in the bindings list (under Jester AI), so we can set all macros independently of the damned wheel.
  9. Now, after the last patch, it's the opposite situation again: F-15C (without bags) struggles to reach the mach 2+ speeds at altitude that it's known for. You can consider yourself lucky if you reach mach 1.7, almost feels like accelerating a hornet, tbh. It's either too much drag or too little... we don't seem to get it right
  10. @HoldmyBeer @Jimi08 Please, read previous posts and attach the required files @Jimi08 IIRC, there are cosmetic differences between static and AI replacements, but, beyond that, I don't think there's anything I can do about it, script wise.
  11. @TrikeFighter Your dcs.log is still showing DCS/2.7.7.14727, this isn't the latest OB. If you were using the latest OB, it would be showing DCS/2.7.7.15038, like it does in my case. I'd force a manual update by running the command DCS_updater.exe update I'd also make a backup of important stuff in my DCS.openbeta Saved Games folder (like mappings, missions, liveries, loadouts, etc.), then delete it and let DCS create a new one.
  12. Well, I'm delighted to say that, during this last week, I've been able to do GCI / F10 map stuff for several hours without ever losing my icons. It really looks like the issue has been fixed and I couldn't be happier about it Thanks to @JayRoc for reporting the issue, to @Flappie and @[ED]Obi for looking into it and to @Tholozor for finding the key.
  13. @Flappie Much appreciated, mate Btw, I wasn't sure about the F-5, but I'm pretty sure about the tomcat, since a teammate who flew tomcat got hit by the Moskva without warning in a MP session as well.
  14. @Tippis Moskva and Piotr Velikiy don't give any kind of radar warning, not even in the terminal SARH phase. Also, hornet gets warning (I haven't tried with the viper yet), just like all DCS aircraft with RWR have always done. Also, it makes no sense that all ships equipped with anti-air missiles in DCS give warning to the affected aircraft, except for these four (Kuznetsov 2017 gives warning, while old Kuznetsov doesn't) It all points to a bug.
  15. @Flappie Thanks for looking into it I've performed testing with F-15C and pretty much all ships with anti-air capability. The following ships don't give me warning: - Moskva - Piotr Velikiy - Kuznetsov old (the new model gives warning, though) - Neustrashimy
  16. @Flappie Well, you're a luckier man than me and other players who are experiencing the same issue with F-15C, F-5 and tomcat (hornet seems to get the warning just fine). Here's proof that I'm not making it up : https://streamable.com/v3t3wf I've also attached the test mission I'm using. It doesn't seem to be coalition related, since changing the coalitions of both Moskva and Eagle makes no difference. I don't know what's going on, but it's affecting a bunch of players, not just me. Btw, I've also tested with the Pyotr Velikiy and get no warning either, so it's not just limited to the Moskva. F-15C Moskva test.miz PS: Using the latest OB, btw. DCS 2.7.7.15038 Open Beta - 28.10.2021 Also, I'm using a cockpit texture mod for the eagle, but it's not related to the issue (problem appears with the default cockpit as well) I'll perform further testing with all kinds of ships, see the results I get.
  17. Slava class cruiser (Moskva) doesn't give missile warning to F-15C (I think F-5, tomcat and other modules are also affected by this issue) Other ships might have the same issue, haven't had the chance to test it yet.
  18. This thread has several posts by people who jumped the gun after AMD and DCS OB releases, getting it wrong each time. I'll give it a week of proper testing, then we can draw conclusions. So far so good on my end, we'll see if it holds.
  19. 30 minutes of testing is not nearly enough to determine whether the bug has actually been fixed. We'll need to conduct tests during entire BF sessions in order to be sure. I'll start tomorrow.
  20. I can also reproduce the issue by setting polygon thickness to 1 (or changing it to any other value after restarting DCS and reopening the mission). Nice catch, @Tholozor
  21. @Flappie Nice to know Could someone tag the thread as "investigating", though?
  22. 6 months later, the issue is still around and this thread isn't even tagged... is it funny or sad?
  23. I didn't ask the Nvidia user to provide a log because it's not my job... but apparently I'll have to end up doing it anyway. Here's the thread (same issue, loss of UI icons / buttons across the board): The user is @G.J.S Like you, I also suspected the issue was AMD related, but then he replied that he was also experiencing the issue with an Nvidia card, so that put 2.7 back at the front of the suspect list. Anyway, blaming it on AMD won't solve anything, since AMD employees will say that everything worked fine before DCS OB 2.7 (and they'll be right about that), returning the ball to ED's side of the court.
  24. Nvidia card users have reported this issue as well, the "blame it on AMD" card can't be played here. This is clearly a 2.7 issue.
×
×
  • Create New...