Jump to content

DCS: Eurofighter Typhoon - Avionics


Recommended Posts

I worked on the Project when the MHDDs were CRT technology, none of this AMLCD stuff, although I did see the transition to AMLCD and assisted with the 'disposal' of the CRT assets - if only had been interested in pit building 12 years ago....

 

They were still called MHDD's though and they were driven from a Computer Symbol Generator IIRC, key panels were the product of Sirio Panels and the MHDDs from Smiths Indistries.

 

Oh what fun work share was. If you lost one of the keys (MHDD key 6 'lost' pixels) you had to return an MHDD to Smiths to remove the key panel for them to send it to sirio. Sirio would repair and retest (although they tended to be a black hole) and return it to Smiths who would reassemble MHDD and retest before returning it.

 

No wonder the project is expensive, add the number of no fault founds and Sirio and then no fault found at smiths the unit comes back to find a bent pin on the Typhoon or a problem in the CSG!

 

Not a lot has changed. Although we are better at stopping the NFFs than at the beginning. 2 CSGs per aircraft (redundancy), but yeah, you're on the money. They also drive the HUD as well.

 

Spoiler

Intel 13900K (5Ghz), 64Gb 6400Mhz, MSi RTX 3090, Schiit Modi/Magi DAC/AMP, ASUS PG43UQ, Hotas Warthog, RealSimulator FSSB3, 2x TM MFDs + DCS MFDs, MFG Crosswinds, Elgato Steamdeck XL

 

Link to comment
In the Hawk forum someone raised the question of data-link interoperability between multiple 3rd party DCS add-ons.

 

There are too many variables at the moment to say how this could be achieved, and maintain the level of accuracy to each particular aircraft we are looking for.

 

It would also require a certain level of co-operation between 3rd party devs to make it happen (i.e. all agree on a basic method of interaction that enables the function to operate within the scope of each individual aircraft development).

 

Best regards,

Tango.

 

Well to my mind its down to ED to implement the link 16 gateway functionality (maybe an API, but coding isn't my thing, so i could be talking rubbish there) to enable the various DL standards to talk to each other. Well the link 16 standards at least.

 

When we have jets, ground units and naval forces running the various TDL types there will need to be a gateway of some sort to disseminate data between them. At least if we want to realise their full potential rather than only simulating a limited part of the functionality as was done in the A-10C.

 

Spoiler

Intel 13900K (5Ghz), 64Gb 6400Mhz, MSi RTX 3090, Schiit Modi/Magi DAC/AMP, ASUS PG43UQ, Hotas Warthog, RealSimulator FSSB3, 2x TM MFDs + DCS MFDs, MFG Crosswinds, Elgato Steamdeck XL

 

Link to comment

With ED and various 3rd parties working on link-16 capable jets I hope it's a problem that can truly be solved.

 

On the upside, the Typhoon, Eagle and Hornet all use MIDS so at least they are on the same link-16 system, assuming recent blocks are modelled of course.

 

Spoiler

Intel 13900K (5Ghz), 64Gb 6400Mhz, MSi RTX 3090, Schiit Modi/Magi DAC/AMP, ASUS PG43UQ, Hotas Warthog, RealSimulator FSSB3, 2x TM MFDs + DCS MFDs, MFG Crosswinds, Elgato Steamdeck XL

 

Link to comment

with a bunch of 010101010101111010010010001010101010101011

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Link to comment

actually in 2013, it's prolly a bunch of Right Click, Start Function, CTRL+C, CTRL+V, Right Click, Apply Function, CTRL+C, CTRL+V, Left Click, ENTER, Right Click, Fucntions, End Function.

 

Along with the 10101000010100010101010101111010101001001010100101011011110

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Link to comment

Are you insinuating this is an arcade game? :noexpression:

 

X, Y, RED, GREEN, BLUE+YELLOW, X, LEFT/RIGHT (at the same time) followed by double backflip whilst running forwards against the wall??

 

:noexpression::noexpression::noexpression:

 

Along with the 10101000010100010101010101111010101001001010100101 011011110
Now I just think you're trying to send subliminal messages in an attempt to get me to divulge information. :noexpression:

 

Best regards,

Tango. :P


Edited by Tango
Link to comment

nah, just making fun of some of the cookie cutter SDK's out there...

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Link to comment
With ED and various 3rd parties working on link-16 capable jets I hope it's a problem that can truly be solved.

 

On the upside, the Typhoon, Eagle and Hornet all use MIDS so at least they are on the same link-16 system, assuming recent blocks are modelled of course.

 

Same principle there though Eddie. Yes we will model MIDS for the Typhoons to talk to each other and we can open it up that other units can talk as well. But the 3rd party devs of those units would also need to model it, and essentially code it, all the same way.

 

As Tango hinted, it would need a cooperative agreement between ED and the 3rd party devs to develop it jointly for it to see it's full potential.

Link to comment

For data link maybe ED should have a standard datalink network code that is used and shared by all other 3rd party devs if their aircraft requires one. The major difference is type and compatibility so Link 16 for example wont be able to talk to KA50s data link etc but would be compatible with other datalinks that are compatible with that type IRL.

[sIGPIC]2011subsRADM.jpg

[/sIGPIC]

Link to comment
The major difference is type and compatibility so Link 16 for example wont be able to talk DIRECTLY to KA50s data link etc but would be compatible with other datalinks that are compatible with that type IRL.

Yeah. They can, but the signal needs to be "translated" first. Usually this is done by an AEW&C or C4ISR aircraft.

 

Or ships, because ships are battlefield magic. In fact, if one were to blow up a Ticonderoga, one would see that it simply vanishes in a puff of magic blue smoke.


Edited by Pyroflash

If you aim for the sky, you will never hit the ground.

Link to comment
  • 5 weeks later...
At this point, any fast mover for DCS would be awesome. But a Typhoon would definitely be in my top 5.

 

The best way to support a Tiffy being made is to buy the Hawk when it comes out.

 

This is my number one want for a fast mover and by the time its out i will be able to afford a TM warthog to fly it with.....

PC:

 

6600K @ 4.5 GHz, 12GB RAM, GTX 970, 32" 2K monitor.

 

Link to comment
  • 3 months later...
I'm away for a few days relaxing in the Spanish sunshine and then I'm full speed earnest working on Tiffy cockpit integration so expect eye candy soon.

 

By soon, I mean by Christmas :megalol:

 

By Christmas, you mean,... This year? :music_whistling: :P

Good holiday :thumbup:

DCS Wish: Turbulences affecting surrounding aircraft...

[sIGPIC] [/sIGPIC]

Gigabyte GA-Z170-HD3P - Intel Core i5 6600K - 16Gb RAM DDR4-2133 - Gigabyte GeForce GTX 1080 G1 Gaming - 8 Go - 2 x SSD Crucial MX300 - 750 Go RAID0 - Screens: HP OMEN 32'' 2560x1440 + Oculus Rift CV1 - Win 10 - 64bits - TM WARTHOG #889 - Saitek Pro Rudder.

Link to comment

I'd rather have it for Back to School, roflmao.

Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2),

ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9)

3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs

Link to comment
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...