The Post Ninja

  • 0 Posts
  • 61 Comments
Joined 2 years ago
cake
Cake day: July 8th, 2023

help-circle





  • About two years ago, Microsoft axed the entire MR devteam, and a few months back announced they will remove MR entirely in a future update to Windows.

    I once had a Samsung Odyssey (not the +), and while the Quest 2 has a better screen resolution and much better controller tracking (and the 3 improves on both again), the Samsung’s OLED displays have way better contrast ratios, which makes it much better when running games that have dark scenes.


  • If you package it, they will come

    A lot of people use Quest standalone, but the PC VR experience is much, much better if it can be setup right. Eliminating the major issues that hold it back from working would make a big difference.

    That and a whole smorgasboard of Windows MR headsets will be useless bargain bin items soon, as Microsoft is pulling support for those headsets entirely, and I know the linux community has added support for Windows MR in Linux. They’re not bad headsets, and being super cheap would let a lot of people try out VR, even if the experience is a bit behind compared to the modern headsets (Index, Quest 3, etc.)







  • DHCP, when set up properly, makes for less work. Reservations will have the DHCP server hand out the same IP to the same hardware (MAC address) when it asks. If you have a device that is from the dinosaur age that doesn’t play nice with DHCP, then make sure you give it an address that is outside the DHCP range on the same subnet. ex: Some home routers use 192.168.1.100 to 192.168.1.200 as the dhcp range. Setting anything from 192.168.1.1 (or 2 if the router is on 1) to 192.168.1.99 is fine, as is 192.168.1.201-192.168.1.254 (or 253 if the router is on 254). However, by setting static ips, you have to remember those ips specifically to interconnect devices on the lan, whereas reserving via dhcp allows you to use local dns resolution to connect to devices via their hostname instead. In additon, you run the risk of ip conflicts from forgetting which device has what ip in an increasingly complex system, and if you change internet providers or routers, you have a lot of extra work to do to fix the network settings to get those static ips to connect.

    Alternately, just use the link-local ipv6 address to interconnect on the lan. That doesn’t change on most devices, as it is based on the MAC address, and is always reachable on the lan.




  • For IDE drives, Master/Slave is both correct and describes properly the functionality.

    Only one device can talk on an IDE channel at a time (one IDE ribbon cable is one channel). The Slave Drive requires the Master drive to be able to connect to the controller. If there is only one drive, it must be designated the Master drive.

    We don’t share multiple devices on a single channel anymore - SATA, PCI-E, these techs have only one device per channel (or only a certain number of channels dedicated per device).

    The old Master/Slave system was a hack to get double the IDE devices connected per controller channel.