Hey, so I'm back into Wildstar. I used to use Lockdown for my SS. I tried using it again, when I reload the ui after installation i get an error. Is there any way you can help me, this is what I get:
...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: attempt to call field 'SetMouseLock' (a nil value) stack trace: ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: in function 'SetActionMode' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:335: in function <...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:313>
...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: attempt to call field 'SetMouseLock' (a nil value) stack trace: ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: in function 'SetActionMode' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:926: in function 'PulseCore' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:940: in function <...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:939>
...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: attempt to call field 'SetMouseLock' (a nil value) stack trace: ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: in function 'SetActionMode' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:926: in function 'PulseCore' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:940: in function <...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:939>
...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: attempt to call field 'SetMouseLock' (a nil value) stack trace: ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: in function 'SetActionMode' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:926: in function 'PulseCore' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:940: in function <...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:939>
...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: attempt to call field 'SetMouseLock' (a nil value) stack trace: ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: in function 'SetActionMode' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:926: in function 'PulseCore' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:940: in function <...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:939>
...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: attempt to call field 'SetMouseLock' (a nil value) stack trace: ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: in function 'SetActionMode' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:926: in function 'PulseCore' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:940: in function <...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:939>
...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: attempt to call field 'SetMouseLock' (a nil value) stack trace: ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: in function 'SetActionMode' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:926: in function 'PulseCore' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:940: in function <...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:939>
...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: attempt to call field 'SetMouseLock' (a nil value) stack trace: ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: in function 'SetActionMode' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:926: in function 'PulseCore' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:936: in function <...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:935>
...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: attempt to call field 'SetMouseLock' (a nil value) stack trace: ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: in function 'SetActionMode' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:926: in function 'PulseCore' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:936: in function <...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:935>
...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: attempt to call field 'SetMouseLock' (a nil value) stack trace: ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: in function 'SetActionMode' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:926: in function 'PulseCore' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:936: in function <...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:935>
...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: attempt to call field 'SetMouseLock' (a nil value) stack trace: ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:1366: in function 'SetActionMode' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:926: in function 'PulseCore' ...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:940: in function <...Roaming\NCSOFT\WildStar\Addons\Lockdown\Lockdown.lua:939>
Ye, that's what we're discussing so far: Carbine removed the old function SetMouseLock and moved the whole logic to a semi-hardcoded/embedded system that we cannot directly control.
I don't know if I can or Xuerian may need/want my help but the current Lockdown logic will require some overhaul. Let's give him time to work on it.
but they aren't documented by the patch notes. So it seems like we need to hook each and every single opening/opened window in order to lock/unlock the camera at will.
Sounds a bit awkward but still doable... hopefully.
The built-in autolocking camera is far from perfect.
The thing I ate the most is the fact that you cannot freely lock/unlock your camera when you have any escapable window opened (eg. inventory, player stats panel, master loot, etc.).
It's extremely annoying cause you can't play just like you're used to if, for some reasons, you also have to keep another window opened.
I was trying to figure out how they renamed the SetMouseLock API for a quick bandaid but had no luck and I had to run at work.
Can someone explain why, from time to time, a friendly party member is targeted if my current enemy target dies and there are no more hostile targets? Also why does a new target get automatically selected in first place?
Well, there's not really a lot of someones here. Mostly just me.
The dead unit is untargeted because it's a unit Lockdown is tracking as a potential target, and was the subject of a UnitDestroyed event. This is mostly intended behavior, as I found no use for continuing to target a dead mob in combat mode. Counterproductive actually. This also explains why a new target is selected in the first place.
As far as why it will target a friendly? What are your targeting settings in Lockdown?
Sorry for the late answer.
My targeting setting are only "hostile" checkbox selected. No reticule targeting.
I'd love to simply have no target at all. Having a friendly unit automatically selected is simply confusing.
Also whenever I manually select a target, it keeps on changin the selected target ass soon as I lock the mouse cursor again (usually selecting a friendly unit).
My only solution is getting close enough to the mob and tab targeting it without unlock the mouse cursor.
Can someone explain why, from time to time, a friendly party member is targeted if my current enemy target dies and there are no more hostile targets? Also why does a new target get automatically selected in first place?
0
Ye, that's what we're discussing so far: Carbine removed the old function SetMouseLock and moved the whole logic to a semi-hardcoded/embedded system that we cannot directly control.
I don't know if I can or Xuerian may need/want my help but the current Lockdown logic will require some overhaul. Let's give him time to work on it.
0
By the looks of it we now only have these new functions:
Window
New:
and Narthorn is referring to the vars:
https://forums.wildstar-online.com/forums/index.php?/topic/131228-automatic-mouse-look-feedback/#entry1365318
but they aren't documented by the patch notes. So it seems like we need to hook each and every single opening/opened window in order to lock/unlock the camera at will.
Sounds a bit awkward but still doable... hopefully.
0
The built-in autolocking camera is far from perfect.
The thing I ate the most is the fact that you cannot freely lock/unlock your camera when you have any escapable window opened (eg. inventory, player stats panel, master loot, etc.).
It's extremely annoying cause you can't play just like you're used to if, for some reasons, you also have to keep another window opened.
I was trying to figure out how they renamed the SetMouseLock API for a quick bandaid but had no luck and I had to run at work.
I'll try again later.
Cheers,
Twinkie!
0
Sorry for the late answer.
My targeting setting are only "hostile" checkbox selected. No reticule targeting.
I'd love to simply have no target at all. Having a friendly unit automatically selected is simply confusing.
Also whenever I manually select a target, it keeps on changin the selected target ass soon as I lock the mouse cursor again (usually selecting a friendly unit).
My only solution is getting close enough to the mob and tab targeting it without unlock the mouse cursor.
0
Can someone explain why, from time to time, a friendly party member is targeted if my current enemy target dies and there are no more hostile targets? Also why does a new target get automatically selected in first place?
0
Unfortunately I can't reliably reproduce it either and I only notice it when I'm in my healing spec (which doesn't happen that often).
I'm trying to better understand what's the root cause of it.
0
It seems like the cursor doesn't get properly centered when it's automatically unlocked/locked by opening/closing escapable windows.