In my MonkerSolverFree.l4j.ini file this is written:

Does anyone know what values I should change these to? I have 8 gigs of ram and 64 bit windows 10.

Can someone please tell me how much ram I would need to run postflop 6max 100bb plo srp sims with 3 sizings on each street? Buying a new computer and would also appreciate any other recommendations for it to use monker effectively (postflop only). Many thanks.

few days ago I bought MS. Unfortunately support did not answer for this few days. I installed MS on 2 laptops. On one of them its absolutely usefull bc RAM only 8 gb. Is it possible to cancel license and than get a new one? Or maybe if install virtual mashine on my slow laptop I will not need another license?

to put simulation whith rake and Cap there is some "milli chips" 1000=1 chip ... I hope 1 chip is 1 sb in this program. Than cap 2,5 bb = 5000 millichips?

support did not answer for a week... seems I just waste 500 euro

As far as I know support no longer exists. You should be able to reinstall on another machine though with no issues as I had the same issue.

Sent from my SM-G965U using Tapatalk

Does anyone have a 200bb 6max preflop sim for sale/trade?

I'm also looking to buy 100-200bb plo 6max as well as 6max nlhe and huplo.

If anyone wants to go in on buying some sets together too hit me up.

How much do these run for? Looking for NLHE 6max

Server offline and I cannot login for 3-4 days.
2 guys in skype group told already that server is offline but they can login in same way as always.

I tried as well and nothing happens.

Maybe my "same" is different from their "same"

Help plz

Is there a way to put Monkerviewer local files onto my android phone or is it cloud support only?

Thanks!

Got the same problem. Have you been able to login yet?

cant login in the viewer. Bought the monker but i cant see the ranges there. What should I do?

Have read recent posts and seems like support doesn't exist anymore. If I purchase monker... I will be able to download/install/run it , right ?

Major update - Monker is alive!

https://gyazo.com/f6847e7820372a013cada5ffbaf495bb i see update but it fails me each time i open monker? any ideas?

Nice update. Massive performance improvements.

No one else getting an issue with the update? It times out everytime i start up monker.

Is there a way to do the opposite and import .rng files into MonkerSolver?

My preflop ranges in monkerviewer suddenly become pure (no more mixed combos). It wasn't like this before. What could be the problem?
https://pasteboard.co/IzV8uai.png

Solution: press Enter

Anyone experienced any of these after the update?
- I am not able to remove nodes from the tree after the update, only able to add new ones.
- I get very different frequencies on older runs that I've done before the update. I have recorded frequencies on a file from sims I've ran 2-3 months ago and with the new version I get much different cbet%/xr%, etc.

I noticed "cloud" popping up when loading sims from the library. Does anyone know whether it's possible to run sims from Gdrive or other cloud providers?

Problem removing nodes here as well. However, clicking the "Count nodes" button after a removal attempt refreshes the tree, and the node now goes away. I emailed the developer about it, so it should be on his TODO list.

I havent redone much previous work, but during a quick rerun of a preflop sim I saw some small discrepancies (for example, a 3B% vs a tight open range dropped from 2.5% to 2.0%). I'm assuming this is related to optimizations/improvements of the algorithm (we'll have to take the developer's word for it, since we don't have reference sims to compare to).

Did you see the discrepancies when rerunning an old tree built in the old version? You could try to rebuild the tree in the new version, run it, and see how that fares against the previous sim. There could be compatibility issues between old trees and the new version.

I have had mixed results with the tree refreshing, sometimes what you are saying works, but not all the time. Seems like a quicker thing to fix tho, so lets hope it gets better soon.

I haven't reran an old tree yet, since I looked at larger trees, so I have to run them for quite long before I know. I know for sure my discrepancies were way bigger than what you suggest - like cbetting ranges going up by 20% in absolute terms and xr% going from 20% to 40%, which skews everything else.

Do you know in what direction the optimizations are - are they for the speed/size of the trees or for the accuracy? Do you think its a good idea to rerun older trees with the new algorithm?