There are some hard coded settings in the elite.exe that can be changed via hex editor, the info is here in this thread... but I will just wait for the next official version.
ED and the Oculus Rift Developers Kit 2 (DK2) Discussion Thread
There are some hard coded settings in the elite.exe that can be changed via hex editor, the info is here in this thread... but I will just wait for the next official version.
One more good point for FD to upgrade to SDK 0.4.1 would be to be able to start the game via SteamVR and this gives you access to the SteamVR Browser to use with some of the web tools for trading. But right now ED only works with service off and SteamVR only with service on.
First my own question, below an answer to a previous post:
Does anyone else playing with the "brute force" solution (no DK2 drivers left, so it's playable with an older AMD CPU) know if there's a way to keep the "drift" of the viewpoint as low as possible? I have noticed that usually my viewpoint drifts to the right at a random speed. Sometimes I can play for half an hour before it rotates 90° from the starting point, sometimes I have to restart the game after ten minutes. Sometimes it even drifts to the left.
It's a real pain. F12 doesn't help, of course as it only works with functional head tracking.
So I have a "proper PC" that runs ED on high with AA etc but with only (drifting) rotational tracking and a laptop that can't run ED at an acceptable FPS but with full tracking... AAArgh!
Help very much appreciated.
Now for the answer
Does anyone else playing with the "brute force" solution (no DK2 drivers left, so it's playable with an older AMD CPU) know if there's a way to keep the "drift" of the viewpoint as low as possible? I have noticed that usually my viewpoint drifts to the right at a random speed. Sometimes I can play for half an hour before it rotates 90° from the starting point, sometimes I have to restart the game after ten minutes. Sometimes it even drifts to the left.
It's a real pain. F12 doesn't help, of course as it only works with functional head tracking.
So I have a "proper PC" that runs ED on high with AA etc but with only (drifting) rotational tracking and a laptop that can't run ED at an acceptable FPS but with full tracking... AAArgh!
Help very much appreciated.
Now for the answer
After using the "hex fix" (some pages up this thread) the colour aberration disappeared completely for me. Also this made text much easier to read. Admittedly, reading the smaller prints is half reading and half guessing (It' pretty obvious usually), but manageable. So it might fix both your biggest problems. Especially if you do have head tracking (in which case leaning closer to the respective monitor helps a lot)
SlackR
Banned
I really hope so, but there are issues with implementing the new SDK that weren't foreseen. The issues are from Oculus' side, not Frontiers, so they are waiting for a resolution - fingers crossed though. Might well be a case of needing to wait for the NEXT SDK before anything can be done.
It would be enough if they replaced their OWN tracking with one compatible with the old AMDs. I don't mind killing the Oculus process as long as I can use positional tracking. As it is now, the Frontier's OWN tracking causes the crash on these CPUs.
It's 1080p, the screen from a Samsung Note 3 to be precise.
massive url!
I have that phone and it's a great screen - not that I've tried looking at it that close!
massive url!
I have that phone and it's a great screen - not that I've tried looking at it that close!
Mine shipped from Ontario, CA in USA (Los Angeles)...
I would like to learn more about the issues, I know there were some Unity issues. But I thought FD had there own Cobra engine... do you have a source or some more information on this topic?
Indeed ..it could be as simple as the AMD fix ,on or off
Hopefully Frontier thought of that or something simillar. A good funtionall ED on the Rift draws a lot of attention.
The benefits of Oculus does not compensate for disadvantages (horrible and oppressive helmet, nausea, eye strain, according to some users)
You think those are the disadvantages? Check this guy out.
SlackR
Banned
It's not for me to say, as I think it may well have been an "off the record" conversation I had with with Mr Brooke's, but the big picture is that new model SDK didn't behave as expected and caused more problems than it fixed.
Have you guys seen this?
http://www.digitalspy.co.uk/tech/news/a593423/oculus-rift-wearers-can-use-their-hands-with-leap-motion-mount.html#~oOvrGIoRwEJErB
Hopefully E will support it at some point.
http://www.digitalspy.co.uk/tech/news/a593423/oculus-rift-wearers-can-use-their-hands-with-leap-motion-mount.html#~oOvrGIoRwEJErB
Hopefully E
will support it at some point.
Hi,
sounds like you get some pretty good framerates even in the Cobra. Do you also get big drop into the 30s when looking around the cockpit (LOW/MEDIUM settings)? My rig is starting to date a bit now with a i7 2600k and gtx 680. Could you tell me what hardware you have so I can rest a little easier knowing that it is nothing to do with any settings I have.
I don't seem to have any issue with the smearing you mentioned but this seems specific to only some setups.
I wouldn't have thought so, as it specifically mentions the Rift. It would be great if my hand positions were replicated in VR.
Then the only thing missing would be a virtual keyboard, so I could use the galaxy map search function without having to lift the Rift up.
It's an odd coincidence, but I spoke to a couple of the devs at LaveCon 2014 and said how great it was if E
supported VR gloves.They did look a little scared when I said it though, because I was asking for the impossible. However, I did say not to worry, because I doubt the technology even exists yet, but just to make it a consideration for the future.
Well it seems the future is almost here, so...
No head/position DK2 Tracking
I could use a little help. I got ED up and running fine, but after going back and playing some different demos I'm having problems with tracking now.
I can't get the OVRService_x64 to force quit in the task manager. It automatically keeps reopening, and I think this is what is stopping the tracking from working on my DK2.
Could someone explain what I'm doing wrong?
Thanks
I could use a little help. I got ED up and running fine, but after going back and playing some different demos I'm having problems with tracking now.
I can't get the OVRService_x64 to force quit in the task manager. It automatically keeps reopening, and I think this is what is stopping the tracking from working on my DK2.
Could someone explain what I'm doing wrong?
Thanks