Frontier will not be supporting oculus rift on launch?

Status
Thread Closed: Not open for further replies.
pardon my ignorance on the whole topic, ive been away for some time due to lack of hmd.

what I dont get is why they dont seem too interested in the cv1, unlike all the hype and support for the dk2.

granted it was the only system available...

That being said, how is it other developers can keep up with the SDK no problem? It cant be that much work...its a lack of interest.
Project cars is selling like crazy because they are keeping up with the sdk and being proactive about the launch.

given that eve-V is a launch title, wouldnt you think FD would want to stay on top to try to get more sales pre and post launch of the cv1?

it smells a lot like they are just giving up on the oculus and focusing on the vive. if that is the case then just say so...no harm


Firstly, they have been very clear they intend to support Oculus and they have no plans on just focusing on Vive.
It's not a lack of interest, they have cited technical issues as to why its not working. Presumably as they haven't said in great detail, getting the Cobra engine to work in direct mode isn't simple and requires some changes from Oculus to assist. Oculus as you can imagine are trying to ship their product so the needs of 1 developer are not priority.

How do other developers keep up? Because whatever engine they are using ports to direct mode a lot easier than the Cobra engine.

</2cents>
 
Firstly, they have been very clear they intend to support Oculus and they have no plans on just focusing on Vive.
It's not a lack of interest, they have cited technical issues as to why its not working. Presumably as they haven't said in great detail, getting the Cobra engine to work in direct mode isn't simple and requires some changes from Oculus to assist. Oculus as you can imagine are trying to ship their product so the needs of 1 developer are not priority.

How do other developers keep up? Because whatever engine they are using ports to direct mode a lot easier than the Cobra engine.


</2cents>


makes sense i suppose.
still feels lacking compared to the dk2 train...

but an engine issue is big stuff, that is a serious scenario for the devs to contemplate.

i guess the extra sales wouldnt be enough to justify the cost to rewrite.
 
https://www.reddit.com/r/EliteDange...d_news_cmdrs_no_new_fixes_until_next_planned/

What a massive slap in the face of both those who decided to go with the rift and those who forked out for a season pass with no content for half the season.

I am done with frontier, they wont be getting any more money from me, they havent been able to live up to their promises and the game is broken. This season pass crap was just a fast cash grab with very very little up front content available. Given what is available to base game content in the upcoming patches, there seems to be very little reason to go beyond the purchase of the base game.

We deserve better than this FD.

errrrr the RIFT already works with the latest 08.0 SDK and I see no reason why 1.0 wont work either as it uses Steam VR.

For those having trouble just calibrate using the steam vr software. hey presto it all works
 
errrrr the RIFT already works with the latest 08.0 SDK and I see no reason why 1.0 wont work either as it uses Steam VR.

For those having trouble just calibrate using the steam vr software. hey presto it all works

do you have a confirmed source for this? I want it to be true but it is not what people with access to the current 1.x runtimes are reporting, and the bios in CV1 which supports 1.x runtime no longer supports 0.8 runtime.

- - - - - Additional Content Posted / Auto Merge - - - - -

Braben has said that there will still be minor updates before 2.1 although it's probably safe to assume that Rift support won't be a minor update.

ok, well that is good news (for the rest of the game at least) i missed this quote from DB.
 
Last edited:
Re: Frontier will not be supporting oculus rift on launch.

Have not got one at this time.
Do not want one at this time.
Could not care less at this time.

I think that just about covers it for me.
 
do you have a confirmed source for this? I want it to be true but it is not what people with access to the current 1.x runtimes are reporting, and the bios in CV1 which supports 1.x runtime no longer supports 0.8 runtime.

.

No I was unaware of what you just mentioned. I'm just stoked I managed to get it working the other night to be honest :)

I do have faith in FD though, even if it takes time.
 
Slap in the face?

Oculus
Vive
all the other VR HMDs

These are brand new consumer products.
Early adoption always has drawbacks
- Cost
- Bugs/Wonky design
- Lack of a unified platform
- Limited dev support/available games
- Lack of publisher incentive to put out games for a niche and unproven market

To expect a midsize development firm to pour resources into supporting a new widget, taking away time and money from advancing the game's development is just selfish and foolish.
 
Slap in the face?

Oculus
Vive
all the other VR HMDs

These are brand new consumer products.
Early adoption always has drawbacks
- Cost
- Bugs/Wonky design
- Lack of a unified platform
- Limited dev support/available games
- Lack of publisher incentive to put out games for a niche and unproven market

To expect a midsize development firm to pour resources into supporting a new widget, taking away time and money from advancing the game's development is just selfish and foolish.

To be fair FDEV set the expectation, with what is widely acknowledged to be one of the best VR implementations in any game to date. If ED could be so awesome with a dk2, and an early SDK, why would any of us think that CV1 would cause so many problems ?
 
errrrr the RIFT already works with the latest 08.0 SDK and I see no reason why 1.0 wont work either as it uses Steam VR.

For those having trouble just calibrate using the steam vr software. hey presto it all works

the CV1 will not work with this, there was a guy who got his hands on one on these firums and he cannot get it to work with ED
 
To be fair FDEV set the expectation, with what is widely acknowledged to be one of the best VR implementations in any game to date. If ED could be so awesome with a dk2, and an early SDK, why would any of us think that CV1 would cause so many problems ?
That is true.

Frontier never spoke about VR as a priority though. They found that the game (in pre-release) could, in a straightforward way, be adapted for the VR.

What has happened is the final SDK for Oculus had come out with not enough time for Frontier to support it. Again, keep in mind that it isn't a higher priority than game development. From what I've seen the way Oculus communicates with the game was significantly changed in SDK 1.0. I'm no expert but it seems to me that a near total rewrite of the implementation is needed.
 
the game is broken.


Have you tried one of these ?

Plaster_682_1003912a.jpg
 
Slap in the face?

Oculus
Vive
all the other VR HMDs

These are brand new consumer products.
Early adoption always has drawbacks
- Cost
- Bugs/Wonky design
- Lack of a unified platform
- Limited dev support/available games
- Lack of publisher incentive to put out games for a niche and unproven market

To expect a midsize development firm to pour resources into supporting a new widget, taking away time and money from advancing the game's development is just selfish and foolish.

THIS!

But you know what... we all are gulity of this, we as costumers have the choice to decide what to buy and what not... to tell companies hey! we are not agreed with this and change the rules.....

Price expectation of consumer versions of VR devices... FAILED... people complain... AND BUY ANYWAYS!
Support of games for a very expensive device... FAILED.... people complain....AND BUY ANYWAYS!
Distibution... opportunity of testing devices...canceling orders polcy.....ALL FAILED... and people buy anyways.

And then they open a thread ,,, for complaining after buying thinking they will solve anything.

i admit. i'm Trolling again about all this but it's just.... i can understand it.
 
Can't say I'm not disappointed.

It is very likely we won't see support for the Rift on launch.

The rendering changes needed for a proper fix are almost certainly on the baseline 2.1 branch and dependent on code there.
Integrating only the rendering parts of that back into the 2.0 trunk would be enough work for them to not even consider the idea.

Sigh ... gonna wait then..

P.S Reminding all of you:
CV1+0.8 runtime + OVR works bad
CV1+1.x runtime + OVR still does not work at all
 
Last edited:
Can't say I'm not disappointed.

It is very likely we won't see support for the Rift on launch.

The rendering changes needed for a proper fix are almost certainly on the baseline 2.1 branch and dependent on code there.
Integrating only the rendering parts of that back into the 2.0 trunk would be enough work for them to not even consider the idea.

Sigh ... gonna wait then..

2.1 shipping mid-late late April

Oculus shipping in June

In the words of Peter Gabriel and Kate Bush ...

Don't give up
You're not beaten yet
Don't give up
I know you can make it good
 
It's not a lot of fun reading this tirade of speculation (not a criticism, I'm prone to it too) when all it would take is for an official word from Frontier to inform us one way or the other.

Will ED run on the Rift and if so approximately when?
Will ED run on the Vive and if so when?

WHY can't someone comment when this is financially affecting the customer base and causing dissent. What would FD have to lose by clarifying this even in a vague way? The silence is just insulting!
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom