adirtynurse

I'm 90% certain this is solved. The F16 has this in the game. The auto lase function is customizable and works as well.

As they mention "other businesses" I would assume its related to government contracts of MCS. It could be that they have access to classified L16 to provide a government project the actual capability to link into other systems, sims, etc. And to avoid confusion that they haven't implemented any part of that classified L16 capability to the consumer market, they renamed it to appease their government clients.

Can't wait for this to release!

+1

Hopefully the current Lantirn will be made optional for all the "period" simmers

+1

Are you using export montiors that you're having an issue with? I ask, because I haven't had any of the issues you've mentioned on my main monitor and as shown above, the picture is pretty clear. I expected the MMS feed to be even worse due it being 80s tech, but as it is right now, I've had no issues with identifying Snow Drift radars at 12+ km away for example. Are you fiddling with the MMS focus or other buttons on the side that tune the MMS picture? I do this to have a clearer picture. You have to use RMB and LMB when using these, because they're the up and down functions for those buttons. Clicking on the top or bottom of the MMS tune keys doesn't work.

Yup. I left that for last and after completing the reinstall, its fixed for me. Good luck

That might be, but for me the F4 is the only one experiencing significant FPS issues. Don't have that with other modules. Not even the F14. I tried that, but unfortunately it didn't do anything

So I've scoured and looked for help on ED's discord, DFA's discord, PC's discord, created a ED support ticket and have come up empty. I haven't seen anyone else report this issue, so I'll just create this post to leave a mark that this happened. I'll preface this by saying that DFA's Grayflag servers are the ones I enjoy the most. I have no issues with no other module on those servers, other than the 58. I've literally flown another module on GF and then when I try to select the 58 - game breaking issues. I play the Steam version DCS in multithreading. So what happens is my game freezes. It doesn't crash, so it doesn't trigger the DCS crash report tool, but windows recognizes DCS as non-responsive app and offers to kill it. The game isn't completely frozen though. It has a frame rate of about 1 frame per 2-5 minutes. Just weirdness. I can fly the 58 in SP and other MP servers like Rotorheads, BSD's Helo Ops, etc. Its just the GF servers. So what have I tried to fix this so far? Tried a different GF server - Didn't work I usually play on Syria or PG, but the issue started with Syria. Then I tried PG and Sinai. Both worked for one flight and then the same issue started. GF Syria has always had this issue for me. GF PG & GF Sinai started to have this issue a week after release of the module. This is when I noticed it. Verify game files - Nothing missing As with any issue in DCS, this was my first actual go-to attempt to fix something, but it found nothing missing or out of place. DCS Log analyzer - No help here unfortunately Didn't give any other answer than to do the following two steps. Remove all mods (except for the ones required on GF - UH60L & C130). - Didn't work I'm not really interested in removing the required ones, because I know it works on other servers where these aren't dependencies. Also other people successfully play on GF with these same mods, so the issue lies elsewhere. Lower graphics settings - Didn't work By now I've tried every settings from as low as you can possibly go and then start to raise the settings in increments. No dice. Run DCS in single-thread mode - Didn't work Starting here I was beginning to get worried. I was scouring DCS forums, Reddit, and Discord. Anything that even gave me a whiff of this might fix something, I started to try. This being the first attempt out of desperation. Updated my BIOS - Didn't work Worry has set in as you can see. I went after BIOS drivers :D Remove all other modules (except for the ones required on GF) - Didn't work I tried to remove other modules to see if there's something underlying, but no. Uninstall & reinstall OH-58D DLC - Didn't work Worry has turned into desperation. Uninstall & reinstall the entire game - It worked! Only had to uninstall & reinstall 800GB of DCS to fix this issue. You might ask why so much trouble for 58 and the GF servers? I just really like the OH58 and PC's presentation of it. I also think the GF servers are the best public PVE servers out there atm. I just want to fly my favorite aircraft on my favorite server. My system specs: ○ ASUS PRIME Z390-A ○ Intel(R) Core(TM) i7-9700K ○ CORSAIR 32GB 2x16GB DDR4 3200MHz ○ CORSAIR 32GB 2x16GB DDR4 3600MHz ○ NVIDIA GeForce RTX 3080 ○ BEQUIET! be quiet! CPU cooler Dark Rock PRO 4 ○ CORSAIR RM650x 80 PLUS Gold Modular PSU ○ SSD 2TB Intel 660p M.2 NVMe ○ HDD Seagate Barracuda 3 TB SATA III Serial ATA ○ LG 34GN850 UltraGearTM 34" ○ DELL U2312HM 23" dcs.log

This was addressed on Discord. The reaper is an ED product, which they don't think is a priority to develop, since none of their modules have a function like the L2MUM. So for the time being PC and other 3rd party devs have to play magyver with ED's toolset OR start creating a whole new module just for the AI. Its also something to do with local vs server assets. Supposedly in testing the devs implemented community mod stuff, that would work in SP, but not in MP etc.

Zoom in/out keys on the Copilot stick controls

No. There's no functional datalink between the 64 and 58nin DCS

Yep. Works now. Thx

Nope

Kneeboard

Why the KW-way is good is that using Voice Attack I can very easily implement voice commands, where I'm essentially speaking to the AI. I use only one button for that - the intercom PTT. For me I find its more immersive. In addition to the Barundus AI UI and its associated keys, PC also included a metric s#!t-ton of keybinds of what the AI should do. I just used those to create voice commands into my VAICOM VA profile. Tbh without voice commands (VA+Vaicom specifically) I probably wouldn't find the F-14 enjoyable. But because I don't have to navigate menus, its great. Now that I think about it, its the reason why I don't fly the apache. I don't like dealing with AI menus. And the KW made it very easy for me. As they have options for both those who like AI menus and those who don't.

same here

Just to say this again. Me and my buddy had this issue, that the foldable view solved. But when we updated the software AND all firmware separetely for all virpil devices. It was simple but annoying to do, because you have to do it one by one. But that fixed the controls menu issue for me and my buddy.

I had the same issue. What fixed it for me was updating the virpil software and all virpil hardware firmware. I was running the old soft things fell apart with certain aircraft. No more issues after doing what I mentioned beforehand.

nullWhen using night vision, the front cockpit window edges are very low res, when looking through the HUD

Are you guys using virpil equipment?

Do we have a "Pico 4 QVFR for dummies" guide? I did what I understood from the github guide, but how do I know its on etc?