Can you email me the debug logs? http://bigscreenvr.com/debug
And I’m curious if you have enabled Core 2.0 Dash. Can you try disabling and seeing if it improves the perf?
Someone else was having issues with KODI and it was because Oculus Dash was also running and blocking Bigscreen
Howdy! Rainmeter is the best for that, and might have been what you see in Matteb24's Movienites. If we havent met, reach out on discord, same username.
Hey, dev here, send us your logs after trying to open a game when it freezes. The instructions for sending logs are here: http://bigscreenvr.com/help/faq/debuglog/
I have a feeling this is Windows 8 related, we'll have to see if we can fix it. Thanks for the feedback!
Hey iSeeSnek. I was doing some surfing on DLNA, Bigscreen and EMBY (which I have used for years). It looks like it's getting some attention.
I'd like to have a solution for smooth LIVE sports-media (football & hockey).
I figure the posting here might give you a few ideas, albeit a little EMBY-focused.
Good luck.
I will have to see if the logs were retained on my computer after uninstallation after I get home. For some additional context, my suspicion of bigscreen being the culprit is that, despite it not being within the list of startup apps, the process was nevertheless running multiple instances within 30 minutes of turning on my computer. I know for a fact that I did not manually start the process because I solely turned my computer on and opened the excel spreadsheet I was working in. No browser windows or other applications.
On the other hand, other suspected culprits include NordVPN and Teamviewer, both of which are set to initialize with Windows 10, and I have had teamviewer configured in the past such that I would simply be able to boot and login, and then control my computer via my teamviewer account while out and about.
Yes I do know that this might not be the wisest of decisions, hence why I am beginning a discussion and will be looking into Teamviewer as a similarly potential culprit later today.
If you want something cheap and effective try this: https://www.amazon.com/dp/B08Q7VLDQQ/ref=vp\_d\_pbmv4\_TIER2\_cmlr\_lp\_B07XB6VNLJ\_pd?\_encoding=UTF8&pd\_rd\_i=B08Q7VLDQQ&pd\_rd\_w=Nd1vt&pf\_rd\_p=422aea45-f57b-4764-a849-eef933275314&pf\_rd\_r=43T3895MJEWHFAWVH0V9&pd\_rd\_r...
Hi thinking of making a tutorial for it lol, so basically, you have to reencode the file using Handbrake. The file must have the audio tracks in a non-compatible format. I don't remember all the steps, but you can find handbrake here : https://handbrake.fr (no malware detected). Then you reencode the movie according to the settings you want. I recommend H.265, keeping the same ratio for image, and putting 512 kbps for audio track, also, the default choice of audio format should be compatible with Quest 2.
I use a setup like this for some weeks now and I'm very happy with it. The biggest problem for me was to find a way to view the capture card (which counts like a webcam) in full screen without noticable latency with sound. I use this capture card here: https://www.amazon.de/gp/product/B09CGTFY5T/ It's nothing special just the first I found with loop through so I don't have to change the cables when I want to use the TV.
I tried multiple programs to display the capture card - the best result I got was with OBS Studio. OBS has a fullscreen preview mode and can also preview the sound inputs. At first a had some problems with heavy tearing but after configuring the correct fps (60) it's gone.
The controller is still attached to my console as everything is in the same room.
I played multiple hours on my PS4 while being in Bigscreen without any other bigger problems.
https://www.amazon.com/gp/product/B08XW98J7B
​
This USB capture card is amazingly low latency. Depending on how perceptive you are, you might not even notice it (it's there, though, zero latency just plain isn't possible). Don't bother getting a more expensive version, they're all the same chip under the hood. Best you're gonna get without spending absurd amounts of money.
Maybe ur USB isn't supplying enough power. Here is the cable I use https://www.amazon.com/dp/B01MZIPYPY?ref=ppx_pop_mob_ap_share Along with these angle connectors https://www.amazon.com/dp/B078YRKTKM?ref=ppx_pop_mob_ap_share You don't need the angle connectors though, optional.
Are you on the SteamVR beta? If not, maybe give it a try. I think they just overhauled the SteamVR service to make it more responsive.
Since you said that you have not had problems with anything else I'd try the beta (or getting off the beta if you're already on it) to see if maybe it helps.
But the only time I've ever had this problem with the Index was when I didn't have enough USB bandwidth. I bought a pci-e USB card to ensure the headset wasn't sharing bandwidth with anything and it took care of my problem.
The cards aren't that expensive but it's worth it. I linked to the one I bought years ago as an example, but you may want to shop around for something newer or better.
I'm not sure offhand what might be causing that.
Can you submit your debug logs? http://bigscreenvr.com/debug You can post them here, or if you want them to be private, DM them or email them to . If you email them, be sure to include your Reddit name and a brief description of your issue so that we know what the logs are in reference to, or link to this post.
Sound like it crashed.
I can't really even guess as to the reasons why though without more information. If you could link or post or DM your debug logs, that would help. http://bigscreenvr.com/debug
Hi, this is a bug we're actively trying to fix. It would be helpful if you could send me your logs. http://bigscreenvr.com/debug will tell you where to find them, and you can send them to - if you link this reddit post in the email, that will tell me what the logs are for.
I saw your other post. Even for this, need more information. What PC do you have? Do you have Flux or Night Mode turned on? Are there tons of errors in your output_log.txt debug log file? Location here: http://bigscreenvr.com/debug
Crap! I've only seen this error a couple times on my machine and I have no idea why it's happening.
Two things. First, please help us fix this! Send us your debug logs and I'll see if there's an obvious error in there: http://bigscreenvr.com/debug
Second, when you start Bigscreen, you should see the UI also on your desktop. Just start typing your name and hit enter. Then the continue screen should disappear entirely.
edit: are you only using the public Oculus Home version? You haven't tried our upcoming version (10 days away), which is being alpha tested privately, right? Aka the "topsecret" version?
For windows - Bino 3D player For android - SBS video player https://play.google.com/store/apps/details?id=org.hotpattern.sbs3dplayer I use SBS video for opposite reason I watch LR in RL so that I can watch them Cross eye 3d. I've ordered Anaglyph glasses though
edit: sorry, I keep forgetting that you're talking about a jailbroken Firebox. That would mean that you don't have an account with Fire TV, right? So their app will be useless to you
No problem I’m sorry that controller input does not work yet for quest standalone, here is the link to the keyboard that I’ve been using for years when I use my quest natively
https://www.amazon.com/Logitech-Wireless-Keyboard-Multi-Touch-Touchpad/dp/B005DKZTMG