After demonstrating the McLaren Car Configurator live at GDC and showing it off on the livestream, we are excited to explore the creation of this tool with two of its developers. Max Preussner and Alan Willard will be joining us to discuss how the iPad companion app communicates with the PC and also how Blueprints were used in the making of the Configurator. There is a lot to learn, so be sure to not miss it!
This is product placement, no?.. Any self-respecting game maker already owns one of these…
At the very least I think McLaren should offer a competition to give one away for free on here!
It would help make up for the pain of watching so many brutal Formula-1 performances
No product placement We partnered with the team at McLaren to help solve some Enterprise related challenges that help us serve the community of those working in real-time spaces. This is a look at our approach to the configurator
The project we’ll be showing isn’t something that will be shared, but new engine improvements made for it will be included in 4.12. We’ll be doing a high-level overview, but not a “how-to” style tutorial.
Just in case Max and Alan aren’t touching on this, but: Can we use this new technique to control a GearVR app from a tablet (by a second person ofc, for example to guide someone through ArchViz without a controller, or even make changes in the world they experience there)?
Hey BhaaL, yes, in principle this is possible. If your app is built on top of UE4, it will be very easy, because all the needed pieces are already there. Your app doesn’t need to use Engine - you can build a standalone Slate application that is built on top of Core, CoreUObject, Messaging, and Slate. You can look at /Engine/Programs/UnrealFrontend and /Engine/Programs/UnrealLaunchDaemon to see how we have done this in the past.
If your application is not built on top of UE4, then things get more complicated. The main limiting factor right now is that we have only one actual implementation of a message transport (the UdpMessaging plug-in), and it uses a rather complicated (and currently not very efficient) protocol. You would have to reimplement this protocol in your application in order to be able to exchange messages with the GearVR app.
In the second half of this year I hope to find the time to make the UDP based transport more robust and efficient, and I also want to implement a second transport using HTTP and JSON. The latter will make it much easier to interface with non-UE4 applications. In the meantime, I recommend that you build a standalone Slate application with plug-in support. We do not currently have any tutorials that describe exactly how to do that - the initialization process in particular is somewhat cumbersome - but if you can’t figure it out based on the code that’s in UE4 then you can always post on AnswerHub and I will push you in the right direction.
When I’m done with the current Media Framework upgrades, I’m planning to write a tutorial about the design and implementation of the Messaging system in UE4, as well as standalone Slate applications.
My question is:
Is it a Skeleton mesh include all car parts or separate static mesh components in one BP, which is prefer to do exploding the parts?
If it used a skeleton mesh, is it use skin with 100% bone weight or hierarchy, in high density triangles case which is better for performance?
Other one, separate static mesh components in one BP VS separate static mesh actors which is better for performance?
@gmpreussner Thanks! You already mentioned that on the Stream, but samples are always nice. My problem until now was that I didn’t know what to search the docs for, but with the keyword “Message Bus” this turned out to be a lot less troublesome than expected.
It’d probably make sense to have both apps built on the engine, especially for ArchViz where a simplified model could be used as overview map; but stripping it down to just a floor plan for example could just aswell use a simple Android app with the appropriate UdpTransport.
I’ll see how far I can get this, and if necessary I’ll drop you a PM or just throw it on AnswerHub so everyone can follow along.
For anyone interrested in how the Message Bus works, I wrote up some brief instructions on how to hook into the bus and get messages flowing:
It doesn’t show the whole range of possibilities provided by the Message Bus, but it contains the vital parts to get you going. With that (and the docs), doing a simple server discovery and initiate a one-to-one session shouldn’t be too hard. Depending on how much free time I have this weekend, I might extend the post by the one-to-one messaging part.
Yes, we will be releasing our automotive shaders in the near future. The work involved is cleaning up the materials. standardizing the parameters and integrating the relevant engine features to 4.12 release. We are nearly there, though!
I also thought I’d mention that we have a second GDC car demo configurator livestream planned, which will go into the new dual normal clear coat shading model (as used for car paint and carbon fiber) and the new reflection accuracy improvements.
Hang on tight and thanks for speaking up.