Hippo

Muy bien, muchas gracias.

Thanks for replying, but I must be missing something. I don't know where to set the localisation to ES and can only find four missions under \DCS World OpenBeta\Mods\aircraft\C-101\Missions\EN\Training (no ES folder). Just to be clear, what I mean is whether there are versions of these missions with the instructor speaking in Spanish?

Hi. Sorry if I'm being a bit dense, but I can't proceed past step 36 (intercom panel). I don't have the option to press "Space", and I'm not sure if I'm supposed to do something. Are there versions of these missions in Spanish? Thanks for any help. **** EDIT **** I haven't tried yet, but I think it's probably because I haven't pulled the various knobs. I was only rotating them - I'll give it another go tomorrow. **** EDIT **** Yes, it was me. Apologies. After pushing and pulling in several knobs I managed to progress. Apologies for wasting anyone's time. I'll leave this here in case it helps anyone else. These training missions really are excellent as are the cockpit graphics, your artist(s) have done a fantastic job. Really looking forward to the advanced flight model.

Agree entirely. To add to the frustration, I pre-ordered the F-18 assuming I had found settings which would work for me. This is no longer the case, and the sense of disappointment is enormous. I'm thinking of asking for a refund.

Well on my system, with my particular settings, MSAA off is an atrocious shimmering mess. 2x is a lot better, and 4x is considerably better than 2x. Unfortunately fps goes down the toilet. When reading your comments, I wonder at how our subjective experiences can be so different.

Well I bit the bullet and allowed the latest 2.5.1 update. IMHO, my experience in VR has been completely ruined. When I test as I describe here, I used to get around 115 fps (in 2.5.0). Now with the same settings I get 50 fps. If I turn off MSAA (from 4x), I get 100 fps, but it looks like sh1t. I realise VR users are a minority, but I am now very annoyed. I have spent a lot of money upgrading my system, in the main for this game. The way ED just made the DS change on us without warning, causing a cut of > 50% of frame rate, is, I think, unacceptable.

VR zoom function?

Great post. Hope someone's listening. Yet - perhaps slightly unfair on ED. They are now the only study-level combat sim game in town; and I guess their development tactic is what they've found to work best for them - so it's that or nothing I suppose. Still, they do sometimes drop significant changes like this on us out of the blue, and with no explanation, which I find a bit frustrating.

Entirely agree. And IMHO VR without MSAA is a no-no. I'm rather gutted as enforced DR is going to FAQ it all up for me. I'll stay on 2.5 for now, but I have the F18 on preorder and assume upgrade will be necessary.

Pls ignore. Sorry.

Thanks for replying. I do not see any judders or any difference with alt-enter. With the variation in systems, settings, etc, I suppose it's not surprising that different people are having different experiences. If you can spare the time and hassle perhaps you could try what I posted here and let me know if you see a noticeable frame rate difference between full-screen and windowed?

Exactly my experience as well. I suppose it's possible to cause a problem if you click right on the edge of the VR display, but I find this to be a very unlikely scenario. And one that only a pedant would find the need to bring up in this particular discussion ;)

Please could you elaborate on this statement, what other metrics do you use?

Is this a known issue? I don't get this, fullscreen or not.

Dear Neil "How to Win Friends and Influence People" Willis, I apologise for my previous post, now deleted (by a mod who aspires to join the FSB, perhaps?). I was merely commenting on your posting style, which runs the risk of making you come across as pedantic and supercilious. More's the shame as, no doubt, away from these forums, you are polite, charming and considerate. And handsome. Still, after numerous posts of handbag swinging, we are no further as to whether running DCS fullscreen improves performance in VR. Is anyone able to provide me with a quantifiable way for me to test this on my system? As I have posted previously, my (limited) testing has so far shown no discernible difference. So far all we have are unverifiable assertions.

I'd be very grateful if you could: - Explain how you have tested to come to your conclusion - Quantify your findings Your argument does sound reasonable, although I suspect that in practice any gains are negligible on today's systems. I notice that you are not using a Rift, so are presumably not running the Oculus software layer; I think that probably makes your system different enough from mine so that comparisons may not be completely valid.

There is an option in Settings -> VR : "Cursor confined to game window" which accomplishes the same thing. I sometimes find it very useful to have the spare desktop space available for other windows. I will be keeping the fullscreen option in DCS unticked for now.

Not sure whether you're replying to me, but, yes I had to go alt-enter to go fullscreen, however, after doing that, in terms of performance: on my system, having full screen ticked or not makes no discernible difference whatsoever.

No problem. Deferred shading is a setting that has a major impact on how DCS looks and performs, you may want to check out: https://forums.eagle.ru/showthread.php?t=205841 and I also would have thought that with your 1080 you should be getting higher frame rates than me. Are you still referring only to your mission or to any? What frame rates do you get if you try the mission I suggest (I'm assuming you own the A-10C)? I doubt it is down to your CPU. When you did the test (HMD not active), were any of your cores hitting 100%? If not, then I expect the GPU probably was, and if so, it wouldn't be a CPU bottleneck. If neither were at 100% then (a) your system isn't behaving like mine or (b) something else is limiting your system's performance. At this point, I'd guess something's not right. I assume you've done all the usual - latest drivers, etc.

Just tried this. On my system, having full screen ticked or not makes no discernible difference whatsoever.

I've had three attempts at this mission (so far): 1st attempt. Requested taxi, moved slightly but then waited a bit (I was trying to work out where my wingman was). Wingman beat me to the threshold. I taxied around him and took off, but he never took off and the mission never progressed any further. 2nd attempt. Requested taxi, didn't hang around. Requested takeoff, we did both take off but I had the same result as previous poster. If I tried to come off 300 course to get to the EFATO WP, the wingman would complain. 3rd attempt. When moving from threshold to takeoff, I must have hesistated slightly and wingman crashed into me. I'm guessing this must be related with getting the taxi / threshold / takeoff sequenc having to be just so. This is not the first time I've tried this campaign. I've been away from DCS for a while, and I'm on a new install of 2.5. I had managed to complete this mission previously on 1.5. I just have a few questions, which relate more to DCS quirks that anything to do with this campaign. Sorry for the trouble, but it's the price you guys pay for knowing your stuff ;).: When holding at the threshold before requesting takeoff, I think the aircraft has to be very close to the runway for ATC to respond, i.e. at the point where the runway and taxiway meet. Is this right? Realistically, the aircraft should hold at the threshold holding point (solid yellow line on taxiway); but I think that if I do this ATC will never respond to clear the takeoff. Why is the takeoff on 31 and the landing on 13? Aircraft should be taking off and landing from the same runway, according to wind direction. Is this a DCS thing, or a mission thing? This actually bugs me quite a bit: considering the trouble that the mission designers have gone to make a very realistic campaign, this spoils the effect, as it's completely wrong. I've seen this on other campaigns as well, so I'm guessing DCS "feature"? Is it necessary to make the radio calls to ATC (request startup / taxi / takeoff) for this mission to play out correctly? I checked out Frooglesim on YouTube the other day (he's put up a video RE this very campaign in VR). Noticed that he replied to the wingman's radio check request (through the Other... menu). I'd never noticed this before. Are there other comms options like this in the campaign? Thanks.

I've been trying to find optimal settings for my system recently, so will reply to your question and waffle on a bit about my findings, perhaps we can get a discussion going - not that I'm trying to hijack your thread ;) Try the following, as then you'll be doing what I did and we can attempt a comparison: Keep the HMD on your desk, we do not want its screens to activate. Start Oculus Home. I'm running version 2.whatever the latest update is. Start DCS. I'm on OpenBeta 2.5 at latest (not Steam) Bring up the frame rate counter (ctrl - pause) Load your mission. Do NOT put on your HMD. On my system when I do this it goes full whack, so is a very good indicator for performance. With your mission sitting on the cockpit unpaused I get around 110 - 120 fps. My CPU is at around 30%, my GPU is at 100%. As soon as I put the HMD on, Oculus's routines kick in and I get a frame rate drop to 45 fps, with ocassional stutters below that. In my limited experience, you really want to see 90 fps at all times. On 2.5 I find this very hard to do without bringing down my settings; and there will always be situations (especially on airfields with other aircraft) where it's just not possible. So it's a compromise; my settings are below. I am using PD 1.2, no mirrors. I'm sure most people will consider those to be too low, but I find it's a compromise that works for me. One thing's for sure - deferred shading is a no-no for me. Cockpit shadows are also too much of a hit. As soon as CPU / GPU gets close to 100%, ASW kicks in and you get 45 fps; at this point of course your CPU and GPU have a lot less work to do which is probably why you're seeing those low percentages. I suspect you're JUST pushing your system to its limits with this mission. Then again it does seem odd, since as far as I can tell I can't see anything obvious to tax the GPU. I'm just sat in the cockpit. Some have suggested disabling ASW through an external tool (Oculus tray tool). However, my experience doing that is not good, as I then get constantly fluctuating frame rates, which I find rather uncomfortable. I just accept that ASW will kick in sometimes, it's not ideal - but it's the best option, imo. For my own testing I've been using the A-10C mission "Free flight over Black Sea region. Runway start.". No particular reason, just landed on that one by chance. Following the same procedure for that mission I also get around 110 fps (HMD off), however when I put the HMD on, I sustain 90 fps and my CPU and GPU are both around 60%. This would suggest to me that there is something peculiar about your mission. BTW, when I close the mission, I get a script error. No idea if that has anything to do with it. edit: I don't look at all cores, as I believe that is an average. My cpu % relate to the most heavily utilised core, which I think is what you should be looking at.

Sorry if this has already been asked, I did try searching. Is it possible to remove the (default) maps that appear (the ones showing the waypoint route at different scales)? I would like to be able to have none of the default stuff and only what I want. So far I've been to do this, with the exception of those maps. Many thanks for providing this brilliant app.

I suspect that this has always been there. But if I change the key for display frame rate (default Ctrl + Pause) to something else it doesn't work in-game. No matter what I change it to only pressing Ctrl + Pause enables the frame rate display.

OP - I think I know what you're referring to, but do you have a link that describes in more detail what the issue is? I don't think the default head position is correct, and have adjusted SnapViews.lua; but then I can't see all of the HUD. Just wondering if others have made adjustments, and if so what are they using? [13] = {--default view viewAngle = 40.000000,--FOV hAngle = 0.000000, vAngle = 0.000000, x_trans = 0.100000, y_trans = 0.050000, z_trans = 0.000000, rollAngle = 0.000000, },