Hippo

+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

I'm getting this issue as well. Since I only got my Rift recently, and from reading other posts, I get the feeling that a bug was introduced into a recent version? I'm using KP5 to recentre, but I would really like the zoom functionality.

I am unable to assign anything to these commands. I double click with the mouse as usual but nothing happens. Any idea why this might be? Thanks for all the info, btw, very helpful.

"The training that comes with the a10 is a must." Yes, I get that, and that I must RTFM (both of which I have done). But a checklist has been provided that is different from the one in the DCS manual. The startup procedure in the checklist has differences from the one in the training mission. The point I was trying to make was that it would have been nice (just out of interest) to have been provided with a bit of background as to where the checklist came from, and why it was decided to use it instead of the checklists that come with the DCS manual. Where there are items that are different to / not in the DCS manual checklist, then an explanation would have been welcome. I've spent hours just investigating the Ground Handling Practice Mission, it's inspired me to look into all those obscure switches I've never bothered with, and to take a much deeper look into the checklist and systems. So, all good really.

... is that in the mission builder, or in the cockpit?

Please provide the option in the mission builder to provide a debriefing text at mission completion, i.e. the option for mission designers to put in a custom debrief text dependent on mission outcome - like the briefing text at the start.

Or ED could just implement this feature... I'm surprised it's not requested more often. Off to the requests forum I go... I mean, something like this has existed in most of the flight sims I can think of going back for decades. Thanks for taking the time to reply.

Checklist questions Before takeoff checklist Left console 4. CCTVS / DVADR Remote control panel. Don't understand what I'm supposed to do. Instrument Panel 3. Armament Control Panel - SET , should items 4 - 12 be subitems a) - h) instead? Right Console 5. Oxygen system - CHECK. Don't understand what I'm supposed to do. Prior to Engine Start 14. CDU - Set for desired alignment. Don't understand what I'm supposed to do. Starting Engines 10. Flight controls - CHECK. Don't understand what I'm supposed to do. 11. AC generators - CHECK. Don't understand what I'm supposed to do. 11. Instrument inverter - CHECK. Don't understand what I'm supposed to do. Before Taxiing 16. Trim - CHECK. Don't understand what I'm supposed to do. 19. Slat operation, peak performance, etc... Don't understand what I'm supposed to do. 21. CDU data - VERIFY / ENTER. Don't understand what I'm supposed to do. AFTER EGI INS ALIGNMENT IS COMPLETE. 22. CDU Align page The thing is I don't see a message that alignment has completed. I see IFFCC NOT RDY. Should turning on the IFFCC come before this step?

RE - bindings in "View Cockpit" section of "Adjust Controls" Dear ED, Please (really, PLEASE) consider making the following additions to the in-cockpit view system. Add a new set of bindings: <modifier key> + direction (e.g. LShift + Num0 - Num9) These would match the current snap views (LWin + Num0 - Num9), but once pressed* the view would STAY CHANGED. Once at the new view, the camera view movement keys would allow you to continue changing the camera view as usual. F1 Cockpit view would return you to the default front view. I realise that there is a "Cockpit panel view toggle" (RCtrl + Num0), which tries to achieve something similar, but I find it completely impractical. * and released, i.e. no need to keep holding the keys down. ***** Supplementary What is the point of the "Cockpit panel view in" (Num0) function? It seems redundant to me. What is the point of the "View direction" (RShift + Num1 - Num9) functions? They appear to do nothing. What is the point of the "Return camera" (RCtrl + Num5)? It appears to do nothing. What is the point of the "Return camera base" (RAlt + Num5)? It appears to do nothing. Thank you.