shashkes Posted October 14, 2020 Share Posted October 14, 2020 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:0 errors:0 dropped:0 overruns:0 frame:0 - TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 - collisions:0 txqueuelen:1 - RX bytes:0 TX bytes:0 - dummy0 Link encap:UNSPEC - inet6 addr: fe80::4ca6:37ff:fe3c:c054/64 Scope: Link - UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 - RX packets:0 errors:0 dropped:0 overruns:0 frame:0 - TX packets:84 errors:0 dropped:0 overruns:0 carrier:0 - collisions:0 txqueuelen:1000 - RX bytes:0 TX bytes:5880 - wlan0 Link encap:UNSPEC - inet addr:10.0.0.245 Bcast:10.0.0.255 Mask:255.255.255.0 - inet6 addr: fe80::b6ce:f6ff:fe3c:9ad4/64 Scope: Link - inet6 addr: 2601:643:8301:6510:c60:902:8eab:eeef/64 Scope: Global - inet6 addr: 2601:643:8301:6510:51c1:ed00:6504:1fb/64 Scope: Global - inet6 addr: 2601:643:8301:6510:b6ce:f6ff:fe3c:9ad4/64 Scope: Global - UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 - RX packets:206208 errors:0 dropped:0 overruns:0 frame:0 - TX packets:29738 errors:0 dropped:0 overruns:0 carrier:0 - collisions:0 txqueuelen:3000 - RX bytes:106618343 TX bytes:4440951 - p2p0 Link encap:UNSPEC - UP BROADCAST MULTICAST MTU:1500 Metric:1 - RX packets:0 errors:0 dropped:0 overruns:0 frame:0 - TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 - collisions:0 txqueuelen:3000 - RX bytes:0 TX bytes:0 Link to comment Share on other sites More sharing options...
shashkes Posted October 14, 2020 Author Share Posted October 14, 2020 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 Address. . . . . . : 2601:643:8301:6510:bdcd:736e:bff0:d009 Link-local IPv6 Address . . . . . : fe80::d5cf:555a:b442:51a9%8 IPv4 Address. . . . . . . . . . . : 10.0.0.148 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : fe80::1256:11ff:fec6:6939%8 10.0.0.1 Link to comment Share on other sites More sharing options...
VIVE_chengnay Posted October 14, 2020 Share Posted October 14, 2020 @shashkes From your PC, could you try to ping the ip address from Command Prompt? To know your device's ip address, use below command, > adb shell ip addr show wlan0 From your message above, I think your device ip address will be "10.0.0.245" Link to comment Share on other sites More sharing options...
shashkes Posted October 14, 2020 Author Share Posted October 14, 2020 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 Link to comment Share on other sites More sharing options...
VIVE_chengnay Posted October 14, 2020 Share Posted October 14, 2020 @shashkes First, when you start streaming server, you need to ensure that the command prompt window is waiting on your desktop. If the server failed to wait, the command prompt window will disappear. Next, after start the device apk, you need to check that in Focus, it is waiting for connection. NOTE: if it fails the first try, repeat the steps again by stop device apk and stop streaming server and re-start them again Link to comment Share on other sites More sharing options...
shashkes Posted October 14, 2020 Author Share Posted October 14, 2020 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? Link to comment Share on other sites More sharing options...
shashkes Posted October 14, 2020 Author Share Posted October 14, 2020 I think the timeout error just appeared behind my head so I thought it was a black screen ... Link to comment Share on other sites More sharing options...
VIVE_chengnay Posted October 14, 2020 Share Posted October 14, 2020 @shashkes It seems your server does not run. You can manually run the server by going to "Assets\WaveVR\Platform\Windows" and launch "dpServer.exe" UPDATE: Yes, the wording will appear to the front of your HMD but it will not follow your HMD, so you need to look around inside XD Link to comment Share on other sites More sharing options...
shashkes Posted October 15, 2020 Author Share Posted October 15, 2020 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? Link to comment Share on other sites More sharing options...
VIVE_chengnay Posted October 15, 2020 Share Posted October 15, 2020 @shashkes Please try running directly from command prompt and paste the result here, thanks! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now