• Log InLog In
• Register

Logitech Setpoint (MX518) & SC2 Bigfoot launcher

Post a Reply

L1ghty Belgium51 Posts January 14 2012 15:14 GMT #1 I have a Logitech MX518, which has the two thumb buttons (the buttons you use to skip back and forth in your browser). I reassigned the 'return button' to 'backspace' for all my programs (so SC2 as well), so I can use it for hatchery injections using the backspace method. Up until recently this hasn't been a problem. However, sometime ago I acquired a NA account. At first I had 2 clients installed, both EU and NA and I didn't have any problems. My hard drive is quite small though, so last week I was forced to find a way to delete one of the clients. That's why I downloaded the Bigfoot launcher (thread). The problem I face now, is that when I start SC2 using that launcher, the reassignment doesn't work anymore. I can still start SC2 the normal way and then there is no problem. But when I launch it using BF (so basically when I want to play on my NA account), it doesn't work. I've tried fiddling with the Setpoint settings. I would think it shouldn't matter, since I had this setting selected for 'all other programs', but I tried adding any SC2-exe I could find, as well as the BF launcher. I also added an exe from the 'Version' folder (under Program Files\Starcraft II\), since I read somewhere that that might help. Unfortunately it didn't and when I minimize and later bring Setpoint back up, that SCII.exe is no longer in the list. Any help would be greatly appreciated. This problem hinders my playing quite a lot.

Flaiker Germany235 Posts January 14 2012 15:23 GMT #2 Why would you want to gloabaly remap the sidebutton to backspace? Can't you just assign Base Cam in the Starcraft 2 hotkey section to the button? I had a MX518 1/2 a year ago and it worked fine for me.

L1ghty Belgium51 Posts January 14 2012 15:32 GMT #3 No, I can't reassign the Base Cam in Starcraft 2 hotkeys to a mouse button. That's the reason I started using Setpoint. And I don't really have to globally remap it for all my programs, I can do it for SC2 only if I want to, but it's a preference that's not really relevant to the problem. As I tried to describe, the problem really isn't the mouse or Setpoint or SC2 or a combination of those, it's the combination of Bigfoot launcher and Setpoint that's causing the problem (I think). EDIT: I managed to fix this by starting Setpoint with administrator rights (using Task Scheduler).

Please log in or register to reply.