Log in to Web Manager (web dashboard) at https://app.garagefarm.net and download our renderBeamer app for you operating system.
Install the renderBeamer app and start it. Once renderBeamer is done with the installation process, you need to choose the default download directory. This path will be used as the main output place for all your renders. Next, just log in using the account ID you received or your account email. Please keep in mind that the app should always be running in the background whenever uploading a project or downloading rendered frames.
Once renderBeamer is installed and you’re logged in, you’ll see the Plugins panel. Plugins installation panel should automatically open after the first renderBeamer startup. You can also open it anytime you need to install additional plugins for your 3D apps.
Here in the plugins panel, you can install plugins that allow you to work with our farm. Once you installed the plugin for your 3D app, you can proceed to the next step.
After launching renderBeamer, launch Blender and navigate to Preferences. In the addons tab, search for “renderbeamer”. Once renderBeamer is added to Blender UI you can continue with the scene preparation.
Open your scene in Blender and prepare it for rendering on a render farm.
If you haven’t activated our plugin yet, please go to Preferences > Add-ons and look for “renderBeamer”.
Once your project is prepared, please locate the renderBeamer menu in Blender (in the main "Render" tab). Depending on the project you are going to render, there are two modes to choose from:
For both modes, our Blender plugin is a “one button” solution. You don't need any additional setup to render your scene on the farm. Everything - including frame range, resolution, quality settings and output format will be rendered just like the settings you have in the scene.
Once our plugin completes the scene export, your project will be redirected to renderBeamer to be uploaded. In a nutshell, renderBeamer is a standalone uploader/downloader application that works in conjunction with our plugins. Simply put, it takes care of the file transfers.
After the scene has been fully uploaded, the app will show you a window with a direct link to your scene on Web Manager (web dashboard). To continue use the click here to submit job button. If for some reason you closed the window with the link or it didn’t work, don’t worry, you can locate your project in the web dashboard and submit your scene by clicking on the scene file any time (more on that in the next step). You can also copy the link to clipboard and manually paste it into your web browser.
Now that your project is uploaded you will need to follow the final step - creating and submitting a job to render farm. Web Manager is a home to all your projects and render jobs.
If you followed the link generated earlier by renderBeamer, you will now see the job submission window with several fields and settings. If you didn’t follow the link or it didn’t work, you can do it manually by locating your project in the projects panel, finding the scene file within the project folder (in your folder structure look for the folder called “data”, i.e. Project_name/data/SceneName.blend), and clicking on it to open the job window.
Basically, our Blender plugin automatically detects your settings in the scene and based on them automatically puts the relevant details needed to render your project. Beforeh adding a scene to the render queue, please make sure that all settings are correct and adjust them if necessary.
Frame range - in this field put the range of frames you need to render. For animation, this will range from the first frame of the animation to the last one set in your project. For example, 1to780s1 - this means that the full sequence of 780 frames for the range 1 to 780 will be rendered. The parameter "s1" means that every subsequent frame in your range will be rendered. If you need to test the scene first, then we suggest you set a higher value, eg "s20", then every twentieth frame in the animation range will be rendered. So if you set the range to 1to780s20, then frames 1,21,41,61,81,101,...,741,761 will be rendered.
If you only want to render a single shot (still image), the range should always be one frame, for example: 1. Then you will render one frame number 1.
Resolution - here you can set the resolution (in pixels) for your project.
Aspect ratio lock - if you need to change the resolution and want to keep the aspect ratio, you can use one of the available options: 4:3; 16:9; 16:10; 21 9; 1:1. Leaving the option as "none" means that you can modify the values for the "Resolution" field without the aspect ratio.
Bucket X/Y - in this field, you will find options relative to the "Tiles" settings in Blender. The values are automatically set by our system based on your chosen render device and resolution. If you assume that changing these settings will be more optimal for rendering your scene, you can set a different value.
Output path - here you can find the default save path for rendered frames from your project. The default output path is based on the name of your project and scene. You can edit this path if you clone your job and need to render a different range in that project.
Output file (w/o ext) - by default, the frames file name is set based on the name of your scene. If you want to create a unique name and/or you need to customize naming for the output according to your pipeline, you can set your own name for the output file.
Extension - a format for the output file(s) is the same as in your settings in the scene. However, if you want to change the extension to a different one, you can choose from the available options, i.e: BMP, IRIS, PNG, JPEG, TGA, RAW TGA, CINEON, DPX, MULTILAYER, EXR, HDR, TIFF
Priority - before adding your scene to the render queue, please decide how you want to prioritize your job. Depending on the queue and traffic, a higher priority may allow your job to quickly acquire nodes to render your project faster. Each priority has a different rate and gives you a different number of nodes - a detailed list can be found here:https://garagefarm.net/pricing
Version - by default, the version of Blender is set as the same one you have used on your PC to upload your project via our plugin. However, if you need to use a different version of Blender than the one detected, then you can choose a specific version available in the list.
Retries - the value for this option is set to 2 by default. This means that if a rendering process fails or the software crashes, our system will perform two additional rendering attempts. We recommend leaving this option set to default (value 2) as this is the optimal setting to retry rendering in case of random 3d party software errors.
Node groups - depending on the priority you choose for your job, you have two options:
The full technical specification of nodes can be found here: https://garagefarm.net/pricing
Render device - depending on your preferences and the specifics of the project, you can use one of two options: CPU or GPU.
Rendering engine - our plugin automatically detects the render engine that you have used in your project. If you need to change this setting, you can do it without sending the project again by changing the engine to one available from the list.
Supported renderers: Cycles, Blender Internal, Blender game, V-Ray, LuxCoreRender.
Cycles path tracing samples - if you need to increase or decrease these settings, you can do it by changing the value in this field.
Camera - if you use several cameras in your scene, you can select the one you want to use to render your project. Moreover, if you want to render several cameras using the same scene, you do not need to send your scene again, just clone your job and select a different camera from your project. Then set the proper settings for the next job based on the same scene.
Strips - this is our custom distributed rendering system. It’s designed especially for high-resolution still shots. It works with all rendering engines and for both render devices (CPU and GPU). Depending on which settings you choose, submitting your scene with this mode creates two jobs: render and merge.
This option allows you to choose the number of strips that will be used when rendering your job. You can choose from options: 4 (2x2); 16 (4x4); 25 (5x5); 64 (8x8). If you leave the value set to 1, then your job/frame will be rendered on one node. Otherwise, each strip (part of your frame) will be assigned to one node. You have to remember that the number of strips is strictly dependent on the resolution you have set. If your resolution does not have many divisors, please try to modify the height/width values of the resolution.
Frames per execution - this option is only available for animations. By default, the value for this option is set to 1. This means that each frame will be rendered as a new execution (the scene will be loaded every time on each node).
The FPE (Frames Per Execution) option allows you to render several frames (the value you put in) in a row without a need to reload the scene on a render node, and potentially may improve rendering efficiency. If your scene has a long loading time but a short rendering time, you can set FPE to a higher value (for example 4). If the loading time is not long but the rendering time is long, leave this value as default or set it to 1.
Job node limit - by default, the value for this option is empty and so the nodes are assigned automatically depending on the priority set for your job and depending on the nodes availability on the farm. Nevertheless, if you want to limit the number of nodes for a given job, please put here the value of the maximum number of nodes you want to be used while rendering.
Add job as paused - if you tick this option and then submit your job, it will be added with the status “paused”. This means that it will not start rendering automatically. It is worth using this option if you intend to add your scene to the queue, but you do not intend to render it at the moment - after adding a "paused" job, you can resume it at any time by selecting the "resume job" option (right-click on the job).
Submit - selecting this button will immediately add your scene to the render queue. Please remember to check all settings before choosing this option!
Cancel - if you do not want to add a scene to the render queue or you want to reset your settings and add the scene again, you can use this option. The submission window with the settings for the given job will be closed and all changes will be cancelled.
After giving your render settings a final check and choosing your preferred priority hit Submit to add your job to the render queue. If you’re a first time user, you will have received $25 worth of credit to test out our service. The credits should be enough to run a few test jobs and get you familiar with the service.
When the job has started rendering, you can check the real-time progress of currently processed frames. To do that, just select the render job from the main project list and then click the arrow on the top right side to open the progress panel.
The Progress Panel (the panel on the right side of the screen) will show its content only when any of the jobs is selected. The panel is divided into 3 sections.
Active frames - it shows currently rendering frames. When a frame finishes, it is moved to the second section Done frames. If you select any frame in the Done frames list, you can then access the render output process log in the bottom section called Process results.
Each frame that has completed rendering is downloaded automatically to your local drive to a directory you selected in the renderBeamer application. If you’re not sure where your download folder is located, you can double check it or change it in renderBeamer’s settings (click on the cogwheel). Also, make sure you have auto download turned on to get the frames downloaded as soon as they are available. If this box is unchecked, you will have to click on each job in Beamer's "downloads" tab, and manually download the frames.
If you prefer more control over what to download and when, you can also download your frames manually. To do that, just turn off auto download switch in renderBeamer settings and go to the “downloads” tab. Next, select the desired render output using a checkbox, and click the download button.
This kind of workflow will download all rendered frames for the selected job or jobs. However, renderBeamer also gives you an option to download individual frames. To do that, you need to use the list files function under RMB.
Once files for the selected job are listed, just roll down the list and select the files you’d like to download using checkboxes. Next, use the same download button.
Once your frames are downloaded, you can use open directory option under RMB to open the folder where frames are saved.
When you use up all your trial credits, you’ll need to charge your account to continue using the service. Please note that when your balance goes below $0, you won’t be able to download rendered frames or start new render jobs. You can make payments in the Billing panel in Web Manager. We accept debit cards, credit cards, PayPal and DotPay payments.
If your rendering needs are high or you plan to render regularly, please make sure to check out our volume discounts.
You can talk to the GarageFarm.NET’s tech team any time of the day, any day of the week. We’re here to help you get started, answer your questions, and assist you in any way. Don’t hesitate to give us a shout.
You can contact us through our live chat accessible in the web dashboard or our desktop app when you log in to your account or message us here through the guest chat.
We also recommend checking out our FAQ page which answers most of the questions new users have.