Skip to content
Avatar

soalokin

soalokin

About

Username
soalokin
Joined
Visits
113
Last Active

Comments

  • I say, its about time survivors get something actually good. Survivors have taken a huge hit ever since the DS got nerfed. Nerfs boons, DS, DH, and more. They nerfed killer perks too, but even after the nerfs they are still pretty overpowered cough pain res. The biggest slap to the face was DH nerf. The devs obviously want us to hold W against these anti looping killers like knight/skull merchant, so I can't really complain much about MFT. MFT isnt even that good in the hands of average survivors. As for the hope combination, yeah its annoying to go up against, but at least that doesnt trigger until the late game.

    in Made for this + Hope is busted Comment by soalokin

  • most wraiths i see do this.

    in This kind of slugging shouldn't be possible Comment by soalokin

  • @SnowyLynn said:

    working for me with the following changes:

    <smbios mode="host"/> under <os>
<vendor_id state="on" value="123456789123"/> under <features> <hyperv>
<hidden state="on"/> under <features> <kvm>
<hint-dedicated state="on"/> under <features> <kvm>
<qemu:arg value="-cpu"/> and <qemu:arg value="host,-hypervisor,+kvm_pv_unhalt,+kvm_pv_eoi,+topoext,hv_spinlocks=0x1fff,hv_vapic,hv_time,hv_reset,hv_vpindex,hv_runtime,hv_relaxed,kvm=off,hv_vendor_id=amd"/> under <qemu:commandline>
<qemu:commandline> has to be added manually, add xmlns:qemu="http://libvirt.org/schemas/domain/qemu/1.0" to domain opening tag

    ive done a lot of testing, the only things that seem to be needed are the smbios, and vendor_id blocks. also you dont need to have any qemu args specifying hypervisor features, this can be done using the hyperv block. the solution looks more like this.

     <os>
  ...
  <smbios mode="host"/>
 </os>
 <features>
  ...
  <hyperv mode="custom">
   ...
   <vendor_id state="on" value="123456789123"/>
  </hyperv>
 </features>
    in Launch Error , Cannot run under Virtual Machine. Comment by soalokin

  • This fix seems to have let me play again, without having any disconnection from host problems.

    Under the hyperv block you must add this.

    <vendor_id state="on" value="123456789123"/>

    the original fix is still necessary as well. cheers.

    in Launch Error , Cannot run under Virtual Machine. Comment by soalokin

  • Agreed, there is no reason this should not be implemented.

    in Suggested Bloodweb change idea Comment by soalokin

  • looks like undoing the fix leads to the original issue. guess we are screwed for now. Would be nice to get some dev response or something.

    in Launch Error , Cannot run under Virtual Machine. Comment by soalokin

  • @TCUofficial said:

    https://forum.deadbydaylight.com/en/discussion/comment/3151143#Comment_3151143

    Consider me a curious Beaver, are you having an issue with the latest 6.3.2 bugfix patch where you are consistently disconnected from the host, showing you and the killer as having disconnected?

    You are a curious beaver indeed, I have been 100% disconnecting from host either in lobby or 30 seconds into the game. Going to try loading the game without the fix and see if that works.

    in Launch Error , Cannot run under Virtual Machine. Comment by soalokin

  • @TCUofficial said:

    Same thing here -

    I *really* don't want to put Windows on bare metal as I severely distrust it and am a longtime Linux user. This issue wouldn't matter to me whatsoever if BHVR finally implemented Proton support in EAC. The lack of it is the only reason I used a KVM.

    Hello fellow linux user, I did a bit of experimenting last night, and I may have a solution, hopefully it sticks, but it worked for me. Im using libvirt, for me I had to add <smbios mode="host"/> in the <os> section of the configuration. I hope this helps. Let me know!

    in Launch Error , Cannot run under Virtual Machine. Comment by soalokin
Avatar