AlpineGTA

If it's useful, these are the settings I'm using btw, with the system specs in my sig. I could turn down the eye candy a bit to get higher FPS but I only have the time to play mostly simple Instant Action missions, so I like to turn up the eye candy as mush as possible. I'm sure I'd have to turn some of the settings down if I played online or heavier missions. I can even just about play missions on the channel map with these settings, although my FPS does take a big drop on that map.

All set. :thumbup:

I had only a quick free fight the other night in the M2000 on the Caucasus map. I tried all Ctrl+Number pad 1-4; I didn't notice any difference in FPS between any of them (I get around 40FPS in all four), but I'm sure there was no ghosting when I used Ctrl+Number pad 1 (ASW off). It was only a quick impression though using the F3 flyby view. I will need to do more flying to be sure.

Great! Thank you.

I've just ordered the Gladiator-K to replace my T16000 stick. Does anyone know what the measurements are between the mounting holes in the base, or where I can find them? Thrustmaster usefully provide a link to the dimensions for their T16000 but I can't find anything similar on the VKB website. I want to machine a new mounting plate for my homemade chair mount so that it's ready for mounting before it arrives. Thanks.

Thank you. I'll give it a try.

Do you need to use Oculus Tray Tool to disable ASW or can you do it in the Oculus software? I don't use Steam, I'm running DCS stand alone set to open in VR automatically, which automatically opens the Oculus software in the background. I've tried OTT but didn't notice any performance improvements no matter what settings I applied. In fact, I found the image quality in VR to look worse, so I uninstalled it as it just seemed like another unnecessary background process to have running. I would like to try disabling ASW though to see if it improves the ghosting.

https://gpu.userbenchmark.com/ This website is a good resource for researching and comparing GPUs If you're looking to upgrade your joystick at some point, I'm using the Thrustmaster T16000M and think it's a really good balance of performance and features for the price. It has lots of extra buttons on the throttle and joystick base.

I already have the Tomcat but I've just purchased the Viggen after trying it out over the past two days. I've been really impressed with it. It's a really nice model, good cockpit with nice textures, easy to read dials (I fly exclusively in VR) and a joy to fly. And it must be the easiest DCS plane to land that I've ever flown. After my first quick cold start flight I put it back down on the tarmac no problem, without even reading the manual or knowing how to switch to any landing modes, no auto throttle, no reverse thrust, or anything! Just by eye and seat of the pants. And it looked a perfect touchdown on the replay. :) That's a testament to the plane, not my skills! The only issue I seem to be having is the cockpit lights not working when I'm rotating the lighting dials in the cockpit. I read in another thread that there's been an issue with the cockpit lights not working; it says it's been fixed but is there still an issue with them?

It seems like everyone's flying around in the Huey at the moment to soak in the details. I did the same myself last night. :D Yes, it's a bit slow and stuttering at times with my PC spec but I still found it massively enjoyable to just fly around and admire the scenery.

I was getting low FPS on the Supercarrier too. I've found the biggest change you can make in your settings that will noticeably improve your FPS is to change your cockpit resolution to 512 and pixel density to 1.0. Previously I was using a cockpit resolution of 1024 and pixel PD of 1.3 and my FPS was in the low teens on the Supercarrier, now it's still not fantastic, probably low 20s, but at least it's just about usable while I'm on deck. Once I'm airborne it goes up to around 40FPS. I was worried the lower cockpit and PD settings would make my cockpit an unreadable blurry mess but surprisingly it's not that terrible. I'm used to using the zoom a lot anyway to read my dials.

You said in a previous post that you'd tried it with all internal lighting turned up to max but in those two pictures you posted I don't see any cockpit lights on. Are you sure you've tried it with the flood lighting on? I'm assuming you know this, but you know that the Mirage instrument light dials have an inner and outer dial? The inner one turns on the orange back-lighting to the dials and the outer one turns on the green cockpit flood lighting. I too find some of the Mirage cockpit switches dark and difficult to see but I have my gamma turned up and, if your fps can handle it, turning on the flood lights really does make a big difference and allows you to see the small switches in all the dark nooks and crannies. You may already know all this but just checking to be sure in case it's a help.

I had it happen to me for the first time yesterday whilst I was in Google Earth VR so I'm guessing it's not a DCS related thing but something to do with Oculus.

I used to have all my curves set to 25 but after seeing or reading a good tutorial somewhere, I forget whether it was something I read or a YouTube video, sorry I can't remember now, I have my curves set to 15 and a dead zone of 6 and I'm finding it's working well for me so far on all of my aircraft.

Thanks, I'll try a different port. Seems odd how it only mainly happens on OB though and only with DCS. It never happens when playing any other VR games or apps.

I get a lot of "Display port not connected" error messages and crashes running 2.5.6 OB. The picture will freeze then the view will go off to the left. After a few seconds the display port not connected error message will disappear in my Oculus software, the picture will un-freeze, but only on my monitor, inside the headset the display will be black and even though I can move the headset around and see DCS still running and moving around on screen, it remains blank inside the headset. The only option I have is to close the Oculus software and restart. It occurs at random. Sometimes it happens within moments of starting DCS, other times I can go a good two hour session before it crashes, or if I'm luck, not at all. It barely ever happens when I'm running 2.5 stable. It's only ever happened once or twice on stable, most of the time I have no problem with crashes on that version.

I installed the WW2 assets pack on the Stable and tried again the Spitfire, the Mirage and the Fw 190 and, apart from the occasional stutter when I was flying close to the B17 in my Spitfire, which I put down to my PC specs, it was fine. So for me at least it seems to be an issue with the OB. Hopefully future updates to the OB will fix it.

Since today, I'm having the same issues. The Normandy map is no longer playable. It freezes and crashes DCS and sometimes hangs with a painful flickering bright white light. I downloaded the FW-190 module to try and at first I thought it was something to do with that module, but I tried it again with the Spitfire, which I own and I've used the Spitfire on the Normandy map fine previously and it was still freezing and crashing. I think I last flew on on the Normandy map, maybe two days ago and it was fine then, so I don't know what's changed, I haven't altered any settings. I might add, I fly exclusively in VR and even with my middling specs I've previously been able to fly on the Normandy map fine without these issues. Sorry, I should add, this is on the Open Beta and free flight mode. I tried to fly my Spitfire in free flight on the Stable release and it wouldn't let me, it said I needed WW2 Armour & technics installed. I'm guessing this means the WW2 assets pack? I installed the WW2 assets pack on the Open Beta version but don't have it installed on the Stable. I flew the Mirage 2000 and TF-150 Mustang in free flight on Stable and they ran fine - I was getting my usual 25 - 40 FPS in VR, depending on altitude and terrain. So I'm wondering if it's something to do with having the WW2 assets pack installed that's causing the frame rate issues and crashing? I'm going to install it on the stable version and test again.

I have the T16000 and am very happy with it. I looked at the Logitech controllers but was put off by some reviews of poor reliability. The stick has the same 16bit control system as the Warthog stick and I find it very smooth and precise. I would prefer if it had a couple more hats and buttons on the stick and a front pinky lever for nose wheel steering would be useful, but it makes up for it with the 12 base buttons, which I find useful for assigning things like flaps, landing gear, master arm switch etc. Especially if you fly in VR. You can also twist the stick for rudder controls if you wish. The best part for me is the throttle, it has plenty of hats and buttons all in the right places that fall easily to hand. And they closely mirror the positioning of those found on real jets, compare for example to the real F/A-18 throttle, which really helps with easy control mapping. There are also paddles on the front that you can use for rudder if you don't want to use the stick twist. I also like the smooth sliding action of the rails. I think it's one of, if not the best HOTAS out there for the price. Also, there are lots downloadable control profiles for this HOTAS. I believe it's also possible to pair the Thrustmaster Warthog control stick with the T16000 throttle, if you feel like in future upgrading the stick to something with more hats (although you would lose those buttons on the base).

If you mean within visual range dogfighting, where you don't need AMRAAMs, one of my favourite FC3 aircraft is the SU-27. Using the helmet mounted sight and launching an off bore-sight R-73 is a real boon in a dogfight. One of the deadliest missiles in DCS. There's a great guide by Santi871 on using the SU-27 here: https://drive.google.com/file/d/0By_jGRnxUhnUSGNLeGNZS0R1aG8/view If you prefer to learn a high fidelity module with a fully clickable cockpit to dogfight with, I think the Mirage 2000C is quite an underrated module. It gets criticised for it's poor BVR missiles and it can only carry two heat seekers, but if you want a fairly modern fly-by-wire jet I think it makes an interesting alternative to the F-16 and F/A-18, if you take the time to learn it's systems. I'm really enjoying it.

I'm new to DCS myself. I started with the SU-25T that comes with the game, then I bought the Flaming Cliffs module because it seemed like a good 'Starter Pack' and it gives you a few extra aircraft to play around with, albeit they're not high fidelity models with clickable cockpits. But it does give you a bit more variety to play around with and get a feel for DCS. For my first high fidelity module I pre-ordered the Super carrier which automatically gives you the F/A-18. I think it's a good all round choice for your first hifi module. You can do bombing as well as air to air with it, it's a very popular module so there's lots of help and support out there for it. And I actually find it really easy to fly, compared to the SU-25T. In some ways I find the clickable cockpit easier to learn. I prefer to learn in what order to click switches rather than memorising keyboard shortcuts. Everyone's preference is different of course but personally I'm finding the F/A-18 a lot of fun.

dburne and A2597, sounds exactly like what I'm looking for. Thanks very much.

Oh yes, a good point, Sorry, I forgot to mention, I did also upgrade my power supply to a 700W unit to make sure I had enough juice to power my new graphics card.

I know I can go in to settings to define my own controls, but which specific section am I looking for? Is it somewhere in the general tab, the axis controls tab, etc? Do I need to have the Oculus controls disabled in the VR section, or something set in a specific way in the VR section? I'm looking for specifically where do I need to go and what do I need to assign in the control options to do this? Thanks.

Hi, I've just bought a Rift S and starting playing DCS in VR, but I'm not keen on having to reach for the Rift hand controllers to operate the cockpit switches. How do I map the controls so that I use the on screen cross that mirrors where I'm looking and then map a button on my Hotas to act as the mouse click to operate whatever switch I'm looking at? Thanks.