Goblin

Try warming the extension. With a heat gun or hairdryer. My base has gone to another fellow simmer in need, unfortunately :)

The King of Kings! :-D

Epic! :-D

I agree... It is hard to explain to someone who never tried VR, but breaking it down to reality is a good idea. One thing that baffles me is that you believe in the virtual environment, even if you clearly are watching a computer generated image. Graphics are good, even at low settings. But not so good you mistake graphics for reality. Even so, you look at a part of your aircraft, and your eyes shift focus between near and far objects, just like when looking at something in the real world. You need to turn your head 90 degrees to see your wing, just like IRL. I am amazed at how quickly the brain adapts to the virtual world, and start believing in what they eyes are seeing.

You are absolutely correct! NielWillis just expressed his opinion :) And Hegykc must be able to cope with critisism and disbelief when nothing happens. But I think his future customers can express their opinions without using words like trolling and scam, don't you?

In hegykc's defense, I'd like to say this. I have built a sim controller... I actually built two. Here's the story. I wanted to build a throttle quadrant, with 8 axes, 5 rotary encoders and 22 buttons. I started out with a Bodnar board, and built a throttle. As the build progressed, I learned a lot. I found better hardware and smarter ways of solving issues, problems and challenges. This meant that I rebuilt my throttle at least 3-4 times because of this. When it was finished, I found out that it was too big..! I really couldn't use it. My emotional attachment to this throttle stopped me from tearing it apart and rebuild it again. Nor did I want to sell it, because it was a DIY project, and I couldn't back it up with a warranty. So I gave it away... I then started from scratch and built a better throttle. I applied the lessons I learned from my first build, and learned some new tricks. What should've taken 3-4 months, evolved into a process of 18 months. It probably ended up costing more than than a professional simulator throttle quadrant, in the end. But I did have a lot of fun, and I learned even more. Plus I got to know some really cool dudes on some forums. Making a gamecontroller isn't for everybody. You get carried away as you learn more about the subject, and you feel the need to try new stuff - all the time. I have huge respect for guys like Slaw, Milan, Baur, etc. that produce and sell controllers at such reasonable prices. Bottom line. Cut hegykc some slack. He hasn't taken anybodys money. So what if it turns out it's all a dream. It is a very nice dream..! And if his stuff is on the market some day, we all win...bigtime!

Really nice! Yours, Sokol?

Just for Nvidia? Any certain drivers needed?

Yeah, it can't be compared to VR. But I went from a 27" 16x9 to a 34" 21x9, and this effectively just widened the screen but the height remained the same. So instead of looking through a narrow split, I was looking through a wider split, which was better... But you're absolutely correct, using screens, wide screens, 3 screens, gives a very narrow vertical view. That's what impressed me the most with VR, the vertical FoV...

He asks how it affects immersion and gameplay, not if TiR can be used with it :) I liked the curve and ultra wide (21:9) aspect ratio of my screen. Peripheral vision improved, and the curvature made it easier to view the entire screen when sitting closer to it. I sold it once I got the Oculus Rift though ;)

I have used TiR 5 with a curved 34" 3440x1440 screen. Works great!

Check if there are any double controller entries in the controls setup. It may be that your rudder toe-brakes are mapped to pitch and roll, or something similar.

This is actually quite realistic. Although it's even harder IRL, wearing a full helmet, strapped to a seat with shoulder harness, while pulling g... ;) It can be hard to find the mouse. Try a trackball, or a touchpad. They will stay in the same position.

Yep! And that's what I'm seeing in the Draken video. Disagree?

Yeah, there is a small altitude increase when performing a cobra. the Flanker has that as well. ${1}

Brewnix, Try setting the encoders up with 2 columns and 6 rows, instead. So the encoders use the same 2 columns, but individual rows.

Check this vid @ 1:50

Immovabledust, I have a Warthog base I can part with. I also have the old "gimbal" that I repaired. PM me if interested.

The TM Warthog "gimbal" can't take twist loads. The inner "ball" will break. Mine did this when I un-screwed an extension. The magnet normally sit at the end of the part of the handle that goes through the broken ball.

But from your pictures, it looks like the red wires go to column ports on the pro micro, and there should be diodes between column and the outer pins of the encoder. Center pin should connect to the different rows. Looks like it's wired backwards, as if you have connected the outer pins via diodes to row, if you know what I mean.

Brewnix, It's hard to trace the PCB image because of resolution, but it looks like you have the diodes connected to row, instead of column..? https://github.com/MMjoy/mmjoy_en/wiki/Connecting-basic-inputs-and-setting-up-software Hm? Did you switch rows and columns in mmjoy?

This is a serious amount of information to digest... Very interesting though. Thanks for putting it together.

This: http://www.realsimulator.com/html/tusba.html The Cougar TQS is, as you know, dependent on the Cougar stick electronics. The TUSBA makes it stand alone.

Ah! :-) Glad it worked! I use encoders for aileron, rudder and elevator trims, and two encoders for sight range and wingspan. Works great!

Take a look at my setup again, My first encoder activates buttons 25 & 31. These are the two that flashes when I turn the first encoder, so I put them beside eachother on the row for the first encoder. Buttons 25 & 31 will then show as "encoder" in the button list to the right. There I set a timer (I use delay 50ms) both on and off. The buttons in MMJoy will still flash together and seem wrong, because they show the hardware signals. To see if your encoder work correctly you need to 'save sets to device' and test the encoder with 'VKB Button tester'. So for you, if your encoder activates buttons 01 & 02, you must put them beside eachother in the encoder list, not 01 above and 02 below, like you have in the picture.