N
Another error I just got. Left for a while to do other things and when I started the next episode I got:
"First stage stream initialization failed" and that was followed by "Initialization error" once I acknowledged the first message.
Naturally, each of the errors consumes a token, even though nothing has been downloaded.
They must be onto you buddy... Now might be a good time to sell the house and go underground for a few years until this whole thing blows over.
Someone's panties are in a wad.Just stick to the facts. Don't try to be smart.
The reports and logs are for the developers to interpreted to see how they can make the product better and more stable.
Enough, behave or don't post at all.
Another error I just got. Left for a while to do other things and when I started the next episode I got:
"First stage stream initialization failed" and that was followed by "Initialization error" once I acknowledged the first message.
Naturally, each of the errors consumes a token, even though nothing has been downloaded.
How does one know if it's consuming a token?
I get this error frequently but never realized if it was consuming a token or not since the d/l never initialized.
I'm continually amazed at this obsession about tokens.
No one should ever use up the token limit, you are paying for the service download them when your tokens are refilled. Nobody can watch 100s of movies a week. I don't even care if they are cartoons. Watch with your subscription and then download them at your leisure.How does one know if it's consuming a token?
I get this error frequently but never realized if it was consuming a token or not since the d/l never initialized.
No one should ever use up the token limit, you are paying for the service download them when your tokens are refilled. Nobody can watch 100s of movies a week. I don't even care if they are cartoons. Watch with your subscription and then download them at your leisure.
I have no idea as I have never come close to the limit.I'm not worried about them at all - If i were to hit the limit, so be it. I'm just curious as to if a failed initialization of a d/l actually uses one or not. I would think it doesn't, but i'm not the developer so I wouldn't know.
Trust me, I sleep fine at night knowing what AS can and can't do. Like I said, I get that same error but just clear it and try again and it works if you give it a second or two to load the screen before just clicking through. If the error consumes one, so be it - how would the original poster know if it does or doesn't?
Perhaps I should have explained better - I don't understand the obsession because: 1) it was explained to us all before buying, and 2) even with that, there are dozens of posts about people being unhappy with it (and likewise people saying they are fine with it), 3) many posts explaining it again, and again, and again, and last, 4) the developer's have said it is not going to change.
I understand that people care, no doubt more than I do. But I don't understand why the same things get rehashed ad nauseum.
Now - crashing when you have reached your token limit is one thing. Consuming a token when it should not have may be a valid complaint; petty, but valid. And a token counter would be nice - but harping on it won't make it happen. A counter has already been considered.