Freedom Fighter: F-5A(G)

@Stona_WT surely it can, but after seing how GCS-1 was treated I think it is reasonable for developers to disclose their source for Penguin’s capability to lock ground targets

5 Likes

The predatory nature of this game has to stop. Mechwarrior Online gives you a free vehicle once a year that you can earn in 15 minutes or less in a single game. Meanwhile, Gaijin makes you work a 2nd job. Name another game that takes 3 to 4 hours a day to earn an item. Between this and the auction house its obvious they are giving the finger to the player base and forcing them to buy items instead of offering a chance to earn them easily. Warthunder is becoming about as much fun as a prostate exam but the feeling is still the same.

1 Like

Look here as well: “An inertial navigation system (INS) ring laser gyro was installed enabling accurate navigational information to be transmitted to the HUDWACS to improve the accuracy of the information for weapons delivery”.

Spoiler

image
“Canadair CF-5 Freedom Fighter” by Anthony L. Stachiw

1 Like

“Ships being the intended target” and yet again another ASM that’s useless against ships because Gaijin don’t want to put any effort into modelling ASM’s or AI ships correctly

Yeah, the CF-116 HUDWAC is also GEC-Marconi’s work.

As installed in a CF-116D

cf116-7

Logic would tell you that the CF-116 AUP and F-5A(G) Tiger PAWS HUDWAC upgrades from the same year ~1991 only really differ in therms of the Pilot’s Display Unit (where the Tiger PAWS one is modelled to look the same as the F-16C PDU using the same Optical Unit, UFCP, and Combiner assy.). Both programs share the same RLG unit and SADC in addition to having Marconi-built HUDWACs.
But the Report Manager seems to believe it has to be the same computer architecture as the F-16 the display came from (even though the brochure explains that the EC architecture is modular and custom built for the aircraft), and for some reason Viggen and Blackburn Buccaneer that use 20 year older technology for the HUDWAC, as they appeared in the history footnote of the 1984 brochure.

With that said. BAE’s (who took over GEC-Marconi) own avionics heritage organisation the Rochester Avionic Archive, state that the fire control unit for the F-16C is a component contained in the HUDWAC Electronic Unit - which follows how the HUDWAC brochure describes the EU in providing combined imagery and fire control computation
https://rochesteravionicarchives.co.uk/items/f-16c-d-hud-electronics-unit

The F-16 C/D Electronics Unit contains twenty circuit boards. The Processor/Symbol Generator uses the MIL-STD 1553B (Standardised Electronic Data Highway) databus architecture, the MIL-STD-1750 (Standardised Computer architecture) processor and the MIL-STD-1589A (Standardised Jovial J73 Computer language) software. This was the first time that all three Standards had been used together and the Company was way ahead of its US rivals in this respect. The foundations for the implementation of these Standards was laid down by FARL from 1978 and led to a highly successful LSI chipset for the 1553 Databus. The HUD EU has comprehensive video mixing and scan conversion and self-contained weapon aiming capability.

2 Likes

They rejected the chaff pod bug report.
https://community.gaijin.net/issues/p/warthunder/i/qShe7RuZK1RJ
One of the most interesting features.
Welp I don’t even know why they keep adding event vehicles if they don’t even bother to fully develop them.

2 Likes

https://rochesteravionicarchives.co.uk/items/the-f-16-head-up-display-system-1

B-but the F-16 didnt use a Ring Laser Gyro, so therefore the HUDWACS wouldnt work!1!11

In fairness, the response is reasonable. Only a single secondary source has never been enough for a report and there are no sources provided, or at the very least listed, for the specs

Regarding the A38N pods, found some info about an A38DK at tinbox.dk
Its the insides from an ALE-38 pod inside an ALE-2 shell

Spoiler

image

1 Like

Working on fixing the report :)

2 Likes

Their source is “it’ll sell more aircraft”

Because it is “unbalanced to go through smoke” they said lol

Might be a little better i hope
https://community.gaijin.net/issues/p/warthunder/i/6gdX6in2WViB

2 Likes

https://rochesteravionicarchives.co.uk/items/the-f-5-hudwac-tactical-superiority-for-the-tiger
didnt saw this in ur brochures
iys for f-5 e/f hudwac but clearly says
CCIP MODE
(Continuously Computed Impact point)
HUDWAC takes into account actual
airspeed, dive angle and G forces from
airc",ft sensors to continuously predict
weapons impact point. The CCIP pipper 50-=
marks the impact point if bombs were =
released at any given Instant.
https://ark-raa.s3.eu-west-1.amazonaws.com/documents/XWyo2MjBm9_1698822344.pdf this also may be useful

Was aware of them, but they’re for the F-5E which is pretty different from the F-5A (has a radar for example).
I didn’t want to draw too heavily from systems not installed either on F-16C/F-16MLU or a direct F-5A subvariant like the CF-5A/CF-116A.
It was the Report Manager that suggested manuals detailing HUDWAC architecture for Buccaneer (1960s HUDWAC) and Viggen (1970s HUDWAC) is applicable to a 1990s F-5A upgrade, not me.

And they’ve shot it down once again.
I think the best course of action would be to get in touch with the Museum.

Try to contact DavidBowie through DMs regarding that.

Some more information about all the stuff for the F-5 has shown up, so there will be a new one after that has been sorted trough haha

3 Likes

This post was flagged by the community and is temporarily hidden.

They are getting lazy.

2 Likes