Forum Discussion

elmtxvash's avatar
elmtxvash
Honored Guest
11 years ago

oculus thirft question

Let me start off by saying if you are going to talk trash please don't even respond. I'm seeking a unbiased answer to my following questions.

1. Could the fov on a homemade HMD, with a smart phone and these lenses http://www.ebay.com/itm/5x-pocket-loupe-magnifier-with-Aspheric-Lens-/251148139033?pt=LH_DefaultDomain_0&hash=item3a79987a19 ever compare to the fov that oculus has? i saw many oculus owners replacing the stock lenses with these thats why i have picked them.

2.is it possible to achieve a head tracking latency comparable to oculus by using either an gyro mouse or Wiimote Ir combo/Ps3Eye ir combo.(if youve never tried it please just be quiet. As i said before, Im looking for people who have actually experienced both not some random know-it-all on the internet)

Also as far as the latency from splashtop or kainy goes(because im sure someone will bring it up) i think i found a work around that many of you may not know about via reverse tethering on android OS.

And yes i plan on purchasing a consumer version and or DK2 when i have the funds necessary to do so..im just wondering if i can get a very similar experience for a fraction of the cost and a bit of HillBilly charm..


Thanks, I'm looking forward to your responses.

7 Replies

  • I can't answer any of your questions, but if you get that field of view thing sorted out I'd like to know what you did. I've tried every lens I could find and nothing has taken away the feeling of looking through a box.
  • "dboxvr" wrote:
    I can't answer any of your questions, but if you get that field of view thing sorted out I'd like to know what you did. I've tried every lens I could find and nothing has taken away the feeling of looking through a box.

    Even with the rift?? or are you talking about on homemade HMD's specifically
  • Jose's avatar
    Jose
    Heroic Explorer
    This is an android HMD I made in 2012 using info from MTBS3D. It's an android phone attached to a welding goggle and held in place using double sided tape and cardboard from a USPS shipping box. The lenses are the 7x ones originally recommended for the FOV2GO project. I used this HMD to play Doom 3 BFG and to watch SBS 3D videos on YouTube. It uses Splashtop over USB networking with reverse tethering.





    "elmtxvash" wrote:
    1. Could the fov on a homemade HMD, with a smart phone and these lenses http://www.ebay.com/itm/5x-pocket-loupe-magnifier-with-Aspheric-Lens-/251148139033?pt=LH_DefaultDomain_0&hash=item3a79987a19 ever compare to the fov that oculus has? i saw many oculus owners replacing the stock lenses with these thats why i have picked them.


    The magnification on the 5x lenses is too low. If you use these lenses, what will probably happen is you will be able to see the center screen divider and the outer edge of the screens, which will show up as black bars. The FOV will also be limited by the size of the screen that you choose for your HMD. Even if you use a 5-6 inch tablet, the screen edges will probably be visible.


    "elmtxvash" wrote:

    2.is it possible to achieve a head tracking latency comparable to oculus by using either an gyro mouse or Wiimote Ir combo/Ps3Eye ir combo.


    No. The sensor on the Rift updates at 1000 hz, which is much higher than the PS3 eye cam which can do around 120 hz at 320x240. Latency on the Rift is further reduced by Oculus's motion prediction algorithm.

    "elmtxvash" wrote:

    Also as far as the latency from splashtop or kainy goes(because im sure someone will bring it up) i think i found a work around that many of you may not know about via reverse tethering on android OS.


    I was able to get lower latency by using USB networking and reverse tethering to a spare linux machine which was then bridged to my network. I verified that it worked by using terminal emulator on my rooted android phone to ping the machine that hosts Splashtop. There was a significant improvement compared to Wifi, but I don't remember how much exactly.

    Even with the workaround, it is not comparable to the Oculus Rift DK1.
  • "Jose" wrote:
    This is an android HMD I made in 2012 using info from MTBS3D. It's an android phone attached to a welding goggle and held in place using double sided tape and cardboard from a USPS shipping box. The lenses are the 7x ones originally recommended for the FOV2GO project. I used this HMD to play Doom 3 BFG and to watch SBS 3D videos on YouTube. It uses Splashtop over USB networking with reverse tethering.





    "elmtxvash" wrote:
    1. Could the fov on a homemade HMD, with a smart phone and these lenses http://www.ebay.com/itm/5x-pocket-loupe-magnifier-with-Aspheric-Lens-/251148139033?pt=LH_DefaultDomain_0&hash=item3a79987a19 ever compare to the fov that oculus has? i saw many oculus owners replacing the stock lenses with these thats why i have picked them.


    The magnification on the 5x lenses is too low. If you use these lenses, what will probably happen is you will be able to see the center screen divider and the outer edge of the screens, which will show up as black bars. The FOV will also be limited by the size of the screen that you choose for your HMD. Even if you use a 5-6 inch tablet, the screen edges will probably be visible.


    "elmtxvash" wrote:

    2.is it possible to achieve a head tracking latency comparable to oculus by using either an gyro mouse or Wiimote Ir combo/Ps3Eye ir combo.


    No. The sensor on the Rift updates at 1000 hz, which is much higher than the PS3 eye cam which can do around 120 hz at 320x240. Latency on the Rift is further reduced by Oculus's motion prediction algorithm.

    "elmtxvash" wrote:

    Also as far as the latency from splashtop or kainy goes(because im sure someone will bring it up) i think i found a work around that many of you may not know about via reverse tethering on android OS.


    I was able to get lower latency by using USB networking and reverse tethering to a spare linux machine which was then bridged to my network. I verified that it worked by using terminal emulator on my rooted android phone to ping the machine that hosts Splashtop. There was a significant improvement compared to Wifi, but I don't remember how much exactly.

    Even with the workaround, it is not comparable to the Oculus Rift DK1.


    You sir, know your shit..thanks for crushing my hopes and dreams xD..and saving me around 30 bucks..I knew the ps3 eye had around 120hz but,i had no idea the polling rate on oculus was 1000..
    thats as much as my razer mouse O_o..granted i feel like its a bit over kill..but still..ehh well thanks man i wanted a well informed answer and i got one :(
  • Jose's avatar
    Jose
    Heroic Explorer
    It's not my intention to stop you from building an HMD. A lot can be learned from assembling your own unit. If you like making things, you will have fun. Good luck.
  • Mine is a homemade HMD. I just use it to play games made for it though. I tried to use Splashtop to stream but I'm not smart enough to figure out headtracking with it so it didn't work so well.
  • "Jose" wrote:
    It's not my intention to stop you from building an HMD. A lot can be learned from assembling your own unit. If you like making things, you will have fun. Good luck.

    Yeah, I know I just dont want to spoil the actual oculus experience by making something sub par. Eh I probably will anyway xD i guess it wont be spoiling much.

    "dboxvr" wrote:
    Mine is a homemade HMD. I just use it to play games made for it though. I tried to use Splashtop to stream but I'm not smart enough to figure out headtracking with it so it didn't work so well.

    Ohh alright I thought you were talking about the rift ;p.
    You can code a game but cant figure out the head tracking?? Dont sell yourself short man its not that difficult..Just a few IR leds and a webcam with a high refresh rate. Plus you've got the internet :p anybody can do anything with the aid of Google xD