eff

Members
 View Profile  See their activity

  • Posts

    5

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

eff's Achievements

Noob

Noob (1/14)

1

Reputation

  1. eff
    ah looks like the Validate to "true" was causing it to overwrite the files. After removing this server.cfg files is working fine. Thanks! now I just need to figure out how to get the console commands to work on the server
  2. eff
    Has anyone gotten CS2 server.cfg to work? I've tried modifying it directly, but it seems to be overwritten when the container is restarted. I followed server_default.cfg over to gameinfo.gi in csgo_core but that seems to be getting overwritten as well. I'm not seeing anything in the docker container that mentions how to set this up. Currently trying to name the server, set a password for it, and make it public. Thanks
  3. eff
    Tex8503, not sure what motherboard or GPU you have, but try going through SpaceInvader One's tutorial https://www.youtube.com/watch?v=UilWLtMYd-U. I'm running into an issue with the x570-I having the same USB controller address on different buses/IOMMU groups, but maybe you have a different board and will have different results. Just be careful when specifying the vfio-pci.id and make sure it isnt the same on other IOMMU groups. I didn't pay attention and the flash drive wasn't being read properly so I had to pull out the flash drive and fix the syslinux.cfg from a different computer.
  4. eff started following Oculus Quest w/ Oculus Link on Win 10 VM?
  5. eff
    It looks like the VM is only passing through pieces of the quest like you mentioned above. Watching some Spaceinvader One videos, the VM won't be able to or know to pass through the entire device without a USB controller. If you have a space PCIe slot you might be able solve it this way. I only have an ITX board so I'm seeing if there are alternatives.
  6. eff
    Hey Tex8503, Did you manage to get this to work? I'm running into a similar if not the same issue. When I plug in the quest I'm prompted to "allow access" on the quest, but the VM doesn't seem to see the device. I don't see it pop up in the explorer as an attached device like I do if I plug it into a bare metal setup. I managed to get the Quest working through Virtual Desktop, but that requires SideLoading and a strong network. I was hoping to use Oculus Link to see if there's better performance.