Playing with a controller causes framerate issues?

[TigertheLion]

Frankly I'm somewhat bewildered, I've been struggling to get the game to run at an acceptable framerate (ie: more than 7 bloody FPS) and I've tried every solution posted in the FAQ. When none of those worked I decided to unplug my controller as a last-ditch effort and suddenly it runs at a buttery-smooth 60 FPS with the default settings.

Anybody have any idea why this would be a thing, or better yet know how to fix it? I'm using a wired Xbox 360 controller with up-to-date drivers as far as I can tell. I have an AMD 7900 card with an AMD FX 8320 processor and I'm running windows 7. I just finished updating everything including my video card drivers so I don't imagine they're the problem.

[reverendloc]

Hey there,

This is a weird one!

I'd recommend that you try to verify the integrity of the game cache in case there's some corrupted file.

If you run the game by launching Transistor.exe directly outside of Steam does this still occur?

[TigertheLion]

Heya,

I verified again just to be sure, no changes. Yes it still occurs when I launch directly from the .exe, also when I launch as administrator and with the launch options you guys recomend to improve performance like turning off bloom. I also tried running in offline mode and with the overlay turned off, no joy.

I appreciate any help you can give, I don't mind playing with keyboard and mouse but I'd prefer to use my controller if possible.

[[IT] Yecki]

sorry, for bumping.. I just had the same problem, went through a lot of hoops throughout the day (differend launch options, updating grafic drivers, verifying game files, compatibility mode, different resolutions and window options (btw, it seems like /noborder is currently not working) restarting pc, redownloading game, you know the usual xD)

just to find my controler appears to be the problem.. so for me ( I use a CSL 24130 Gamepad) updating the controler drivers to the proper (and not the microsoft provided HID-compliant game controler) drivers fixed the problem.. it seems to be a problem with the communication to that driver?

so to anyone else running into this: try updating to more accurate drivers