oldmanflan

I just tried using the AGM 65E's in the Hornet to attack a JTAC target. It's been a while since I used these. However, I'm noticing that I can no longer uncage the maverick to scan for the lased target. I ensured my key binds remained unchanged ('C' for Cage/Uncage). But I can't get it to uncage, even when i have the target waypoint designated, proper JTAC codes programmed (1686 in this case) and within 10nm of target. I checked Matt Wagner's videos to see if there was a recent video discussing a change to this system and didn't find anything. Any suggestions?

Unless I missed an announcement, I wouldn't say it's "confirmed". Nvidia and board partners have not officially confirmed it. But based on all the reputable leaks, I think it's safe to say it is definitely coming. With that said, I'm with you on the wait. While I do think 10GB VRAM is adequate for almost all games, including DCS, waiting a bit longer for a 20GB 3080 seems like the smarter move. I'm going to hold off on the GPU upgrade, which is out of my control anyway, considering the complete lack of stock. For now, I'm going to turn my focus to the 4000 series Ryzen CPUs. I know I'm leaving a bit of performance on the table with the 3900x, compared to something like the Intel 10900k.

Interesting. Well maybe I should shift focus from the GPU to CPU. I've got a 3900x but the Ryzen 4000 CPU's are about to get announced and reviewed shortly after. If they provide a notable bump over the 3900x, that may be the smarter upgrade path. It would be cheaper and satisfy my desire to tinker, for now.

Ah crap. I figured I was likely failing at navigating this forum properly and posting in the wrong section. Apologies. I do appreciate your response, regardless. I think I'm with you, though. When I first learned that the 3090 would have 24GB VRAM, I assumed I'd inevitably be spending the cash. But after seeing reviewers post disappointing real world improvement, compared to the 3080 on all the games I play (minus DCS), it just doesn't seem worthwhile. I'll hold out for some videos of DCS in VR, where people will inevitably compare the 2080 ti vs 3080 vs 3090, and see what those results pan out to be. Solid point. I imagine 8gb vs 11gb vs 20gb will have minimal difference. But in the case of DCS with VR, where we are fighting to maintain 30fps, even with a watercooled, overclocked 2080 ti, I want to make sure my next move makes a consistent difference, even if it is minimal in the grand scheme of things. Though, at this point I'm convinced that carrier FPS will remain at 30fps or below, even with quad 3090's in SLI.

With the launch of the new Nvidia GPUs and impending AMD "Big Navi" GPU, I'm getting the itch to upgrade and tinker with my machine. I've already got a 2080 ti. However, I'd like use this upgrade opportunity to move that GPU to my living room HTPC. Performance per dollar, the 3080 is looking excellent. However, the 10GB of VRAM concerns me. Especially since DCS (with Rift S) maxes out the 11GB VRAM on the 2080 ti. Also, at some point in the near future, I am likely going to upgrade my VR headset to something with a bit more clarity as more products become available. As such, I want to "future proof" (I know, that term sucks) for my next headset. For this reason, the 3090, with 24GB VRAM, looks appealing. But at 2x the price of the 3080, I just don't think it's worth it. All that said, I'm now wondering if, for my use case (DCS in VR), going with a GPU that has lower VRAM, is potentially a step in the wrong direction. Every system has a bottleneck somewhere. Is maxed out VRAM a potential bottleneck, in this case? Or am I looking at VRAM usage, incorrectly? ... On another note, supposedly there's a mystery 20GB 3080 SKU that's in the works to 'best' the 16GB Radeon 6900, which is still awaiting announcement. This 20GB 3080 has been leaked on a couple of different sites. Based on previous Nvidia GPU launches, I'd imagine the 20GB 3080 ("ti" or "Super") will get released sometime in Q1, 2021. Waiting for that would probably be the wisest move. But now I'm rambling and I'm curious to get thoughts from those here who are more knowledgeable on this.

I prefer carrier ops. So the Hornet is my go-to. Also, rippling 8 JDAMs/JSOWs on 8 separate targets at once is extremely fulfilling. That's something the Viper can't do, at least not yet. But I do find myself jumping in the Viper every now and then, when I feel like drinking a beer and cruising around with 9X/120's, looking for A/A trouble.

Mine wasn't offering it either. But you can easily force the update by navigating to the "DCS World OpenBeta" folder on your computer, then going into the "bin" sub-folder and running the "DCS_updater.exe"

Planes drifting into each other on the carrier deck has been an issue on MP servers for many months. I wouldn't call that a new bug, by any stretch. In fact, this bug has had me avoiding carrier spawning since late 2019. With that said, I do agree with some of your other statements. It's astonishing to me that many bug fixes/patches have been consistently rolled out. Meanwhile, a nearly game-breaking bug (carrier plane drifting) has remained a consistent issue since at least Q4 of 2019. Even earlier if memory serves.

I'll start by saying I'm no novice to custom PC building. I've got a full custom watercooled system with a 2080ti, Ryzen 3900x, 32GB RAM yadda yadda yadda... Anyway, after my Wife and I hosted Thanksgiving and Christmas at our house this year, my Dad fell in love with my DCS VR setup. He could not get enough and has been dead-set on getting a setup of his own, so he can play online with me. He finally got the green light from my Mom to make it happen. As a result, I've started getting the parts list put together to build a system that will give him a solid DCS VR gaming experience, without going overkill. I'm going to get him an Oculus Rift S. I love mine and figure he can't go wrong there. I'm also sticking with the Thrustmaster t.16000m HOTAS, since that's what I have and it's been excellent. With that aid, there are two areas I'm struggling with... GPU: A 2080ti is obviously overkill but I don't want to hinder his DCS VR performance. My inclination is to go with a 2080 Super. But if a 2070 Super will give him the same performance, I am not opposed to saving a little money and going that route. I'm hesitant to go any lower than that as I do want to ensure he is at least slightly future-proofed, as well. CPU: I'm partial to AMD, so I'm definitely going that route. I initially decided to go with a 3700x. But now I wonder if a 3600x would be perfectly adequate, in this case? Anyway, I'm open to your thoughts and recommendations to get this project completed!

Another unhappy VR user here. 2.5.6 made playing in VR with Oculus Rift S and a watercooled 2080ti completely unplayable. Frames dropped by ~50% with tons of stuttering and even full game freezes, requiring force closing the game, while playing in multiplayer servers. I wasted hours trying to "repair" the game, re-installing all graphics and Oculus drivers/software. Nothing fixes the problem. VR aside, the game completely hangs while trying to load into a server 4/5 times. Requiring a force close in task manager. 2.5.5 was issue free. It's as if they didn't even try and user test this update. Come on guys!

I went to the Viper for 100% of my game play for the first 3 weeks after it was launched. However, I found myself going back to the Hornet more and more and now find myself never usually touching the Viper. However, I am one that truly prefers Carrier Ops, just about every time I play. So that is a major factor for me.

^^ :megalol: I laughed too hard at this.

Welp, after wasting a ton of time and energy, I resolved the issue and realized that Frederf was right the entire time. While both his comments were informative and much appreciated, they still didn't contain the clear answer and didn't make sense to me until I found the solution elsewhere and then pieced together what he has been trying to clarify for us. Solution: When he says that in order to use the radio comms menu while airborne, you have to hit (R-ALT + \) to get the proper VHF comms menu to pop up and (R-CTRL + \) to get the proper UHF comms menu to pop up. Just hitting \ on it's own, while airborne, doesn't cut it. I've tested this in both the F-16 and F-18 and can confirm that adding R-ALT or R-CTRL to the mix completely solves the problem. I now get responses from the tankers and air bases again. I can't say this solves your issue for comms on the ground. But it should definitely solve your issues with comms in the air.

Ugh, now I'm thinking there is something wrong with my game install. Thanks for looking into it on your end.

I truly appreciate the help!

Thanks for the input. I assume you mean making sure 'Radio Assists' and 'Easy Communication' are both toggled on, correct? I just double checked and both of those are turned on.

I've tried everything. Including ensuring the server I'm on has Easy Comms enabled, as well as playing a simple single player campaign. I've even re-watched tutorials to ensure I'm not just completely forgeting something simple all the sudden. Regardless of my efforts, comms won't work, despite using the same methods that worked 100% of the time, up until a couple of days ago. I'm now convinced that a bug has been introduced into the game or something has gone awry with my game install (which I haven't touched). I'll hold off until the next update (scheduled for 11/27) and see if that resolves it. Otherwise I'll try to install the game from scratch. Assuming this is a bug, I've got to say that, at least for me, this is definitely a game breaker as it eliminates half the fun. Hopefully it gets resolved soon.

Hmm... I'll check that. It's the same server I always use so if that's the case then they just changed that setting. It also didn't work on another server I tested but didn't think to look to see if "Easy Comms" was enabled.

Interesting. Thanks for the input. I hope this resolves it. I'll try in a bit. But, is this new from a recent update? The procedures outlined above worked perfectly fine for all AA refueling and air base inbound notifications prior to yesterday. Not sure when this changed.

This is a strange one that I simply cannot figure out, no matter how much I mess with it. As of 2 days ago, I can no longer contact tankers or air bases and get a response in either the F-18 or F-16. It worked perfectly fine in each jet, up until yesterday. Changing frequencies in the jets using normal procedures (outlined below) successfully lock those frequencies in the cockpit comms displays and even change my SRS frequency as desired, allowing me to hear other players. So the procedures appear to be working as usual. But I get no responses from tankers/air bases anymore. F-18 Procedure: 1) Click the Comm 1 dial to turn it on 2) Turn the comm 1 dial to "M" 3) Punch in my desired frequency to contact a tanker (256.000 for instance) and hit Enter. The frequency sticks on the display and changes my SRS to 256.000. 4) Hit "R-Alt" and "backslash" and use the function keys to contact the tanker (F6 - FX - F1) F-16 Procedure: 1) Click the Comm 1 button 2) Punch in 256.00 and hit enter. 3) SRS is now changed to 256.000 and when I check the Comm 1 frequency it's solid on 256.00 4) Hit "backslash" and use the function keys to contact the tanker (F6 - FX - F1) Both of the above scenarios previously allowed me to contact the appropriate tanker or air base on the channel (256.000 in this example). But now I cannot get a response from anyone. At this point I'm worried there is something messed up with my game install as I know the procedures are not changed from when they worked. Anyway, I know this is a weird one and I hope my post makes sense. I'm looking for any help/recommendations as this issue is pretty much making the game unplayable for me.

Thanks for the info. Yeah, I wasn't sure if it was just a bug or something that hasn't been implemented properly yet. I guess I'll just have to practice proper landing with little to no braking required! :)

For those with HOTAS, how are you setting your toe brakes to achieve gradual wheel brake pressure? In the DCS Controls for the F16, I'm only seeing one option for wheel brakes: Wheel brake - ON/OFF I have this bound to 'B', which is set to a specific button on my throttle controls. However, it basically makes my brake pressure 100% or 0%. I'm not sure how to set gradual brake pressure with this setup. I do have a slider on my throttle that I can set to 30% - 50% - 75% - 100%. This would be ideal but I'm not sure how to properly program this slider to achieve the goal of gradual brake pressure since it seems to just be ON/OFF in DCS controls. Any input would be greatly appreciated.

You're awesome. Thank you!

Just swapped my key mapping from CMS Left to CMS Up. But I think I'm missing the "Countermeasure Mode switch to MAN". Do you know what that is specifically called in the DCS controls interface? Alternatively, where abouts in the cockpit is that switch so I can toggle it manually? Thanks for the help!!

I've got just about all of my controls/HOTAS system setup properly for the F-16. However, the last piece of the puzzle I'm stuck on is the countermeasure release. I have the following properly mapped: Countermeasure Management Switch - Left (mapped to "U" in my case) CHAFF/FLARE Dispense Button (mapped to "R" in my case) I previously just had the CHAFF/FLARE Dispense Button mapped but nothing would dispense upon button press. Then i read that you also have to toggle Countermeasure Management Switch - Left for it to work. That didn't solve it either. I've tried with Master Arm on and Master Arm off, as well as in AA and A/G modes. But no matter what I can't get my countermeasures to launch. Can someone please guide me as to what else I'm missing to get this working?