obious

Small update. I found some time to dry-wire the non-LED version of the PCB (images below). All the switches etc fit perfectly. As I said a few posts ago, I've got a bunch of these going spare so if anyone wants one of these (or the LED version), just shoot me a message!

I do not have motion blur in DCS settings enabled. Edit: correcting my previous reply.

Hi All, Has anyone else noticed what I can only describe as micro-stutter when banking left or right in VR? this is particularly evident in the Hornet but is present in all aircraft. For my test (although it's present in every quick-start mission, map etc), I've been simply flying the quick start F-18 Nevada mission. To reproduce, when in the cockpit keep your head still and move the stick laterally left and right and you should notice (if looking at the UFC) that for a fraction of a second the console gets blurry. I've tried turning off the 'G force moves head in cockpit' setting and that eliminates maybe ~80% of the blurry-ness but its not gone entirely. I also tried this with my OG Reverb, QUEST Pro and Pico 4 and I get the same result so just to be clear, I don't think this is headset, aircraft, map or graphic setting related (hence why I'm not attaching a track file). Anyone else notice this? Thanks

Hi All, I took delivery of a new Pico 4 yesterday, installed Streaming Assistant (as I plan to use a USB cable), set all settings in the headset to max (ie 90fps, ultra quality), set SteamVR SS at 150% (just as an experiment) and to my disbelief when I put on the headset the image was horrible. The image looked like something I used to get from my OG Rift; the resolution was awful. I even opened up fpsVR to see what my system was doing and the GPU frame time was around 9ms so my system was obviously being maxed out and trying to push as many pixels to the headset as possible but for some reason, the device wasn't rendering them. Anyone have the same experience?

May want to update your signature

do you think you're asking a bit much of a 2080ti to push that many pixels? Before I had a 4090 I had a 3080ti and even that struggled to give me 90fps with half decent settings in DCS

Awesome, just what I was wanting to hear. I take it you also run the Varjo Base app on your PC? FWIW, I’ve just returned a Quest Pro; whilst the lenses and vertical FOV were excellent, the resolution left a little to be desired so I’m hoping the Aero is worth the £2.5k price here in the UK. Also, I've seen that there was/is some stuttering issues with the headset and RTX 4XXX series cards, that still the case or have Varjo fixed the problem?

Hi All, I’m thinking of buying an Aero next month but to save me reading all 23 pages of this thread, can someone tell me if I have to go through all the setup/config steps as listed out on the first post of have things been simplified since then? I currently have a Reverb G1 and whilst technology may have moved on since I bought it, I do love the fact that I can just plug it into my PC, fire up SteamVR and DCS and I’m flying pretty damn quickly. Thanks

Just had the UPS driver drop of these, I don’t have time today to wire one up so I’ll do it in a few days. Exciting times ahead

YMMV but for me (running a 4090), the only noticeable improvement I saw was that annoying loading flickering you get with SteamVR was gone. I saw next to no FPS increase at all. Using OXR with med-to-low tier hardware may work wonders but on high end gear, I think it does very little if anything. I also find the lack of ‘fpsVR’ equivalent app a bit frustrating when trying to fine-tune settings in OXR

Got it. Thanks for the write up. Mine arrives next week but I'll be sure to keep the packaging as you've given me a lot of food for thought. Is the Aero as plug and play as other devices or does it need as much tinkering as the Pico 4?

Interesting. Where did you buy from? I had to buy mine directly from Meta here in the UK so I'm hoping that they handle returns as well as Amazon. I notice in your profile that you've got a Varjo Aero. How is that? I've heard great thinks about clarity but also heard that the FOV leaves a lot to be desired.

A little late to this party but I've just ordered the Quest Pro (here's to hoping the 30 day return policy holds up if I don't like it). What software are people running on their PCs to get this to work? I've pre-empted delivery and installed the Oculus Tray Tool but for the life of my I can't figure out if I need to install something else. The last Meta/Oculus product I had was the Rift S, do I use the same software as that?

Will do. I sent them for manufacturing last week and the UPS tracking says they’ll be delivered this week at some point. Once they arrive I’ll wire one up and report back.

Hi All, Simple question really, does anyone have any plans available of the F-15E's UFC? I'm looking to design one in Fusion (including the PCB in EasyEDA) but I'm having a tough time finding any reference drawings that detail size etc. Any help would be appreciated! Thanks

For those still following this thread/project, I thought I'd turn my attention to putting together a custom PCB after spending the last few weeks learning how to design them for my F-18 build. I'm yet to send them for manufacturing as I have a few things still left to tidy up but I'm getting pretty close. I've designed these to fit within the UFC housing that I've made available right at the top of this thread and will expect the PCBs alone to cost around £20-£30 in case anyone is thinking of buying any (low volume manufacturing means I'll have a fair few spare ). I'll also be producing a LED-less version that uses purely 6x6mm tactile switches to save on the complexity of soldering and overall cost. Note that both version won't have space/be designed for any segmented displays (I primarily fly in VR). Edit: In case anyone is wondering, these are designed to be plugged directly into a Leo Bodnar USB interface board (or equivalent breakout board) and will share a common ground connection

I should have said, I don't plan on replacing the WW PCBs, these are for my own 3D UFC and DDIs

Thanks. 1. I don't plan to add segment displays as I fly mainly in VR. I also don't really have the time to figure out all the coding etc required to actually connect the segment displays to DCS (via DCS BIOS). I should have said in my previous post that these PCBs I'm putting together are designed to plug into a Leo Bodnar board/other breakout board and to not connect to a PC via USB directly; again, don't really have a time currently to investigate how to incorporate logic chips that register as USB devices in Windows when plugged into a computer. I may do it further down the line though. 2. Not currently. It may be possible to modify the PCB schematic slightly so that an axis/potentiometer could control the voltage/brightness of the LEDs but I just haven't explored that yet. Good idea though. 3. Definitely not. As much as a like what WW has produced, the additional buttons they've added (in particular to the DDIs) are a big turn-off for me. Maybe I'm a slight realism purest but my goal is to recreate only the buttons/inputs on my PCBs that exist on the real jets.

Thanks for the reply. As with others, I feel that if you make a few small changes to the UFC (most notably using 6x6 tactile switches) you'd have a near-perfect product. Please consider if you ever make a UFC V2 (I'd buy it in a heartbeat despite having the original)

You mean like this? This is just a prototype that I've been designing over the past few weeks, I'm also doing a UFC PCB. I'll be posting these prototypes for sale here in these forums once the WAGO PCB terminal blocks arrive (I'll be looking for about £15 each) as I feel like someone could use them and they'd be going to waste sitting in one of my drawers. I'll also be including the design files/schematics in the sale of each one so that people can see how they're built and modify if needed. Edit: these tactile switches have LEDs built into the unit themselves and are ridic cheap. I'm also designing PCBs that take the more standard 6x6mm tactile switches in case people don't want/need to use backlighting (for VR etc). Edit 2: added UFC picture

I doubt they would change something like this without mentioning it in the logs but it wouldn’t surprise me if they did

I didn’t say (nor do I believe other people did) that I want ‘mil-spec’ buttons/switches, I’m suggesting that Winwing make their buttons have a more ‘positive’ feel/engagement so that when I’m flying in VR, I get confirmation that a button was successfully pushed tactfully/through feeling rather than having to look at which button I’m pressing in cockpit to ensure activation. I also think there’s a difference between ‘flimsy’ and activation type; what you describe sounds like whoever manufactured those switches did so to meet contract costs hence why you call them ‘cheap’. I’ve already mentioned above that I think replacing the soft smushy buttons Winwing used with tactile switches wouldn’t cost much more to produce (if at all)but ultimately they’d know that more than I would

Thanks to the replies everyone, given me a lot of food for thought. Anyone know if Perspex is cast or extruded?

Hi All, Let me preface this by saying that I have a ‘cheap’ Chinese K40 laser that I’ve had pretty good success with when making cockpit panels (specifically for the F-18). However, laser cutting does have its limitations; the size of the unit makes bigger panels/projects difficult and gets really expensive in a hurry, they’re dangerous and can only either cut or engrave (ie there’s no ability to create depth). The question I have is, has anyone had any success with using a CNC router for their cockpit projects rather than laser cutting/engraving? If so, what are the benefits? Thanks

On my unit there wasn’t any anti-tamper/‘warranty void’ seal and to be honest, at the price point these are being sold at, I can just buy a new one if it breaks (by my hand or it’s own). I’d also say that the UFC wasn’t too hard to get into, just 12 screws