blender VS obs_scripts

Please try looking through some large open source projects and contributing major contributions by familiarizing yourself with the code base, learning multiple programming languages, and not having major bugs in your code. I'd imagine you wouldn't want to do this.

Here is a weblink: https://github.com/blender/blender

This for example is the complete source for blenders procedural noise functions: https://github.com/blender/blender/blob/main/source/blender/blenlib/intern/noise.cc

Maybe you're only using object lights. To make it look like Material Preview, you'd want to use an environment texture [instead]. If you don't want to have to find them in the blender folders, here are the ones listed in Material Preview, forest.exr being the default

forest.exr https://github.com/blender/blender/tree/master/release/datafiles/studiolights/world

Everything was good. And then a developer decided to abandon the custom CLAMP macro and use the standard std::clamp function. And the commit that supposed to make the code better looked like this:

Or simply git clone official public mirror and build it yourself.

I'd also highly recommend This script which lets you add sound effects for when the replay buffer is triggered.

It was an absolute bitch to find, but this script has been the perfect companion to OBS's Replay Buffer. Lets you play a sound effect when a replay buffer is actually saved, or when you start/stop manual recording, so you can always be certain that your keypress was registered and that the recording saved properly.

One problem though, it has no form of alert system for when you actually save your replay buffer. No sound or visual notification. I found this great plugin for that and it's been working perfectly.

An official solution is best of course, but in the meantime I've been using this plugin to great effect. Note that it's sound effects, not a visual notifications.

NVidia Shadowplay > OBS: I'd long since fantasized about moving to OBS but like Linux itself, never really had anything encouraging me to put the effort in. It took some time to get my settings accurate to my Shadowplay ones, and I had to mess around with a third party plugin to get any kind of notification on whether my Replay Buffer recordings were even saving. But once it was all done, I'm much happier with it than I was with Shadowplay. Now I have my microphone, Teamspeak and game sounds all on separate channels, which makes recordings significantly easier to work with! But the fact that there's absolutely no form of notification system by default is pretty bad. Rainmeter > KDE Plasmoids: My Rainmeter setup wasn't a major thing I'd miss, I mainly kept it around for some visual flair and a few quality of life shortcuts. But when I found out that KDE Plasma had its own system for widgets, I was excited! Unfortunately their selection is very lacking both in functionality, and theme, compared to Rainmeter currently. Through sheer determination, a bunch of Googling, and eventually just cannibalising a paragraph of code from another user's widget, I did eventually manage to code together my own Launcher Plasmoid and re-create my old Rainmeter setup (Also using Plasma FancyClock). It was mostly enjoyable, but there was a sore lack of documentation on the whole process compared to Rainmeter: A very large part of what I learned came from repeatedly pestering the same user with questions, hence why I'm putting this one in the Harder Alternatives area. Paint.NET > Krita: I tried Gimp for a while, but felt like I was constantly grappling with the UI more than anything else so I moved to Krita. It's still a learning experience, and I feel like I take much longer to make the simple edits I need to often, but I'm slowly getting there. I would have preferred a more middle-ground editor for sure, Paint.NET is effectively just Paint with Layers, and usually that's all I need. GDrive > Insync/RClone: I quickly managed to replicate GDrive's automatic Backup and Sync with a basic RClone script. I only have a few files I need backed up and I can run the script manually when needed. I much prefer it this way, as now my internet connection isn't saturated every time I move a large file into one of my backed up folders. The shared folder functionality was the hard part. I tried many alternatives, GNOME/KDE's built in file browser support is slow and has to download everything you interact with every time, OverDrive was suspiciously broken by Google, Grive is abandoned and Grive2's developer is an ass. Repeatedly people recommended InSync, which I was against as it was paid. I was already paying for my Drive subscription, and didn't want to pay more on top of that just for a feature that had become a basic requirement for me. In the end, I got it for 50% off during a sale and haven't regreted my purchase since. I find it significantly better than the shit new client Google forced upon users. With selective sync, support for multiple accounts, and it supports syncing other locations without you needing to mess with Symlinks. However, the pricetag is still a hurdle, and I know how proprietary closed source software is frowned upon in this community. It's just a shame that there are absolutely no alternatives that come close. Plex: Strangely, while there's been a Plex Server Linux Version for several years, they don't have any player for it. They've said it's planned, but multiple months have passed and still no news on that front. I did manage to find a Community AppImage which does the job, but it is the older discontinued Plex Media Player software, not the current Plex program.