Kula66

I had a 1080ti and Rift S and got good (not great) performance with DCS settings set fairly high, around 40FPS - happy simmer. I then bought an HP Reverb G1, but my 1080ti just didn't have the grunt to run it. So, I waited until the new nvidia cards cam out and got a 3090. Installed the card and the Rift S is super smooth at high settings and on the Syria map - 40FPS, but very smooth. Now, plug in the HP Reverb and the view goes to hell ... when you roll the 14 at 15k', the ground just turns into a stuttery/teary mess. In fpsVR says the card is running at 60-70% as is the CPU - the odd red spike, but mainly steady orange. I've tried turning settings down in WMR and SteamVR (70%) and it makes no difference. I've deleted shaders, Nvidia control panel is set to default. Latest drivers. etc. Is there something I'm missing??

Sorry, I only just spotted this ... this is odd because I get this: The left-clicked plane is always centered, so half the screen is 'wasted'.

My experience is that TWS-A works most of the time with Jester in 1v4 SP or 6v6 MP, so: RWS, point the jet to centre the target and then TWS-A ... you can then crank reliably up to 50degs and keep supporting the missile. I've seen 80 mile range Mk60s v F-16 hit using this in MP and in SP reliably 1v4 F-16s and getting 3 or 4 hits. I have had issues with Jester, usually the one where I can no longer switch TWS/RWS/PAL or anything else ... and sometimes, it just cures itself and sometimes I get shot down struggling with Jester. The other option is to STT.

I fly Jester only in the 14, and have done since it launched and so IMHO: In bfm ignore him, he is usually a few seconds late in calls and in a fast moving df he is always wrong. You have to fly level for a few seconds for his tally calls to be valid. In AAR switch him off! he is really distracting. In BVR, he is hard work and some people find major issues. I find him ok in SP with a couple of minor limitations: * He calls out missiles all over the place if there are multiple bandits flying which is very distracting. Again, best ignored. * Working the radar up and down is hard work, the Jester wheel is too clumsy and there isn't really time - this is my major issue. However, in close and at long range the 14s radar is superb - 30+ and <15 (PAL). Big scan volume good long range detection. Trouble is its between 15 and 25 that things get deadly! * He is very good at IFF'ing things quickly. * He locks and highlights tracks in an odd order sometimes (usually) - so he'll focus on the farthest bandit rather than the nearest threat - annoying. * Things like switching range and RWS/TWS all has to be done manually ... not ideal but doable with a good HOTAS. * I see some people jump between back and front seats ... amazing, I'm not smart enough! * I don't think he's good enough for busy MP servers, but you said SP. * Some of his phrases are annoying 'the sink rate's too high' ... so? I find him ok and miss the chatter from the back seat in a single seater :) Hope this helps, James

Really sorry to hear you have so many issues with BVR in the 14. For what its worth, I get very different results. I've flown a lot in SP (1v2/4) and a fair amount in MP, including a round in a comp, all with Jester and the only time I've seen the issue is on busy MP servers, ie. the TID is showing many contacts and was unusable anyway. In a 2v2, 4v4 or 6v6 fight, of which I've flown dozens over the last months, BVR has worked while using TWS-A and even with multi-shot engagements. Jester has his issues (odd TWS target order and no easy way to say radar up a bit or down a bit being the biggest issues for me), but generally he works as expected and I've not seen the TWS->RWS switch and keyboard bashing in these fights. I would post some tracks, but mine never replay correctly, usually appearing to crash while taxiing! Although there is this YT: of a couple of shots missing for other reasons, not Jester.

How patronising. I did indeed ... and in the hope it was an option and doesn't become a mandatory step, I voiced my personal opinion. Not everyone agrees.

-1 ... not for me thanks. My flying time is limited enough already.

Low in the mountains, go PAL and switch your 54s to ACM mode :)

AI Ace level targets seem to fly perfect notches every time ... Veteran's seem more believable/killable :)

Thanks BuzyBee ... I think that's the mode I normally use and it centres me, but the other a/c is off to the side. I've tried various options under that dropdown. I was looking to use this primarily on BVR replays and I'd ideally like the green line between the 2 a/c centred so I was about a 1/4 of a screen from the left and the other a/c was a 1/4 screen from the right edge - hope that makes sense!

'They' are not 'all' in agreement, there have been a number of sited examples in books and videos, where experienced pilots admit to have done it. You seem very quick to dismiss them as not valid. Perhaps you can add a trigger condition or LUA script option that explodes you if you exceed x G?? Not something I'll be using it, but hey, each to their own. Enjoy.

Yes I deliberately didn't post on that threat ... it was already a train wreck! With the greatest respect to our SMEs, how many of them have been involved in a gunzo fight against a 4th gen a/c, where one person is going to die? Not many ... may be in that situation, they'd pull the wings off!

It depends. If that bandit is carrying an AAM and about to pop your AWACS or Air Force 1 or your wingman or ... yes, absolutely. Pilots did it in training!

Back in the old LockOn days, I must have shot down the entire USAF KC-135 fleet in my 15 in frustration! Now, being older and wiser, I just curse them loudly.

Cheers ... I had the tanker up high so I could find it easily ... I know, not really necessary because of TACAN & radar, so I'll try it 10-20 and see how it compares. Issue doesn't happen at 28k'.

At the moment I can center one a/c. Is it possible to have a Tacview option to centre the highlighted pair please? I'd like to left-click one a/c, then right-click a second a/c, and have the green line centered in the view. So, the mid point of the green line is centered. Possible?? Thanks.

In the 14s case, the NATOPs limits were about reducing maintenance hours/prolonging the life of the airframe, not what the airframe could sensibly do - this is a game and I don't care if my maintainer gets cross! How about a 500' bubble during BFM? How about no face shots? Because that didn't go so well for the 'real' pilot in recent AI test flights - one side played fair, the other won! Whats next, we have to say 'trigger down' rather than actually shoot someone down? Because that's what real pilots do in training!

Ahhh ... thanks!

Not something I’ve come across and I df quite a lot. I use VSL high and PAL (although not plm) ALOT!

‘Sth’ ... not sure what that means. Lowing alt definitely helped!

Any update on a fix or progress for this. I never really saw this in SP, but now flying more MP and it’s still a big issue ... jester goes click mad and ignores all radar control from the front seat. Really frustrating.

240 @34K'? Hmm, that seems slow ... I'l' have to do some experimenting. Thanks.

I think it just me getting too slow ... I lowered the KC down to 28k' and had no trouble and stayed over 300kts.

Thanks guys. Beta - yes, and its on a 135, left station, wings in bomb mode ... Very simple take-off, climb and tank. I'll post the mission later. Its not a problem with hooking-up, its a sudden change in pitch trim after a while connected. So normally when I AAR, I have to add a little trim in as the weight increases, this is a sudden nose drop. I'll have to try creating a new mission - maybe its a speed/weight thing, I did notice I was pretty slow. F-14b-GroundToAAR-Syria.miz

I can AAR in the 14 ok, but recently I fall off the basket after a couple of mins connected, like a sudden change in trim or trim reset. So one second happy with min stick inputs, the next I'm dropping and then into PIO. I've tried AARs with Jester disabled, and it still happens ... I'm sure this didn't happen a couple of months ago - any changes that may cause this? Or is it me? Anyone else seeing this??