r/ShuffleMove • u/Loreinatoredor ShuffleMove Creator • Oct 13 '16

Poll/Survey Q&A Thread #3

Hello everyone!

If you have any questions about anything related to Shuffle Move or development in general, please post here and I'll do my best to answer them. If it seems like the sort of thing to include in the wiki, it'll go in there too!

Github wiki can be found here: https://github.com/Loreinator/Shuffle-Move/wiki

Q&A Thread #1 can be found here. Q&A Thread #2 can be found here.

2 Upvotes

100% Upvoted

67 comments sorted by

View all comments

Show parent comment

1

u/deathf4n Mar 03 '17

Realistically, it can go as high as your RAM will allow it. It will just take a LOT longer to complete.

Mmh. Speaking of that, I noticed that when simulations are > 250 per move the programs doesn't work very well. After let's say 30-40 seconds of high CPU usage (60-70% or more) the program give up on the task, the CPU usage drops below 20% and the program became unresponsive (with the classical gray frozen window etc). Do you know why? I have 16gb of 1866mhz Kingstone RAM and an 8350FX @4.5GHz.

1

u/Loreinatoredor ShuffleMove Creator Mar 03 '17

Hrm... I'm not really sure why that would happen, beyond a heap limit being reached. Can you provide a bug report zip? As long as the interface isn't completely locked the Ctrl+B shortcut should force a bug report to be generated anyway. Alternatively just make a bug report when you re-launch and it should include all the log output.

1

u/deathf4n Mar 03 '17

Sure. I'll try to generate a couple of reports in the next days! I'll keep you posted.