RoyMi6

That's fair, I'm in the same bought, but I'm putting off the 3080 and Reverb G2 until next year. If you don't back this now it might never happen :D

Out of interest, for people that haven't backed, what's stopping you backing? All the alternatives are easily $200 more when you include shipping... I appreciate it's not 1:1 but given the price and extra functionality it seemed like a no brainer to me...

Cheers hippo, I don't have the KA-50 - you got any suggestions of where I might see it on the F18? I don't have shadows on (like many of us in VR I too and pushing for those frames!) Sorry if it seems like I'm trying disprove you or something, I'm honestly just trying to find out how to make it work, or if it works. So can you help me understand that if you believe it should be a rectangle, then why can't I see any change in the MSAA in your images that have that kind of change within a rectangle in the view? Why shouldn't the change be as much as I suggest? MSAA has a pretty direct relationship to image quality in the example I posted (https://i.imgur.com/mef1kY6.jpg) and heres some images that back up my understanding of what's going on - how do you suggest the changes should look? EDIT: Wait, I had a look through your other threads - are you using SteamVR? I'm on an Oclus Rift CV1. I can easily see the difference between no MSAA and 4xMSAA normally.

I can't see any difference even with just the mask size change, let alone performance. Is anyone able to provide a screenshot that shows the mask size actually having any effect? From HIPPO's own images I can't see a difference in the edges of the view where the mask should be "on" and "off" in theory.

Yeah... I'm not seeing any visible difference with the mask size... If I change my settings to Pixel Density of 0.8 and MSAA of 4x you should see a pretty substaintial difference between the centre of your view and anything outside the mask. With the MSAA mask set to 0.5 it shouldn't matter if it's bigger or smaller with whatever setting - I can't see a single pixel of difference. I mean, you should literally be able to draw a cirlcle where you can see the difference in MSAA. I am 99% sure that the MSAA mask is making no difference, and if anyone can prove it does in a framerate side I've been unable to SEE any difference so might as well be put on 0.1.

Hopefully I'm doing something wrong but at the moment the only way I can see for making changes to a lua is to remove the action "do script file" then re-add it before the mission recognises the changes... EDIT: Found a fix: https://forums.eagle.ru/showthread.php?t=178227 Basiaclly just created a "mission-loader.lua" that runs "dofile([[c:\to\my\script.lua]])" - only thing I need to do is change my loaded files to on load triggers when I want to share with others.

It sounds to me like you're having a similar problem that I had. I resolved it by uninstalling everything (both stable and OB versions of DCS) and then installing it all again. To me it was like the "dcs path" setting and "OB" tickbox weren't working in the VAICOM Pro settings because it was always trying to generate the files in the folder for my DCS Stable version. I tried just copying them over but I think there's just too many diferences between versions now that they're not compatible. You defintely need to get the logs out of your saved games folder (e.g. : "C:\Users\blah\Saved Games\DCS.openbeta\Logs\dcs.log") to find the route cause.

Hey guys, Long time programmer, first time mission DCS mission builder! What's the minimum I should have to expect to restart to test a mission and it's scripts? I'm very much planning on building the mission in LUA scripts, so at the very least if I found a bug I'd imagine I'd have to restart the mission - but does anyone have any boilerplate mission.lua that includes some sensible debuging options? Maybe something like a command menu that reloads the mission and the script in game or something? Cheers, Roy

Be aware that as of yet the optical hand tracking hasn't officially been announced for the RiftS. Oculus have mentioned that they make decisions about what is being worked on from comments made on their user voice feedback. So PLEASE vote this request up: https://oculus.uservoice.com/forums/918556-oculus-rift-s-and-rift/suggestions/38690920-optical-handtracking-for-rift-s Comments made by Oculus suggest that the differences in camera hardware between the RiftS and Quest are enough that means while the lessons learnt are transferable the systems that were developed aren't - so if we want this we need to make sure we're heard asking for it.

Awh man, does the leap not fit in the index's frunk? EDIT: Wait, looks like it does, just needs a little support. That's also assuming you've short adapter rather than regular cable.

I've also experienced this. Playing in VR and found that key bind didn't work but I could interact with the RIO cockpit buttons with the mouse. Telltale sign is that the HCU doesn't move when I move the joystick. In the control options I can see the sliders move so I know the joystick is being picked up. As with SgtPappy, the only way we could get it to work again is by the pilot getting a new plane. We also experienced it for the first time after my game crashed but have since had it again simply by trying to join as a RIO mid way through a game. I.e. my pilot was playing by himself for 20 minutes before I could join. It's almost like if Jester is in the RIO seat for a couple of minutes (say 5 mins) for any reason (e.g. taking over after RIO leaves mid flight or even just sitting on the ramp for a couple of minutes) then that's enough to reproduce the problem when a human RIO jumps in.

Ok, so what am I doing wrong here? - Downloaded and extracted to c:\games\dcs-kneeboard-builder - Ran KneeboardBuilder.exe - Set Install directory: "OpenBeta" "C:\Games\DCS World OpenBeta" - Saved games directory: "C:\Users\RoyMi6\Saved Games" - Left defaults for everything else All I want to do is add a single PNG image for the kneeboard in the F14 - Clicked on "create custom kneeboard" - Select Aircraft (F14) - Created a new group: "TESTGROUP" - Clicked modify on my "TESTGROUP" - Clicked on "import images" - Selected my 400px X 500px png file, it appears fine, then clicked "save" - Moved my group from available to "groups selected for custom kneeboard" - Clicked "build custom kneeboard for 14" That seems to work fine. If I go to the top menu and select "View -> Kneeboard Folders -> F14 Kneeboard" That brings up: C:\Users\RoyMi6\Saved Games\DCS.openbeta\Kneeboard\F14 That folder contains my 001-TESTGROUP-001.png Soooooooo I think that's everything?... But... when I bring up the kneeboard in the F14 it isn't visible... (instant action -> free flight) What am I missing?

I don't have my computer at the moment so can't check but just before you shoot off to work on other cockpits there was a knob in the RIO seat that was really hard to see what direction it was pointing... I think it was a TACAN one, possibly the radio. Don't suppose you can see about adding contrast to the lines that some of the knobs have or adding lines where they dont have one at all?

Just popping in to express my support for this! Not all of us have the time to play DCS on a daily or even weekly basis so dropping into the F14 RIO seat with VR once a month is a nightmare for me! I'm lucky I've got a competent pilot that can almost point out from memory where I need to look if I forget but for others I can imagine this being 100% necessary to be able to play. I'm eager awaiting your RIO seat update. The light up buttons are a nightmare and I'm constantly just pressing them all in order to find the functionality I want rather than pressing the right one first time - again, because I don't play it often enough. I've created mods myself for other games and applications to help solve similar problems so I know how hard it can be to find motivation when the work in creating the fix means you no longer personally benefit, but please do keep up the good work. It's massively appreciated by the quiet majority :)

Now if someone could just add wee indicators to the twisty knobs for the radio (7,8,9) so I know what the hell option I've got selected...

ohhhh snap - you can switch even in SP? Didn't know that!

And then get ban hammered so quick by Disney they won't know what hit them :(

I'd imagine for anyone without a Warthog they wont have a two stage trigger so I asumme keybinds get around this quite easy? I mean, I do, so a combination of Warthog in my right hand with Rift controller in my left could likely see me very far... How many things are on my right hand side that might be awkward to control in a normal mission? Everything Fri13 points out is all valid as well. Plenty capabilities in the Rift controllers to represent any piece of functionality in the cockpit :pilotfly:

Super excited for the F14, like everyone in this forum, but I was just thinking this morning of how usable the RIO cockpit is going to be with VR controllers. I'd imagine that all the buttons and switches are going to be as usable as any other plane, but specifically I was thinking it would be cool (as I imagine it's not going to be possible) to use the HCU by "grabbing" it with the VR controller, VTOL VR style. I think it's unlikely that anyone playing DCS isn't going to have access to a joystick but I just thought it would be a really nice a addition. I hope at the very least I'm able to bind the HCU to the Rift controllers mini joystick because I can't easily access my joystick without a lot of shuffling things around and I do hope to play quite a bit of COOP as a RIO :joystick:

Suppose I don't actually look down that much when I'm playing and when I do I'm usually not holding the joystick - so find it breaks immersion more for me.

Amazing work - can't wait for this one! :pilotfly: Just out of interest, where exactly are you gauging interest in this feature? For me personally it's a complete non issue as framerate is key for VR and I'm literally disabling everything I can to push that as high as possible. I mean it's not as if the hands are actually tracking my controllers if I'm pushing buttons so it's only accurately showing my body position 60% of the time. IMHO I just don't feel it needs to be anywhere near a top priority :huh:

Why... the hell... were you turning off the windows page file??!

Think it's still "KeyPad 5" to recentre by default.

I've not played DCS in VR for a couple of months now but I used to do this the opposite way. I'd leave my mouse cursor in the middle of my view and I used JoyToKey (https://joytokey.net/en/) to bind a joystick button to mouse click. That way I can use VR zoom with one key / button on my joystick and (with the mouse cursor in the middle of my view) I can simply look at what button I want to press and use the second button on my joystick (modified with JoyToKey) to "mouse click" on the switch. I found that worked really well and meant I never had to take my hands off the HOTAS to work 90% of the cockpit switches. I think rotary dials were the only ones that were still a bit of a pain. Note: JoyToKey is shareware and $7 for full licence. I think you can use the shareware version if you're only wanting to bind one button/key though.

Use Oculus Dash and notepad? Pin notepad to your knee in game? Helps if you can touch type of course!