Switching monitors via windows-shift-arrow doesnt workt anymore

Support Technical Support
1

After the prepatch hit I could no longer move the game between monitors via the windows shortcut (windows shift arrow). As the launch was close and that usually means chaos and long hours for the devs, I accepted this as a temporary loss.

However, we are now a few months down and RWF has finished. Can you please fix this issue? As someone who uses the (Windows) feature a lot, it would really help!

Thanks!

(in case it helps, here is my wininfo)

Summary
OS Name Microsoft Windows 10 Home
Version 10.0.19045 Build 19045
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Manufacturer Gigabyte Technology Co., Ltd.
System Model Z390 GAMING SLI
System Type x64-based PC
System SKU Default string
Processor Intel(R) Core™ i9-9900KS CPU @ 4.00GHz, 4008 Mhz, 8 Core(s), 16 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. F8, 05/06/2019
SMBIOS Version 3.1
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer Gigabyte Technology Co., Ltd.
BaseBoard Product Z390 GAMING SLI-CF
BaseBoard Version x.x
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume5
Locale United States
Hardware Abstraction Layer Version = 10.0.19041.3636
Time Zone W. Europe Daylight Time
Installed Physical Memory (RAM) 32,0 GB
Total Physical Memory 31,9 GB
Available Physical Memory 16,1 GB
Total Virtual Memory 45,4 GB
Available Virtual Memory 11,0 GB
Page File Space 13,5 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
1 Like
2

Hello! :slightly_smiling_face:
Same Problem here and everyone i asked in my guild is unable to do that aswell. So its not based on your (or my) setup.

It works in windowed mode but not in Fullscreen (Windowed)
That’s a workaround i’ve been using since, but playing in windowed all the time isn’t really a solution.
I hope this will get resolved soon.

Best Regards,
Käse

1 Like
3

This is the Technical Support forum, but it doesn’t feel like Support.
Can we get a Reply?
Something along the lines of: “We are aware and we’ll see what we can do” would be enough. Even if that’s not top priority right now we’d know that this will get addressed eventually and isn’t lost in the depths of the forum and was never read by anyone.

Best Regards,
Käse

1 Like
4

Week 42:
Just did a test run, but sadly no fix or blizzard reply yet
Launcher does still comply to windows rule, and is moveable

Week 43:
Dear forum,

It has been some time since i last wrote to you. How are things on your end? Over here the struggle continues, and im pondering if running the game in a dedicated VM would be easier… Local VM’s can still be transfered between screens, but it would take a bunch more resources… perhapse containerized? might have to check on that one. Ill let you know next time i write.

Kind regards,

Urth

5

Hello Urth,

I have good news for you. Not a fix from Blizzard, but a (crappy) workaround that ChatGPT and I came up with.

An AHK script that (somewhat) restores this function.

It’s very janky and has a lot of workarounds, but it works for me and I hope it can help you too

It uses Win+Arrow keys (because I couldn’t get it to work with Win+Shift+Arrow)

Also, the script needs to short press the Win key every time so that the taskbar is not constantly displayed.

I hope it helps and I hope blizzard fixes it properly soon

Howto Use:
Win+Arrows to move WoW.
Win+Arrow Down to remove “Always on Top”-property of the window (this is the janky part :stuck_out_tongue: )

#NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases.
; #Warn ; Enable warnings to assist with detecting common errors.
SendMode Input ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory.
#Right::
WinGet, activeWindowProcess, ProcessName, A
if activeWindowProcess != Wow.exe
{
Send, #{Right}
return
}
WinGetPos, winX, winY, winWidth, winHeight, A
winX += 1920
if (winX > 1920)
{
winX := -1920
}
WinMove, World of Warcraft, %winX%, 0
WinSet, AlwaysOnTop, On, A ; Temporarily make it Always on Top
Sleep, 30 ; Pause briefly to ensure it moves to front
return
#Left::
WinGet, activeWindowProcess, ProcessName, A
if activeWindowProcess != Wow.exe
{
Send, #{Left}
return
}
WinGetPos, winX, winY, winWidth, winHeight, A
winX -= 1920
if (winX < -1920)
{
winX := 1920
}
WinMove, World of Warcraft, %winX%, 0
WinSet, AlwaysOnTop, On, A ; Temporarily make it Always on Top
#Down::
WinGet, activeWindowProcess, ProcessName, A
if activeWindowProcess != Wow.exe
{
Send, #{Down}
return
}
IfWinActive, A ; Check if the window is still active
WinSet, AlwaysOnTop, Off, A ; Remove Always on Top if it is
WinActivate, World of Warcraft
sleep 30
Send, {LWin}
WinActivate, World of Warcraft
return
RemoveAlwaysOnTop:
IfWinActive, A ; Check if the window is still active
WinSet, AlwaysOnTop, Off, A ; Remove Always on Top if it is
WinActivate, World of Warcraft
return

1 Like
6

Thanks!
This might help for a workaround!

@Blizz, can we pls still get a fix for this?? Or at least a reason why not if its to hard?

7

I also noticed that Win+Down has some strange interaction with WoW(in fullscreen) not sure if that is part of the same issue and helps Blizz to fix that - or is completely unrelated.

Also i updated the script and added a “Howto Use” section in my earlier Post.

8

AHK is bannable software. If any of Blizzards monitoroing software detects AHK as active on your PC, at the same time as World of Warcraft, you will get a ban, which could be permanent, for “botting”.

9

Dear Blizzard,

can you please fix this…
You’re a Microsoft division, so it shouldnt be that hard to conform to default Windows behaviour

10

I doubt that. Thats like saying Python or C-Programs are forbidden, its just a scripting language. What matters is what the program does or doesn’t. And what it doesn’t, is send any kind of Inputs to the WoW-Client, it merely resizes and repositions the window. Nothing forbidden there.

11

Same issue , still no official statement or fix sadly. Seems to only be broken for win10 users

12

Still no fix, @blizzard can we at least get a reply on if its on the backlog?

13

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