Please help ScriptPlayer crashing

Every time I launch ScriptPlayer and try to connect Handy directly, ScriptPlayer simply crashes.
Yesterday everything was fine, but today it’s already crashing. Although I didn’t change anything and nothing has changed in the computer or Windows.

EDIT: For a moment the best solution what I can find, it’s downgrade the handy FW to v3 and ScriptPlayer to 1.2.1

3 Likes

Happening here too!

Not having any issues with ScriptPlayer. No problem connecting to handy directly either.

Same issue. Crashing when connecting to The Handy. Gave the crash log to chatgpt and it seems like a simple API fix. Just gotta wait on someone to update.

I’m also having the same issue starting today

rip no work for me aswell :frowning:

Same issue here for me too. Started on the 22nd and is still happening. ScriptPlayer 1.2.2.454 on Windows 10 Home. (Laptop, traveling) Handy is on Firmware 4.
Might have coincided with the downtime shown here.

Checking on the Handy website side of things.
new.handyfeeling.com seems like it no longer has firmware update and change pages. It mentions going to handyfeeling.com.

Going to handyfeeling.com and connecting my Handy v1 shows that a firmware update is available. I’m currently on 4.0.18.

If I click on Update, the new page loads but the section that would provide the new firmware seems stuck and won’t load.

i uninstalled 1.2.2 and installed 1.2.1 all working at the moment

1 Like

Did you also downgrade the Handy to firmware 3? As mentioned in my newest post above, I can’t get to any firmware pages at the moment.

im running 4.0.18cba495e6 it works with script player 1.2.1

1 Like

Good, I thought it was just me. I tried factory resetting my Handy, and also reinstalling script player

It might have been the recent Windows 11 Update 25H2 that caused some issues with the new Handy API, there is a new version, that should fix it:

(SP 1.2.1 is for old Handy FW, 1.2.2+1.2.3 for FW4)

6 Likes

Just tried it. It works again! Thank you!

2 Likes

thankyou for the update

1 Like

In case it stops working again: I’ve added a new version 1.2.3.464 which undoes yesterdays fix.
I think they changed the API or something … (same link)

2 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.