Mod Chris E posted an in-detailed explanation (following Mod Nick’s short evaluation of the problem that occured). I re-post it below, followed by my take on the situation.
“Perhaps I can explain a little more why we couldn’t release the game content this week, even though the problem only resides in the game engine.
When we build our Release Candidate (RC) build of the game ready for next week’s update, we build/compile all the content (scripts, models, graphics etc) against the RC build of the game engine.
In this case, we have been building a new engine version for the last two weeks with numerous new features and bug fixes. At the end of last week, this was ready so we pushed it to RC. We then built the game content against it ready for launch this week.
On Monday, during final compatibility testing that we do every week, our QA team noticed a problem with some Intel chipsets and HD. At this point, it meant we couldn’t do what we call a ‘Content Only’ update, because the content was built depending on the latest version of the engine, and wouldn’t work on the engine currently running on the live worlds.
Whilst rolling back the build systems for the engine and content is possible, it would have taken so much time that we probably wouldn’t have been able to release the content this week anyway (and besides, some of the new content relied on new engine features!).
I’m pleased to be able to say we have resolved the Intel issue (although our HD developer has been tearing his hair out most of the week!), so hopefully you will see the update early next week, barring any further problems. “
Perfectly logical and justifiable. Having worked in a company with multiple builds which incremented each time, I can understand the problems you had here. I was not at all surprised that it was a game engine bug.
I remain intrigued as to why the Intel chipsets had a specific problem from a CompSci point of view, clearly your work here is on a much lower level than I expected (normal Java-OpenGL work doesn’t involve chipset specific coding to my knowledge).
I’m still wondering what portion of the audience this affected – to quote my post from Qeltar’s thread:
“It’s difficult for anyone to accurately analyse the possible effect of the update on the number of users affected unless you have the data on your users. Jagex clearly do have this data.
One specific chipset on one operating system, which itself has a maximum of a 22% general market share in December 09, would seem like a bad reason to delay an update in my opinion.
A few things differ however. Vista may be more common on the RuneScape user base than in the general public. This is difficult to argue for – there’s no specific reason it should be.
The main factor however is that despite the wide range of actual hardware, the relative popularity of specific chipsets (for example the Core 2 Duo family) coupled with the fact that it may actually be multiple highly related families (I’m not entirely sure what the incremental changes are on differing chipsets and it’s stupid to try and speculate), of which only one they have the resources to test (they probably don’t have 1 chipset from each Intel processor family), means that it could be a larger than expected proportion.
So there is the possibility that it affects (given the dominance of Intel these days) upto and maybe above 20% of their market, it’s hardly surprising that they decided to wait.”