Jump to content

shashkes

Verified Members
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About shashkes

  • Rank
    Settler

Recent Profile Visitors

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

  1. This is showing in the headset so i have no way to show you, it says "connection timeout" @chengnay @Tony PH Lin
  2. BTW I tried to get this to work on another computer and after updating Nvidia drivers there and starting the server i'm still getting a time out error. Can there be something wrong with the headset?
  3. so I got some advice from someone else at vive that seemed to help actually start the sever but still getting time out errors, and yes i checked the ip of the device and reinstalled and went through the process you outlined. The advice i got was to go into Nvidia control panel and make sure the gpu of NVIDIA was selected (in mine it was on auto select, you can see the image attached). I needed to re enable the intel card to get into nvidia control panel. This is the log that i get now, so you see nvidia is in [0] location and it seems to actually start. after I start device apk should i
  4. Server is connected! but i'm still getting time out error after installing the device apk 😞 I've tried stopping everything and starting it and still not connecting... so close, uploading direct config preferences too The HmdList is loaded! 1 2 OnPipeInfo : Pipe Server Started Pipe accept begin. [2020-10-16 01:53:16.736 -7 6100 DEBUG logger] [Main] Set Log level as DEBUG [2020-10-16 01:53:16.743 -7 6100 INFO logger] [Main]dpServer Version: 0.4.5.3 [2020-10-16 01:53:16.743 -7 6100 INFO logger] [Main]Init() Config from json: H265:false, Bitrate:23000000, GOP:100, EncodeHQ
  5. any instructions on how to do that and how that will affect my computer?
  6. ok that was a big adventure, i used DDU to uninstall the Nvidia (i don't think i have an AMD driver) and then reinstalled but still getting the same error 😞
  7. Unity 2018.4 LTS + Wave SDK 3.1.94 as recommended here:
  8. Hi, thanks for your support, i ran the server from cmd and got the log below with the errror that Nvidia drivers might be too old. I updated my nvidia drivers using Nvidia Geforce app to latest driver. version is now 456.71 released 10/7/2020. I restarted the computer and ran the server again but still getting the same error that Nvidia driver may be too old. any idea what is going on? The server config:.\config\serverSetting.setting is loaded! The HmdList is loaded! 1 2 OnPipeInfo : Pipe Server Started Pipe accept begin. [2020-10-15 13:45:09.903 -7 12488 DEBUG logger] [Mai
  9. I'm pretty sure the dpserver.exe isn't launching the server the command prompt flickers on for a second and then closes even when i try running it directly from the file system. Any ideas why?
  10. I think the timeout error just appeared behind my head so I thought it was a black screen ...
  11. I stopped the build and the server and started again just to get the time out error again. but even when its timed out the device controls the unity view. is there a way to see if the server is running. the cmd window immediately closes when i run the server from unity. can i run it manually instead of from unity?
  12. Thanks... some progress... the headset is now controlling the view in unity... when i move it the view moves but inside the headset its total black screen
  13. i've also tried ip config and put in the two ipv4 different addresses Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::6992:5893:3ac1:c2b2%5 IPv4 Address. . . . . . . . . . . : 192.168.137.1 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : Wireless LAN adapter Wi-Fi 2: Connection-specific DNS Suffix . : hsd1.ca.comcast.net IPv6 Address. . . . . . . . . . . : 2601:643:8301:6510::6c60 IPv6 Address. . . . . . . . . . . : 2601:643:8301:6510:d5cf:555a:b442:51a9 Temporary IPv6 A
  14. I'm following the documentation. trying to find my device IP with adb shell ifconfig I get the long message bellow. is my device ip 127.0.0.1 or 10.0.0.245? i tried both, built a new apk each time to the headset, then started sever, a window pops up for a second and closes, then I start device apk and a message "connecting..." and timeout error do i need to disable windows firewall or something? - lo Link encap:UNSPEC - inet addr:127.0.0.1 Mask:255.0.0.0 - inet6 addr: ::1/128 Scope: Host - UP LOOPBACK RUNNING MTU:65536 Metric:1 - RX packets
×
×
  • Create New...