Morat

Hi, first up I can't get the simple comms menu to work on \ or shift \ (nothing happens) so I used left-win-B and the command "Flight Engage Bandits" does get issued. My wingman just flies around dumping flares until he gets killed. Is this intended? Cheers!

Huh, that makes a lot of sense now. I've just been to the optician and they gave me my correct IPD so I can now use that in my G2 (I was way off!). I was wondering whether to change the IPD in DCS settings to match but it seems that isn't necessary. Thanks!

Just for comparison, I run a 3080 and a G2. With 109% SS in SteamVR (damn that slider!) I'm able to hold 45FPS flying over Guam with the default VR settings and some increases for things like Tree radius to avoid the "Genesis Effect" which is very distracting on that map. My CPU is a 9700K and it is now holding me back as CPU Frametime is higher than GPU Frametime. I went to overclock and realised my temps are too high so I'm messing with fans and AIOs at the moment. Long story short, I'm also looking for better CPU performance but the good news is that I'm sure you'll get a lot more out of your 6900XT than you are at the moment.

That's pretty much where I am with my 3080/9700K both at stock clocks. The sweet spot IS pretty damn sweet though, no problem reading the A-10C cockpit (apart from looking at the really tricky switches by your hips). GPU timings are usually 20ms or high teens which I can live with but I'm hoping the ED give VR some love in the new Vulkan engine. Also hoping it arrives SOON rather than Soon (tm)

Guess I just need that 3080 to finally turn up! Thanks for the reply

My G2 has arrived, and I'm loving it so far - however there's a very big but. My 3080 hasn't arrived (pre-ordered on launch day) and I'm stuck on my trusty Asus 980 Strix. It shouldn't work at all being a Display Port 1.2 connection but I've managed to get everything running in DCS. Is it great? No.. but I can just about play. I've flown online in the A10C-2 and it worked. The biggest issue I had was actually the targeting pod. I could just about make out the targets if I leaned right in and fiddled with the contrast/brightness on the MFD. How good does the TP look to other people with the G2 and a better graphics card? and are there any settings I can look at to specifically help out with the targeting pod? I'm running 50% resolution in Steam VR and 1.0 in DCS with everything in WMR turned down to minimum. It's not great... GPU time is always orange with some red spikes and framrate is about 35 with MSAA on 2x in DCS. I'm getting up to 50% reprojection too! But until I can get hold of a modern GPU I'm stuck.

How hard would it be to implement V-1 flying bombs? They're not exactly crucial but they'd give some great mission options.

This sounds like fantastic idea - especially if we can have a night fight version of the Mosquito with AI Mk IV and IX. That would be a true multiplayer experience for the Mosquito crew.

Slightly calmer now after Christmas You can send your wingman to engage the ships at the start of the mission, watch his SPI in your helmet sight and put your own SPI/Sensor pod over his. Then tell your wingman to rejoin before he does anything stupid. The GBU 54s in laser mode will slow the FFG with about 36% damage but you can't make your wingman use them and he seems to prefer committing pointless suicide by attacking with Maverick and then closing to engage with rockets. I hit one FFG with all 21 Hydra and it caused 22% damage. I did wonder if changing to tail fusing on the GBU-54 would be more effective against a ship, but it doesn't seem to be possible to change it. At least, I lost interest in this mission before I worked it out. I hit another FFG with >250 30mm (according to the post mission debrief) but it didn't care much, and it killed me before I could see the % damage. Above about 12k feet the ships don't engage so that's your change to drop bombs on them. So yeah - forget it with the stock loadout. You'll need 2000lb bombs, at least 3.

It's rubbish :( no radio instructions - but your wingman will engage the ships straight away because he's a computer and knows where everything is. Sadly he bores straight in and launches his Mav and APKWS. Then he dies to the absolute hail of gunfire those FFG can produce. It seems that you can get closer from the back of the ship and use the GAU (the only weapon that does any damage to the ships) but you then die as you pull out because the neighbouring vessels can engage you. APKWS are the HE variant and a full load isn't enough to stop the ship from getting into missile range, let alone sink it. Give up, move on - this mission is broken AFAICT. Things that need to be fixed. 1. Directions to target 2. Weapons that damage ships 3. If you want to us to sink 3 ships, send a flght of at least four. Or reduce the number of targets. 2/10 please try again.

It's OK, the laser-rockets are now mini-mavs and you can carry a ton of them!

Yes! Has anyone actually run DCS on a 3080 yet? I'd love to know if there's a worthwhile improvement. I've been playing DCS on an Asus 980 Strix for ~5 years now. I flip between 2k for FPS and 4k for gorgeousness but I'd like to move on. My processor/Mobo went pop just before lockdown so I'm hoping that a 30 series card will work well with my 9700k and show me enough gains to run in 4k all the time. If I get enough 4k performance, I hope to make the leap to VR with a G2 - but I'm not dropping any cash on that until I see what I can get with a 3080. Oh, and I decided to move on from my 650W PSU, just in case it was the cause of the failure, so I went overkill with a Corsair HX1000. If that isn't enough, I'll have to sell my PC to the power company.

Because crouching in your seat to look at the top of the HUD and peering down/right past the ejection seat handle is a real PITA compared to the old cockpit. My back does not thank ED for this update. (My eyes love it)

Is there a bug with the comms on this mission or am I being stupid? I can make the "mark your moms" call but then that's it. No further options apart from requesting navigational assistance. I thought I was meant to make another call at 10 miles but nothing shows up. I can land OK but I get a NC grade for "No Comms"

Jester isn't much use at all. Just use ACM radar modes, trying to outrun a Flogger is pretty futile anyway. You'll die every time but you'll get some Sparrows off.

I need this on a fully compatible base and matching throttle. There's no point in putting it on a Warthog base if the DLC won't work as an axis. IMO that would just be a waste of money. If you're going to do it right, do it right :) I'll unplug my Warthog when I switch from A-10C to F-14 and v.v. I don't agree with requests for twist or extra buttons, this is a replica for a very niche market. Generic/multipurpose/game sticks are a different kettle of fish altogether and will have different design priorities. GO all in VKB and give us something that works just like the real thing, including wing sweep (with cover) throttles with AB detents and the surrounding switches. It'll sell slowly, but it will sell for many years.

I'm over the F18 stick already. Now I want an F-14 stick with an axis slider/button for the DLC system. Oh, and matching throttles with AB detents and the correct wing sweep controls and cover :)

First thought after loading up the F14 was "damn, what's the binding for a damp cloth and some windolene?"

With a Falklands Map announced and the new detailed Nimitz we could play a lot of What If scenarios in the Gulf and Falklands. :)

My DCS folder seems pretty massive, I was wondering if I could compare? If I've got a load of cruft here I'll delete and reinstall but I don't fancy a huge download just on the offchance. So, I have 2.5open alpha only. No previous versions. Three maps (Caucasian, NTTR and Normandy) WW2 Asset Pack Two purchased a/c A-10C and Spitfire IX the normal default a/c. No campaigns or mission packs. No mods. Folder size is currently 109Gb. Is that excessive? If it's about right, I'll just have bite the bullet and buy a bigger SSD because I can no longer update. Thanks! Morat

Well... in most software dev the beta versions gets changed and hacked around as bugs are fixed and new features are added. It changes rapidly and when the beta testers stop whinging, the beta is released to Stable and the normal users get what the beta testers have been using. I'd predict that 2.5 won't be getting new features for a while because there will be a load of bugs to be squished. Most projects will release a big version and then feature freeze to get rid of the inevitable bugs that come from large changes. Being a beta tester can be fun but you can't complain if you download a new beta version and suddenly your controls are inverted or your chosen module runs like a dog. If you're running stable, you get the new stuff when it's ready but (hopefully) not before. Usually the current stable is just the same as the last beta version before release because the devs don't want to introduce untested changes to the release version. Of course, this is just my experience of other beta programs - who knows how those crazy ED coders work? :) edit: sorry cthulhu68, forgot this board doesn't do nested quotes.

Mine died. Purchased new December 14. It has been plugged in all that time. It was unplugging it when I cleaned my case that killed it, it never came back to life :( Looks like I'll have to buy a new PCB. This is not a pleasing outcome for a very expensive purchase. FWIW I have a Gigabtye GA-Z97X-Gaming 3 motherboard.

I'm distraught! I bought my Warthog about two years ago and both parts have been perfect since they were first plugged in. Yesterday I unplugged them for the first time so I could clean my PC Case out and when I plugged everything back in the Joystick worked fine but the Throttles aren't recognised. When I check device manager I can see: Windows has stopped this device because it has reported problems. (Code 43) A request for the USB device descriptor failed. Does anyone have any clues? I've tried reinstalling the drivers (only the Joystick is seen) and I tried plugging the throttles into my laptop with the same results. The PC was first installed with Windows 8.1 and then upgraded to Win10 - the USB devices haven't been unplugged since well before then. I don't know if that is relevant but I thought I'd mention it. I have contacted Thrustmaster but I have only received a "thank you for your email" response so far :( I can't Fly!!

I have no doubt there are people out there who can get the best out of her, but sadly I'm not one :( I have no problem with the TF-51 and I was able to take off and land that within 10 attempts but the Spit is a whole different kettle of fish! I've spent more time waiting for the view to zoom out and adjusting the trim for t/o than anything else! I'm going back to Mavericks and CBUs :)

Well I waited until 2.0 supported the Spit and I wish I hadn't bothered. The Spitfire may have been a sweet handling beauty by WW2 standards but the DCS version is a vicious bitch with no redeeming features. Welcome back A-10C - I always loved you!