Comstedt86

AMD released new preview drivers with Frame Generation (AMD Fluid Motion Frames) yesterday. Compatable with 6000 Series as well now.

No it doesn't, whatever you enabled was not FSR2 or FSR3. But would you mind sharing what you enabled?

Anyone with Radeon 7000s Series tried the driver level frame gen?

Bought a 6800XT about a year ago and I'm happy with it :). Used morepowertool to undervolt.

Framegen should be available in latest Catalyst on driver level per game (not FSR3FG) Anyone tried it ? I don't own a 7000 series card unfortunately so can't try it out.

With the A, the few times I've seen it go active despite lost track was when it was only 1-2 seconds tops from going active anyway.

Lock specific target works very well I find, even vs D/L targets. Usually Jester complains concerning locks are attributed to the limitations of the AWG-9. Best bet would be to learn the RIO seat and AWG-9, dropping in the seat quickly when you need to do anything specific Jester can't do or can't do quickly enough.

Tried GS server yesterday evening briefly. No issues with Jester. 7 kille (5 with the 54 all in TWS mode) and died once to a sneakt Gazelle with Mistrals.

As stated previously, AI defends at 10nm irregardless of when any missile goes active. If it will be changed or not defends on ED.

I did some testing with the C variant some weeks ago, judging by map measuring when TID starts flashing and the behaviour of the missile TGT size switch seems to work again.

Use it in what manner? Any STT lock the TCS should be slaved on the target. Flip VDI switch to TV and you should be ok.

I can hide it with keybinding

Judging by some PvP observations it seems to work but I haven't tried it in a more controlled environment.

Did some testing down low with TWS and the C versions. Indeed tgt size switch functionality seems to be in game again. TWS shots with both C versions. Measured when TID TTI starts flashing from Phoenix to targets. Small - Approx. 5,5 nm from target. Large - Approx 12,5 nm from target. Didn't bother testing normal. 0,5 nm "error" is most likely a combination of delay me pausing and the TTI doing a full "blinking" cycle.

Added half a year ago or so

Welcome. What exactly do you mean with block?

In TWS doesn't the T point to centroid of the TWS "focus" point or do I have that mixed up.

Dedicated thread here has som info.

Thank you !

Does this trigger RWR like normal STTs? Can the lock be broken once the missile is in air and will it continue to home onto jamming source ? (No RWR warning anymore?) In the case of the 54C, will it go active instead if the jamming source is killed or shut off?

Yes. TGT size switch only affects the A models as of now (DCS limitation)

I believe you can hook the target, press Next Launch button and fire a 2nd Phoenix. Not sure what happens with the first one in the air however.

PH ACT launches the Phoenix active of the rail without any midcourse guidance and should not be used if you want to fire a TWS shot. The missile speed gate does not do anything in DCS iirc. A screenshot if the TID before and after launch might help.

Have you read through this thread? Or at least check JNelsons answer, 9 posts up.

HoJ possibly?