iloveu 0 Posted November 27, 2021 Share Posted November 27, 2021 Hey, So I've been here since alpha, planning to play this game till I die, or the game dies, whatever comes first I've bought a new rig, and started using the 64 bit client. I use this PC for many things that required virtualization (including but not limited to) : docker linux subsystem for win These are quite essential for my life/work so disabling virtualization is not an option. I've read that you are planning to do a case-by-case solution for whomever has this problem so, here I am  please do something, help me, something.  Response is really appreciated, Best, IloveU aka `Khaleesi Link to post Share on other sites
ElementUser 842 Posted November 27, 2021 Share Posted November 27, 2021 Those can be kept on without interfering with HoN, since that uses HyperV It's only an issue if the PC itself you are running HoN on is a VM Link to post Share on other sites
iloveu 0 Posted November 27, 2021 Author Share Posted November 27, 2021 Problem is that AMD is not using HyperV Â that is an Intel technology. And I am not running anything virtually on the machine except for the stuff i have to, docker images, kube local cluster etc, but the game runs on the host machine. Windows 10 Home Link to post Share on other sites
ElementUser 842 Posted November 27, 2021 Share Posted November 27, 2021 (edited) Sorry, you're out of luck then. This may change if we get our anti-grief/anti-smurf system into HoN - the point of the change is to prevent a subset of griefers from bypassing our ban system. Edited November 27, 2021 by ElementUser 1 Link to post Share on other sites
twoscoopsREE 15 Posted November 27, 2021 Share Posted November 27, 2021 Jesus, that is rough. I understand that smurfs abusing the matchmaking are ruinous for the community, but shouldn't the game being playable on modern technology be the absolutely utmost priority? You basically just told him that he's out of luck because he's using the AMD brand. That's insane! Link to post Share on other sites
ElementUser 842 Posted November 27, 2021 Share Posted November 27, 2021 It wasn't an intentional change, as Hyper-V should still run fine on AMD and not get falsely identified. Either way, it *should* work next patch after discussing it internally and considering all of the factors of the current circumstances. Closing thread. Link to post Share on other sites
Recommended Posts