Part 1 - Description of the problem
I have the DK2 and I am working on a VR project. This project uses FirefoxNightly. I've downloaded it and installed the WebVR Enabler Add-On
Got this from http://mozvr.com/downloads/
I have also downloaded and installed the latest SDK and Runtime for Windows from https://developer.oculus.com/downloads/
I am also getting this on the Oculus Configuration Utility (while the oculus is plugged in):
However, I have gone on another computer with windows.. installed everything just like on this windows computer and it clearly shows the Oculus Rift connected properly but the head tracking still not working.
EDIT: I just tried connecting the oculus rift to this "second" pc ( dell laptop ) and now it doesn't even recognize the oculus rift. Still no head tracking.
EDIT 2: I tried installing everything on a third PC without success. I'm getting "service unavailable" on the Oculus Configuration Utility
My display mode is set as shown in the image.
Part 2 - Questions
What am I doing wrong? Is there a step I forgot to do? The weird thing is, I have the same project running on Mac without having any problems. Yes, on windows I can see the screen through the oculus rift but head detection is just not present.
Part 3 - list of possible fixes that did not work
This reddit post talks about the firewall issue however I tried the oculus rift with the firewall disactivated without success.
This reddit post talks about a possible fix by reinstalling everything and updating certain drivers.. however I have followed this fix step by step without success.
This oculus forum post talks about the issue and one person proposes a fix that worked for him/her. I followed the fix without success.
Part 4 - System info
If you require specific translations let me know. It is in French.
Part 5 - List of things I have tried that have been thought of
I have reinstalled everything. SDK (is not even needed in fact), runtime, firefoxnightly, webvr add-on multiple times
I have rebooted my computer multiple times
I have tried the different Rift Display Mode
Basic demos from mozvr.com and other webvr based projects work fine but head tracking does not work.
My Oculus is not broken (maybe for windows), it works fine for the Mac.
I've tried using different HDMI cables and Different minUSB-USB cables without success.
Part 6 - Quotes from the forum
First post
This sounds like the same issue a lot of us are having with the 0.5
and 0.6 versions. It's not something wrong with the cables, but with
the Runtime itself. Direct-mode works flawlessly and in Extended mode
the rift still displays a picture, altho without any tracking etc from
the runtime. Hoping it'll be fixed in the next update.
I've seen head tracking break in Firefox Nightly sometimes but I can usually solve it by restarting the browser once or twice, assuming that the hardware and Oculus side of things is working correctly.
Today, most games made for the Oculus Rift are based on specific versions of the Oculus Rift. I found this GUI desktop application that seems to solve most of those problems.
The idea is to install all Oculus Rift Runtime versions and then use the GUI to switch between each version.
The link above is to a reddit post that talks about how to install the application and the different runtimes.
You must install the runtimes from oldest to newest otherwise you'll run into some difficulties, like I unfortunately did. If I'm not mistaken runtime version 0.8 is very buggy and I never really got it to work.
Good luck.
This is what I did to get the Oculus DK2 working on my Windows 10 Laptop:
Create a windows restore point before you start this.
Download oculus_runtime_rev_1_sdk_0.4.4_win.exe from the Oculus downloads page.
Run the installer. Do not restart your computer when prompted.
Go to C:\Program Files (x86)\Oculus\Service folder, right click on OVRServer_x86.exe and go to properties.
In the compatibility tab, check Windows 8 mode, and Run As Administrator.
Run OVRServer_x86.exe
That's it.
The Good News
You should now be able to run direct to rift games. The HELIX rollercoaster app works well. So does the 6000 Moons demo. Most others do not. Depending on the game, you may need to go to your windows display settings, and fiddle with the screen resolution and rotation of the Oculus display.
The Bad News
Your computer may not restart. When I did the above, and later restarted, the computer hung on the windows loading page. I had to go into advanced start mode and load a system restore point. Definitely not the best user experience, but at least I got something working.
Related
I have written a JavaFX app running on Windows 10 machine in the office which has problems showing (painting/rendering) certain embedded controls such as a Pane with PdfBox when I connect to it with Remote Desktop for Mac. It shows only a black screen in the app instead of the pdf document.
When I connect using RDP from my Windows 10 machine at home to my Windows 10 machine at work, the app works just fine (the pdf is shown in the app).
I have the same problems using AnyDesk and Teamviewer.
The app only shows PDFs properly using a connection from Windows 10 to Windows 10 with Microsoft RDP.
It might be a JavaFX issue. Similar issues are described here (although not 100% identical):
https://bugs.openjdk.java.net/browse/JDK-8239589
https://bugs.openjdk.java.net/browse/JDK-8229394
However, since I guess Microsoft Remote Desktop for Mac is using the same technology as the Windows Desktop client, I would have expected it to work fine.
I have a Mac Mini M1 running the latest OS (Monterey) at the time of writing this post. I am also using the latest Remote Desktop client for Mac.
This problem is not new and was also present in older releases.
I have tried to play around with screen resolutions, both on Host and Client but nothing good came out of those tests.
Disabled also hardware acceleration in Remote Desktop for Mac preferences but it didn't change anything.
The machine at the office has the following specs (which I cannot change nor update)
Edizione Windows 10 Pro
Versione 20H2
Data installazione: 10/09/2021
Build sistema operativo 19042.1415
Esperienza Windows Feature Experience Pack 120.2212.3920.0
Anyone else who has seen this problem and perhaps resolved it?
Could it be a bug in either PdfBox or Remote Desktop for Mac?
Except for the above issue, the Remote Desktop Client for Mac is working great (not lagging as TeamViewer or AnyDesk) and the user experience is phenomenal.
PS: While this might be considered a programming question (since I wrote the app with JavaFX) but it might be better to post on another forum? If yes, which one? On the other hand, many similar posts (look at the suggested thread on the right) have been upvoted despite not dealing with programming issues.
Thanks.
How do you use PDFBox? I ask because this is not a JavaFX component. If you use a SwingNode for that it might be interesting to try one of my two PDFViewer demos here and see whether the problem persists.
https://github.com/mipastgt/JFXToolsAndDemos#awtimage
The difference is in how I do the rendering and maybe that makes a difference for your use-case too. But of course this is just a wild guess and I can't promise anything.
This may already have a question somewhere, but I am at a loss as to how to debug IE11 on my Mac.
I currently run a full Win10 instance in a Virtual Box, but it is so bloated that it is nearly impossible to move nimbly between coding and debugging. IE dev-tools are also inaccessible using this method because it just cripples the VM, so I am flying blind with coding.
I have looked up tutorials as to how to run IE on a Mac direct using Wine/Remote Desktop, but these instructions are out of date or the supporting software does not work as intended. Also, Microsoft (being the evil empire that they are) discontinued support for debugging with Azure so that is another option off the table.
If there is anything that actually works without having to shell out $$$ please let me know as it is so painful currently to debug the worst browser that will never die.
From your description, I can see that you had already try to use the Windows 10 VM but it get hangs.
You can try to go to Windows Features on or off inside Control Panel-> Programs-> Programs and Features and try to turn off the features that you are not using may help to reduce the load.
It is possible that you are running your VM in a very less memory that downs the performance of the OS.
If possible for you than try to install a VM with some more memory.
Otherwise you can try to install Windows 7 in your VM and upgrade to IE 11 in that.
It can help you to solve your issue with the OS and you can debug the code on IE 11.
Below are some helpful references that may give you some additional information.
How to test your website with Internet Explorer on a Mac
How to Debug in IE on a Mac
I wonder why every once in a while, Intel RealSense 3D camera fails to start? I have re-installed the drivers and SDK as well as the DCM but still it is whacky and very unpredictable. Any idea what the source of the problem could be? It should be able to run the examples in the SDK in a normal working situation.
Well, previously that it couldn't init problem was that only two of the its drivers could be recognized (not the virtual driver) like the following but now all of its driver are recognized and still it can't init.
so I am receiving an init failed message when running the SDK examples.
Any pointer for fixing is really appreciated.
If you are also showing an integrated webcam (other than the 3 RealSense listings), try disabling that so the RS camera can be seen as the primary.
Actually you can select the device you want to run the sample on in the menu "Device". If you installed the RealSense correctly and if the latest DCM is running (the current version is 1.4 if I remember), you should be able to select the RealSense device there and then run the sample.
Sometimes the DCM Service fails to start (e.g. if you force-restarted your machine recently). Then you just need to make the service restart and it should work.
Hope this helps.
I’m also facing the same problem (on windows 10), and found a way that solved it for me: search “Scanners and Cameras” in Control Panel, choose “Add Device”, under “Manufacturer” choose “Intel” and under “Model” choose “Intel(R) RealSense(TM) Camera SR300 Virtual Driver” or the version you use, and continue to install.
Have you installed the right drivers? There are two versions of the real sense cameras. The Windows 10 works with Intel Real Sense R3 which has completely different architecture than its predecessor.
I own a ZTE Open, UK edition. I tried upgrading from 1.0 to 1.2 following these instructions.
https://hacks.mozilla.org/2014/01/upgrading-your-zte-open-to-firefox-1-1-or-1-2-fastboot-enabled/comment-page-1/#comments
The update I installed came from ZTE themselves, and was not a custom, or third-party ROM.
The upgrade worked smoothly and had no errors, and I was prompted to reboot my device. Since then it has been in a reboot loop.
I've tried entering recovery mode and restoring to factory settings, but nothing worked. Likewise, I've tried wiping the cache from recovery mode, but with no success.
Any help would be much appreciated.
EDIT: Also worth adding that I cannot access the phone via ADB or Fastboot.
I had a similar problem when I tried to update to 1.2 using the same tutorial
(I have the US model).
The problem seems to be jumping from 1.0 to 1.2. You need to load 1.1 first, then 1.2.
The solution for me was to download both of the ZTE Official 1.1 updates linked on the
ZTE Open device page for my region (on the mozilla developer website under the heading "Upgrading Firefox OS" linked below).
Do not change the downloaded files names, just unzip them both and put both .zip files on the root of an sd card and reboot into recovery.
You should be able to flash one of the two files using the install update choice, the other will give an error (I can't read the full filenames on the phone so I'm not sure which one actually worked for me, that is why I say just try both.)
After flashing you should clear cache, wipe data and reboot.
If all goes well you should have a fresh factory load of 1.1 on you phone and you can now follow that tutorial to upgrade to the developer preview of 1.2.
If your recovery won't flash either of the official EU 1.1 updates you may have some how replaced your stock EU firmware with a stock US firmware, one update will say signature verification error and the other one will give another longer error 7 something or other. I replaced my US firmware with an EU firmware (v1.0) without realizing it and thought my phone was totally bricked because I couldn't get any US 1.1 firmware to flash and I couldn't get to fastboot or adb to manually flash a build (I loaded EU 1.0 version then used fastboot to flash a 1.4 build that wouldn't boot). The solution to that problem was to load an official EU 1.1 .zip from recovery and then load the US 1.2 developer preview from fastboot which replaces the EU recovery and let me flash an official US 1.1 .zip build.
Try not to mix and match firmwares from different regions, the Open doesn't seem to like that.
I was able to get the ZTE preview of 1.2 to work but it has a nasty bug with the notification bar so I went back to the official 1.1 build so you may want to stay at 1.1. If you do load 1.2, the key to using the notification bar is to tap and hold above the screen and slowly "roll" your finger onto the bar until you can pull it down (that might not make much sense now but if you get 1.2 loaded you will understand).
Hope that helps.
https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN
When upgrading to V1.1 before attempting to upgrade further, I might be able to explain why #Foo observed that only one of the two ZTE files worked (ZTE file links: European, US - each has two files). I didn't hit the reboot loop, but I was unable to install what looked like the right file.
The reason is that there are two links for upgrading to V1.1.0B02 - one link is labeled "(for V1.0)" and the other is labeled "(for V1.1)". This really tripped me up as I was scanning the list for 1.1 and jumping over the (right) file labeled for 1.0.
Very clearly, if you are upgrading from 1.0, then you need the "V1.1.0B02(for V1.0)" version. Just downloading both and trying each one may be easiest, but it vexed me to not understand this.
If you pick the wrong one, I found the error message (E:signature verification failed) to be very unhelpful after booting into recovery and attempt to flash from the SD card.
Someone smart who I know just mentioned that the idea of downloading Internet Explorer onto a Mac seems counterintuitive, even though it might make sense to do since Safari seems to have problems on a certain site for a project we're working on. I'm just wondering why this is and would greatly appreciate any clarification. In summary:
Why does it not make sense to download Internet Explorer onto a Mac?
Much thanks in advance!
If you're looking for a serious answer:
The best way to test something with IE7 for Windows is to use IE7 for Windows. Just because you have a Mac doesn't mean you can't do that. You can run Windows through BootCamp. Or buy a used $99 Windows box and borrow the Mac's keyboard/mouse/etc. Of course it's much more convenient, and almost certainly good enough, to run Windows in a VM under OS X via Parallels, VMware, etc. Wine will mostly work, but it can be fiddly to configure, and may crash and/or have visual glitches that don't happen with real Windows; if you really want to get serious about that you may want to look at Crossover.
But the next best way to test IE7 for Windows is actually Opera. Of course in the case of bugs and quirks that are still present in later versions of IE, they'll do a perfect job of emulating IE7, but for bugs that were fixed, that's not a particularly important focus. Opera, on the other hand, works hard to be able to emulate the quirks of all of the important browsers. Make sure to enable IE quirks mode, and set the user agent to pretend to be IE7 for Windows, and you should be golden.
But for the question you actually asked, there is no blanket answer to this that could possibly be correct. There are many reasons it may not make sense to download Internet Explorer onto a Mac, and also many reasons why it might.
You can't run IE for Mac on any modern Mac.
If you have an ancient Mac, and it's running 10.2 or 10.3 rather than 10.4, it already has IE (and if you want to reinstall it, it's part of the OS X install), so there's no reason to download IE.
You also can't legally download IE for Mac from anywhere anymore (except as part of old versions of OS X).
And IE for Mac is actually far less like IE7 for Windows than any modern browser is.
You can't run IE for Windows (or Pocket IE for Windows Mobile) on Mac OS X.
But you can run it under wine.
And you can run it in a virtual machine running Windows.
Except that Windows comes with Internet Explorer, so there's no reason to download it.
Unless your Windows comes with an older version and you want to update it.
And a Mac can run Windows instead of OS X if you want (e.g., via BootCamp).
Same caveats as with a VM.
And there may be other reasons to download it other than running it.
If your Mac has access to a fast internet connection and your Windows box doesn't, you might want to download the installer on the Mac to copy it locally to Windows.
Sometimes you just want to use up internet bandwidth.
Maybe you're testing your download speeds.
Maybe you're about to dump your boyfriend, and first you want to run him $300 over his monthly bandwidth limits.
Someone at Microsoft might find it entertaining when they notice in the logs that you've downloaded IE on a Mac, and it's always nice to bring a smile to a stranger's face.
The last version of Internet Explorer for Macintosh was 5.2, out in 2003. It wouldn't even run on a modern machine. The build is just not compatible.
If you want to try a different browser, both Chrome and Firefox run on OSX.
To run internet explorer on the Mac, you'd need to use some sort virtualization, running Windows either through Boot Camp or Parallels.
I had to do it because I'm developing software and the client wants to have it styled for IE 7 (the version they have on all their machines).
If I had my druthers, I'd run it under virtualization (e.g., VMWare), but I've misplaced my old XP CDs, so I settled for Wine (which works 'okay', but crashes from time-to-time).
I suggest using VirtualBox which would enable you to run MSIE on your Mac directly:
https://www.virtualbox.org/
...and here are the VMs for MSIE 6, 7, 8 and 9:
https://github.com/xdissent/ievms
Good luck!
It's definitely not a good idea to install Internet Explorer for Mac. It simply doesn't work properly as it was discontinued by Microsoft in 2005. However, if you have to use it to view certain websites that will only work in IE, this is the easiest way to download and install it for Mac: http://machow2.com/download-internet-explorer-for-mac/