StiC

Selling Hp Reverb G2. Located in Canada and willing to ship anywhere in North America. The headset and controllers are in excellent condition. The face gasket has never been used. The cable is like new. It was used from Jan 25 until Feb 17 when I received a new headset.

I just wanted to say thank you for adding the support for modded sticks. The Mosquito FFB trim has made it pretty much useless and it's programs like this that are necessary. I'm also thinking about a collective mod using this.

I was having this issue, especially with the Apache in Syria. I did several things at once to fix it so I can't say which one actually fixed it. I upgraded from 32 to 64 GB RAM. I noticed in task manager that nearly all of my RAM was being utilized. I replaced the G2 cable. This was a coincidence. While waiting for my RAM the headset stopped working and HP sent me a new one. This could account for the USB dropout. I went into my BIOS settings and locked it down to PCI Gen 3. DCS has crashed a couple of times since, but I no longer get the headset restarting issue.

I have the same issues. It is impossible to trim properly and maintain full stick control over the elevators. If I trim nose down, it creates a deadzone on the stick aft of center. I can gently pull on the SW FFB2 and the control surfaces do not move until I reach the threshold of the deadzone. At this point the in game stick and control surfaces jump to the FFB2 current position. The opposite happens if I trim nose up. Curves and saturation do not help. In some other modules the center force moves around as you trim. In the mossie, it's as if the game moved the center force, but did not send that information to the stick and now you must reach the new center point before the game responds.

I have seen the same problem. I use a Saitek trim wheel and find that when I trim nose up it creates a deadzone when pushing the stick forward. The same but opposite happens when I trim nose down. I first noticed this issue in a cold and dark Mossie in MP. When I tried free flight in SP the issue did not occur. I will be trying a few different scenarios to see if I can nail down what conditions cause it.

When you look at the axis controls for the Mossie and select your pitch control there is an option at the bottom for FFB. You can find an option to swap axis in there.

My solution was to lean left, reset my view and return to my natural position.

I'm modding an old mouse to be used as an all in one VR input device. Apparently, the encoder I'm using to replace the scroll wheel generates twice as many pulses per detent. This is not a problem for volume/brightness knobs, but is an issue when dealing with the channel selectors in the F-18 UFC. I tried editing the 0.2 value of the following line in clickabledata.lua, but so far no luck. elements["pnt_124"] = default_button_axis_extended(_("UFC COMM 1 Channel Selector Knob"), devices.UFC, UFC_commands.Comm1Fcn, UFC_commands.Comm1Ch, 125, 124, [b]0.2[/b], true, anim_speed_default) Thanks

Absolutely incredible Warhog! You are talented inspiration to all of us cockpit builders.

Mother board in the center panel and daughter boards for the 2 side panels. My panels are based on the A-10 so I will distribute the inputs accordingly.

Sorry Warhog, but I have to correct you on this so no one else makes the same mistake I did. In the image above you need to attach the programmer to the header labelled ICSP for 16U2 NOT ICSP for ATMEGA 2560 which is located next to the reset button. Pin 1 is MISO. This should have been obvious given that the HEX file is named 16U2, but after reading Warhogs post I flashed the 2560 instead. Needless to say my board stopped working. This pinout of the programmer will help orientate the connection. Thanks overpro! After straightening out my mess above I now have everything working. I'm looking forward to finally finishing my panels.

Thanks for providing Icarus. Just a couple of things with the Spitfire. The Boost and Radiator Temp gauges are reporting different values than the in game instruments. If you could explain what the different output values represent for the the instruments in question, I could probably fix it and share the results. Thanks Edit. nvm, I found it in the Wiki.

I found that updates would turn the take off assist option on after I had turned it off in the previous version.

FFB2 mated with an F-22 Pro stick. Second vanilla FFB2 for WWII/civ sims.

Is 256 enough? https://forums.eagle.ru/showthread.php?t=117011

I've already built a nice setup, so I don't really deserve it. As I upgraded with newer gear though I would donate to the more needy. This would be no different as there is a young air cadet who has a passion for flight sims and a need for better gear.

Sorry about hijacking this thread. I'm wondering if it might be possible to put the analogue inputs to better use with voltage dividers. I'm thinking it might be way to replace multi position switches and avoid using up digital inputs. I can follow all the user documentation, but the developer stuff is over my head.

I'm wondering if this could be used on a printout, rather than a monitor. Of course you wouldn't get the visual feedback of seeing a switch change position.

Hey Craig, Here is my DIY pit. It has a USB hub and power bar, so when I set it up, it only requires a USB port on my PC, a power outlet and a video signal. The stick pedestal is removable and the pedals are hinged to fold up beneath the monitor for storage. I've cleaned up the wiring and added helios since the pic was taken. I was lucky enough to have some steel chassis monitors to make part of the structure, but the same thing could be accomplished with wood and a mounting bracket.

I have a 640x240 touch screen that I'd like to use as a UFC. The problem is, when I create the custom resolution with the nVidia software and apply it, the top half of the screen is blank. By default, Windows detects the screen as 640x480. Any suggestions? Thanks.

I think DCS Bios requires a different sketch for each aircraft. So, at the very least you will have to write the arduino each time you change planes. According to the GitHub page, there are three supported aircraft at this time. The A-10C, Huey and Mig 21. I personally love DCS Bios, but it may not be what you a looking for.

I got a copy of 1.80 beta a couple of years ago. As far as I know the only difference is the ability to assign functions to controller inputs rather than just keys. I believe development has stopped on FTNoIR at 1.70/1.80 beta. Open Track appears to be the platform going forward.

Anyone reading this should also consider Open Track. It is the successor to FaceTrack NoIR and offers some extra feature such as relative translation. https://github.com/opentrack/opentrack

FaceTrackNoIR using Point Tracker Input and Accela Smoothing is very steady and responsive. In my case, much more so than Freetrack. The only drawback is it doesn't support relative translation......YET. Even without it though I couldn't go back to Freetrack.

The material is made up of tiny spherical particles which, in essence, turn light around and send it back to the source from almost any angle. Wrinkles, creases and corners should barely be perceived by the wearer. Since it is just a single projector, no alignment is necessary. If they can nail down the headtracking, increase the resolution and FOV (all of which they are already working on) I can see a future of interactive, projected cockpits and environments.