Obviously I want to see this happen so will be more will want to believe the things the company has said that support my argument, but I have no way of fact-checking comments I'm citing or building my case on.
Its an important point – this is all rampant speculation. Were both outsiders with no specific knowledge of the project. None. Years of experience has taught me that when outsiders look at a problem which they are invested in, but which they have no part in solving, human behaviour always leads people to oversimplify. I guarantee you are over simplifying this, and I`ll try to explain at least partly and at a high level why.
For example, going back to the initial pushback against the plan to have NO form of VR in Odyssey whatsoever, the "all hail greg" trope was banded about quite a bit, ciring an interview where David said something along the lines of "one developer, a guy called greg, wanted to put VR into elite, and within 24hrs he had something working", on the basis of that one interview line I'm saying one guy one day to give us VR head-look. So I am chosing to take that quote at face value and believe him.
Okay, so this seems to be the central crux of your position. Let's pull this apart, and I`ll share what I know about this stuff from my software career.
When a team want to implement something, it's common when the complexity and risks are high to first do a proof of concept. This means that the desired technical approach is tested out to see if it holds water. The outcome of this POC is then used to decide whether to commit to that approach, or whether to abandon that idea (either altogether, or to try something else). But there’s no guarantee that any of the work put into the POC is fit to be rolled into the final solution – you are literally lashing something together to test an idea. In most cases, the POC won't really resemble the “finished article” at all – simply the important technical aspects of it you’ve chosen to prove actually work. You may well choose (or be forced) to re-code the actual solution from the ground up once the POC is done.
What this also means is that – in terms of the output from that POC exercise – it almost certainly is nowhere near the bar in terms of either quality or completeness. So in other words ignoring that fact this is an anecdote from Braben, forgetting it was years ago, forgetting it was from a completely different part of the game, that “1-day” job has pretty much nothing to do with the actual effort involved in deploying VR – however rudimentary - into something customers could play.
I am exerting to draw the "Greg did VR in one day" comment into this as evidence that it can be done "easily".
So as I`ve said extrapolating an anecdote from years ago in the way you have to present as “evidence” of the work required to implement something profoundly different just doesn’t work on any level.
But there's something else to consider - that as part of the effort required to make the change, there is a quality bar to meet. What do I mean by that? What I mean is that anything that a player can get their hands on and play, whether it be a core part of the game or something that can be turned on by an ini change or any other kind of “hack”, will have to meet certain quality standards before it would be made available. Why? Well, that is simple – Frontier are accountable for what they put out.
You might say “it doesn’t matter – its experimental” – but you would be thinking in artificially narrow terms about what “quality” can mean. We're talking here about
any adverse event, not simply nausea, but profound control issues (e.g. I can look around but I can't move), the game crashing constantly, corrupting game saves, instancing and multiplayer not working, experimental player sessions having an impact on other instanced players who are not even using with this experimental “feature” , UI considerations, exploits, - all manner of myriad adverse effects you probably couldn’t even think of which literally and fundamentally stop critical functionality from working or otherwise profoundly screw things up.
The point here is that when you think about it properly - what’s is being made available to players to play – even experimentally -
does have to meet a certain quality bar. That requires work. A lot of work. Work you are not even considering at all.
I know its been proposed to see this stuff hidden behind an ini file change as a kind of “insurance policy” against this, but the truth is if it doesn’t work well enough – for example, if Frontier deem it completely unplayable if it makes the game unstable, or other fundamental issues Ive eluded to earlier , then that option is off the table completely. And that decision firmly lies with Frontier and with them alone. You can`t negotiate on that.