I recently updated my #Unity project from 2022 to 6.3 LTS and everything went absolutely flawlessly. Didn’t expect that. Pretty impressive, I gotta say.
#Unity
$5.11 for two Mac builds on #Unity Cloud Build. Bruh. Shit’s getting expensive. What are people using for devops these days? #gamedev
Lesson learned (again): When getting a pooled object in Unity, set the position and rotation *before* setting it active. The lifecycle methods and the physics engine might otherwise interfere, even when it looks like you have a clear path in your code from A to B. #unity #gamdev
As a #Unity old-timer, I often miss when Unity introduces new functionality, like the ObjectPool class that seems to around for years now. Totally missed this one. Good bye homemade…
So I guess this means better backup all those #Unity packages right? 🤷♂️ 😬 #gamedev #indiedev
While I have successfully managed a #selfhosted GitLab with automatic CI/CD for #Unity game builds, I realized the whole signing/notarization process is only possible on a Mac, so the dream of the one CI/CD to rule them all is suddenly out of reach again.
I added a public property “debugLog” to all of my ScriptableObject events, to see when listeners are registered and the event is fired. Great for insights. #unity #gamedev
So I tried a dual monitor setup for #gamedev with a big central horizontal monitor and a vertical one for code. At a 16:9 ratio, the vertical monitor was just too thin for me. I’m back at a dual same-size 16:9 setup, #Unity on the left, editor (#Rider) on the right.
So another #Unity #ScriptableObjects realization: If you clone a ScriptableObject for and later Destroy() it, it might still stick around before being garbage collected. Instead of cloning the object for runtime data, I ended up using a regular C# object.
After all these years using #Unity I just learned about the cost of null comparison against Unity objects, duh. #gamedev github.com/JetBrains/resh…