Kuky

careful though, you need to have other components being able to take on more force from stronger springs also, you don't want the gimbal to get damaged. Probably your best bet (and what I did also) is to get stick extension, then mount springs on the extension shaft.

I'm sure you'll run out of ideas how to use all the flags, before you run out of flags :D

I've put TrackIR on top of the TV... while TV was on a standard height desk which I used before it was too high and I would lose tracking looking down. Then I decided to remove the desk and mount the TV lower so that my eyes are looking at about middle of the screen... and with this lower position I don't get TrackIR losing tracking any more when looking down.

Well its not your fault that its been discounted so you have nothing to be sorry about :)

What an awesome commercial :megalol:

you are bloody lucky to get it so much cheaper, unlike me :cry:

There you go, it's so easy to overlook things like that (resolution, full screen etc)

Make sure you are not running Full Screen option, you have to be in Windowed mode

EDIT: I got it now :) he's secondary is 1024 pixels vertical Fixed :P

If you use 2 monitors (side by side) you don't have correct starting X and Y coordinates, see what I modified it to

nope

Something like this (replace logical flags with ones not used in your profile) I left the /I and /O in there if you want to add more things when S3 is presses, if you don't use it you can delete the /I and /O out of the code

you fly with keyboard? :huh:

reported already (Bug#27969)

correct... provided the Foxy software allows going up to 90 logical flags. I think there is a limit but I forgot as to how many... maybe 42 or so.. you can actually try this (keep increasing the X number and when it gives you an error you got the limit :)

This works because instead of defining a logical flag as combination of pressed buttons, you created a temporarily (200ms long) logical flags (X8 and X9) that are used later to define 4 other logical conditions (X10 to X13). You used the 2 flags X8 and X9 to be true for 200ms when you press H3U key, one is with combination of S3 button and one without. So then 4 other flags are defines to say, when you press and release H3U button, if you quickly release it (less than 200ms), flag X8 is still true and H3U button is not pressed, this satisfies flag X12. If you do the same (press and quick release of H3U) while S3 is pressed also, then condition for logical flag X13 is satisfied. On the other hand, if you press and hold for more than 200ms button H3U, in 200ms the flax X8 is not true but H3U is true, so this satisfies logical condition X11. And again doing the same (press and hold H3U) with combination of S3 button, satisfies logical condition X11. In short press and relase H3U quickly... X12 is satisfied press and relase H3U quickly with S3 button... X13 is satisfied press and hold H3U... X10 is satisfied press and hold H3U with S3 button ... X11 is satisfied So basically, you use these flags X8 and X9 to create logic for short and long button release... and yes it works... I just checked my profile and I am using same logic to program short and long press buttons.

er... so you sold a faulty card? I hope you were honest about it when you sold it and whoever bought it knows about it, otherwise you just shifted your bad experience with it on someone else ;)

By the way, H3U AND NOT S3 should be just H3U NOT S3 Also, DEF X12 NOT H3U AND X8 should be DEF X12 X8 NOT H3U (both work but writing it like this is easier to read, for me anyway) Also put brackets, its easier to read as well DEF X12 (X8 NOT H3U) is easier to read than DEF X12 X8 NOT H3U

Those X keys are not keys or button presses of the HOTAS, they are logical flags or states. By the way I still use HOTAS Cougar as well as Foxy (and I love how Foxy is versatile and has so many ways and options to program things, although I don't know all of them, but do know most usefull ones, things like short press, long press, with other button combinations and standard /U /M /D /I /O combo's) Now, you define each by saying what button combination(s) define a logical flag. (each logical flag must be defined somewhere in the file, otherwise it won't work). You can not only define logical flag as some button press (or release or combinations of, but also you can set one logical flag true (and stay true) untill some other condition is satisfied, and that logical flag is 'released') For example DEF X1 (H2U) This means the logical flas called X1 is true when H2U button is pressed DEF X2 (S3) This means the logical flas called X2 is true when S3 button is pressed These two work independently, meaning if you press both H2U and S3, logical flag X1 and X2 are true (ON), when you release the buttons they are no longer true (OFF) But if you define logical flag (its actually a condition that satisfies the flag to become true) like this: DEF X3 (H2U AND S3) This means the logical flag called X3 is true when H2U and S3 button are presed at the same time DEF X4 (H2U NOT S3) This means the logical flag called X4 is true when H2U is pressed but S3 button is not presed at the same time comparing the X3 and X4 with X1 and X2, if you press just H2U or just S3 you get one condition satisfied (namely X1 and X2) but if you press H2U first X1 becomes true, but then keep it on and then press S3, X1 is no longer true and X3 becomes true... see how it works? You can even have new logical flag depend on other logical flags... really, your imagination is the limit.

It is not, I just checked it, so make sure you flip this switch to UP position, then the bombs will explode.

Well I am running my pc still on HD7970 and it's still giving me playable FPS. Like other people have said it depends on how much you want to spend. Its hard to recommend someone to spend lots of money but if you want to be safe and not get stuck with 30FPS in case the TV you get can't do 60FPS at 4K res then either get the same TV I got that has display port or check if some have HDMI port that can run 60Hz (some TV's have 3-4 HDMI ports and one of them is labeled for 60Hz). But then I would also recommend you upgrade video card to GTX980 (I am thinking getting it also)

Its not your video card, this is not a graphical bug, it's coding of the MiG-21 cockpit instruments/input bug, it has nothing to do with your video card drivers or hardware.

Long live Windows 7

only one way to find out... do it and you'll see if it works (I wouldn't know, probbaly not as there need to be registries in your PC during installation... but you never know) :)

I recently replaced my 3x 27" monitors with single 58" 4K TV, I think also single large screen (preferably a 4K one) is better (I used to use 3 viewports with 3 monitors and framerate is now better with 1 viewport even if number of pixels are bit higher)