Hi are you sure that they are correct ?
they increased a lot from version 3 to version 4
thankyou
Hi are you sure that they are correct ?
they increased a lot from version 3 to version 4
thankyou
Yes, they are. More people at even micro stakes are 4-betting today. The numbers are what they are, but that's why it's good that the information has been re-analyzed and updated.
i noticed a strange thing : i play microstakes
my 4bet % is 1.61
in step 1 is in "needs attention" section and if i select graph green zone is delimited by ranges 1.4 and 2.6
in step 2 green zone is delimited by ranges 2 and 3.8 !!!
Thanks. I'm looking into this. There's different ranges for micro stakes than other stakes. Did you run any other stake levels recently? I'm wondering if the step 2 is a left over from another stake. Regardless, I'm going to take a look at it and get the developer involved if need be.
i use filter : last 120000 hands
actually more or less are 100000 NL2 18000 NL5 and 2000 NL10
Ok, so it's all micro stakes. We're double checking this. Thanks.
We cannot re-produce this. Can you confirm that you aren't running a different analysis in step 2 than you have in step 1? If you run a separate analysis in step 2, it will NOT update and show in step 1. Step 1 is only when you do a completely analysis without a filter. I have a feeling that you've run 2 different kinds of analysis.
I guess the easiest way to confirm what you're doing is, run a complete analysis in step 1. No filter. Check step 2. Then run what you're doing with the filter and give me a step by step of your process.
i Always run complete analisis from step 1
i tryed without filters and result is the same : all range from step 1 to step 2 are more or less different :
step 1 step2
4 bet 1.4 2.6 2 3.8
sb reraise steal 7.1 11 7 10.8
flop fold vs cbet 46.7 64 41.7 53.8
Ok, thanks for the feedback. I'm having the developer double check this data.
Fyi, there was a new bug here. We think it occurred a couple of versions ago. It mainly has to do with how it was saving the data to file. The developer fixed it though and a new version was sent to HM2 so it will be out in next build. Thanks for letting us know.