Hippo

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, },

+1

I've not spent much time in 2.5, and am just investigating now, but it seems there are two options: Enable deferred shading, result: outside world looks great, cockpit looks poor. Disable deferred shading, result: outside world looks not so great*, cockpit looks good. Not a great pair of choices. Hopefully I'm missing something, and someone more knowledgeable can correct me. * those very light green trees in Caucasus look imho dreadful.

Thanks for replying. I thought that snapviews.lua didn't make any difference in VR, but I now see that it does. I realise now that what was confusing me was that the head position appears to be lowered after takeoff (rotation). I guess this is done to line up the HUD better, but seems a bit unrealistic to me, especially in VR.

Is it possilble to change the default viewpoint in VR? It is possilble to change it in non-VR by editing snapviews.lua, but this seems to have no effect in VR. I would argue that the default eye position is incorrect. For one thing, it appears correct on the ground but then seems to shift down after takeoff. I think it's too low and possibly too far forward. This has been discussed in detail here and check out this picture. I am aware that the seat can be raised with the cockpit switch, but I don't think that this has anything to do with the issue.

Completely agree. In terms of realism, it also better simulates the ability to rest your hand on a button while looking around. Please give us this OPTION.

I had assumed that it was the horizontal field of view angle in degrees. I'm now doubtful and wondering if it is the VERTICAL fov? I wonder if someone could confirm this for me?

yes

This works ok for me. Sorry to state the obvious but you do have the full path to the exe? I have (I expect your path will be different, and the quotes ARE required): Target: "D:\DCS World\bin\DCS.exe" --force_disable_VR Start in: "D:\DCS World\bin"

And apologies again. This does work; I was sure I'd tried it last night and it didn't. Many thanks.

ED: Any chance functionality to assign these commands to keystrokes (and not just joystick buttons) can be added as well?

Ah - apologies to all - I should have mentioned that I have been using 1.5.7.7741 - which is where I am seeing the issue. I have just tried 2.1.1.8491 - and indeed it works ok in that version. Sorry for any confusion.

That's great - thanks.

First question: yes. Second question: have tried both in rift and non-vr. It just doesn't work. I suspect a bug has been introduced in a recent release.

I suspect that this could be fixed by manually editing the keyboard.diff.lua (like the OP I'm hoping to bind keystrokes, which I'll then assign using my joystick software), or the <joystick>.diff.lua. If it's not too much trouble, would you mind posting the part of the file that references these commands?

Hi, Thank you both for your suggetions, unfortunately none of them has worked. I should add that I am able to bind other commands without issue.

I do have free buttons, but I don't even get that far. When I double-click the space (for keyboard or joystick) in the options to assign a control, nothing happens - the assignment window doesn't even come up. I have posted in the issues forum https://forums.eagle.ru/showpost.php?p=3221434&postcount=1

Hi, I am unable to bind the VR Center and VR zoom commands in the options (and most of the other UI layer commands). Double-clicking on the command to assign a keystroke or button has no effect. I am able to bind all other commands without issue as always. Version 1.5.7.7741. please see https://forums.eagle.ru/showthread.php?p=3221521#post3221521