ED and the Oculus Rift Developers Kit 2 (DK2) Discussion Thread

[9of9]

Just tap 'A' when the cursor is over a star (or rather the base point, where that star is projected onto the grid).

I guess it can be a little ambiguous because it doesn't really indicate that you've selected it - but when you close the galaxy map, you should have that star in your targeting info then.

 

[SlackR]

Just tap 'A' when the cursor is over a star (or rather the base point, where that star is projected onto the grid).

I guess it can be a little ambiguous because it doesn't really indicate that you've selected it - but when you close the galaxy map, you should have that star in your targeting info then.

Will give this a go now
Thanks

 

[9of9]

A or, you know, whatever the default 'confirm' button is for you.

 

[SlackR]

Still doesn't work ...

 

[TiLT]

This is by far the best experience available in the Rift so far, and I've put in several hours in it in just two days already.

One question though: What AA should I choose for this game? Even with the last one in the list selected, the graphics still seem very aliased. Is this just something I have to live with, or is there a better choice that gets around the "problem"?

 

[Spyder78]

Will give this a go now
Thanks

As an X55 owner I was struggling with the Galaxy Map too but plugging in a 360 controller solely for the map has solved that problem for me, can navigate around and select systems with ease.

Really glad as using a keyboard and mouse with the Rift is a real pain.

 

[SlackR]

As an X55 owner I was struggling with the Galaxy Map too but plugging in a 360 controller solely for the map has solved that problem for me, can navigate around and select systems with ease.

Really glad as using a keyboard and mouse with the Rift is a real pain.

Am trying with the controller but getting no joy ... Could you post a photo of your controller setting iN the map please?

 

[RiftFlyer]

This is by far the best experience available in the Rift so far, and I've put in several hours in it in just two days already.

One question though: What AA should I choose for this game? Even with the last one in the list selected, the graphics still seem very aliased. Is this just something I have to live with, or is there a better choice that gets around the "problem"?

FXAA is all that is implemented yet I think.

 

[ceno]

Headtracking not working because of CPU?

Please help, cant get Headtracking working... tried all workarounds, i guess.

Can someone confirm that HT is working in Elite with a Phenom CPU?
I suspect this may be the cause.

 

[Mazhurg]

One word. Incredible

That's essentially my first impression of the DK2 and Elite.

Almost in the uncanny valley (positioned my X52 exactly where they are on a Sidewinder) - and if it wasn't for the current (minor) issues then it would be perfect...

Minor:
- Crossfire not yet implemented, so there is some variability (and ghosting) in frame rates in busy areas. No stuttering encountered.
- Contrast on text is poor, making things harder to read for the resolution provided - still readable, but must pay a lot more attention than would normally be required.
- Occasional screen redrawn with a shadow pass.
- strong colour separation on (space) orbit and gravity lines.

(rift / G35) - Cabling gets in the way for your head movement. Sigh for a release from the umbilical cords..

On first point, system is currently an I5-3550 with 2 HD7950's (obviously only one active in game). Will the SDK4 update fix improve on the ghosting?

Thinking of changing the vid cards to an R9-290x, but also wanting to wait for the next gen as I usually upgrade every other iteration.... Worthwhile for the experience?

Of course, will get the CV when released in conjunction with the above.


But otherwise, this game HOTAS, rift, G35, VA is so immersive that just quickly trying this out with the rift for the first time turned a 10 minute session into a 2hrs plus until the wife shook me on the shoulder complaining I was not responding to her dinner call..

 

[MiNi]

Mazhurg
I see you mention G35, are you running the rift with the service Lcore active ?
Because i shut it down, as advised from oculus. But would like the better soundscape the unit provide.

 

[DuncanIdaho]

Oculus Rift DK2 non SSE 4.1 CPUs

Hey there,

I have run into a similar issue as described on the link below:
http://www.reddit.com/r/oculus/comments/2cbo5e/amd_cpu_and_elite_dangerous/

I do not have AMD CPU, but an Intel Q6600 - which also lacks SSE 4.1

ATM I am using a workaround by using Oculus Service Manager Utility by Bilago (http://www.reddit.com/r/oculus/comments/2c6qqc/updated_unofficial_oculus_service_manager_by/), which runs OVRService_x64 through Intel SDE Emulator.

This allows me to run every game/demo with DK2 support thus far - except Elite: Dangerous.

However the workaround is not working, since Elite has OVRService bundled into the game. Would it be possible to use OVRService - or give us an option to execute just the OVRService under emulation.

Like mentioned on the first link - running whole Elite through the emulator works, but it also makes the game unplayable, due to performance reasons.

 

[Tankshell]

Hi all,

Am still waiting for my DK2 to arrive, so meanwhile I am still using my trusty DK1.

I have noticed a drastic drop in FPS in the latest beta release (compared to premium beta 2).

Sitting in the starting dock, without the Rift, all settings on low at 1080p I am getting:
130fps

Without changing any other settings, and only altering the rendering mode to Oculus Rift (headphones) my fps drops immediately to:
35fps

I could swear that in PB2 my fps in this exact same situation using the DK1 were a lot higher, somewhere in the 80fps range!

Any ideas?

My rig is:
2500k @ 4.5ghz
EVGA 780Ti
8Gb Corsair Vengeance DDR3

 

[SlackR]

Please help, cant get Headtracking working... tried all workarounds, i guess.

Can someone confirm that HT is working in Elite with a Phenom CPU?
I suspect this may be the cause.

Most common cause of no head tracking is not quitting the three processes in task manager...

 

[hekkel]

Most common cause of no head tracking is not quitting the three processes in task manager...

Following your guide "9. Ok now open up the oculus config file again and hit Ctrl , Alt and Del. in task manager, close wscrip.exe and ovservice.exe in processes.

That's two, is there another added later that is missed?

Since the last update i'm having problems with headtracking.Game also takes over a minute to start (used to be less than 10 sec)

But i did recently install a saitek x52 and had several windows updates, so i'm not sure where the problem is.

 

[SlackR]

Following your guide "9. Ok now open up the oculus config file again and hit Ctrl , Alt and Del. in task manager, close wscrip.exe and ovservice.exe in processes.

That's two, is there another added later that is missed?

Since the last update i'm having problems with headtracking.Game also takes over a minute to start (used to be less than 10 sec)

But i did recently install a saitek x52 and had several windows updates, so i'm not sure where the problem is.

Windows updates are always a pain in the ass, but first thing to try is ending the oculus config.exe in task manager as well as the other two... That seems to sort out windows 8.1 issues

 

[hekkel]

I will try that next time when i start. Now it's all working and i dare not touch anything

 

[Bingo Brewster]

One word. Incredible

That's essentially my first impression of the DK2 and Elite.

Almost in the uncanny valley (positioned my X52 exactly where they are on a Sidewinder) - and if it wasn't for the current (minor) issues then it would be perfect...

Minor:
- Crossfire not yet implemented, so there is some variability (and ghosting) in frame rates in busy areas. No stuttering encountered.
- Contrast on text is poor, making things harder to read for the resolution provided - still readable, but must pay a lot more attention than would normally be required.
- Occasional screen redrawn with a shadow pass.
- strong colour separation on (space) orbit and gravity lines.

(rift / G35) - Cabling gets in the way for your head movement. Sigh for a release from the umbilical cords..

On first point, system is currently an I5-3550 with 2 HD7950's (obviously only one active in game). Will the SDK4 update fix improve on the ghosting?

Thinking of changing the vid cards to an R9-290x, but also wanting to wait for the next gen as I usually upgrade every other iteration.... Worthwhile for the experience?

Of course, will get the CV when released in conjunction with the above.


But otherwise, this game HOTAS, rift, G35, VA is so immersive that just quickly trying this out with the rift for the first time turned a 10 minute session into a 2hrs plus until the wife shook me on the shoulder complaining I was not responding to her dinner call..

I'd be interested in the performance of the R9-290X.

I have an Intel i5 and and R9-270x. With a bit of overclocking, (not too much else ED seems to crash windows), and all graphics settings set to low I am getting an average of 72 fps in deep space (acceptable) and average 56 fps in stations (a LOT of judder and heavy on the eyes).

I bought the GPU especially for ED (with no thoughts about a rift back then) but its not really an ideal experience with the DK2. I'd rather not have to replace it, but the Rift experience is worth it!!.

I am optimistic for further optimisations of ED and the SDK.

 

[Ryder35]

Hi all,

Am still waiting for my DK2 to arrive, so meanwhile I am still using my trusty DK1.

I have noticed a drastic drop in FPS in the latest beta release (compared to premium beta 2).

Sitting in the starting dock, without the Rift, all settings on low at 1080p I am getting:
130fps

Without changing any other settings, and only altering the rendering mode to Oculus Rift (headphones) my fps drops immediately to:
35fps

I could swear that in PB2 my fps in this exact same situation using the DK1 were a lot higher, somewhere in the 80fps range!

Any ideas?

My rig is:
2500k @ 4.5ghz
EVGA 780Ti
8Gb Corsair Vengeance DDR3

Yes same here. 780Ti max settings go from about 120 to 37 fps sat on the pad.

Does seem a bit extreme. Anyone else care to test?

 

[SlackR]

Yes same here. 780Ti max settings go from about 120 to 37 fps sat on the pad.

Does seem a bit extreme. Anyone else care to test?

The 780 ti (overclocked) is giving me between 70 - 144 fps on the monitor and around 70 - 78 fps on the DK2 (high settings)