You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running latest Wabbajack in guest Windows 10 in VirtualBox (hosted on Gentoo, but that's not relevant I guess), resolution 1152x864 (and I have tried 1280x1024 too), all Wabbajack windows are maximized.
Sometimes, I think it was only after longer downloads, when one download ends and the next nexusmods download page opens, for some reason it clicks on the gallery image instead, effectively stalling everything. That happens both when the VirtualBox is in and out of focus.
I only caught it in the process once so I'm not sure what exactly happens, but it now occurred to me it might also be Wabbajack glitch where the page might jump down (so the autoclicker would detect button) and then jump back up before it could actually click, but as I've said, I haven't seen what exactly happened.
The text was updated successfully, but these errors were encountered:
Hi! I'm sorry that NDF could not properly work for you. If it's clicking but at the wrong location, it probably comes from the resolution/aspect ratio handling of NDF script...
Did you run NDF in the same virtual box you are running Wabbajack?
Please also provide a log file if you are using NDF v2 🙂
I'm running latest Wabbajack in guest Windows 10 in VirtualBox (hosted on Gentoo, but that's not relevant I guess), resolution 1152x864 (and I have tried 1280x1024 too), all Wabbajack windows are maximized.
Sometimes, I think it was only after longer downloads, when one download ends and the next nexusmods download page opens, for some reason it clicks on the gallery image instead, effectively stalling everything. That happens both when the VirtualBox is in and out of focus.
I only caught it in the process once so I'm not sure what exactly happens, but it now occurred to me it might also be Wabbajack glitch where the page might jump down (so the autoclicker would detect button) and then jump back up before it could actually click, but as I've said, I haven't seen what exactly happened.
The text was updated successfully, but these errors were encountered: