Pixyz Scenario Processor: Frequently asked questions (FAQs)

We’ve listened to your feedback and are introducing Pixyz Scenario Processor (SP), a new automation/batching tool that is simpler and more affordable than Pixyz Batch, which is being replaced.

SP is for IT professionals, independent software vendors, and creative studios looking to rapidly automate their 3D, CAD and point cloud pipelines. Learn more in the blog post announcing our 2021.1 release.

SP can be deployed on AWS Marketplace, or as stand-alone executable for Windows, Linux and Docker. If you are an existing Pixyz Batch user, you can follow this tutorial or contact our sales team to migrate to SP.

Here are answers to several frequently asked questions about this new product:

1. What is Pixyz Scenario Processor?

Pixyz Scenario Processor allows you to industrialize and accelerate your 3D digital transformation by enabling you to create scalable, cost-effective and secure 3D content optimization pipelines.

SP is the union of two key concepts:

  • Optimization scenarios: A package that encodes all the steps and settings to get the most optimized result from your 3D data.
  • A compute node that can easily scale with demand, based on virtualization (Docker container packaging available).

Scenario Processor for AWS

SP can be deployed on your Amazon tenant through the AWS Marketplace. It is natively ready to scale by leveraging Amazon solutions (like ECS or EKS).

Scenario Processor standalone: For other situations

You can also choose to deploy Scenario Processor as a standalone application (similar to Pixyz Batch) in your own private data center or on another cloud solution. When deployed this way you’ll be in charge of designing or re-using your own scaling infrastructure.

If support and professional services are needed, Unity Accelerate Solutions is here to support you in building your private data preparation platform, or in supporting your migration.


SP is a headless application that lets you run ready-to-use 3D optimization scenarios.

These scenarios can be designed for different kinds of use cases, whether you are aiming for a specific polycount to fit your target device, or want to convert CAD files (even point clouds) into optimized meshes.

SP comes with a pre-installed scenario. You can find more scenarios on our dedicated Gitlab page. We will regularly add new ones and update the existing ones.

1a. Your GitLab documentation pages (Standalone and AWS versions) show that Scenario Processor offers built-in optimization scenarios, but what if they don’t match my specific needs?

You can create and publish new custom optimization scenarios using the new Plugin Scenario Editor in Pixyz Studio.

You can use the Plugin Scenario Editor instead of the scripting window or your traditional IDE to develop your scenario. You’ll always need the Plugin Scenario Editor to package your scenario as a .pxzext for SP.

Note: Alternatively, starting from the Pixyz Scenario Processor 2021 Update 2 release (March 2022), native python script will be back, allowing our most trusted users to keep running their existing / former Pixyz Batch pipelines at no cost.

1b. How can I scale my automation capacity with my needs?

SP uses Docker container elasticity and orchestration capabilities to support usage ranging from occasional on-demand use to intensive use with scaling for peak loads.

Running on your on-premise or your own cloud vendor tenant, your data stays fully safe. And last but not least, SP on AWS adapts to your budget, so you only pay for what you consume.

2. I’m a Pixyz Batch user, should I migrate to Pixyz Scenario Processor?

SP was created to ease deployment and scalability, as it takes advantage of containerized and virtualized environments, keeping you on the road to modern automation.

The technical difference

Pixyz SP and Batch share the same 3D data preparation engine. The only difference is that SP adds on top of Batch the ability to work with optimization scenarios packaged as binary plugins, whereas Batch only worked with optimization scenarios packaged as Python text files.

If needed, custom optimization scenario plugins for SP can be edited and published from Pixyz Studio. They are meant to be easily exchangeable across the Pixyz community and deployable on all of your Pixyz environments.

Priced by use

The pay as you go model offers automated data preparation that will start at $15/hour (billed by the second, first minute indivisible).

If you prefer to pay for an annual licence, you will still save money as the annual SP floating licence subscription has dropped by over 40% by compute node (and even more if you subscribe to the AWS pay-as-you-go service).

Each former Batch offer contained a shared license for both Studio and the command line batching tool, but SP contains only a license for the scenario batching tool.

The benefit of this approach is that you can scale additional compute instances of SP without incurring the cost of a Pixyz Studio license for each.

You only need only a Pixyz SP license to execute off-the-shelf scenarios (scripts or plugins). A Pixyz Studio license is needed only to prepare & publish your bespoke magic scenarios for Pixyz SP.

We hope you see the benefits of migrating from Batch to SP to better empower Pixyz technology within your 3D workflows with Pixyz.

What is the new pricing?


Pixyz Batch command line interface tool (including the ability to run Pixyz Studio IO) was €18,000 / $21,000 (per annual floating license).


Pixyz Scenario Processor for AWS:

  • €13 / $15 per hour (pay-as-you-go)
  • €10,000 / $12,000 per year, per compute instance. More details.

Pixyz Scenario Processor Standalone (on-premise or cloud vendor agnostic): €10,000 / $12,000 (per annual floating license)

Note: Pixyz Studio is required only for custom scenario generation and publishing. A Pixyz Studio subscription starts at €1,800 ($2,100) per year.

4. Are there any additional resources?

Getting started documentation is available for SP for AWS and SP Standalone.

List of SP packaging

Scenario Processor comes in different flavors:

Standalone versions require a FlexLM license server (that we provide). Please contact your Unity sales representative to get access to those packages.

The AWS version doesn’t require any FlexLM license server. The procurement, entitlement and licensing are handled by the AWS Marketplace. It also natively benefits from AWS resource elasticity and containerized applications orchestration (ECS, EKS, EC2).

Previous Article
Automotive HMI Template: Take it for a ride
Automotive HMI Template: Take it for a ride

Check out our HMI Template, now available for free on the Unity Asset Store.

Next Video
How to create the next generation of automotive HMI with Unity
How to create the next generation of automotive HMI with Unity

Unity’s real-time 3D technology brings HMI design and development workflows together to take visually compe...

Learn how to build dynamic digital twins with Unity

Explore more