MRTX

Like I mentioned before, just make the IHADSS adjustable and all of these problems would go away over night.

To the guys of OnReTech. Do yourself a favour and claim that there was some mistake being made and immediately resolve this issue and you might have the chance to keep some small piece of trust with your customers. After that you better deliver some serious content in order to make up for this.

Keep in mind that the Eurofighter developed by Adams Simulation and Training for MCS and the Eurofighter developed By HB/TG for DCS are two completely different products. The Eurofighter by AST was made as contract work (probably for the Luftwaffe) with access to all the needed classified documentation, hence why not much of it can be Transfered to the DCS Eurofighter (if their contract would even allow to do so).

Bump! I just got stomped by a M2K with all of the AMRAAM's I fired getting trashed by the M2K's roll and jam BS.

A situation many of you probably experienced when flying with George as your CPG: George spots a stationary target out in the open, you ask him to engage with the M230 and the rounds land right next to it. You ask him to re engage, but since he's not able to properly lead the target in the slightest, you're presented with the same result. As a last resort you give your pedals a small kick in order to overwhelm the TSE with sudden movement, whilst telling george to engage to somehow get your rounds on target. The result is that you've now wasted 50 rounds on a measily truck, due to George not being able to adjust his fire when engaging targets of boresight even under good conditions (sub 90 knots, less than 2k of distance to the target). The TSE being far from perfect (or at least its rendition in DCS) whilst george is forced to use the MTT is obviously also not helping.

Awesome to hear, thank you very much!

Its been nearly two years without such a major problem being fixed. If somebody at ED (or BN) sees this, i would very kindly ask to forward this again and maybe suggest to put it up there with simmilarly severe bugs of the Apache.

Bump (Like i said over half a year ago, fixing this really is just a matter of editing a single value!)

Yeah, the Eurofighter seen in the NOR AAR video is the one from Adams Simulation and Training (although its obviously still in the early stages of development).

I mean Gero Finke is also the CEO of Adams Simulation and Training, which already developed a Eurofighter for MCS (the Prosumer version of DCS) being used by the Luftwaffe as a part task trainer. On top of that they're also currently developing a Eurofighter for NOR. And we also shouldn't forget that besides Gero the Truegrit Team mostly consists of former Eurofighter Pilots and Maintenance personnel.

The Eurofighter was designed to be an air superiority fighter with its radar built in mind, so isn't the whole point of having the ability of such a high scanrate to enable dynamic dwell times on TWS targets by revisiting tracks, allowing for high target update rates at the maximum radar search volume. For example the radar would initially perform normal bar sweeps to scan the airspace in a rather classic fashion at its maximum search volume. After detecting a single or multiple targets and creating TWS track files, the radar is still able to perform normal bar sweeps at the maximum search volume in order not to compromise the detection of new targets. Between every other bar sweep the radar would then quickly revisit all existing radar tracks ensuring a high track rate no matter the radar search volume. On top of that this also allows the radar to prioritize TWS tracks by their RCS or the necessity of higher update rates for a missile track. This overall allows for extremely stable TWS tracks at full radar search volume (which currently no fighter in DCS features) at unpresidented ranges. The only real factor influencing TWS performance would be the number of simultaneous tracks.

All publically available information about the detection range of the MAWS are guesstimations at best. The only concrete facts that we can work with is the size of the rear MAWS antenna and its operating frequency in the K band. The big factor we have no idea about is the power output. On top of that the MAWS is designed with LPI characteristics in mind and therefore most likely operating with a rather low power output at rather dynamic PRF's, which is not helping in making any accurate estimates either. Overall the best shot we probably have at making out a threshold for a minimum of performance we can expect from the MAWS is looking at what its designed to do. Obviously the MAWS's most appealing function is to detect non radar guided missiles, predominantly MANPAD's and short range IR missiles. These tend to be small in size, therefore often have rather low RCS's (often well below 0.1 square meters). Most MANPAD's out there have ranges of 2-3nm. (4-6km.) resulting in an extremely low time to impact even at max range. This means that in order to give an Aircraft enough time to react, it's pretty much a requirement for the MAWS to be able to detect an approaching missile almost instantaneously after launch. Hence why i find it reasonable to believe that the MAWS should at least be able to detect targets with an RCS >0.01 at 2nm. in order to fullfill its function properly. Obviously this is still just speculation and by no means indicative of the exact realworld performance of the MAWS of the Eurofighter.

I think i can speak for a lot of VR users when saying that having the option for an increased font and symbol size would be a very nice addition to the aircraft. Especially the readability of the MPCD can be somewhat difficult at times (I'm currently running a Q2 with 1.3PD).

Well, i think we can all agree upon that Heatblur is most likely capable to code the needed systems for the Eurofighter as long as Truegrit provides them with the necessary information. Yes the eurofighter would be a challenge to develop for any seasoned developer, which is mostly caused by the lack of access to needed documentation and knowledge (which isn't a problem for Truegrit) and the fact that many systems of the Eurofighter are deeply interconnected building up on each other. This leads to a situation in which developers will be forced to release the Eurofighter in a very complete state in order to give the user a faithfull representation of what it is like to interact with it. Obviously that leads to a very long development timeframe which most smaller DCS devs simply can't afford to sustain without any additional revenue during that period. This is something Heatblur and Truegrit also don't have to struggle with, due to the nearing realease of the Phantom (on top of that i wouldn't be supprised if Adams Simulation and Training was also still cashing in to support the project). Overall the Eurofighter development will take considerably longer than that of most other modules in DCS untill it can even be considered read for EA.

Nothing a bit of sanding and a couple coats of paint can't fix.

The biggest problem that I suspect causing this long development and reluctance of ED to show off Afghanistan besides the development of the terrain itself is the COIN focused nature, which currently due to both terrible ground/infantry AI and lack of assets is just not feasible in a realistic and immersive manner that will live up to player expectations.

I think me and many others included would really appreciate if there was an option for bigger RWR symbols due to the current ones being very hard to read especially in VR.

Would be awesome to get some beep-boop-language about the DASS! On another note are you by chance a pilot or maintainer at the Luftwaffe?

Like the title suggests i would love to see the ability for us to preselect our programmed MPD pages through the special options as irl. would be done through the DTC. Later on this option most likely will become obsolete if ED properly implements their DTC functionality, but since the timeframe for the implementation is in the realm of Soon™ it surely would come in handy.

A plain and simple option to remove the Apache's canopy reflections (including the window deviding the pilot and cpg) would be a very simple but usefull addition to the helicopter. I think I can speak for many of us in saying that I would greatly appreciate this being implemented, since there are often moments in which I just want to jettison the canopy in order to see a thing.

Just a very simple request. I would love to see the X indicator of the emitter being Jammed to be implemented with the SE. (i know the refference foto is from the TEWS of an F-15C, but the system hasn't changed that much on the user side of things with the SE, and have fun finding any declassified documents about the F-15E)

I seriously don't get what the guys are up to at ED. Fixing this problem seriously just involves a single dev opening the encrypted and now "safe against cheaters" weapons.lua and editing a single value. This is a job that should take 5 minutes at max to solve a problem which is now known for over a year.

Yeah would be awesome if ED could implement some form of motion smoothing for the nightvision system in VR.

So we're basically F'ed when using MT since this is not a bug persé ?

Its most likely something that has to be fixed by ED