It should have priority track which could be implemented by C&P AESA code and tweaking it slightly. At the moment it takes about 4+ seconds to update a targets location, with p-track the target and 5 other contacts would be updated every 2 seconds.
It could also have interleaved PRF that would fix its massive deadzones.
PIRATE should also have a 200 target TWS mode that could be overlayed with the radar.
The radar is also missing GMTI which be useful for GRB
It may not be an escan but it’s not that off either
And of course, If none of that can be added. The typhoon has both CEASER or CAPTOR-E as AESA options
From what I understood. Tws+ was about updating the algorithm used for the intertial track.
But p-track would actually update the contact track, including contacts outside the TWS scan area. This also means that partial scans at the edge of the radars fov should still be seen properly
TWS+ makes it so that all targets are refreshed after the scan pattern finishes, but this made it so that they don’t refresh when the radar beam passes them.
This causes the locks to drift or to just break in tws
The TWS change made it so that we still have the same problem as before:
Some targets aren’t getting refreshed fast enough depending on where they are in the scan pattern
Has anyone on the dev server had the chance to test out the new frame generation features, and kf so, how do they work? Is there obvious visual lag? Is image quality affected?
you can try it out yourself, fsr isnt locked to a particular amd card.
anyways there will be some ghosting but thats pretty much all i noticed with ui elements
this mode should probably decouple the mouse from your aimpoint for vehicles that rely on actually turning their turrets. without doing this the aim point will drift as the targets move
I don’t have the dev server, I’m too busy currently to justify taking the time to explore it myself. Hence why I’m wondering if others have tried it out and can share their experiences.
I definelty need to give it a proper go when it hits live. DX12 kills my frame rate for some reason. So I am hoping that Frame gen might allow it to run a lot mroe smoothly
It’s not necessarily the gunner though. It can also loft and use data-link from another source (often an Orion drone), to do all the terminal guidance.
More importantly, it’s the same class of missiles we’re all talking about anyways.
Possible, that or a drone, like I mentioned above.
Yk, I’m kinda disappointed with the British three-tank pack, on the surface it appears to be themed around Operation Overlord and the D-Day landings, but is largely not good picks imo.
Firstly you have the A30 Avenger, a largely post war development (in fact the project was canned in 1950), a bit weird historically no? (for those that don’t know Avenger was an improvement programme for A30 Challenger, new turret and rolling in improvements on the Cromwell chassis that where fitted to the Comet).
Then you have the Firefly just isn’t a great pick for newbies, it’s got bad gun depression and isn’t the most nimble or stable, nor does it have great armour.
The SPAA is fine I guess, but the Crusader AA mk.2 isn’t anything special tbh, and the damage is lackluster.
The Camo netting isn’t super historical, should be much more colourful, probably just a dev server thing though, and more random in pattern.
Personally I would have done a Canadian, or South African pack, but if you wanted to keep it British there’s better options too. (Keeping to the same range as the other packs, 5.3 to 6.0. 4.7 isn’t a great BR in general).
Canadian (1944):
Firefly with APDS (5.0)
(Open to suggestions here tbh, maybe the QF Ram? Could also do Achillies with APDS. Captured German thing maybe?)
Skink (5.3)
South African, Timeline is extremely fuzzy lmao:
Comet (5.3)
Not sure, Concept 3 with APDS or something maybe?
Bosvark (5.3)
British (Late 1944/Early 1945):
Comet (5.3)
A30 Challenger with ADPS (5.3)
Skink (5.3)
Or a British “Experimental testing” pack (End of WW2ish)
