Quote:
Originally Posted by kapetain
- Why does your client has to be worse with every new iteration ?
I think it's better with every iteration. Milestones had a performance impact that we weren't expecting, but that will be off in a week or so when 105m hits.
Quote:
Originally Posted by kapetain
Right now it's very laggy and I'm playing just 2 tables. Your client is taking much more resources than a simple 2d application should.
It takes more resources than some other companies clients because it uses Adobe Air. It uses Adobe Air because it means we can maintain the same codebase across all of our platforms. Without it we'd probably just about be ready to release the Mac client, let alone the iPad, Browser or Android (which should be released next month, depending on QA).
Quote:
Originally Posted by kapetain
And its just too bad, because you have a good concept but the software is just bad. And I'm playing 6 months already on it, still no improvement whatsoever in software optimization, shame on you.
I disagree with you there too. Table and site loading times are significantly better than they were at launch.
Quote:
Originally Posted by Heisenberg1
Is it possible to quit as many challenges as you like? Then its possible to "choose" challenge or???
Quote:
Originally Posted by Gerzson
I've been wondering the same question. How does this challenge "reset" works?
You can cancel one of each per month. If you click cancel on one, it'll give you a dialogue saying that you won't get any points for partially completed Challenges.
Quote:
Originally Posted by YouAreHappy
Hi andrew. Could you convert all my MTTs and SNG tickets to one 50nl ticket. Alias: "DrunkenSanta"
Sure, done.
Quote:
Originally Posted by smetje
playing 6 tables, involved in some pots aaaand down goes the site again :/
internet page is down too so I guess it's a big issue :/
Quote:
Originally Posted by SuddenlyGood2
Yes still down but got a box to type a name into this time haven't seen that before.
As it's site wide this must cost the company a small fortune.
It turns out that this was scheduled downtime that I didn't know about. There's not a very effective system for communicating this stuff internally, otherwise we would have prepared for it by e.g. timing our server restart & release for the same time.
Sorry for the problems, it's all back up again now.