Since I have experience with ZBrush plugins, I decided to fix this issue as part of my CopyPaste plugin. The fix itself is ridiculously simple—just a few lines of code to write the subtool name into the OBJ file. When the OBJ is written to disk, my plugin parses the file and injects the correct subtool name where it belongs.
Python can seem daunting to non-technical users. Even after writing simple scripts in Maya, creating interfaces with PyQt can be challenging. Many users resort to adding buttons to Maya’s shelf, but this method is unreliable. Updating Maya or dealing with corrupted preferences can lead to lost scripts and frustration.
I created ScriptMate because I needed a reliable, portable solution for managing my scripts. It’s designed for anyone who wants a clean, scalable way to organize scripts in Maya without relying on its fragile preferences system. Whether you’re a solo artist or managing a team, ScriptMate makes script management effortless.
I started reading Hacker News a year ago, and it was amazing. Sometimes, very smart people get involved in discussions.
But what I see here now is disappointing—people who most likely don’t even have an understanding of the CG industry, real post-production, 3D programming, and so on, trying to push immature arguments. Discussions about whether Blender can have an "abstract Linux moment," or if it can be adopted by big players, lack depth and seriousness. It's just sad to see discussions at this level.
On the other hand, in the world of post-production, we face big problems with very expensive per-seat software from large vendors. We need solutions because even the best industry-standard software—not Blender—has bugs and lacks necessary features. Sometimes, small software projects build communities, push boundaries, and save you at the peak of a deadline, but they’re still not perfect.
You need to understand that Blender is young and has only recently started its own path. It's a very good tool, first and foremost, and it can offer much more if you’re a strong artist or programmer.
But it’s a tool that anyone with knowledge of coding or 3D programming can improve. You don’t need to pay for a license or deal with closed SDKs.
Sure, businesses build around stability, and Blender isn’t a first choice for many. Investors don’t want to make risky decisions. But very soon, we’ll see Blender integrated into pipelines alongside other tools. In the end, it will become the first-choice software for many tasks in the CG industry.
Over the last decade, I’ve seen different companies acquire solutions, integrate them into their own tools, and claim they "innovated"—but they often killed the original ideas and didn’t push anything forward. Most of the major advancements in the CG industry have come from open source or studios that made their tools available for everyone.
Just look at how many new technologies Autodesk has developed in the last decade: none. They just bought solutions or received them from open source.
Stop being narrow-minded and look at the bigger picture
In that moment when i decided to create my own plugin, I didn’t find any useful information. I did a lot of crash tests, read different very old ( oldest discussion was 19 year old ) discussions on forums. Tried to understand how to glue all this stuff together. And finaly structurised all my knowledge in this article. That was interesting experiance for me, as i didn’t have any experience with Zbrush and ZScript before even with C compabilities in Rust. But as end result I hope this documentation will help you to save your time and avoid my mistakes
UPD: Im not professional developer, this is what im doing for my needs as 3d Artist. The code may contain a lot of core mistakes, but it works for me.
Feel free add comments, what I've did wrong with rust and what i can improve.
(Although I think the program still needs a bit of time to smooth out the edges, plus not everyone may be a fan of the AI and collaborative features, which get a lot of care in the GUI. You can turn all of it off, but still.)
But I don't like the implication that Nova is abandoned or less modern compared to Zed. Nova is arguably one of the sexiest apps on the Mac right now – it looks gorgeous and it's far more "Mac-assed" than any of Apple's software, for starters. And in terms of development / maintenance, it should be in VERY good hands at Panic.
You're 100% right on open-source vs closed-source, though.
> Nova is arguably one of the sexiest apps on the Mac right now – it looks gorgeous and it's far more "Mac-assed" than any of Apple's software, for starters.
Really? Looking at the screenshots from the front page it looks like a custom GUI framework and doesn't even look like a native macOS app, even the folder icons in the file tree are wrong. The only way I can tell it's a macOS app is by the traffic lights on the top left.
You're not wrong, the frontpage screenshots don't entirely do it justice. That title bar you mention is one of the most custom-looking components for sure, especially in the "Neon" theme.
But it gets better when clicking around the app – all the different settings, modal sheets and sidebars feel very much like home.
The filetree icons are… a choice, yes. They kind of lean more into the "smooth skeumorphic squircle" look which is normally applied to apps, NOT files and folders. I'm guessing they didn't want to and/or weren't allowed to use the plain icons that Xcode does.
I use zed but I had to switch to the preview because the regular has an awful bug where the fuzzy file finder immediately crashes the app. I thought there would be less of this in Rust.
Is it only me feel the Obsidian overcomplicated for the notes?
I just prefer flat Notes directory and create .md files, which i can sync everywhere i want.
To be honest Obsidian is so good, but i like simple solutions.
This is exactly what Obsidian provides out of the box. All the other stuff like backlinks, tags, Mermaid diagrams, canvas whiteboards and knowledge graph etc are completely optional.
I use Obsidian as a CMS for my website for example. The filetree shows me a list of Markdown files, I add YAML as needed for things like title, date, etc, and that's it.
In that moment when i decided to create my own plugin, I didn’t find any useful information. I did a lot of crash tests, read different very old ( oldest discussion was 19 year old ) discussions on forums. Tried to understand how to glue all this stuff together. And finaly structurised all my knowledge in this article. That was interesting experiance for me, as i didn’t have any experience with Zbrush and ZScript before even with C compabilities in Rust. But as end result I hope this documentation will help you to save your time and avoid my mistakes
UPD: Im not professional developer, this is what im doing for my needs as 3d Artist. The code may contain a lot of core mistakes, but it works for me.
Feel free add comments, what I've did wrong with rust and what i can improve.
