-Painter-

I do not have any VR controller - just using the mouse and keyboard (and flight controls of course). Would be nice to be able to use your software with that very minimal hardware setup as well though.

Is it possible to use this without any additional hardware? Like with PC mouse and keyboard only?

Just a quick request at ED as the title says: Please focus your manpower and obviously limited time on bug-fixing instead of implementing new features (& bugs regarding that new features) or even new modules. It is really kinda sad to see that some important bugs are not getting fixed for ages, while new stuff is being worked on (e.g. https://forums.eagle.ru/showthread.php?t=225295&page=4 ). Some of these bugs are really annoying and getting you killed when fighting bandits. Seeing the F-16 in the pipeline I really hope that such workflow will be avoided in favor of a much more quality model than the Hornet with all its bugs we are facing from day one. Comparing the F-18 from ED with the F-14 from Heatblur I have to say that Heatblur delivered a lot more quality and is a lot faster in fixing bugs (if there are any at all). In short: ED, please shift focus from quantity to a lot more quality. Thanks.

Would be great if it would be possible to tell Jester to switch the MLC (MainLobeClutter filter) out (and if out: Auto).

Jester is too slow to IFF the contacts. Yesterday on a busy MP server (Blueflag PG) the airspace in the AO was really busy with like 10+ aircraft. I came from 120 NM away. Problem: I had contacts and Jester did IFF them like 60 NM away. To get a good result of my shots I aimed for a launch distance of around 40-20 NM. But when I came closer like 50 NM targets dropped and popped up again due to Alt changes, filters etc. Result was, that I had only not IFFd contacts within 40 NM and that did not change until I ended up merged. I wasn't able to fire, since I was not sure who is Friend or Foe. Finally I died from a Hornet at 2 NM abeam. At the same time Jester IFFd contacts and called them out to me 60-80 NM away. Would be great if: - Jester would be much faster regarding IFF in general (sometimes he isn't doing that task for ages, then all of a sudden he IFFs 10 contacts within 5 seconds). - Jester would prioritize to IFF the closest contacts on top of all other tasks (except tasks that are given to him by the pilot via menu - e.g. "go nose cold" or "select A2G station 2,7").

+1 It appears SAMs are not engaging TALDs if SAMs are not set to "engage weapons" in the ME. But SAMs should go for TALDs regardless of the setting of that option since the TALDs are not really a "weapon" but made to look like an aircraft on the radar.

+1

Got it right now again after I got hit and lost both engines on the BF:PG server. Re-slotted into a new plane after that event - right engine not spooling (left engine starts fine, cross bleed air doesn't help for the right).

Blueflag - complete session with human RIO - a certain amount of PAL locks - no CTDs for pilot & RIO

Make sure Attitude Hold autopilot is off (most right autopilot mode on the left side panel). If it is on, you won't be able to apply pitch trim since the autopilot is doing that.

Scratch all my thoughts - I missed an important part in the manual (see pic):

@lunaticfrinch & @WindyTX: I am all with you. My discussion with Spiceman is all based on that exactly same base. The problem of a shot with the Aim-154 is, that it is not active at all and never becomes active when I shoot it out of a PD-STT lock if I understand the manual correctly: " PD STT SARH In pulse doppler STT the AIM-54 uses SARH all the way to the target receiving guidance commands at a greater rate than in TWS and also continous spotlighting of the target because of the STT mode being used. This increases the effective range of the AIM-54 seeker slightly." That is why I would prefer to fire it from TWS, because then it will become an active Fox-3 when commanded active. After a PD-STT-shot it will never ever hit the target because I have to turn defensive at some point when I am facing a bandit that has Fox-3s too. As soon as I turn away my radar doesn't illuminate him anymore, my missile doen't go active (because shot out of PD-STT) and is trashed.

My problem with that tactic is: - bandit head-on, has Fox-3s - if I launch PD-STT I need to guide the missile and keep my radar painting him all the time until impact - if I turn cold, because I fires a Fox-3 at me as well, my missile is trashed - if I launch in TWS I have a good chance to guide the missile until it becomes active and being still able to turn cold to avoid his Fox-3, still having a good chance my now active missile will get him

Thx a lot! Didnt know you can do that with Jester. Additional question: From my understanding the 154 acts like a Fox-1 until impact and dors not get an "go-active" command at all. But you still think it is the better choice than a TWS launch, correct? Or would you select PD-ACTive in the WCS panel? (given everything is implemented and the missile acts as IRL)

"wing will STT the trailer at 30 NM using Jester". How? P-STT or PD-STT? Isn't PD-STT as likely to get notched as TWS? If so - what's the reason to use it at all in favor of TWS? How do you get Jester to STT exactly that target (trailer) instead of the primary thread (lead)? Do you really get an STT lock at 30 NM with Jester? From my experience he is completely unable to STT all the time until I am inside 20 NM.

No - had it today after a fresh DCS launch, first sortie, first engagement, Blueflag:PG - bandit over Abu Musa within 20 NM - PAL - lock - CTD. Wingman got a CTD a few minutes later in the same AO.

Spiceman, thank you for your awesome videos! Very appreciated and we use them in our squads "classroom" ;) . A few questions: 1. STT ranges At what ranges should it be possible to get a STT lock on the bandit a) in PD b) in P mode? 2. STT advantages/ disadvantages - when to use STT? What is a good practice to lock the bandit in STT (and which STT)? I am sure there are all kinds of different situations and you have to use the radar in different ways. What I am interested in is a general rule of thumb roughly. Especially for 2 or 3 typical situations: a) single bandit b) mutiship bandit flight c) furball with bandits and friendlies in the mix My thoughts about it are: - I usually try to avoid STT to maintain a good situational awareness picture and track of "all" what's going on in the airspace. - When flying with Jester and I tell him to STT the bandit ahead he usually answeres with "unable" when the bandit is further out than 20 NM. Is that correct? Even in PD-STT? - What triggers bandits RWR "spike" ? My idea to stay in TWS only is on top of the above, that I wanna avoid that the bandit is becoming super-aware of me. Maybe he is not sure where I am or how far out I am and keeps tracking towards me. But as soon he is getting "spiked" he will usually turn cold or into the notch at least - which is not always what I want him to do because I want to come closer first maybe. 3. Launch range Phoenix Given a bandit head-on mid-to low altitude: At what range would you fire the Phoenix at him (rule of thumb)? I understand you in the video that you usually would fire much further out than 20 NM because you don't wanna have the Phoenixes on the plane still when you are getting within that range. 4. How to after the Phoenix-launch As a rule of thumb, what would you do usually after the Phoenix launch? My usual procedure currently is: - Launch the Phoenix at around 25 NM - Support the missile with the acft. radar until the bandit is as close as like 15 NM - Split S and run away from his Aim-120C he most likely fired at me at this point Thank you in advance!

Hearing about the CTDs a lot on Blueflag:Persian Gulf. I have it very rare myself. A guy in our squad does have it like every day when he flies the cat - he flies the aircraft a bit more agressive than I do. On Blueflag it seems like if you have 5 people flying the cat, some with RIO, some with Jester, 1 out of 5 will see a CTD.

Aircraft was damaged - landed with no gear on the belly successfully - repair started, aircraft going up - repair finished -> aircraft drops down onto the apron with no gear still (handle was in the down position all the time) - damaged aircraft again because it dropped onto the apron with no gear

CTD - PLM mode not used, 3 contacts in front, all of a sudden CTD - Blueflag Persian Gulf

+1

@Eldur Geforce or NVIDIA driver site - you can click on Archiv.

+1

+1 In general it looks kinda smooth, but stutters during head-movements as if the tracking would be disturbed for a split-second constantly during head-movements. NVIDIA driver 430.86

+1 My RIO reported the same to me today after the 2.5.5 update.