does anybody has problem with transferring preferences from 4.1 to 4.2. After it is done addon and extensions window are blank

@@Alex-wg1mb If you don't find a solution, best to write a bug report. Else, they can not improve it.

@@Raimund58 Dug almost the same report, using some workaround until final fix

Things like tint, clamping, and fine-tuning the threshold can be done by adding extra nodes. So the node replacement is just core functionality, you can customize it further than the post effect.

the “fog glow” mode also has more options

@@kenziemac130Of course everything can be done by most basic image manipulation nodes. but why do we have bloom node? you can make it by levels and blur nodes as well , you will use levels to make highlights bright then blur it and then make a node called bloom, thats how people do in adobe premiere etc. if no bloom node exist., and for blender, simple things like vignette was never easy to do in blender for long. So its a big time loss. Therefore point is same goes for those extra settings for bloom, so its wrong to make people be node or image manipulation expert to do simple things. There will be various usermade nodegroups that cause lack of standards, its always better to have best or standard implementation of things Compositor is always longer way to do things for simple post processing due to the fact its missing many pratical nodes . They should just add same settings to compositor at least, its not that hard

yes they always downgrade and we wait for love so they fix something to old version. Even commercial softwares make old settings legacy for long time so people wont feel suddenly that a setting they always use is gone. Thats the only side commercial softwares are better. They dont easily get rid of some features by big changes

@@Ericaandmac or deliver it in a node-group

Thanks! Oh surely, one can achieve the same effect adding more nodes, still, having the same options as in the old Bloom menu right away would be nice :)

May be u cou do tut on these node's 😅​@@MartinKlekner

​@MartinKlekner if they're completely changing the workflow under the hood, a redundant boom would only hurt things.

@@MartinKlekner yes who cares about workarounds, then we also dont need bloom node cuz people can do bloom from blur and levels or exposure nodes easily so noone need bloom node as well (or udont need color ramp or map range node cuz u can do it by math nodes) (or we shouldnt have gotten principled bsdf, we can use blendergurus pbr shader groups). , the point is not wheter u can make it nor not, its about official implementation that is standardized for all users without always making things yourself and doing things easily and not getting downgrade from previous workflows..

@@MartinKlekner Or may be instead of a redundant node, the greate thing would be to have nodes presets. Finally. Personnaly I find that Blender is lacking a solid global presets system. It's good to pull information from data blocks of other projects, but you literally have to organize folders by your own and keep track of them all. In Houdini for example you can make everything a preset, so next time you open a new project, you have you preset for anything right at one or two clicks away. And not even talking about HDAs.

Glad you enjoyed it, Zach 🤩

Thank you! 😊

Not the point. Of course, there is milion ways to do it. Previously, though, it was more convenient and with more immediate options.

@@MartinKlekner They don't get it bro. They just don't. I feel ya tho. Shame that they nixed it.

I strongly disagree with the bloom refactor, it was really nice and convenient as it was in 4.1. Big mistake in my opinion

@@MartinKlekner I can see the immediacy returning with the use of the library system to create a sort of post fx layer stack, with compositing node setups packed up as assets. There's no real evidence that this kind of solution is on the horizon, but it's the only reason that comes to mind that they'd remove the previous one click solution.

Ow that's a good tip. But you get ghosting is I'm correct. I know this sort of effect from photoshop. You still see the sharp edges. Unless you can make some kind of mask for edges

DEFINITELY learn Unreal bro. Blender does not even come anywhere close to rivaling the kind of technology in UE. Everything you're seeing here is grounded in incredibly dated screen space technology, something Unity and UE were already doing as early as 2015. If you want to be able to render massive worlds in seconds with trillions of polys, and GI nearly on the level of cycles without having to worry about so much CPU bottle necking, you definitely wanna go with the tool that is leading the industry right now. As a Blender user myself, I can't even begin to explain to you the benefits of UE5 over Eevee because there is just so much to cover. It's one of those things where you cannot fully understand it until you start really using UE, and then you'll be saying to yourself: "OMFG, why in the world did I EVER try to do this in Blender!!!??" Take the leap as I did, and I promise you that you will NOT be disappointed. UE is not as hard as you think it is, its actually very easy once you get used to it, Unity is fantastic too.

Thank yoou, Louis! 😉 Let's hope!

Thank you Cov! 🤗

Glad you liked it!

Thank you, sir, always a pleasure to meet a fan of ancient history & warfare 🙂

Haha, appreciate it buddy 🙏☺️

Good idea for future video.

It was an issue in the shader of the AutoEye addon ☺️ kzfaq.infoyzZT6JoVljQ?si=hEECboOKMcnV8Jpk

@@MartinKlekner ah got it!

Oh yes, agreed, linking in Eevee would be awesome 🙂

Yes, it makes sense, but as I mention in the video, stripping it off most of the very useful and fast settings is a downgrade, in my opinion..

@@MartinKlekner I see :p But I think having it in two different places means you could accidentally leave it on in the legacy menu and potentially ruin a very long render. Having to double check in two different places is quite an inconvenience.

@@stargazestudios Definitely, Im just arguing for giving the new Bloom effect inside the Glare node the same capabilities as the previous Bloom menu. The way it is right now, its downgrade.

Yeah, I just LOVE having to go through my entire compositing tree of nodes I don't need right now just to see what bloom looks like, compared to a simple checkbox. That was sarcasm by the way.

​@@MartinKlekner They or someone else just need to create a nodegroup that recreates the original internal bloom. There are probably already examples of it out there somewhere :)

Awesome! The course uses mostly Cycles, so no changes in Eevee influence it :)

@@MartinKlekner awesome. Thank you for the very quick reply. Have a great day

Thanks but not sure what you mean, I see no refraction settings in Shader editor shelf...

🤭

Worked in some cases but not for these eyes, thanks for the tip though! Ill try to fiddle with settings some more :)

​@@MartinKlekner I have an eye setup that was originally based on Auto-eye and I got it working about 90%. You should set the refraction type to "sphere" not slab and also you need to connect a value to the "thickness" value on the Material Output node of your Cornea material. If I understand the node correctly setting the value to Zero actually makes it use the objects volume to calculate the refraction and works basically like classic eevee. It's fine on all but extreme closeups which have a tiny white infinite distance square in the refraction for some reason. if you don't connect any value to thickness it just seems to use the scene default thickness set in render options which is often way too big for something like eyes

Great to hear! :-) When it comes to lots of CC characters, economy is still the key, so I recommend using LODs and as few smaller size textures as possible. Overall though, the viewport performance seems better!

@@MartinKlekner Thanks for the reply. No i am talking with only a couple characters and only 2K textures. 32gb Ram and RTX 2080Ti my PC Specs and UE5 runs loads of assets from CC/Kitbash etc and no slow down so wondering if Blender is on the same scale as Uneal yet re realtime.

I normally do 1v1 fight sequences, so I don’t have loads of characters on screen like your epic videos. Usually 2 CC characters, and assets from kitbash etc, but it slows down to a crawl in the viewport. (Using normal Eevee.)

Thank you! Already fixed by the author of the addon :-) kzfaq.infoyzZT6JoVljQ

Sadly, not working, but thank you! :-)

@@MartinKlekner I just figured out basically if you have back light it will break throughout mesh, jest delete the back light, or make the cornea another sphere with glass shader.

It is somehat unpredictable at this point, hope they can fix it or provide solutions :)

That's literally what adaptive subdivision is. We've had it for years.

​@@choo_choo_ no that's different nanite is real time auto lod, it's decimating geometry based on how far the object from camera

Lol, Blender is following UE.

@@zedeon6299 Adaptive subdivision is doing the exact same thing. More geometry close to the camera, less far away. For more extreme decimation, geometry nodes handles that extremely simply.

@@choo_choo_ if so then why it increase memory usage instead of reducing it?

Maybe a topic for next time ;-)

Thanks a lot! :-))

Not even as a faster preview so you can wysiwyg model your scenes before cycles? that's how I use it most. The closer eevee is to cycles the more convenient for me.

Oh yeah forgot to mention that thanks 😊 This new workflow is so much better

@@MartinKlekner yeah most definetely :) I hope we get even better gpu accelerated raytracing for eevee soon !

Cycles can still handle heavier scenes with more textures better, and give you slightly more realistic result, either overall softer light quality. But Eevee is slowly getting there…

Yes, the point is though that while it was super easy and convenient before, now its more complicated - and that’s a step back in my opinion…

@@MartinKlekner I agree, just hopefully they understand people like whatever formula it was using. Maybe they just want to improve on that and it wasn't ready, I hope that's the case.

of course, I'm literally using a 1050ti

@@godwinyo5206 o nice I'm using rx 560

Weeell, don’t think so, but for Blender users, it gives us even more powerful tools, slowly gaining on Unreal :)

I use both depending on the complexity of my scenes.

does it matter tho? in most cases the userbases overlaps anyways, any big leap for any of these two sofwares is a win for us users no need to pick a camp they complement each other very well

Gain some, loose some. Bloom is a post processing effect, it was weird that it was in render in the first place. And eevee is meant to be physically accurate as possible, while staying real time, bloom is not a physical effect, but a stylistic one. Photographers apply it also after they made the picture. Volumetric halos like in mist are physicall, but you can still do that in eevee with volumetrics.

@@DrTheRich sure, but ease of use and ergonomic conveniences are nice and user friendly. Why remove it? To properly categorize so specialists can feel it's now in it's proper place? There was a clear advantage to having it where it was.

@@enigmawstudios4130 Because if you went with your method with everything, the entire program would become a mess and no one would be able to make sens of anything at all. Putting things in their proper place IS to make things more user friendly. But you can only see that as the whole picture. Some individual cases it might look less user friendly. If you're looking for post processing effect called bloom, you now know to find it with all other post processing effects in the compositor. And no one gets confused anymore why there are two different bloom effects. Not to mention the final result will be more consistent now between eevee and cycles. I suspect the color management panel will eventually also move to the compositor. Yes there was a clear advantage to having it where it was, there are more advantages to having it where it's now. They just have to upgrade the bloom compositor node a bit so it's as powerful as the old settings, but i'm sure they will. Or you can submit that yourself, it's opensource blender is made by everyone who wants to contribute.

@@DrTheRich not sure how that's a realistic conclusion, as it isn't "my method" lol it was Blender's!

@@enigmawstudios4130 With "your method" i don't mean the specific bloom settings. I mean the idea of lets just go with what just seems most convenient on a surface level without regards for structure. But you're right, that WAS blender's method in the past. And that's why blender user interface sucked. I've been using blender for 15+ years now, i know what it was like. Blender UI is a dream now compared to when i first started. And i've had the feeling you had many times on the way, but looking back, I don't miss anything about the old way. One thing to think about, is to try to see the different between if something is actually convenient, or it's convenient because you're used to it. That's really really hard to separate. And the blender developers only became good at that, after they created a purposeful UI team. And these decisions aren't made on a whim. They have lengthy discussions you can read about on the blender development sites. And if you think you're view is important, join in these discussions, and help make blender a better program. Instead of just complaining.