![]() |
|
#171
|
|||
|
|||
|
I am getting the following error when I try to use SS.
Job Error "Unexpected protocol character from backend (send_query); Unecpected protocol character from backend (send_query) I connected to my Postreg DB and got a successful message. This is using 1.0.0.21 AND 1.0.0.23 versioins |
|
#172
|
|||
|
|||
|
I just downloaded this today and am enjoying playing around with it. I do have a few questions though.
-How often does this refresh without hitting the Refresh button? -I notice that sometimes it is lagging behind 20-30 hands behind what I have in PT for stats on opponents I am seated with, is there a way for me to change the frequency of refresh to keep it more up to date? -Even when I hit refresh, the hands recently stored in PT do not come up, atleast not often. It might update every 15min or so, what can i do to change that? My PT stats are a bit lacking for what I'd like to use this for, obviously the more HH's I gather, the more effective it will be. However, I am enjoying it thus far. I'd just like to find a few optimizations before it goes Beta and I consider paying for it. Thanks for all the help! |
|
#173
|
|||
|
|||
|
[ QUOTE ]
I just downloaded this today and am enjoying playing around with it. I do have a few questions though. -How often does this refresh without hitting the Refresh button? -I notice that sometimes it is lagging behind 20-30 hands behind what I have in PT for stats on opponents I am seated with, is there a way for me to change the frequency of refresh to keep it more up to date? -Even when I hit refresh, the hands recently stored in PT do not come up, atleast not often. It might update every 15min or so, what can i do to change that? My PT stats are a bit lacking for what I'd like to use this for, obviously the more HH's I gather, the more effective it will be. However, I am enjoying it thus far. I'd just like to find a few optimizations before it goes Beta and I consider paying for it. Thanks for all the help! [/ QUOTE ] Your lobby does not refresh at all unless you hit the refresh button. You can use the clear cache option to clear the player stat cache and re-load and refresh it. This will make it run slower though, because it will have to re-calculate all of the players stats every time you do it. I would definitely suggest datamining to you. Look (or do a search) for threads in this forum about FPHG or iWitness. This will help you build your database and get statistics on more opponents. |
|
#174
|
|||
|
|||
|
[ QUOTE ]
Question about custom scoring: What happens if several categories match a player? It seems to me like the first one is chosen. In that case, it would be nice if you could re-arrange the order of the categories. Thanks for your hard work and the quick releases. Your coding fingers seem to be on fire right now [img]/images/graemlins/smile.gif[/img] [/ QUOTE ] hehe thanks. [img]/images/graemlins/smile.gif[/img] Yes that's correct, the first rule would fire. It does need some buttons for rearranging them, I'll put that on the list. Thanks. -Ben |
|
#175
|
|||
|
|||
|
[ QUOTE ]
I am getting the following error when I try to use SS. Job Error "Unexpected protocol character from backend (send_query); Unecpected protocol character from backend (send_query) I connected to my Postreg DB and got a successful message. This is using 1.0.0.21 AND 1.0.0.23 versioins [/ QUOTE ] This sounds like you have an old version of the Postgres OLE DB driver. SS installs this for you automatically. One thing to try: shutdown ALL applications, then reinstall SS. After doing this open up your Windows\System32 directory, and file the file PgOleDB.dll. Right click it for properties, click on the version tab. It should read "1.0.0.20". If its something different there is something going wrong during installation. -Ben |
|
#176
|
|||
|
|||
|
Just wanted to say *cough*6maxfishscoring*cough* great piece of software!
|
|
#177
|
|||
|
|||
|
Good news: your addition of the proxy capability solved my connection problem.
Bad news: so SS lists all the tables and starts pulling stats...but it took 24 minutes to get stats for all 88 tables it listed. Clearly this can't be normal. I have it pulling from 4 SQL DB's, each with about 500K hands...I know that's a lot, but it doesn't seem like SO much that it should slow SS down as much as it appears to be. Any idea what's going on here? (Just an idea...have a field where the user can specify the minimum number of players a table must have to even appear in the table list...e.g. i don't care about tables with 1,2, or 3 players...so it seems like a waste of resources to have SS even look up players at such tables.) P.S. now when I start up SS, I get a "Invalid Floating Point Operation" error popup screen with a red cross and it doesn't work at all...any idea what that means? |
|
#178
|
|||
|
|||
|
[ QUOTE ]
Just wanted to say *cough*6maxfishscoring*cough* great piece of software! [/ QUOTE ] We are definitely working on that. That should be ready in a couple of days. -Ben |
|
#179
|
|||
|
|||
|
[ QUOTE ]
Good news: your addition of the proxy capability solved my connection problem. Bad news: so SS lists all the tables and starts pulling stats...but it took 24 minutes to get stats for all 88 tables it listed. Clearly this can't be normal. I have it pulling from 4 SQL DB's, each with about 500K hands...I know that's a lot, but it doesn't seem like SO much that it should slow SS down as much as it appears to be. Any idea what's going on here? (Just an idea...have a field where the user can specify the minimum number of players a table must have to even appear in the table list...e.g. i don't care about tables with 1,2, or 3 players...so it seems like a waste of resources to have SS even look up players at such tables.) P.S. now when I start up SS, I get a "Invalid Floating Point Operation" error popup screen with a red cross and it doesn't work at all...any idea what that means? [/ QUOTE ] The 88 tables in 24 mins does seem kind of slow. But with 5 databases that is possible. There is some good news though, another 2+2 user is working on a technique of creating a summary database from your PT databases that only includes the aggregated stats. That summary database is small and fast. Once that piece is working, you should have no problems with the speed. Also, once you have SS scanning the tables the first time, the 2+ times you do it should be much faster due to SS's caching. The invalid floating operation is a new bug to me. Does that list a memory address for the error? Could you send me a screenshot if it does ([email protected])? Does it just happen at startup, or do you have to do something to make it happen? -Ben |
|
#180
|
|||
|
|||
|
I'll agree with previous posters that 29.99/month is a rather steep, but that it is reasonable to charge monthly. I think you should base your pricing on the number of people that participate in your beta. If you have a larger user base, you should charge a little less. Also, support for number of sites does make sense, as that will heavily change the bandwidth used.
I would fully suspect that a price of around 10-15 dollars/month would be highly profitable, yet reasonable for all users. (anything more is kind of ridiculous, considering the price of stuff like online games). At this price, you could bill this as an essential tool at a great price. |
![]() |
|
|