Thursday 16 November 2017

Python in Unreal Engine 4

While Autodesk University might seem like too much of a manufacturing kind of thing for most game developers, a lot of game companies actually take part in this initiative. Just a couple of hours ago we’ve received a little email from Epic Games, giving a little glimpse of using Python and Blueprints in Unreal Engine for the purpose of data preparation. The piece is published by Ken Pimentel, the senior product manager at Epic.

Where we need to go

To get to a truly frictionless workflow, we also have to address issues of automating and preparing data for real-time use. We can’t always expect data pushed through Datasmith to be “render perfect” or “optimized,” so we have to provide some means of addressing these kinds of issues in a non-destructive manner (meaning you can easily make changes to the upstream data without repeating work you’ve already done).


Traditional workflows to get data ready for the Unreal Engine rely on other tools to optimize the data.

The future revealed

This week at Autodesk University, for the first time we’re showing an early preview of using Python and Blueprints in Unreal Engine for the purpose of data preparation.

 Future workflows to get data ready will use Datasmith and Unreal Engine-based tools.

The demo provides a quick window into the possibilities when users have the option of working in Python and/or Epic’s Blueprint Visual Scripting to take advantage of new, sophisticated data preparation tools that process and optimize scene data. Data prep functions we’re exploring range from “find all parts smaller than 1 cubic centimeter and decimate them” to “find these objects and automatically repair them (fixing bad topology, gaps and overlaps).”


 In this example, the motorcycle is processed with a series of simple rules that create a more optimized version.

You can find the full post over here.

© kikundra for 80lvl, 2017. | Permalink | No comment | Add to
Post tags: , ,

Feed enhanced by Better Feed from Ozh

Read the full article here by 80lvl

No comments: