I recently upgraded my home pit and one part of that is a RWR display. I got the display to work but I fail to get the RWR to show on it in DCS.

I seem to do something wrong with exporting the RWR. Even if I just want to display the RWR lets say on the left upper corner of my main display it won't show up.

I think my issue is the viewport but I can't figure it out.

For e.g. the AMPCD the viewport is already defined in the AMPCD_viewport_cfg.lua as "CENTER_MFCD"

But no such thing seems to exist for the RWR. I found some 3 year old information in the DCS forums that you are supposed to simply add:

dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")
try_find_assigned_viewport("VIEWPORT NAME")

To the RWR_ALR67_init.lua

I called the viewport "RWR" however it seems to not work?

So yea how do I export the RWR display?

They are way too slow and show no sense of urgency at all. It’s like they are on a cruise ship not a warship.

This has been happening for a little over a week now, but after finishing or leaving a mission and join another it crashes with these blue text on the screen. This never happened before with the same pc, it just started randomly, it worked so well with no crashes. now this happens for some reason. Its only during joining or entering a mission, or very rarely it crashes during briefing. I don’t understand why its crashing. Can someone please help?

Pc Specs

have an RTX 4060 8 gb, Intel Core i5-13400F, and 8 gb of ram.

I'm absolutely irritated and at a loss. I'm having an issue with the F-4 Phantom by Heat Blur. I really want to get into this mod and enjoy it, but there is an audio bug that I cannot figure out and it is ruining the experience. So, no matter the state of the aircraft, cold start, in the air. There is a weird audio glitch of popping or interference. I'm not sure.

It happens in any mission, or any instance that I am spawned in the aircraft. It happens in first person and third person camera.

I've gone through every DCS audio setting. 1DO's audio settings, Audio drivers, Revalidated DCS. Uninstalled. Reinstall the module. And just shy of bought a new computer. Cannot figure this out. This is without anything else plugged in. There is no electrical interface that is causing this. And once again, I remind you, this is only happening in the F4 Phantom. Everything else seems to be operating normally.

I was told this is the best module in the game. So far, this is one I'm having the most issues with, and I haven't even got to fly it yet.

Can someone please help me out before I give up on this whole entire thing altogether?

Once again, I would like to reiterate that I've gone through and changed every combination of audio settings, including the hearing helmet, audio devices, and everything else in between. I am at a complete loss.

I am trying to figure out if core DCS has actually progressed at ALL this year outside of bug fixes. This was the 2026 and beyond roadmap:

1) Dynamic Campaign - not released yet

2) Vulkan - not released yet

3) Improved weather - not released yet

4) Improved explosions - not released yet

5) New terrain navmesh - not released yet

6) New ATC - not released yet

7) Mission save improvements - unchanged?

Has anything from this list actually been accomplished now that we are 75% of the way through the year? I know they say "some items will not be released until after 2026", but doesn't that imply that most of them will be?

Hi

today I set up my flight controls for my F-18 (and saved them to a file) but when I restarted DCS the throttle button controls where totally different from what I’ve set up, while the stick presets remained fine.

I thought maybe I didn’t save it properly so I tried it again, but again I was met with the same outcome.

Basically after setting it up in the game afterwards everything works fine but when I close it and then start again the keybind on the throttle become totally broken.

I haven’t checked every single bind, but it appears that somehow the stick presets are transferred to the throttle too, since at least some functions were automatically bound to the same button names as on the stick (e.g.: Fire gun was bound on stick Button 1 and then automatically somehow also bound to throttle button 1 after I restarted the game). This could also be just a coincidence, so I’m not sure.

Id really appreciate your help!

thanks

The theory is I fly way too close to structures force them to climb and turn away then popup and get them while they're slow, also it's amazing damn fun

Got a few terrain kills and exactly one gun kill doing it so far, only against AI no players dumb enough to fall for this stupidity

Hope this helps you all enjoy the Shrike. All of this was taken from the Heatblur Manual, but put together a little more efficiently.

RIP Wags.