Author Topic: Force Feedback?  (Read 805 times)

0 Members and 1 Guest are viewing this topic.

Offline zloaf

  • 23
I just recently purchases a Sidewinder 2 with Force Feedback. Sometimes on 3.8, the game will run with decent feedback but a pretty weak centering force. How can I increase the centering force and overall force effects? Also, randomly some effects like explosions or the afterburner effect will not play


Offline m!m

  • 211
Have you tried a recent nightly build? I think there were some fixes in the force feedback code which was a bit broken in 3.8.


Offline zloaf

  • 23
I downloaded a nightly and extracted the files into my FSO directory. When I try to select it I get an application crash error and something to the effect of 0xc0000007b. Any idea?


Offline ngld

  • Administrator
  • 29
  • Knossos dev
Which FSO version did you have before? Was it a 32 or 64bit build? If you have a 32bit and a 64bit nightly (or the other way around), try downloading a nightly that matches your existing FSO build.


Offline zloaf

  • 23
I was using an x64 build and tried the x64 nightlies which seems to work for one missions before losing the centering force.


Offline deathspeed

  • 29
  • i can't think of a good avatar
    • Steam
Maybe someday God will give you a little pink toaster of your own.


Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
This thread fixed it for me:
That PR was merged, so that code should already be present in recent nightly builds. So unless zloaf downloaded a really old nightly for some reason...
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.