About the Maverick Render category

RandomControl is a pioneer in the development of light simulation technology, and a reference in GPU-accelerated rendering. In 2006 we were the creators of Fryrender, one of the first physically-based render engines in the world, and in 2010 we released Arion Render, one of the first GPU-accelerated render engines ever.

Maverick Render is the result of those 15+ years of experience in the field of light physics simulation.

Maverick is a tool for product visualization like no other that allows designers, engineers, and marketing specialists to bring their projects to life with truly unprecedented speed, quality, and ease of use.

We invite you to download and try it out for free with the 30-day trial. More info at https://maverickrender.com

Rhino connection at Maverick Render: Rhino 6 bridge plug-in | Food4Rhino

I just purchased my perpetual license today. This is the best rendering software I’ve used so far and I’ve tried/own most of the well known renderers out there. By best I mean in all aspects, UI, performance (loving the fact its GPU based), final output, overall ease of use.

I saw the GPU performance chart that the Maverick team posted on their Instagram account and immediately started bidding on two GTX 980 Ti’s on eBay. I just installed one and the other should arrive in the next few days. I wish there’s a Maverick benchmarking tool though. Would love to see the actual difference between the 980 Ti and the 1070 FTW that I pulled out today. What dictates how fast scenes render in Maverick? Is it purely on the number of CUDA cores or does the other tech/features in newer cards play a role as well?

1 Like

:open_mouth: Thank you for the kind words on behalf of the whole team!!

About releasing a Maverick-based benchmark: yes. We are considering that possibility. Actually, we made an Arion-based one (arionbench) time ago. And it would be quite nice to do something similar now, adapted to the newest GPU architectures.

Regarding your question about performance: A number of factors are involved. The characteristics of the render naturally matter a lot (e.g., the complexity of the scene, and the resolution). But then, hardware-wise, the card architecture and the number of cores both matter a lot as well. From one architecture to the next there is usually a very significant leap. For example if you compare recent top-of-the-line models such as GTX1080Ti and RTX2080Ti the performance difference is about +50%. Then, if within the same architecture you compare higher and lower end models (e.g., 1080 vs. 1070, and so forth) the performance gain is also significant. Then of course these raw numbers must be leveraged by the price of each particular model.

1 Like

I am anxious to try Maverick’s trial version as it looks simply fantastic. I will be forced however to replace my AMD Vega video card and replace it with an Nvidia Cuda based video card in order run the software. I hope that RandomControl can find a way to permit AMD video cards to work with Maverick.

Hello @Robb, and thank you very much.

It would be fantastic to support AMD video cards, for sure. But all our code is written entirely on CUDA (Nvidia), and adding support for other types of hardware would require a partial rewrite of the Core, which we can’t do at the moment.

In case that you decide to get a CUDA-capable card, we published a benchmark here:

I have no negative intentions in my comments, but will consider strongly an Nvidia card to support Maverick. Also, will animation find it’s way into the Maverick suite?

Yes, definitely. We are currently working on the UI necessary to comfortably access the animation capabilities of our Core. There will be easy options for basic turntables, object explosions in their parts, camera paths, etc… and then a hardcore/classic timeline with keyframing capabilities.

Thanks so much for paying attention to my feeble needs. Ever more am I committing to Maverick. A very well done renderer indeed! All the best, Rob

I’m trying out Maverick and very impressed with it so far
A quesiton and a comment:

How do I create an emitter? For something like a LED strip?
My Pan function doesn’t work - neither from the scroll wheel or the icon from the UI. Any idea why that is?

Hello @arail

  • “In order to create an emitter, such as each individual LED in a LED strip”:

1- if the leds are meant to be bright, but are not the key light source in the scene, the easiest solution, by far, would be to simply apply an “Emissive (coated)” material from the library.
2- if the leds are a main source of illumination in the scene, you would need to create and place a light in each led object.

In both cases, you might want to enable bloom/glare in the tonemapping panel (available in the most recent build).

  • “Pan function does work.”

You must keep in mind the following:

If you mean PAN as in camera pan:

1- Maverick Studio provides multiple navigation modes to accomodate to our user ecosystem. Some users come from Rhino, and some from other platforms. Go to Settings (or to the Start dialog), and select the navigation mode you prefer. We provide a mode where the navigaton controls match those of Rhinoceros.
2- Then the HELP panel provides an exhaustive list of all the mouse and keyboard shortcuts.

If you mean PAN as in render image (2D) pan:

Select the pan/zoom tool on top of the viewport. Then click and drag to pan, and use the mouse-wheel to zoom in and out. This type of pan does not pan or zoom the camera, but the image, as you would in, for example, Photoshop.

Thank you!

I just tried this, and walked away very disappointed:

  • 0.5gb STEP file assembly exported from Rhino… had to cancel it after 1.5 hours, and it was still at 50%…
  • Quite small recent STEP file assembly exported from Catia… hard crash…
  • No FlexLM floating license support.

Keyshot is still king, unfortunately.

Dear Robert. I will reply in continuation with the conversation you were having with other member of our team by e-mail earlier this morning, since I just saw that you have decided to continue by yourself over here:

1- I am not sure what the problem with your STEP files is. I wouldn’t mind digging into that problem deeper myself if you want. But regardless, Maverick NATIVELY SUPPORTS 3DM FILES. We even provide a Rhino bridge plug-in for this (which is optional, since you can simply import .3dm files directly into Maverick Studio). Using .3dm is by far the easiest, most light-weight, and most natural way to get your models from Rhino to Maverick. Also, assuming that you save your .3dm model from Rhino, there is guarantee that “what you see in Rhino is what you will get in Maverick” tesellation-wise. .3dm being such an efficient file format, import speed is expected to be generally blazingly fast.

2- We import STEP files here on a daily basis. We haven’t been given any information on your GPU, machine specs, etc… So there is no way we could help you there (the problem might be in the tessellation settings, or maybe somewhere else?)…

3- We note that you would wish for FlexLM support. But we have carefully and deliberately opted for online activation as the best solution to allow for us to keep a competitive edge in our prices.