imo fps serves as a final target, but not a valid performance metric. Same way you can say a car can go up to x km/h, but we measure the cost of driving at that speed in more appropriate terms such a L/100km. Same applies here, FPS for final output, μs for cost.
hopefully the quotes in that message convey my disdain for those performance reports since they are not based on a good measurement at all.
Anecdote, I am sent "detailed performance reports" on rendering changes from the tech artists, and it's always measured in fps. They run at a capped fps when testing.
Hopefully one of these days I'll get a report listing microseconds instead of fps, but it's a long road to get this changed.
If I may extend this question, in case you touch everyone's code, how do you ensure people understand and learn from the why and how, to improve performance understanding across the studio?
Meanwhile in Mitte it gave the most Death Star looking version of the Fernsehturm.
Quality video, loved every bit of it. Not sure if you stumbled on this while researching, but none the less recommend browsing the Game UI Database. It doesn't cover everything out there, but still gives you a great overview over many years.
A quote that still keeps me awake, "Don't call them game engines. Unreal and Unity are like advanced UI toolkits."
Followed with a questioning rant from my side asking how they could possibly see physics, wind, etc as UI toolkit related. The whole "engine Y for Industry" license is to blame imo.
Also, for those that have a good offer open to them to take a super-long-unknown-duration-sabatical from game dev, maybe worth thinking about it for the next few years
Pff, we worked together. You toooootally weren't the kindest most chill person every that was a pleasure to work with. But you tooooootally were a gym chad macho bruv. 😉
for more details that are public, here are two articles from Rivian using Unreal in their cars.
www.unrealengine.com/en-US/spotli...
www.unrealengine.com/en-US/spotli...
You can sit in a car for a moment and very quickly realize just how much isn't just the compositor blitting a bunch of icons.
Got to be vague for obvious reasons. Those mountains are not flat images. Neither are the tubes and needles on the driver display. Each screen also has a mix of renderers layered on top of each other. Also, the driver display has stereoscopic rendering that is based on your head position.
Aside from that, amazing week and looking forward to the next edition.
Looking back to a fun week at the Graphics Programming Conference, one clear pattern whenever socializing with new folks emerged, everyone was both amazed but also horrified to an extent hearing about all the realtime 3D being done in recent cars and their respective systems.
Hey I'm Tom, Expert Engineer/System Architect for rendering at Mercedes-Benz. Worked on things like Need For Speed, Sniper Elite and Forza. You may have bumped into me at the Graphics Programming Conference or some other one.
The entire site started to feel like we were on a subreddit dedicated to that individual. Strange.
Anyway, on to more interesting and fun things here instead
Still got 3, I’ll dm you on Twitter
Or, in my case “guess I’ll go on this elaborate walk that conveniently passes by my favourite French pastry bakery”. At least it helps get the steps in between meetings.
One of the most shocking things to see outside of games is people treating engines as “just a renderer” that can easily run 20 times side by side on embedded systems.