Forum Replies Created

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • rich
    Participant
    Post count: 10

    Just another note: I just wired up another controlblock from scratch. Works fine.

    rich
    Participant
    Post count: 10

    I can confirm it now works. Awesome!

    Only issue is there is quite noticeable input lag – this is not present on the lower clocked settings or when using other controllers (bluetooth or usb).

    Any ideas?

    edit: hard gpu sync seems to have fixed it in FCEUMM at least!

    Fixes it in other emulators too, SNES runs beautifully.thanks!

    rich
    Participant
    Post count: 10

    That would be great

    It would fix my problem as well as the others in this thread as its clearly the cause.

    Keep us updated as to when the update is out! Thanks!

    rich
    Participant
    Post count: 10

    Well, I’ve actually worked out what the issue was.

    Overclocking.

    My Pi 2 was overclocked to the Pi2 setting, which is what it should run at as default to take advantage of the higher specs. However, the controlblock does not function at all on this mode. If I revert back to the lowest option for overclocking (pi 1 spec), it works.

    Now the issue is that for some reason the controlblock works fine under that spec – but that entirely defeats the purpose of me buying the pi2 in the first place. SNES hardly runs at all and most games are unplayable without that extra speed.

    Now, as you increase the overclocking bit by bit it’s clear what the issue is – the controlblock seems to go into overdrive and registers random button presses. By the point of getting even close to the stock pi2 spec, the controlblock is inputting every button at complete random, choosing random games and rendering it unusable. By the point you get to pi2 spec, it’s basically got every input as ON.

    So that’s why. And that’s why I didn’t get it resolved until I restarted retropie from scratch – because of the overclocking settings, which didn’t even occur to me as a possible issue.

    So my question is this: is there any chance of a resolution for this? It’s a damn shame having a controlblock that I bought for my Pi2 that doesn’t work at all at any spec over than the lowest setting. I’ve had to revert back to using Bluetooth controllers which operate perfectly even at pi2 spec overclock.

    rich
    Participant
    Post count: 10

    disregard my last two posts. reinstalled retropie and now it works fine! ha, what the hell.

    very happy now. got wifi installed too along with bluetooth. works like a dream.

    rich
    Participant
    Post count: 10

    Also in addition, the power switch does not function correctly. It turns the system off and shuts down correctly, but then the LED does not turn off. I also cannot get the switch to turn the Pi on.

    rich
    Participant
    Post count: 10

    I got my controlblock today and I am having the same issues – which is absolutely infuriating as I only bought it for this functionality.

    I have followed all installation steps correctly, set up the service, snesdev is not installed and the soldering and wiring is decent and correctly done. I have followed all troubleshooting steps. It still does not work.

    I have tried it with both an official SNES pad and an unofficial one. Emulation station detects the controlblock as active but then does not register any button presses during the initial controller configuration. When I unplug the controller the software goes mad and assigns two buttons by itself and continues to attempt to do so in a cycle.

    Not happy.

    rich
    Participant
    Post count: 10

    Excellent! Thanks!

Viewing 8 posts - 1 through 8 (of 8 total)