RSharpe

You will have to make sure you're getting Hynix and not Samsung. He did it on M-die, but A-die works as well. My kit is A-die. Trident Z5 Neo kits at (2x32GB) 64GB 6000 CL30 are likely all A-die for the moment.

Buildzoid's Hynix DDR5 timings increased my bandwidth a bit, but dropped my latency a lot. Worth trying. Timings are stable. Buildzoid vs EXPO timings on Trident Z Neo 64GB 6000 CL30

Thank you. This would be a huge upgrade to the module Sent from my iPad using Tapatalk

I was just about to place an order when everything went out of stock. The product pages says a new v2.0 grip is coming in May? Does anyone know anything about this? Have RS stated anything anywhere? Thanks

I've followed the GitHub installation instructions, but when I try to capture coordinates from the map, I get a "No connection to DCS detected" error. Does anyone know why this is and how it can be fixed? Edit: I have discovered there's a conflict between Santi's DCS Waypoint Editor and TheWay. It seems I can't have DCS Bios and TheWay.lua in the same Export.lua file. This disables functions in both programs, so I had to choose just one.

DCS recently wiped out my bindings for everything, and I just ended up deleting my user folder and started rebinding everything from scratch. It's working now

I'm having a trouble with key bindings. I'm really not sure what the problem is, but when the DCS Waypoint Editor window has focus, I can toggle capture. However, when I'm in DCS, the keyboard will not longer trigger the capture.

I have a Winwing Combat Panel that I want to bind the ECM knob to it. However. I have found that all bindings for the ALQ-165 are blacked-out and unbindable to the Combat Panel, and ALL USB devices except the keyboard. It's one of the only things I've not been able to bind. Every other switch, button, knob and axis slider for the panels has been bindable. Does anyone have any clue why it's like this and how to fix it? Screenshot of bindings attached. All USB devices have been blacked-out.

That is just ED's catch-all excuse that they use when they don't feel like putting the resources into implementing something.

So the only thing the recce stick button will be good for in DCS is to toggle the JHMCS on and off?

Repeating my experience here. I see high RAM usage, but that may be fine considering I find the performance to be better than any other map in DCS for me. I'm running on a 4930k @ 4.8ghz and 32GB of RAM with around 62GB/s bandwidth and a 1080ti @ 2.1ghz running at 4k. I'm getting way better framerates and frametimes than any other map in DCS. Mind you, the map was quite empty as I haven't built any missions yet. Framerates were around 70-80 on the ground, 60-90 in the air, and in the 50s flying low over highly populated cities like Beirut and Damascus. This map uses a lot of memory though and was hitting around 25GB of system RAM. VRAM was pegged at 99-100% like always on DCS with anything.

I'm running on a 4930k @ 4.8ghz and 32GB of RAM with around 62GB/s bandwidth and a 1080ti @ 2.1ghz running at 4k. I'm getting way better framerates and frametimes than any other map in DCS. Mind you, the map was quite empty as I haven't built any missions yet. Framerates were around 70-80 on the ground, 60-90 in the air, and in the 50s flying low over highly populated cities like Beirut and Damascus. This map uses a lot of memory though and was hitting around 25GB of system RAM. VRAM was pegged at 99-100% like always on DCS with anything.

Not sure what map you're playing on, but this map is has the highest framerates and is the smoothest out of every map. It has high RAM usage, but that's fine if it performs this well.

When might we expect this for the Hornet? Surely that's the reason for a 3D model with thermal ablative coating.

I can't wait for the [CORRECT PER AVAILABLE DOCS] tag, and the weeks and months of arguments between people on why this behaviour is inaccurate.

Had to dig on Hoggit reddit to get a ED response to this problem

Please roll back the lighting. Whatever was done to improve the rare night lighting effects has broken lighting in all other situations on pretty much every single plane.

The brightness has always been a problem on the MFDs, but now the direct sun from behind the cockpit washes out the MFDs entirely, and even the HUD and JHMCS is washed out at some angles

In the same way the Litening TGP features and JDAM auto modes were delivered in 2.5.6.49314?

It's all broken as hell from half-implemented features that were supposed to be included the last patch. They'll probably take a few weeks to fix it all, if they are even capable of delivering on June 3 as they claimed

Don't you find that throttle location to be too far back? The Winwing throttle has fairly long travel, and at idle, it's very far back. I find that I would prefer it to be set way further forward.

Can we please get separate key bindings for Fuel Dump On and Fuel Dump Off so we can bind the commands to two different buttons instead of the current solution of a single Fuel Dump On/Off toggle as it is now?

Does anyone anyone know how you might set this up on the F/A-18C? Right now, the only fuel dump binding there is is Fuel Dump on/off. I can't find a way to map it correctly to the Winwing throttle panel.

But.... Kate said: Basically, none of the 4 new features promised for last patch was delivered to any level of satisfaction.

This makes me wonder... Considering we now know that we got a Spanish Litening TGP, and ED have confirmed they have been using Spanish sources. Could this mean that this "no TGP symbology in the HUD based on our documentation" thing is not accurate to US Hornets armed with Litening?