A good part of my day consits of waiting for Visual Studio (VS) to respond. I work with Unreal Engine (UE) on Windows and VS seems to be the recommended IDE for it, even though it’s not really required by UE or its build system in any way. There are many other IDE choices out there, but I tend to use VSCode for other projects and note-taking, so I wanted to try exclusively using it for UE as well, and this is what I got.
I’ve been getting into machine learning with Pytorch these past few months, and one of my notes which has gotten the most mileage is this “deconfuser” note where I write out all the useful conventions that I need, but occasionally forget. I figured there’s a chance somebody finds them useful, and it would be a good simple post to get some traction and get back to blogging more.
This post describes a simple and minimal workflow for developing Rust apps targetting WASM and running them on the browser with minimal iteration time.
You try updating your project to a newer Unreal Engine version, play around for a bit and realize you need to revert to a previous version. You already changed and resaved some of your assets though, what can you do?
I have a long-term goal of making a GAN that is capable of generating songs similar to the provided training data, mostly as a learning exercise. The idea would be to operate on waveforms directly using convolution, instead of deferring to MIDI approaches.
So this issue cost me about a day of my life. Hopefully you get to this post before the problem wastes your time too.
This is going to be the first of a few of blog posts detailing some stuff I’ve learned doing deep dives in the Unreal Engine source.
This is my first post on this blog.