rof@neoqb.com

Wow.

All I can say is WOW. I am glad I decided not to order this game until they got their act together. GL all and I hope you get to play the game soon.

WWTaco, I did write that email address - and, in fact, got a return receipt it had been read.

However, I did not get a reply. I got a separate email, from the automated registration server (finally) with the registration info.

But no reply to the email I sent directly to neoqb.

Good idea. Apparently not what it takes, either, though.

What seems to be getting overlooked here is neoqb was obviously intent on the online model they use. My point is that, if you want to insist on doing things that way, then you'd better darn well be prepared for the support obligation that goes with.

This is exactly the scenario many feared: Inability to play the game they purchased, when they want, because of problems with servers.

Yes, I know it got resolved - but it was several hours, with little communication (and only that from Jason, basically saying he couldn't do much) and none at all from neoqb. We finally got word it had been fixed, that's about it.

I think we're owed more.

Many people just don't have that kind of time - we sneak in an hour if we're lucky here and there between jobs, family, and other responsibilities. If it takes hours to resolve issues like this, we're sort of screwed. It doesn't make us any less a 'sim-fan' that we cannot afford all the time and money we have being thrown at a game.

I'm not saying they don't have a right to the business model they've chosen. I am saying if you make the bed, you'd better be ready to lay in it.

I wasn't yelling at anyone tamper. I'm sorry you took it that way. The caps was not meant as a shout. The issue has now been resolved. I'm perfectly aware of how upset some people were and what people expect of us. I endevour every day to provide great service to each and every one of my customers. From my days at Naturalpoint, to my days at GoGamer and now with my own company 777 Studios. I know what this community expects, some think I am crazy for even bothering with this community. I disagree obviously. neoqb also works very hard to provide a quality product and flight-sim experience. I would not have risked my personal reputation on a product or partner I did not think shared my same point of view. In this case there were some unforeseen technical glitches that were solved as fast as possible. Call it a teething phase, call it a failure, call it whatever you want it's your opinion. All I can say is that myself and neoqb did all we could to prevent problems and a couple still occured, then everyone snapped into action to fix it ASAP. I can't ask for more.

Let's go fly.

Jason

I wouldn't say this is Jason's fault, it seems he was politely trying to help with his explanatory post.

FlatSpin, mind you - I'm not saying it's Jason's fault. I'm saying that things were mishandled, never mind whose fault it is. I'm saying someone should darn well be listening - and that a lot of people are watching. Not a good time for missteps, especially one concerning the most contested aspect of RoF's design.

No one (including me) expects things to be perfect. I do believe it's fair to expect that people should avoid foreseeable mistakes, own up to mistakes when there are problems, work to correct whatever mistakes they make, and learn from it to keep it from happening again.

Sometimes I'm not convinced these things are all taking place.

Jason,

I don't think it was me who decided that caps on the internet mean yelling; it's pretty much universally understood and has been for, what...a decade or more now? I didn't take anything the wrong way, and I do not appreciate your trying to somehow make what you did my fault. C'mon, man; I'm sure you can do better.

(BTW, I work in support, and I learned the old "I'm sorry you took it that way" trick, too - I also know it really evades taking responsibility). Here's another suggestion: When you've made a mistake, just admit it. Simply a suggestion.

It's not that I don't appreciate what you're trying to do. Believe it or not, I do believe RoF has tremendous potential, and I backed that belief up with my dollars.

It's good to know that the registration fiasco wasn't necesarily a problem with neoqb's servers. And, you did the right thing by getting that explanation up.

But, I do have to ask, though: In the thread that offers neoqb's explanation of what happened, you said "Personally I've dealt with this issue before wih sending email newsletters..."

Doesn't that make this problem foreseeable? One could reasonably imagine that this release was going to involve a substantial volume of emails being sent - which (if I'm follwing the explanation) that's what caused all this.

Shouldn't this have been considered before? As I've mentioned in another thread, neoqb was apparently intent on the decision to require connectivity. Given it was their choice, shouldn't we - the paying customers - be entitled to expect they will attend to foreseable issues?

As I've said all along, I do not expect this to be perfect. I do expect that, since neoqb insisted on this, they'd better be prepared to make it work - and it appears perhaps they are not as prepared as they should be.