Be careful don't make the same mistake I did.

[diverone]

If you are new to using Pixel Plow please read this so you don't make the same mistake I did and yes many have made this mistake in fact PP has a page devoted to it - do not become as they put it a, 'statistic'. I signed up and paid the ten bucks then submitted a job - I uploaded the TG 4 scene with files etc. I actually thought the ten bucks was a starting point.  I wanted a single frame rendered. I started then went out for a bit, came back and bam it was at $211.00. I cancelled the order. Not a single frame rendered  - 0. If not a single frame from 0-100 was actually rendered what did I pay for? I never read about a max budget etc or frames I assumed something and paid the price for that assumption. I contacted Pixel Plow and asked if they could possibly make an exception after all I paid $211.00 without a single delivered frame - nothing. They response:

"We wish we were able to extend more leniency on these sorts of issues, but at the end of the day, we're a business and have operating costs."

Leniency? That's what a prosecutor tells you. They also said that they weren't hiding anything from me, I never said they did. They say this because others have claimed hidden costs, etc.

[N-drju]

What...??

So, in the end, what was that 211 bucks for?!

Thank you for that warning. I will never use Pixel Plow. Sounds like they are just sneaky, little cheats if they so readily take money for nothing. It all sounds super weird.

Luckily, the guys at Planetside here are very transparent and honest and they offer you a possibility to use several machines at once for rendering purposes, saving you the trouble of dealing with unscrupulous businesses.

I'm sorry you learned the hard way. Maybe you could contact a consumer union or something to get your money back?

[digitalguru]

I was considering submitting a job to them, while it might not put me off, I'm definitely going to investigate further.

If it's a single frame - surely must be a massive frame with a large number of tiles and a high power setting requested? Would be good to know.

That's one unfortunate story, would be great to hear any others experiences with Pixel Plow before I pull the trigger.

[Rumburak]

I rendered several (single frame) jobs on PixelPlow and I never paid more than $5 (lowest Power Settings). You have to take care that you select only one frame and the 'estimated costs' in the PixelPlowAgent are not predicted very well for single frame jobs. But in the end I never had a problem with PP.
I agree with digitalguru, it would be good to know the settings of the job you sent to PP.

[cyphyr]

I'm sorry you had problems with Pixel Plow and feel badly treated.
I use them all the time and have never had any problems with them.
I have two jobs on the farm now for different clients and they are going through quickly and well.

A couple of things to keep in mind and this will apply to any render farm.

ALWAYS do a render on your home/studio computer at your final output settings first. Then use the farms render calculator to get an estimate of the final cost. They are pretty accurate and generally slightly overestimate.

Don't use quality and AA settings higher than you need. The time difference and resultant quality is not always worth it and in some cases can make an image look worse.

Remember that the farm is by definition rendering multiple frames at the same time, not one frame after another so it "could" have been that you had a hundred frames each at 90% and they were nearly ready all finished.

A price of $211 for 1 frame after going out for "only a bit" (a matter of hours?) sounds like the render power settings were set at higher than the default 0.8 (the lowest setting) and that you were rendering multiple frames, not a single frame. Were you rendering at a particularly high resolution?

I'm sure there are other pointers for successful farm rendering and others will chime in if they think of any.

Finally, do check on here if there are any scene specific changes that may help with a project. Plenty of helpful users willing to give advice.

[Oshyan]

Cross-posted from this other thread, but best discussed here since the other thread is about a different original subject.

While this outcome is definitely unfortunate, what happened here is that the user submitted a job at default 5.0 power level, and then did not select a single frame to render, but rather accepted the default frame range of frames 0-100. So PixelPlow started a 100 frame job and thus was consuming resources across 50 or more machines simultaneously, each trying to render its own full image. This is essentially the result of not checking all settings on the submission form before pressing submit, and with money on the line I'm not sure why one would do that.

It's troubling that this may be a common issue with PixelPlow users, but I think if you look at the job submission steps and the settings you have available, you should be able to see that you'd want to change some of those defaults depending on your needs. I do think a "Render Single Tiled Image" checkbox might be a good idea for their submission tool though, but of course people would still have to check that box and not simply accept the defaults.

- Oshyan

[digitalguru]

Makes sense now...

Thanks for the info Oshyan!

[diverone]

Cross-posted from this other thread, but best discussed here since the other thread is about a different original subject.

While this outcome is definitely unfortunate, what happened here is that the user submitted a job at default 5.0 power level, and then did not select a single frame to render, but rather accepted the default frame range of frames 0-100. So PixelPlow started a 100 frame job and thus was consuming resources across 50 or more machines simultaneously, each trying to render its own full image. This is essentially the result of not checking all settings on the submission form before pressing submit, and with money on the line I'm not sure why one would do that.

It's troubling that this may be a common issue with PixelPlow users, but I think if you look at the job submission steps and the settings you have available, you should be able to see that you'd want to change some of those defaults depending on your needs. I do think a "Render Single Tiled Image" checkbox might be a good idea for their submission tool though, but of course people would still have to check that box and not simply accept the defaults.

-

$211.00 charged and not a single frame rendered. Zero. So at just over two
Hundred dollars spent with zero frames rendered across 50 cpus what would cost have
Been if 100 frames were actually rendered? $2,111.00? $21,500? If my scene was never actually
Completed what did I pay for?

[diverone]

Makes sense now...

Thanks for the info Oshyan!

[Oshyan]

It's not my intention to argue with you or explain every aspect of how their system behaved and why. Remember, we are separate companies, we can't ultimately provide support for their service. I just wanted to provide some context and point out that what happened isn't inexplicable (though it is unfortunate). Again I'm sorry that this happened and I totally understand that being out $210 is pretty upsetting.

- Oshyan

[archonforest]

If its not done yet, PixelPlow should at least render the needed frame out and give it to the customer anyways. Even though it looks like the customer made an error with the order it would be a bare minimum and a nice gesture. Just to have some exchange.

[Oshyan]

The job was canceled by the user, it can't be resumed so it would have to be restarted. Not to mention it was a 100 frame sequence with - as far as I understand it - no animation, so that wouldn't be useful to actually deliver. It would be difficult for PixelPlow to automatically determine if something is actually animated in the file, so it relies on the user specifying whether they want a frame sequence or single image, which did not happen correctly in this case.

- Oshyan

[archonforest]

The job was canceled by the user, it can't be resumed so it would have to be restarted. Not to mention it was a 100 frame sequence with - as far as I understand it - no animation, so that wouldn't be useful to actually deliver. It would be difficult for PixelPlow to automatically determine if something is actually animated in the file, so it relies on the user specifying whether they want a frame sequence or single image, which did not happen correctly in this case.

- Oshyan

Ohh boy...

[René]

the 'estimated costs' in the PixelPlowAgent are not predicted very well for single frame jobs.

When you buy something, it's nice to know in advance what it will cost. Even if only an estimate is given, is it not reasonable to assume that it will not cost more than twice as much?

[Rumburak]

When you buy something, it's nice to know in advance what it will cost. Even if only an estimate is given, is it not reasonable to assume that it will not cost more than twice as much?

True. But I guess it's really difficult to estimate the correct rendering costs for the first frame - for the customer and for PP as well. After the first frame it should be easier to calculate, but in case of a single frame render job, the job is already finished at this point. The current system is 'OK', and as I said, I never paid more than $5 for a single frame. But I would also appreciate a better estimation of the final costs, if that is possible.