Bullant

Works for me.

Does this work for you? http://winwing.cn:8282/en/JOYSTICK

Multiple threads about it on the Oculus support forum. Seems hit and miss, some have it some, don't. Which has me concerned that it is a hardware issue.

The audio pops annoy me more than the occasional white flash. The audio glitches happen a lot more often ...

Gotcha, I read "real ones" as "production items". I'm happy with all metal, as you said as long as the supporting infrastructure is designed to handle it, but it looks as though it is.

The first post in this thread links to two other threads that are chock full of photos: https://forums.eagle.ru/showthread.php?t=236458 https://forums.eagle.ru/showthread.php?t=235433 Also both the stick and throttle are listed as full metal construction, not resin.

Look a bit harder, there are plenty of photos and a couple of videos of people holding holding/using the physical items.

Thanks mate, I did indeed write the Hornet DCBios module. I would give a review unit an absolute smashing, that's for sure. US$800 (or $1150 in AUD) is quite a lot of money, so I'd want to be sure that someone had really given a set a thorough going over before committing that sort of money.

Yeah I know but you can't blame a guy for trying ;)

Just a reminder that I'm nice and close to China and more than happy to do a very thorough review ;)

DCSBios needs a library specific to the aircraft you are flying, has anyone even made a library for the A4 or F14? To expand on my point, and because I sounded a bit rude. DCS-Bios communicates with DCS through a series of command codes, which are unique to each aircraft. It also knows which aircraft is currently loaded in DCS and loads the appropriate library for the current aircraft. If no such library exists then you aren't going to be able to communicate with the aircraft. I wrote the F18 library and it is no small task ... edit again, I just had a look and ok it should work for the A4 and F14, someone has been busy :) I second what was said above, once you get dcsbios live preview running it makes things a bit easier.

VR is the answer you are looking for. I don't know how many times I tried and failed pre-VR, managed to hook up on the first go with my VR setup. The depth perception that VR gives you makes life so much easier.

I didn't even know you could use the rift controllers in DCS lol. I have the mouse mapped to the unused hat switch on my warthog stick. Up and Down are mapped to right click and left click. Left and Right are mapped to scroll up and scroll down. So all I do is look in the general direction of the switch/knob/lever I want to interact with, hit right on the hat to wake up the mouse courser, adjust my view onto the desired element then either us up/down to flip switches, down to press buttons and left/right to turn dials/knobs. A properly captured 3d hand(s) would be amazing, but considering the cost and vaporware status of attempts like captoglove, I am not holding my breath. edit: obviously this only works in aircraft like the hornet where I have a surplus hat switch, but I spent most of my time in the hornet so it suits my purposes for now.

That's correct. The finger lifts are only for getting in/out of idle. If you look closely you will see that there is a push through gate for the A/B though, as it should be.

Thanks for that ... I just spent 5 minutes watching the throttle video on loop. Damn sexy. Looks like the stick has quite a long throw on it as well, so no need for extensions. If you want someone to review one for you, I live in northern Australia, which is close to China :)

Video doesn't play for me. Considering it is a week until pre-orders open, I really hope we are going to see a review from a couple of trusted DCS reviewers before then.

Thanks for the quick response. It's not the end of the world, but I've been flying it like this since release and the muscle memory is strong lol. The full mapping for the Hornet should be: COMM1 -> Up (currently TX1 - Forward, should be TX4) COMM2 -> Down (correct as TX2) MIDSA -> Forward (should be TX1) MIDSB -> Back (should be TX3) Note that the MIDS radios aren't currently implemented, not sure how long until they actually are. edit: I realise I should be able to work around this by remapping the buttons to the various TX keybinds, but no matter what I do I cannot get VA to recognise button presses from my Warthog throttle in the key binding screen.

Another interesting, if conflicting data point. Upped every setting to max. OB: 30fps Release: 40fps Go figure. Note that non-vr frames dropped from 140+ to 45 in this configuration compared to the VR preset!

Finally got VA/VAICOM working well, after doing the speech training a couple of times. One thing I can't figure out though, is if it is possible to change the aircraft specific VAICOM button assignments for TX1/TX2 etc. In particular, in the Hornet the default is COMM1 is forward press and COMM2 is downward press, whereas the real aircraft is press up for COMM1. Also second the suggestion of a dedicated forum for VAICOM, it is an awesome product and combined with VR it is a game changer

TF-51D Instant Action mission Flight Over Tbilisi Intel i7 6700K @ 4 GHz / ASUS Z170 Pro Gaming / 32 Gb G.Skill DDR4 / Gigabyte RTX2080 OC Gaming / 512 Gb Samsung 850 EVO System SSD / 512 Gb Samsung 850 EVO DCS SSD / Win 10 x64 Pro 1903 Windows was rebuilt from scratch a week ago so it is very clean ... and fast. Nvidia drivers 430.86 Oculus Rift S ASW Disabled in Oculus Tray Tool (confirmed in HUD) Using my normal settings: 40fps rock solid in both OB and Release Using max settings: 27.5 fps rock solid in both OB and Release edit: I wasn't sure that I was trusting the frame rate. Put my settings to VR preset and get solid 40 in both OB/Release, and if I looked at the sky this jumped to a solid 80 in both. This is using the DCS framerate display and the Oculus in headset performance HUD. I know it's not what you specifically asked for, but I tried the framerate with VR preset in non-VR mode and got 140+ for OB and ~100 for Release.

Interesting thread, I've been thinking through the same things myself. I have always planned on building a full close to 100% accurate Hornet pit, but after buying a rift S a couple of weeks ago, I just can't give up on VR The ultimate solution is something along the lines of blender, where you can mark out/green screen the edge of your cockpit and just have the sim rendering the outside view. However I am pretty certain that as long as the cockpit is close to 1:1 that there will be no problem with reaching out and flipping the correct switch. Don't forget that the switches/knobs all have different tops on them for a reason. I've done some practice with a few practice panels and was able to get the correct switch most of the time. The hard bit is getting the panel in the correct 3d position, as I don't have my pit shell yet. What a great time to be alive!

I set up 2 SAM Sites and 2 AAA in a quick test and took them all out with one JSOW-A each, only difference was I was using TOO mode.

So the thing that caught me out ... make sure you select AG master mode BEFORE selecting the JSOW on the stores page. Took me ages to figure that out, thank goodness for Wags' videos.

Funnily enough I just rebuilt my PC so I had to reinstall the arduino IDE. I thought I'd give 1.8.9 a go and see for myself and it imported the dcs-bios library without an issue. So perhaps there is a problem with either your installation or your zip file?

Waves :)