Jump to content

Recommended Posts

Posted

With more testing I can still detect an input delay sometimes. It's just not as bad as it was before I cleared my input profile.

 

Whatever, I still can't understand how this new ffb programming made it into 1.2.6. I would have rather been told, "sorry, it's not ready yet, but we're working on it."

P-51D | Fw 190D-9 | Bf 109K-4 | Spitfire Mk IX | P-47D | WW2 assets pack | F-86 | Mig-15 | Mig-21 | Mirage 2000C | A-10C II | F-5E | F-16 | F/A-18 | Ka-50 | Combined Arms | FC3 | Nevada | Normandy | Straight of Hormuz | Syria

Posted

Hey, lets not be hard on ED here. In my case, everything but the stick shake and 05-1 sec button delay works very nicely, the reported fps drop is no longer an issue at all. Neither of the two issue are obvious at all: I didn't notice the missing shake until I read about it here, and button dealy I did not notice until I tried lock SHkval onto moving air targets... Not that easy to spot.

 

I also give huge props to ED for supporting the outdated abandonware that is our beloved msff2 :)

Posted
In my case, everything but the stick shake and 05-1 sec button delay works very nicely, the reported fps drop is no longer an issue at all. Neither of the two issue are obvious at all

 

Hmmm. I'm not sure we're experiencing the same thing. As Maxander said, the delay makes it unplayable. I was repeatedly pressing keys, believing there was no response, or holding the key several seconds before it registered.

 

But yes, on the whole, 1.2.6 is a great update. I'll just stay out of the Su-25T for now.

Valve Index | RTX 4080 (Mobile) | i9-14900HX @ 2.20 GHz | 32GB RAM

Posted
I also give huge props to ED for supporting the outdated abandonware that is our beloved msff2 :)

 

True, although I often wish CH or Thrustmaster would get off their asses and build a modern and generic FFB stick. The MSSFFB2 works, but that's as far as I'm willing to compliment it. I'd be the first to throw it in the bin given a decent alternative.

Valve Index | RTX 4080 (Mobile) | i9-14900HX @ 2.20 GHz | 32GB RAM

Posted

What's annoying its that i bought my MSFF2 on August 2000 and 13years after it still works perfectly.

 

I'm not sure other "moderns" sticks are as reliable as this one.

Posted

The msffb2 is still one of the premier joysticks for flight simming. Moreover, they frequently appear on the desks of flight sim developers.

 

I would gladly trade those 10fps lost in 1.2.5 for full ffb functionality. Sorry if I sound like I'm being unfair to ED. I am just very frustrated with how much worse 1.2.6 is for me.

P-51D | Fw 190D-9 | Bf 109K-4 | Spitfire Mk IX | P-47D | WW2 assets pack | F-86 | Mig-15 | Mig-21 | Mirage 2000C | A-10C II | F-5E | F-16 | F/A-18 | Ka-50 | Combined Arms | FC3 | Nevada | Normandy | Straight of Hormuz | Syria

Posted

I use the good old trusty FFB2 and I did not notice input lags yet, and I haven't noticed fps decrease - but I might add I upgraded my System resulting in a massive fps increase (just swapped my old PIIX4 965 + 8GB DDR2 for an i5-3570k + 16GB DDR3). I will check the fps with FFB off.

 

But I noticed something I haven't read yet. As soon as the stick starts to shake, it won't stop doing so until the end of a mission. I had shake set to 10 - 50, now I deactivated it completely as a workaround.

dcsdashie-hb-ed.jpg

 

Posted

Interesting Eldur. It seems like there are a variety of different problems ffb2 users have with 1.2.6.

 

Fwiw, there is no longer a fps drop with 1.2.6 and ffb enabled. That problem was from 1.2.4 and 1.2.5.

P-51D | Fw 190D-9 | Bf 109K-4 | Spitfire Mk IX | P-47D | WW2 assets pack | F-86 | Mig-15 | Mig-21 | Mirage 2000C | A-10C II | F-5E | F-16 | F/A-18 | Ka-50 | Combined Arms | FC3 | Nevada | Normandy | Straight of Hormuz | Syria

Posted

Hi all, as i notice, the lag problem is happening in the P-51D, Su-25 and Su-25T.

 

The BS2, A-10C, UH-1H and Mi-8 don't lag at all.

i havent tried the F-15C, Su-27, Mig 29 and Su-33 yet.

 

I use the invincible Microsoft Sidewinder Force Feedback 2.

Posted

I'm pretty confident it's happening in the Ka-50 as well -- it would explain a problem I've been having lately with the trimmer. Going to test it when I get home.

Posted (edited)
But I noticed something I haven't read yet. As soon as the stick starts to shake, it won't stop doing so until the end of a mission. I had shake set to 10 - 50, now I deactivated it completely as a workaround.

 

Did some more testing, the problem is not solved by zeroing shake. Apparently, instead of applying stick force, the stick shakes, but as mentioned above, once it started, it won't end. Makes flying with FFB not amusing for me... and without, I don't want to :D

 

Edit: 09-18-2013

 

To be precise, it seems that a shake force is applied to the stick force as it doesn't shake while the stick is in it's momentary center (depending on trim).

 

After some more testing I'm quite certain that this problem does not occur with Track IR deactivated. I use TIR 4 Pro with 5.1.300 software (on Win 7 Pro 64).

Edited by Eldur

dcsdashie-hb-ed.jpg

 

  • 3 weeks later...
Posted

MS FFB2 Gets stiff instead shake

 

Hi all

 

After Yesterday second 1.2.6.xxxx update and the FFB problem still persists(MS FFB2, gets stiff instead of shake when stalling)

 

Reverted to 1.2.5.6508 and problem is gone.

 

Can anyone point at the files involve in this problem so it would be possible to fix it till official patch comes?

 

Thanks

GP

My rig:

WIN 10 64bit

I7 6700k

Gigabyte GTX 1080 TI

16GB RAM

650W PS

MS FFB2

Posted (edited)

I always use win-merge to compare changes whenever a new update hits the surface , so I have a estimate what mods are save to use and work after updating and which will probably broken and need a edit .

And I made a research about the FFB functions.

 

The FFB functions are probably hard-coded in some DLL files and not accessible by the end-user.

Just swapping some files will not work.

 

So we have to wait till it's got fixed by ED to get this functionality back:

 

 

Edited by PeterP

Posted
I always use win-merge to compare changes whenever a new update hits the surface , so I have a estimate what mods are save to use and work after updating and which will probably broken and need a edit .

And I made a research about the FFB functions.

 

The FFB functions are probably hard-coded in some DLL files and not accessible by the end-user.

Just swapping some files will not work.

 

So we have to wait till it's got fixed by ED to get this functionality back:

 

Thanks a lot PeterP

 

Hope it will be fixed soon:(

 

GP

My rig:

WIN 10 64bit

I7 6700k

Gigabyte GTX 1080 TI

16GB RAM

650W PS

MS FFB2

Posted

ED Team please

 

Reverted to 1.2.5.16508 and the problem gone.

 

Any news about upcomming fix?

 

Thanks

GP

My rig:

WIN 10 64bit

I7 6700k

Gigabyte GTX 1080 TI

16GB RAM

650W PS

MS FFB2

  • 3 weeks later...
Posted

1.2.6 update 3

 

Still no shake, only stIffening Stick upon stall:huh:

My rig:

WIN 10 64bit

I7 6700k

Gigabyte GTX 1080 TI

16GB RAM

650W PS

MS FFB2

Posted

FFB2 lagging

 

while I too have no shake with my FFB2 just a stiffening before stalling (that sounds a lil' dirty...:music_whistling:) my problem is a kind of lagging with stick response (slaggishness with the target designator and even turning the outside view camera (F2 key) around) mainly when there's a busy inviroment with enemy fighters missiles flying and so forth. interesting enough, it happens in FC3 module, but not with the A-10C. any idea what could be causing it?

 

SB11

CPU: intel Core i7 9700K ~ 3.6 GHZ , nVidia RTX2060 SUPER, 32GB 3300 Mhz RAM, DELL 24" LED. Windows 10

Posted
while I too have no shake with my FFB2 just a stiffening before stalling (that sounds a lil' dirty...:music_whistling:) my problem is a kind of lagging with stick response (slaggishness with the target designator and even turning the outside view camera (F2 key) around) mainly when there's a busy inviroment with enemy fighters missiles flying and so forth. interesting enough, it happens in FC3 module, but not with the A-10C. any idea what could be causing it?

 

SB11

 

That's a new bug that came with 1.2.6 and the FFB2. It is already confirmed by ED and they'll hopefully have a fix for it with 1.2.7.

http://forums.eagle.ru/showthread.php?t=103586&page=11

P-51D | Fw 190D-9 | Bf 109K-4 | Spitfire Mk IX | P-47D | WW2 assets pack | F-86 | Mig-15 | Mig-21 | Mirage 2000C | A-10C II | F-5E | F-16 | F/A-18 | Ka-50 | Combined Arms | FC3 | Nevada | Normandy | Straight of Hormuz | Syria

Posted

I sure hope so, ED tends to fix stuff and only then find out that they had broke other stuff. (1.2.5 didn't have this problem) I know it's like that in an ongoing project like DCS but please...1.2.6 was the buggiest update ever..:\

 

SB11

CPU: intel Core i7 9700K ~ 3.6 GHZ , nVidia RTX2060 SUPER, 32GB 3300 Mhz RAM, DELL 24" LED. Windows 10

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...