Raven (Elysian Angel)

CH-53K?

Right? I'd like to think the majority of the DCS users is at least in their 40s, but the forum likely isn't representative of the average DCS user. To be fair, tensions are high in society in general (I don't mean politically but that is included - I mean as a living human being these days) so likely that will bleed through to some extent to forums, but that obviously doesn't excuse regrettable behaviour that's often on display here. Nice post btw

Indeed. On my end it takes around 10 seconds for the full textures to load in after exiting the F10 map.

There have been reports (believe them or don't) about the Typhoon ECM rendering the AMRAAM useless.

Absolutely. I still can’t tell the difference between the old eternal model and the new, even when looking at side-by-side comparisons. But the cockpit model being the same old model with a “fresh coat of paint” is very obvious. And as the thread you linked correctly identified: the main problem with the remastered release was all the lying and gaslighting that ED did.

And the funny thing is that it’s still an abbreviation: the full word is Sitzhöhenverstellungmechanismus

For those who don’t understand German: it basically states “operate the seat height adjustment for maximum 30 sec every 10 minutes”.

I didn’t, which was the point of my post

I'm looking forward to reading this week's newsletter, and the upcoming "2025 roadmap" newsletter too!

Yup there's been very noticeable improvement, but there is still a lot of work left to be done - I have only tested the original region by flying ED-supplied free-flight missions. Some mountains could use some refinements on their mesh (lots of straight lines and sharp angles remain still), and the Kandahar region still sports ground textures that are a blurry mess which is so much more noticeable because of the sharp contrast with other textures right next to them that look pretty decent even at low level. There are small some areas too that likely have some terrain errors behind the scenes as overflying them is a stutter-fest. Luckily those areas are small and not very prevalent (can be reproduced by flying the F-16C runway start IA mission and staying at low-ish level).

I completely agree, and I suspect this is due to the “remaster” we got, which are newer textures on top of the original cockpit - instead of a new cockpit AND new textures. Obviously I’m not a texture artist nor 3D modeller so I don’t know how material properties are defined, but I do notice that other older modules such as the Mi-8 have the exact same exaggerated shiny-ness to it and I suspect this is due to incompatibility with deferred shading and PBR. In fact, this is one of the major reasons why the release of this remaster was so controversial and got so many people angry at ED: we were told the new F-5 would be updated to the latest graphical standards, while it obviously isn’t.

There's been quite a few threads already in the last few years about suggested improvements to the User Files section. I hope you take those into account as well. Just to name one example which has been requested a lot: the ability to filter out fictional liveries...

I seem to remember someone in another thread stating that the difference mainly comes down to ease of maintenance and reliability. Perhaps some radar modes are different - I'd imagine the more advanced A/G modes to be removed/deactivated as there was little/no use for them...

Yes but the effect can be shared among ED modules, no (similar to NVGs using the same shader/effect across modules)? The community has been asking for this feature for ED modules for 7 years now so lack of time is not an excuse they can use. There are keybinds for left and right sunvisor but they are not what you'd think: they are for instrument cluster covers. A proper sunvisor is not implemented in any ED module.

Yes it is tricky. Only recently have I been able to aerobrake reliably. It’s the same with the F-5 really: it can be done but it requires some finesse and a lot of practice.

Nice to hear about the CH-47 updates. Hopefully the ability to turn off pedal trim will also be included - and of course proper visors for the pilots

In short: the community claimed for years the dispersion was quite a bit off (CPE too large, leading to the M61 being far less accurate in DCS than it is/was IRL), while ED was adamant they modelled it correctly. After years of bickering, ED had to confess the community was correct and they fixed the dispersion.

Excellent news about the Su-25, but I have to admit I'm a little disappointed the FM won't be upgraded to PFM, as it's the only aircraft in DCS which doesn't have a FM to that degree of fidelity. Are there plans to rectify that in the future?

Scintillation? Not exclusively: https://youtu.be/M_1g1N4ilQM?si=lSD-MsHftCqy1-wN (purposefully not embedded or I'll get naughty points again ) Already mentioned earlier. I haven't tested it myself yet, but I think it just freezes your motion while the rest of the DCS world continues on its merry way so you might want to be careful using this.

And in Single Player you can use active pause to switch to the WSO seat to manage things there, to simulate 2 people each actively following their own dedicated workflow.

Not to be the bearer of ill news, but when I had a similar error message, the graphics card I was using at the time had started to die. It took over a year, but it did die and replacing it "fixed" that issue. Perhaps something to keep in mind. Why? I for one am happy to see there are at least people who don't constantly make new things about stuff already discussed, bloating the forum even more than it already is. This thread here is as good a place as any (probably better even) to post, as long as the error message received is exactly the same.

HB have stated Jester doesn’t use AEW&C data yet, but that it’s planned for later during the F-4 EA - and since the F-14 is also supposed to receive Jester 2.0 at some point, both modules should benefit.

I’m following. i doubt it’s specifically nvidia related though, as for the first year and a half of this problem existing I was using an AMD gfx card