Not sure (yet), but I think subscription may be optional for BlendSwap ... (fingers crossed)
I've been playing with importing 3D models to Half-Life:Alyx and it does have its challenges as it seems to need collision models as well (super simplified version of the 3D model).
For a simple box this would be easy but for a chair or a building (that you can enter, or with a porch etc) this suddenly becomes quite challenging. I wish there was an "simplify model" button (or: minecraft that model hahah).
The Source-2 engine (the 3D engine used for Half-Life:Alyx) optimizes a lot of things, but sometimes we have to help a little. So the collision model is invisible to the player, but because of its simplicity, it takes of less resources to calculate collisions.
As for baking and such: the Hammer tools handle most of it for you - so not much work to be done there. I have found that importing models is quite easy once you understand a few things better (I'm still learning).
Thanks for the Fusion 360 tip - when Fusion 360 became available, initially for free, I did play with it for a bit. I really liked it. 👍
Switching between Blender and Hammer can be frustrating at times though. The controls for panning and such are just different. So after a few hours of working in Hammer, working in Blender becomes very annoying for a few minutes (and vice versa). I really am impressed by Blender (and Hammer). Just wished the world of 3D tools would become a little more "standard". Oh well, FBX models work for both so I'm good to go. Just have to figure a way to make a super simple model of complex models (for collision).
I found that educated folks in labs are much more eager to get better tools. The current tools are typically quite outdated or horrendously expensive.
Haha I can relate to the "not want to change" culture. Believe it or not, less than a year ago I ran into users that refused to let go of Windows XP.
In their defense: there is nothing wrong with XP, but you will have to put some extra security rules and measures in place, and if something goes sideways, IT people right away point at that one XP machine hahah.
Yeah, I hate those "we're not going to do the work for you" response as well. Then simply do not respond. They seem to be willing to spend time on reading and writing a shitty reply. So either help or stay quiet. 😋
This is what I do, some users totally refuse to read an article, or search the comments for a solution, so I do get repeat questions every now and then. In those cases I refer to an earlier comment/solution. There is no need to be an *ss about it 🤣
I wouldn't say it is an engineers or technical people "skill" to respond like that, but I agree that the majority we would run into are engineers/technical people. I think it has to do with wanting to feel superior? (by lack of better explanation) Oh well, in the end I believe that helping each other is just more fun and more satisfying. Nothing cooler than seeing someone happy and grateful for your help. Sometimes they come with the coolest projects, and being a part of such a project is very satisfying as well. Just like reading that folks find my articles or code useful. Just makes my day 😊
Haha, I totally agree with the point of view that academia want to obscurify their work as much as possible. Kinda sad when you really think about it, and I totally disagree with that view.
However, I do have to say that a lot of people think they have become experts because they know how to Google. Knowing your limitations, be kind, be respectful.
I'll have to look op Noam Chomsky ... sounds like an interesting person!
As for the ESP8266 ... I do not know if it has an internal pullup resistor. From what I read here: there is a pull-up resistor on GPIO2. (thanks Google! hahah)
Working with FastLED works great, and straight out of the box.
Initially I was worried about this, since the pins of the ESP8266 work with 3.3V, where as quite a few LED strips work with 5V (I commonly use WS2812 strips). So after reading a lot about shifting voltages, I found out that none of that is needed and I was able to plug the strip in without any additional hardware. So my current setup, for new LED effects, simply uses a power supply, an ESP8266 and a LED strip. Nothing else needed.
Two tips though:
1) For all Arduino's and other boards: FastLED shows these weird PRAGMA messages (useful for devs, confusing for beginners, useless for me). This can be prevented by adding a define line (red below) before including the FastLED library:
#define FASTLED_INTERNAL // just used to mute the Pragma messages when compiling
#include "FastLED.h"
2) Because of the way FastLED uses interrupts, you may experience the occasional flickering. This worked for me (again: add before including the FastLED library:
#define FASTLED_ALLOW_INTERRUPTS 0
Yes your project is definitely ambitious, but also super cool!
And yes, safe wiring is a must haha ... you're working with a lot of power there.
I'd probably with several power supplies and make sure they share GND.
Also the wires cannot be too thin (having multiple PSU's however will make this easier, since the power per group of LEDs will be lower than the sum).