Aras Pranckevičius @aras@mastodon.gamedev.place

So! I'm told there's a Unity build with raytracing (DXR) goodies, i.e. HD render pipeline with optional raytracing for various bits. Here on github: https://github.com/Unity-Technologies/Unity-Experimental-DXR

Whoa, looks like I've been in build system team for two years already. Time flies! Here's a blogpost, with some neat tools we've built. https://aras-p.info/blog/2019/03/08/Two-years-in-a-build-team/

Measured Materials Library - 300 free scanned materials for Unity's HDRP https://blogs.unity3d.com/2019/02/08/we-have-you-covered-with-the-measured-materials-library/

Quick post on "infinite sky" shader for Unity http://aras-p.info/blog/2019/02/01/Infinite-sky-shader-for-Unity/

Intel's OpenImageDenoise, an open source denoising library (currently CPU based?) is out! https://openimagedenoise.github.io/

Kinda tempted to try it out on my toy path tracer :)

I added flame chart profiler output option to Clang, so I could see where exactly time goes while it's compiling. Already found some good stuff! Here's a blog post with info http://aras-p.info/blog/2019/01/16/time-trace-timeline-flame-chart-profiler-for-Clang/

I made a blog! Where I (again) rant about lack of "where did compile time go?" tools in C++ compilers, and end with a cliffhanger. http://aras-p.info/blog/2019/01/12/Investigating-compile-times-and-Clang-ftime-report/

"Visual Studio IDE is just fine being a 32-bit process", they said :) And now it doesn't have enough memory to *close itself*.

Sure, I am working with the solution that contains whole llvm/clang source code, which is massive. But still!

Direct3D team decorated their office wall with 402 GPUs spanning 35 years of graphics hardware evolution. Nice! https://blogs.msdn.microsoft.com/directx/2019/01/07/wall-of-gpu-history/

Looks like in 2018 I managed to delete more code than I added. Happy with the general downward slope. Gotta delete more :)

Monday mornings are for solving hard problems!

Because "why not", I made my toy path tracer run in the browser via WebAssembly. Was pretty easy! http://aras-p.info/blog/2018/11/16/Pathtracer-17-WebAssembly/

The most excellent and lamentable tragedy of Flat UI Design, in two acts.

I updated my toy path tracer Unity C# Burst code with a 4-wide HitSpheres implementation. PC 84->133 Mray/s, Mac 36->60 Mray/s. http://aras-p.info/blog/2018/10/29/Pathtracer-16-Burst-SIMD-Optimization/

Is good Friday. Removing https://github.com/aras-p/hlsl2glslfork and https://github.com/aras-p/glsl-optimizer from Unity main codebase, since we stopped using them a while ago. They served a good purpose between 2010 and ~2017, but time to let go.

It took a while, but Terrain system and tooling in Unity is getting some updates ;) https://blogs.unity3d.com/2018/10/10/2018-3-terrain-update-getting-started/

I did a talk on Entity Component Systems & Data Oriented Design for junior/future engineers here at Unity (not Unity specific at all). Slides: http://aras-p.info/texts/files/2018Academy%20-%20ECS-DoD.pdf and toy project (C++) for it: https://github.com/aras-p/dod-playground

The t-shirt says the truth.

Evening 7: spaghetti code.

Evening 6: fractals, fractals everywhere.