XPlotter for optimized plots (CPU)
-
@k.coins The last number is the stagger, and if you've used Blago's new plotter - it creates optimized plots, so the stagger is correct.
-
@haitch So no ideas on what could be up with the pools reporting crazy deadlines back to us?
I just deleted it and started a new one with XPlotter at 100000000 instead of 100000001. Not sure why this would matter but I figured I'd give it one more try anyway.
-
@k.coins Don't know why the crazy deadlines come up - the pool and the miner should be using the same algorithm to determine the deadline - I don't know why the miner thinks it's good and the pool thinks it's bad. I've had a number of them as well, and couldn't find anything to explain it.
-
@haitch Fair enough. So no go on the new plotter for you?
-
@k.coins I've used it without problems, and have another 5TB to plot - will be using the new plotter.
-
@haitch Wait.... so your plots are working? Should I just keep trying to report to the pool even though all I receive back are really bad deadline warnings?
-
@k.coins Yeah, mine are fine, but have been done with a variety of plotters. Check the log files - determine which plot file they're coming from and recreate it.
-
@haitch Alright, word. I am just trying to get this new plot I made with XPlotter to work. It seems to be the only plotter that has given me this problem.
-
@k.coins I've got another 5TB to plot - I'll use the new plotter and see how it goes.
-
I have a couple of retries but still having the deadline problem, went back to wplotter and optimizer. no more problems.
-
@Yey_09 perhaps you could switch pools to see if its just the pool your mining on?
-
@ZapbuzZ I've tried switching pools - didn't help anything, still getting really bad DLs back from them.
-
for clarity:
I'd make a plot by XPlotter v0.6 (14603 seconds)XPlotter_avx.exe -id 17930413153828766298 -sn 0 -n 1000000 -t 6 -path L:\plotsI have the same old plot (created by wplotgenerator and optimizer)

I'd compare these 2 files:
fc /b C:\plots\17930413153828766298_0_1000000_1000000 L:\plots\17930413153828766298_0_1000000_1000000 >> res.txtRESULTS:
FC: no differences encountered
-
-
@k.coins Have you tried stopping and restarting the miner while the network is on the Block with the error message to see if it repeats?
Rich
-
@RichBC Yeah - it just repeats
-
@ZapbuzZ said in XPlotter for optimized plots (CPU):
@Yey_09 perhaps you could switch pools to see if its just the pool your mining on?
I've tried but still the same. waste 2 days plotting and replotting.
i just went back using wplotgenerator and optimizer, no more problems
-
@Yey_09 i waist 5 days plotting on 6tb ):
back to the old school method wplotgenerator and optimizer
-
I've plotted two different 1TB drives with XPlotter so far, on two different Win7 64-bit systems, and one was good and the other gave deadline errors. One notable thing was that the bad plot was generated by the SSE4 executable (on an older system) and the good plot was generated by the AVX2 executable (on a newer system). Which versions are the rest of you using?
-
i use the avx methode.
but i had bad deadlines as well after i used xplotter
error 1007



