Alan Sherba

@AnimalCompanyVR w update

@suzpire i don't think so. it's from: assetstore.unity.com/packages/3d/ve…

@AlanSherba I recognise that tree on the left, is it in animal company?

Would you use a tool that lets you leave comments on Unity Scenes? #madewithunity #gamedev

@_rubeki #3 is gorgeous

I use photography these days to find inspiration and farm vibes So I started an Instagram :) Link below if you wanna follow

In the end this lets us randomly generate new map layouts every week. More importantly however, it lets us make big structural changes to an environment. Even if we never used random generation, marking up our environment flow into socket-ed chunks like this is so useful for being able to make big iterations on a level. In the video you can see a few major iterations the mines environment has gone through.

Secondary nodes like ore spawns and enemy spawns target a particular section of the map.

Made this tool to design the environments for @AnimalCompanyVR 🧵

@MohamedHamdy295 Roughly the same as something like this: code.tutsplus.com/make-a-neon-ve… But all done on GPU with compute shaders. Then the final displacement texture is sent to a VFX system instead of just displacing a mesh.

@AlanSherba Its really amazing can you explain to me how did you achieve the background effects

@ZeroCartin Unity :)

@AlanSherba nice! Unity or Blender?

@FreyaHolmer Splender ✨

my modeling tool is still unnamed, idk what to call it ;-; the goal is to make it a mid-poly tool for level art and props, ideally you should be able to use this for all static models for an entire project from start to finish!

got vertex selection up and running~

Prototype I never finished. #madewithunity

@passivestar_ Kinda sound like im just asking for a package manager that already exists lol idk.....

> Resources Oof yeah this makes things more complicated. I was going to suggest using gists to manage it, but you couldn't bundle a texture with it... To me having tiny components is good, but the source code being quickly auditable and fork-able is a requirment. I imagine lots of components in a monoreop would lead to me copy-pasting components into my own repo, where I then loose any benefit of being able to track changes from the original author vs my own. Once I download a plugin, it needs to be edit-able. Either I break the link to the origin, meaning no chance of a future update and i'm removed from this ecosystem, or I fork something. --- Don't have any solution lol. It feels like a Github UI/UX issue. A repo for every node is the answer, but organizing and managing such a thing is horrid. Gists are lighter-weight but less functional 🤷

sir a second pm has entered the figma file