I've already spent enough hours to get a Cobra, and I've only scratched the trading surface so far. I haven't tried assassination, military or bounty hunting missions yet (although I've done some shooting in pre-beta). More content is on it's way and I'm not worried. Even now there is so much to explore, that I haven't got bored of that either. As soon as I get a few extra weapons, I'll start going through the systems for unidentified signals.
3 great reasons to push back ED to 2015
- Thread starter exioce
- Start date
I've already spent enough hours to get a Cobra, and I've only scratched the trading surface so far. I haven't tried assassination, military or bounty hunting missions yet (although I've done some shooting in pre-beta). More content is on it's way and I'm not worried. Even now there is so much to explore, that I haven't got bored of that either. As soon as I get a few extra weapons, I'll start going through the systems for unidentified signals.
It can be stupid when the community starts hyping and shouting about the next update like little kids, giving the Developer no time to time to fix the game before updating it, and then the community starts complaining and whining because the game is buggy. This is exactly what happened with the latest update of Kerbal Space Program. 
Frontier should not set release dates and just finish a good and playable release version.
Frontier should not set release dates and just finish a good and playable release version.
![[VR] Mad Mike](https://forums-cdn.zaonce.net/data/avatars/m/27/27910.jpg?1553527108){kind=avatar}
Not voted as its too open a question.
if it has to be delayed or otherwise face 1st enc type bugs then I will tolerate it.
all your reasons are moot however.
you should never release a game with massive bugs (if known)
there is always better and cheaper hardware round the corner (ie why not delay to 2016 then?)
delaying a game to wait for a periferal that many have zero interest in? that is a bit unfair to everyone who is not interested in VR, and anyway even so, CV1 support can be patched in when needed and until then, why not let the VR nuts enjoy their DK2s which are already (almost) properly supported.
I think it's actually quite simple to decide whether to delay the game or not. Either the game is relatively feature complete and most importantly bug-free and fun to play, then you're ready to release it. Or it's not, then you should give it some more time to prevent getting negative reviews and reducing the possible sales number, given that the game gets patched afterwards anyway.
Again you dont know how far FDEV is internally, your assumption is based purely on gut feelings.
its stupid to assume a delay will mean the game is better balanced or patching isnt necessary
the more they add in that time, which they will, the more needs fixing and balancing.
youll end up in a neverending circle of delay to fix, delay to balance...........
the more they add in that time, which they will, the more needs fixing and balancing.
youll end up in a neverending circle of delay to fix, delay to balance...........
Sorry to say but this is a stupid question and post which can only be answered by the development team as they are the only ones who know what issues they have and how much is going into the first release.
Everyone else is guessing and with all due respect should **** because you just don't KNOW!
Everyone else is guessing and with all due respect should **** because you just don't KNOW!
Exactly as rumtruffle said. More time means more features being added (no way this wouldn't happen, it happens all the time, everywhere) so the argument that more time means a less buggy game is usually not able to hold up to reality.
There is a date (day, month, year, whatever) you have to commit to and then work towards that goal. And you will certainly not move that date just because some armchair developers on a forum will say so when there are still 5 months to go. Nobody outside the dev circle knows how much more advanced, or behind, the current dev build actually is, which means we are drawing conclusions out of possibly false assumptions.
There is a date (day, month, year, whatever) you have to commit to and then work towards that goal. And you will certainly not move that date just because some armchair developers on a forum will say so when there are still 5 months to go. Nobody outside the dev circle knows how much more advanced, or behind, the current dev build actually is, which means we are drawing conclusions out of possibly false assumptions.