

StiC
Members-
Posts
68 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by StiC
-
Thanks. I would gladly take basic support at this point. It's only the elevator trim that is an issue. Fix that, and I will happily fly the Mossie again low over the channel in tight formation.
-
So I've been trying to fly the Mossie again and this is still an issue that has not been fixed. I'm frankly at a loss as to why. DCS supports FFB sticks in several other modules and it's only the Mossie that is broken. If they can get it to work in those, why not this one. They say lack of hardware, yet somehow they got the other modules working perfectly. They say they don't support FFB devices, but they literally have a gameplay option to enable/disable FFB. Please guys look into this. If you need more information, just ask, I'll do anything to get this working properly. Right now the Mossie is unflyable unless you jump through hoops or take the drastic action of disabling FFB altogether.
-
That scratch indicates one hell of a dogfight. What does the other guy look like?
-
It's a complete slew upgrade, ready to install, with a few spare parts, just in case. You will need a 50 mil hex key to install it and the Warthog Throttle calibration tool after it's installed.
-
My pimax Crystal displays freeze when I use the buttons assigned to snap view after enabling the new quad views option in the DCS VR settings.
-
Located in Canada. Will ship to North America. Ready to install and includes spare 3D printed parts and screws. CAD $45 flat rate for Canadian addresses. USD $30 flat rate for US addresses. Prices include shipping.
-
Plug n' Play for the most part. You will need to swap axis in the FF Tune Page and the Mossie trim is completely broken for the FFB2.
-
Yes. Probably the best flight sim investment I've made.
-
Performance issues - New launcher launches ST or MT?
StiC replied to captain_dalan's topic in General Bugs
On the Settings page there is a switch on the right. -
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.
-
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.
-
an Arduino USB HID controller, composite USB controller
StiC replied to overpro's topic in Home Cockpits
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. -
an Arduino USB HID controller, composite USB controller
StiC replied to overpro's topic in Home Cockpits
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.
-
Did the Spit ground handling get updated?
StiC replied to philstyle's topic in DCS: Spitfire L.F. Mk. IX
I found that updates would turn the take off assist option on after I had turned it off in the previous version. -
Force Feedback - Which device(s) do you use?
StiC replied to Flagrum's topic in PC Hardware and Related Software
FFB2 mated with an F-22 Pro stick. Second vanilla FFB2 for WWII/civ sims.