huzar

Fiddly 4-way switches were fixed with a bit of paint (nail paint to be exact:) Single paint layer was enough to remove any play. The main reason for all the trouble: extension and smaller base so the stick can be centrally mounted. The base is a standard ABS project box. I have left all internals and electronics intact. I was thinking about replacing the electronics with MMJoy Arduino board but I thought I won’t be able to replicate single magnetic sensor used by Saitek. Since then I found MLX90333 Triaxis Magnetic sensor, well maybe a future project. Extension is made from 20mm plastic conduit which fits perfectly and doesn’t require any modifications to the joystick (except cutting wires to extend them). First, I did 10cm extension but the throw of the stick was too big for my liking so I made second 7.5cm. Next will be the throttle. I plan to replace its board with MMJoy Arduino and add more switches / encoders. So far, I have added dedicated button for VR zoom, encoder for mouse scroll wheel that can also be pressed as left mouse button and another switch on left throttle. I’m ready for the Harrier now:) I’ll continue with the throttle once I got bored a little with it.:)

I have my x-55 for few years now and I’ve never really had any problems with it, although some of its ‘features’ are a bit annoying. Guarantee or not, I did a few small mods soon after I got it. But recently, while waiting for Harrier and Hornet I’ve decided to do much more extensive modification. First, done some time ago, was the thumb switch which was modified as two buttons. Now with nice 3d printed caps: As I have built myself rudder pedals I removed twist mechanism from the stick and reused the axis for the lever to be used for wheel brakes. Unused lever button has been wired to second thumb switch. Fixed another pinky switch so it’s easier to reach with the hand support. Double trigger switch. No more ‘spare’ switches on the stick so this one is wired instead of side button.

I'm not sure if I understand this correctly but a pot with push switch is a common thing: http://www.ebay.co.uk/itm/B50K-50K-Ohm-7mm-Dia-Thread-Adjustable-Rotary-Taper-Potentiometer-Switch-/121678471464?epid=1543776859&hash=item1c549a2128:g:iPkAAOSwfa9Zunmh

I think they fit the stick perfectly!

I see that you take it very seriously so my advise would be to drop the wood and do it in aluminium. Aluminium is not so expensive and you can buy all pieces on ebay. Also toolwise you need pretty much the same tools as for wood. For inspiration, see below: https://forums.eagle.ru/showthread.php?t=181647 https://forums.eagle.ru/showthread.php?t=171406

Good find!

I'll check the shortcut tonight but I have standalone DCS, surly dcs.exe shouldn't be in steam folder? I have steam installed but it is never running while I'm playing DCS, it's puzzling why standalone DCS is trying to run SteamVR.

I'm having the same issue with 1.5, sometimes I have to reboot PC couple of times before DCS will run in VR mode. How do you disable steam services in DCS?

They are always up to something when quiet! My kids played quite a bit with the pedals, no harms done but I don't think they would survive seating on one side for example:) And I always keep my X-55 out of their reach, wouldn't last for long in their hands:)

TLE5011 plus Arduino Pro Micro with MMJoy2 software.

I have been after rudder pedals for some time but didn't want the cheap plastic ones. I really like Baur's but at the end decided to build my own. I wanted something solid as well as good looking, easy to made with hand tools, so no custom machined parts. I actually learned to use Sketchup to help with the design, helps a lot with small details. Next thing to add is a steering dumper and maybe upgrade to CAM centering mechanism. Sorry for rusty springs but it's what I had lying around! Pictures:

What others said! After three weeks with Rift I won't be flying on 2D screen any more. Shame as it leaves out BMS and CoD, but there are couple of others simms with VR support. Immersion far outweighs the issues. I was sooo disappointed with the screen quality on the beginning, especially screen door effect was very distracting for me. I have geforce 970 so I can't just max out all settings but finally found ones that works really well. I found that increasing pixel density from 1.5 to 1.7 makes a big difference and combined with MSAA x2 plus some AA the picture is as good as probably it can get, all dials readable and target spotting not much worse than on my 1440 screen. And ASW makes it possible even on my 970. Coming from 4K you will be disappointed with VR picture but most people think it's worth it. Some don't, others can't get over motion sickness so try it if you can.

I gave it a try yesterday and I'm really impressed. Easy to configure yet it has pretty much all option I can think of and it's dirt cheap. In about an hour I have installed it, configured for DCS and successfully created comms menu (F1-F12). I'll be buying full version.

I noticed why this is happening: after starting left engine, changing engine selector switch to right engine causes it to start without pressing the start button. Not every time, maybe in 20-25% of cases. It does happen in manual and auto start mode. Looks like a minor bug? Not a problem with manual start up but auto mode ends with only one engine running, can be confusing for a new players.

Yes, it's server setting that overrides your local mode. A bit annoying right now because of the tooltips size.

ASW is great but obviously it's not a magic:) I had a time to play a bit more and I start to notice some artefacts and a bit of micro-stutter when the FPS drops below 45 but nothing really bad, at least for me. I can still play without getting sick or headache.

Thanks! :thumbup:

Win 10 here as well. For a long time I avoided Saitek software like a plague and did all bindings directly in DCS. Last week I bought a Rift and I needed the software to map more buttons on HOTAS, but it is so frustrating. Very unintuitive (but I can learn it and live with it), ghost presses, problems with loading and saving profiles etc. Bouncerj21 - no need to use rotary for Airbrakes, map them to a button. Use one of thumb rotaries for zoom, works perfectly for non-VR. Also I plan to ditch Saitek software altogether and just use DCS bindings with modifiers. Any button can be used as a modifier in DCS:) Edit: Yes, it can be problem with Windows actually, easily resolved with not using the software at all:)

I thought that ASW needs 45fps to be usable? Something interesting: yesterday finally I have set up the shark and to test it I jumped into 104th server. Had steady 22-23 fps all the time but it was smooth, no artefacts, no sickness after 2h playing (my first time in helo in Rift).

In X-55 throttle and stick are separate components, each having its own USB cable. It's probably something with Saitek software, it's piece of garbage.

The easiest option is to use samsung cloning software and clone your HDD to SSD. Leave windows, DCS and other programs on SSD and keep all other files on HDD. I have used cloned SSD for few months without any problems, no issues with DCS registration either.

I have researched this some time ago. The mic is not compatible with PC ones so it needs to be replaced or maybe one of above converters will work. The is also a problem with headset, they are designed for voice only in loud environment, they are completely useless for anything else. Saying that, if you can mode the helmet it will be an awesome addition to your pit!

Even better would be kill messages for player only, like in Open Conflict server, 'good kill' and 'you have been killed by player x in y with missile z'.

I did run traceroutes yesterday while waiting to refuel and had the same results as microvax - grnet.gr had 50-60% packet loss (pinging from UK). Greg - I know it's Uni network but maybe your IT department can open a fault ticket with grnet and provide above traceroutes? If this is an oversaturated link then probably they can't do anything, but it may by a problem with routing, worth a shot? Couple of times I came across similar issues in the past and both times they were sorted by ISP (missing or 'left over' routes).

Thanks guys, I'm glad it is useful :thumbup: