#renderfarmservice

Autodesk Maya render project today ! SuperRendersFarm.COM is a Autodesk Maya render farm fully based in the cloud. Our software integrates with Maya and connects you with the farm through a simple plugin.

Super Renders Farm is a Autodesk Maya render farm fully based in the cloud. We support all CPU and GPU render engines and all plugins. Get $25 free credits to try now!

Cinema 4D render project today ! SuperRendersFarm.COM is a Cinema 4D render farm fully based in the cloud. Our software integrates with Cinema 4D and connects you with the farm through a simple plugin.

Super Renders Farm is a Cinema 4D render farm fully based in the cloud. We support all CPU and GPU render engines and all plugins. Get $25 free credits to try now!

It is very easy to create a test render job with After Effects on Super Renders Farm

You just do as the following steps

1. Prepare the project

This step is very important to render successfully on our farm.

Open your project in After Effects and prepare it for rendering here

Make sure that your project does not contain any missing assets.

Every missing asset will increase job render time and can cause problems with rendering.

Note: Video assets - please be cautious when using MOV assets in your project. We recommend using image sequence as often as possible because that is the most reliable solution based on our experience.

Prepare your desired composition settings - resolution, frame rate and duration time.

When rendering to frames, we strongly recommend using round numbers (i.e 30 frames per second instead of 29.97).

Composition settings

Select composition and add it to AE render queue.

Our system will prepare and send only the compositions added to AE render queue. Any other compositions which are used in the scene will be ignored.

            Adding a composition to render queue

Configure “render queue” composition setup i.e render settings, quality, output format.

Note: Output formats - not all of the output formats are supported on our farm.

We highly recommend using standard output presets.

It could be better if you can render your composition to an image sequence (i.e. PNG or JPG sequence) and ideally rendering a composition to frames instead of video. As we currently not support rendering .mp4/.mov format, or video in general well.

2. Upload the projects

There are some ways to upload your files to our farm

Please take a look at here for more detailed

https://support.superrendersfarm.com/hc/en-us/sections/360004247094-Uploading-and-Downloading

3. Start Rendering

After your project is uploaded, you will need to

Click on your scene file -> Submit render jobs (with some parameter configurations via Add New Render Job Form)-> Start rendering

4. Download

when your render job completed. Let's wait for your outputs to be transferred to your shared Folder

Connect to your Google Drive or Dropbox to get your render output files.

Houdini provides a powerful set of tools when it comes to simulating fluids. However, it’s always a challenge to make fluids look realistic, especially for broadcast work.

In this article, let’s explore some hacks from FuseFX artist Kevin Pinga, to create faster, more flexible FLIP fluid simulations.

Autodesk has announced the release of Maya 2022.2. New features include:

A new Scaling feature has been added to the Solidify deformer that gives artists better control when resizing tagged geometry. It is now possible to use the Scale mode settings to determine how the deformation treats the geometry with Edge, Edge Global and Scale options. Normal Scale and Tangent Plane Scale fields make it possible to apply uniform offsets to the scale effect.

The Recent File list in Application Home has been upgraded to allow you to locate a file’s location faster in the right-side menu.

The script editor has been improved with the addition of new options in the Attribute Editor. The new Save All Script Tabs option saves the script tabs open to a file so that they can be easily recovered. Show tabs and spaces visually display tab and space indicators and view white spaces in the Script Editor.

USD support has been updated with stability fixes, performance improvements and improved UV and geometry export as well as viewport drawing of curves and cards.

Bifrost has been updated to make it more interactive, expressive, and robust. 

To find out more about what’s new, read the announcement on Autodesk’s Maya blog and the online documentation.

Source:

Sometime in your rendering Maya, it is normal that something could go wrong, but if you follow the guidelines for sending your render project to us manually.

Scene file - should be saved in Maya 2015 - 2019. We do support .mb (Maya binary) & .ma (Maya ASCII) files. Also, we can render scenes prepared on Mac or Linux OS, however, those scenes should be saved in .ma format so we can relink all paths with to our local network drive.

Project folder - this feature should be ALWAYS used. All paths to \Prj_folder\ should be prepared and set up in the scene. There cannot be any missing assets or scene references. All scenes should be saved in  \PrjFolder\scenes \. Please try to avoid textures saved in different paths than defined in Project folder settings.

Scene references - if there are any, they should be merged into one file. If Scene references cannot be merged, please be sure that all used assets have correct paths to \ProjectFolder\.

Render layers - all layers that are meant to be rendered the need to have a valid renderable camera set. We are not editing scenes & turning on/off render layers. Also file name prefix options should be prepared as "<RenderLayer>/<Camera>/<RenderPass>";. Name suffix should be "name.#.xxx" (for eg. Scenename.0001.jpg). Any other file saving options can cause issues during network rendering & progress checking process. Please avoid name suffix with .# at the end. Image format extension should be always after frame number

Viewport & save - render camera should be selected as well in render settings and viewport. Viewport should be maximized with render cam. Shading details should be switched to "box" without any shading abilities.  Please turn off any kind of GPU interactive render preview

GI setup - should be prepared for multiple machines rendering in both render engines - Mental Ray & Vray. If you are not sure about GI setup - please contact us. Arnold renderer is using "Brute  Force" method, so Arnold scenes don't have to be cached before rendering on multiple machines

Plugins - we are supporting quite a lot of Maya plugins, however, if you are using an uncommon add-on we may need some time to run a test with plugin & our network rendering system

Render specific settings - Distributed rendering, Low thread priority, Render region - should all be off (VRay render engine)

Animated textures  -  animation files (avi/mp4/etc) are not a valid option for animated textures, also .mov files cannot be used. Please make frame sequence (jpg\png or so) and connect the image sequence

Switches - for VRay render engine - in render settings / common tab: "Don't save the image (ignored in batch mode)- OFF, "Animation" - ON (if the scene is animated, not still shot) + correct frame range set up in "start frame/end frame". By frame" value should be set to 1.000. Resolution & render camera - should be selected with correct values / options. "Use VRayFB" - ON. Hide render view - "OFF", "Disable region rendering in batch mode" - OFF (if render region is not used!). "VRay" render settings tab - "Don't render final image" - OFF "Indirect Illumination" - if LightCache is used, "number of LC passes" should be  = 0. "Settings" tab - "Use distributed rendering"  - OFF "Low thread priority" - OFF

MEL / Python callbacks - if the scene is not using any kind of additional MEL/Python scripts/plugins all fields should be empty

Render elements - if they are used, all of them that should be rendered should be enabled! We are not changing scene setups and if any of the render elements are missing during the rendering process, will be re-rendered & billed as separated render-job. In render elements settings - "Separate folders" switch should be OFF

Maya script editor - Please try to avoid "errors". We are rendering using "Render.exe" - not Maya.exe or any other GUI setups so if there will be "errors" in Maya script editor - scene can cause problems with rendering.  "Warning" issues in most cases are just info about non-critical issues so if they are not important we will ignore them in the rendering process. We are saving Maya log file (to .txt) in \Scene_name-log\ directory so if you want/need to check to render time & scene warnings info feel free to download these files

NAME - Scene name, asset and output paths should not contain any special characters like / \ " % #? etc

Having a Camera that is added manually so that its name is different than default ones (sideShape, topShape, frontShape, perspShape, persp).

Having a Maya project folder with "scenes" directory that contains your scenes, for example:

N:/RenderProject <-  this is the Maya project folder N:/RenderProject/scenes  <-  this is the scenes directory N:/RenderProject/scenes/shot001.mb  <-  the scene

if you are using XGen, the xgen directory should be directly in your project directory: N:/RenderProject/xgen

Avoid using any special characters in your file names and paths like "@$:%^" or language-specific non-ASCII characters like Cyrillic or Korean alphabet.