Plotting with Madmax in Chia GUI

Today for the first time in quite a while, I am plotting again :muscle:

Bought a new 18TB hdd and thought, let’s try the integrated MM plotter that is now in the Chia GUI.

Well…that didn’t last long.

First off, you can’t view you farmer key while in the plotting screen, so remember to copy that first. If you go back and forth the settings go back to default. Same goes for the Plot NFT name (last question! in the list).
Secondly, you can input temp1 and temp2 directory but it doesn’t explain what these do, so for new users they just have to guess I suppose. For me, I had to go to the Madmax github page to have a look which was which again.

Also, you can input both farmer and pool public key and it only tells you at the very end that you have to choose between “pool contract address” and “pool public key”. However the term “pool contract address” is not mentioned anywhere since they just use Plot NFT name in the interface. Again, new user will have trouble here.

Now I created a plot que with 100 plots, realized I made a mistake (wrong NFT, because I guessed and guessed wrong) so I want to stop the que. Well, you can’t… So here we go deleting 100 plots one by one from the que.
(btw, if you delete a running plot from the que you still have to clean up the temp files by yourself. This is not mentioned, plotting just gets stuck).

So back to Plotmanager that has a simple but effective GUI that works great with Madmax and also shows you the output so you can see what’s happening.

#Griping mode off#


Wonder if he is going to upgrade his version soon
This works so easy

Most all issues you are having are solved by using the MadMax through the CLI. Using the plotting GUI is painful and prone to errors from missing/forgetting some option available in the convoluted menu structure IMO.

So do this >

1) Install whatever version latest Chia GUI and enter your keys
2) Open Powershell
3) CD (to the Chia_plot.exe and Chia_plot_k34.exe location) > currently that would be:

cd C:\Users\username\AppData\Local\chia-blockchain\app-1.3.3\resources\app.asar.unpacked\daemon\madmax\

4) run the MadMax command for example (for a k32 NFT plot)>

.\chia_plot.exe -n -1 -r 18 -k 32 -u 256 -v 256 -t n:\ -2 j:\ -K 2 -d h:\ -f xxxxxxxx -c xxxxxxxx

So simple, so easy, everything is on one command line for adjustment. Go for it!


haha yes I agree with you and that is how I used madmax for most of my plots.

I just felt the need to complain about the Chia GUI version

Just seems that there’s still to many real nerds in the team to get really user friendly stuff out :rofl:

1 Like

Certainly justified. For some tasks, a GUI is fine. But for things like MM, and all its parameters (applied to regular plotter too), it just makes it a disaster to configure. How it was designed in the Chia GUI is beyond bad IMO from an ease of use perspective! I tried a couple times, always screwed up something, and then went back to using the CLI with the new plotters (k32 & k34) from the V.1.3.x releases.

Just to let you know, I’m not having any issues once you entry the keys etc it keeps them in a config.yml file to keep track. And when I launch it remembers what the plots count was from the last time. I just wanted to know, when he might come up wit an upgrade. But I know were were texting to the first guy. :laughing: :laughing: :laughing:

For others reading this thread later, the Machinaris WebUI for Chia has offered plotting with Madmax and Bladebit since last summer. The WebUI allows remote control of plotting, which invokes the relevant CLI plotting scripts.

1 Like

I have what @Fuzeguy listed. I have it in a .bat file. Also, I use the command prompt. Powershell is more versatile. But for a two line script (cd and chia_plot.exe (or chia_plot_34.exe), the command prompt works.

I open a command prompt, and run the .bat file, which includes a first line that changes to the madmax directory.

When my hard drive is full, I edit the .bat file to specify the new destination (the new hard drive location).

I believe that could also be accomplished with some %1% variable (or something like that) so that you can run your .bat file with an argument that specifies the destination drive (negating the need to edit the .bat file when using a new drive).

I also keep a copy of my .bat file on a different drive. After the head scratching of getting all of the parameters straight, I do not want to figure it out again, if the drive fails and I lose my .bat file (or if I accidentally delete my .bat file).

Everything comes down to priorities with software development.

Anyone plotting is an “advanced” user because they are farming, so building a GUI interface for plotting is probably not high on the priority list. The Chia software and plotting is still rapidly changing so the GUI today might quickly depart from each plotter’s options, leaving us complaining that the GUI doesn’t work right or support every option.

Tasking someone to make a GUI for plotting right now probably doesn’t fit with the rest of the Chia development schedule. While making plotting user friendly may help with Chia’s adoption, there are more important things to work on, especially with several other plotting frontends and managers in existence today.

I have some super simple Bash scripts for Linux, and even some .bat files for Windows that help automate plotting if you are interested.

1 Like

I would think that it would be really helpful to show a recommended command line for a given setup in UI, so one could copy that and start experimenting. Sure, a working UI would be nice, but most of us end up running plotters by hand anyway. Stil, having half-broken plotting UI is not really helping.

I wonder if anyone ever used bladebit through chia gui (besides Chia devs and QAs)

1 Like

Exactly that. Half-baked is just waste of time.
It’s a few details, but it makes all the difference.

Farmer key and pool key should just be auto filled from the key you logged in with (original plotter did this as well as I recall)

First question should be OG or NFT.

Few more text balloons to explain things like tempdirs etc, or just one info text with a short manual.

The only thing that really requires extra coding is the option to delete an entire que.

1 Like