Input Delay in Dolphin 4 compared to 3.5?

[hariooo]

So I've tried both the latest stable release and the release some people are using for PM netplay (4.0.2 and 4.0-648) and they both have noticeable input delay (2 frames or more) over the version I was using previously, 3.5. I'm using default settings (I've only enabled show fps and input in Graphics settings) and my framerate is a constant 60.

I'm using an official Gamecube controller on a Raphnet adapter, and like I mentioned, it worked perfectly on 3.5.

Any suggestions?

[JMC47]

If 4.02 is affected, then it's on your end. 4.0.2 has no important changes. If you're really concerned, try 3.5-2468 of the Dualcore Netplay branch before we changed the netplay input scheme.

Also, try using a Wiimote (even emulated) and compare. I'd be curious. I noticed that my mayflash has 2 frames worse delay than my Classic Controller via bluetooth, but I thought that was just Mayflash sucking ass.

[hariooo]

Alright I just did some more testing and it may have just been the Radius setting being set to 70 by default on version 4 for some reason.

[JMC47]

It's set to the same thing in 3.5; you probably just used an input configuration setup that is meant for older builds.

[hariooo]

I'm looking at the GCPad settings for 3.5 right now and the Radius setting does not exist, at least not in the same place. It also definitely feels the same as Radius being set to 100 in 4.

For what it's worth the difference was quite huge. With the Radius at 70 I couldn't dash using the same analog stick motion that I could at Radius 100. It took longer somehow so I interpreted it as lag.

[JMC47]

Yeah, it's a bit silly sometimes. I really think it should be 100 by default, but most people don't have GC adapters like us.