rootsrat
Volunteer Moderator
Pink isn't a rainbow colour!
Pink isn't a colour as such in fact
Pink isn't a rainbow colour!
I want the voice from TARS to be added. Best robot voice ever.
Thats not a problem. In all of the episodes they never managed to shoot a single person. I feel pretty safe![]()
Phew. Lucky I'm not in Korea then.
Uhh.... Thanks ?
Thats not a problem. In all of the episodes they never managed to shoot a single person. I feel pretty safe![]()
I'll be happy to be wrong on this one but reading between the lines suggest that Horizons has done very badly and thats why sales were defered in FDs statement. There can't really be any other reason. Unless you think its sold amazingly and FD are just having a laugh. Let us please apply some logic here.
I won't be happy at the demise of this franchise but if things dont change direction I suspect its coming.
Not as bad as ED then ?
?
I don't follow. Isn't this just normal practice?
When you accept payment up front for a product or service which will be delivered incrementally over a period of time, you defer the sales over that period. Portions of the revenue will be recognised as release milestones are hit. Otherwise you risk having one blow-out period where you get lots of sales with minimal costs, then several subsequent periods with reduced/no sales and high costs.
You don't want the liability of revenue received but not yet earned, so you defer its recognition over the time to deliver. In FD's case, if the release 2.1 is delayed, then the recognition of deferred income is delayed as well.
?
I don't follow. Isn't this just normal practice?
When you accept payment up front for a product or service which will be delivered incrementally over a period of time, you defer the sales over that period. Portions of the revenue will be recognised as release milestones are hit. Otherwise you risk having one blow-out period where you get lots of sales with minimal costs, then several subsequent periods with reduced/no sales and high costs.
You don't want the liability of revenue received but not yet earned, so you defer its recognition over the time to deliver. In FD's case, if the release 2.1 is delayed, then the recognition of deferred income is delayed as well.
Yes, that is correct. But this is how Chronic Complainers look at it:"everything is terrible, any random info is further proof that everything is terrible."
Seriously, if it wasn't for the epic Forum battles/discussions/speculations over yet-unknown-and-untested-content ... the heck - what would we do in the meantime ?!
I'd say : let it roll!
After all, it can't be worse than PowerPlay(tm) or CQC(tm) [*]
[*] *lol* don't quote me on that! xD
We'll see when V2.1.00beta goes live...
?
I don't follow. Isn't this just normal practice?
When you accept payment up front for a product or service which will be delivered incrementally over a period of time, you defer the sales over that period. Portions of the revenue will be recognised as release milestones are hit. Otherwise you risk having one blow-out period where you get lots of sales with minimal costs, then several subsequent periods with reduced/no sales and high costs.
You don't want the liability of revenue received but not yet earned, so you defer its recognition over the time to deliver. In FD's case, if the release 2.1 is delayed, then the recognition of deferred income is delayed as well.