Bog9y

I'm pretty sure that Nick Grey said in this interview that they are looking into DLSS & raytracing : And if it's not this then Simon mentioned it here:

I know future proofing is usually futile but with DCS developers talking about DLSS and raytracing coming to DCS in the future wouldn't a NVIDIA card be the safer bet if you're planning on buying a new card? Just going on benchmark results with RTX and DLSS. Not sure how Vulkan affects these things.

Jeti, is there any issues I should consider when installing the new CPU? Just about to receive a 5900X and upgrading from a 3600. I've never changed a CPU before, it doesn't seem like a big deal. 1) update BIOS (I have a B450 mobo) 2) remove old CPU 3) install new CPU 4) download new chipset drivers perhaps? Anything I forgot?

Is this still available?

Still available?

Can somebody explain to me why Process Lasso says that all my CPU cores are operating at a similar load with DCS when DCS is supposed to be a single or 2/3 thread user? This is during a super carrier mission on the deck with loads of AI in the F-14. CPU is a ryzen 5 3600. GPU 2080 Super RAM 36 Gb 3600 Mhz CL16 I'm not a computer whizz kid but I was expecting to see 1, 2 or 3 cores to be peaking significantly in the Process Lasso screen but that doesn't seem to be happening here.

Interesting that your results are that the 6800XT performs better. Babeltech found this: https://babeltechreviews.com/vr-wars-the-rx-6800-xt-vs-the-rtx-3080-15-vr-games-performance-benchmarked/

Aha ok, so the video above is ok for MS flight sim but not DCS. That clears it up. Thanks. Apparently some people have noticed a performance improvement but that must be placebo effect.

Hi guys, A guy on the VR FB group posted this link: Can someone here confirm whether this actually works for DCS Steam users? Am I right in saying that this is called native resolution support? I tried it but doesn't seem to do very much. I did a search here and read about native resolution support discussions from a year ago but nothing recent. So, does actually work with DCS ?

It's nice to see you put the SEC and EPU check right after the start instead of what everyone else does, which is switching on the avionics.

Flew this yesterday, really enjoyed it! Searching for the target was hard!!! In the end I cheated and claimed I found them to get the coordinates. On the return I had to refuel as I was running on fumes but didn't think the wingman would just fly in without thinking. He crashed into the tanker and killed us all. Stupid wingman! Also, just wanted to know, are we supposed to wait for a set take off time or just go whenever you're ready? It seemed to me that the SEAD flight should have gone first but they didn't move at the EOR.

Yeah, I read that in the MLU 3 manual too but thought that maybe the DCS Viper is based on different/more updated software

Fixed it, turns out that if you set MSAA to OFF in the graphics settings the crosshairs disappear.

Hi guys, I had this exact problem (crosshairs not appearing on WPN page) and have just figured out exactly what's causing it. As Deano87 suggested, removing the options.lua file fixes the problem. But, as soon as I set my settings back to where they were I lost the crosshairs again. After lots of testing I found out it is the MSAA setting. If you have MSAA set to OFF, the crosshairs are not displayed. Setting it to 2x or 4x makes them appear again. I have no idea how this is linked but there you go...setting it to 2x fixed it for me.

Hi guys, I had this exact problem and have just figured out exactly what's causing it. As Deano87 suggested, removing the options.lua file fixes the problem. But, as soon as I set my settings back to where they were I lost the crosshairs again. After lots of testing I found out it is the MSAA setting. If you have MSAA set to OFF, the crosshairs are not displayed. Setting it to 2x or 4x makes them appear again. I have no idea how this is linked but there you go...setting it to 2x fixed it for me.

Well, I just had another go at it and had it all working properly. This mod is fantastic when it works! CAS is so much better with it.

I would say it is, yes. But of course need ED to confirm this.

I noticed that the SPI bearing indication in the HUD (bottom right) is indicating true instead of magnetic. Is this a bug or correct? I tried to find more information on this through all the F16 manuals I have but no info on it.

What do you mean by "copied other lines in the new export.lua"? I have the same problem with VA and want to fix it but not sure which lines I will need to copy.

Ooooh....I like that! Looks like a better version of the Virpil throttle. Virpil just has too many buttons and things on the grips.

Interested but just curious, what would make your manual more realistic than others? Have you got real F-16 time?

Hi, Just noticed that in STRG SEL the A/P flies the aircraft to the T-POD TD box, not the steerpoint selected. when I slew the TD box left of my heading the a/c steers left. When I slew the box right of my heading the a/c steers right. Surely this is a bug?

Yep, same here...still got MAV issues. urgh

Whoever can not get this MOD to work, try this: move the NATO.lua file (the suitable one for your module) into Saved Games\DCS\Mods\Script\Speech This did the trick for me after trying several times with JSGME or OVGME. I use Steam for DCS so that was probably the problem, although all my other mods work fine with JSGME/OVGME CAS is WAAAAY easier now! Thank you whoever made this mod!

Has anybody else got issues with the D models Mavs in a inflight start mission? I dont have any crosshairs on the WPN page.