Myrsnipe

I'm relatively new to VR gaming, but I belive whats happening is that your VR headset doesn't receive the next frame to render, and it injects whats called a synthesized frame that ultimately doesnt help at all, as the mainthread is almost completely locked during loading and it makes the image jump around like that. During gameplay it will happen if you have framedrops. Personally on my rig, with a now 'older' 7700k I cant really use oculus link as the video encoder sucks up too much cpu time (quest 2 isnt a native pc vr headset so it encodes the display as a video), but Virtual Desktop works fine for me as it presumably uses a less intensive encoder. Regardless this really isnt a bug on DCS side, although one can wish it didnt completely stall the render during loading

Another sticking point is that you might need to boresight the Maverick so that the TGP and Maverick seeker points at the same location, if I remember correctly this needs to be done per missile

Keep in mind a higher resolution requires a beefier machine, but you can adjust the render in DCS trough the pixel density slider under vr. My 7700k also struggles badly running the video encoder of the Q2 (the Q2 is not a pc native vr headset so it encodes display as a video, unlike the Rift), but using virtual desktop works fine although induces some wireless latency, your mileage may vary. All in all im very satisfied with the Q2, its cost value is just unbeatable at the moment.

Using my rudders I tipped over time and time again until I put on some heavier springs, it was just too easy to tumble around during takeoff with sensitive settings

While 8gb is doable, it is going to stutter some Sent from my XQ-AT51 using Tapatalk

I enjoy seeing this coming along Crosshairs, going to design my own cdu based around a keypad scanner like the TCA8418 that im experimenting with, but it's always interesting to learn from others experiences.

Oh yeah, autoroute is a bit of a gimmick, for anything simple enough for it to be reliable you can just do by hand fast anyway, and anything complex you should never trust it

This is looking very impressive, I take it you are driving it trough DCS-BIOS?

Im impressed with the illuminated lines along the keys, it seems like it is possible to get a fairly decent illumination despite the pcb being so close to the panel. There's some spots near the corners that are dimmer but it seems like careful positioning of the leds is possible

I had issues with this as well, but it turns out they WONT contact you, when you do the registration theres a line of text that tells you to send an email. It took me a few days from sending it to getting access. Viperpits is by my estimates a bit archaic, but there is for sure a very dedicated F16 sim community there. As for your throttle, an F16 style throttle would be amazing, even just a quality grip would be nice. I can always engineer my own mechanical solution, but high quality injection plastic molds are hard to do for a hobbyist

If you want to expand your gpio there are a few ways to do it, I'd recommend giving https://electronics.stackexchange.com/questions/83720/a-good-circuit-for-a-large-number-of-push-button-inputs for the basics. That said it really pays off having one arduino per button box, they can be quite cheap, especially if you buy nobrand Chinese clones (Arduino is open source so its not piracy). You can get a nano clone for ~1$, dont let this be a limit of your design. As Blue73 mentioned, if one is to go for a full cockpit then it is a lot cleaner to have a master/slave setup over a network

Fusion 360 is quite nice with its web view, doing a X plane section analysis right there in the browser was sweet

Just want to chime in that the new Raspberry Pi 4 supports OpenGL ES 3, might be relevant for the work youre doing Pindrought

It's been a while since (5 years) since last I made circuits, but am I was under the impression that 8 bit encoders took 8 inputs and had 3 outputs (since you can represent 8 with 3 bits), and that you could combine them to do 4-16 or 5-32 in this case Sent from my E5823 using Tapatalk

When the inputs exceeds the io pins of the target ic you are going to need an encoder, shift register or some other way of multiplexing no matter what, you can only create as many physical connections as the ic has io pins after all My choice would be to use 8 bit encoders, they are easier to work with than shift registers and works perfectly for this application Sent from my E5823 using Tapatalk

There is no digital display, the '1000 X psi' is just a label, you are supposed to multiply the gauge value by 1000 Sent from my E5823 using Tapatalk

I had this stick years ago when I first bought the a10c module, but after a few months I sold it due to the deadzones it had, I was extremely frustrated with it. It's a real shame, the setup was really great otherwise Sent from my E5823 using Tapatalk