🧵 They massacred my girl...
Anonymous at Tue, 9 Jul 2024 19:43:38 UTC No. 989283
Anonymous at Tue, 9 Jul 2024 19:54:34 UTC No. 989285
who cares about eevee
Anonymous at Tue, 9 Jul 2024 20:44:36 UTC No. 989289
>>989283
That’s not how light works, eevee next looks like flaw lighting and will ruin lighting on many projects.
Anonymous at Tue, 9 Jul 2024 21:08:08 UTC No. 989293
>>989283
>jUsT uSe tHe cOmPosiToR bRo, iT's tHe sAmE tHiNg
Anonymous at Tue, 9 Jul 2024 21:25:07 UTC No. 989296
Next has great potential to make your scenes look a ton better but many people don't get that it does not translate 1:1 between those two versions.
You must completely rework your materials and also use the compositor now in addition like >>989293 already pointed out correctly.
Many got used to the old Eevee and prefer the old workflow so I wonder if they'll keep the old thing around or will just drop it.
Anonymous at Tue, 9 Jul 2024 21:29:47 UTC No. 989297
>>989293
just went and checked a vid of them, doesn't look bad if what I saw is real then the OP pic doesn't make it justice
Anonymous at Tue, 9 Jul 2024 22:52:16 UTC No. 989303
ive noticed the only people complaining about eevee next are weebs upset they will need a slightly different workflow for making their porn.
Anonymous at Tue, 9 Jul 2024 23:26:17 UTC No. 989304
>>989302
SOVL
Anonymous at Tue, 9 Jul 2024 23:33:42 UTC No. 989305
>>989303
precise
Anonymous at Wed, 10 Jul 2024 01:21:01 UTC No. 989306
>>989303
I just like the bloom as a viewport toggle without bullshit. Everything else for Next is a win.
The viewport compositor is similar, but not the same, and on top of that you have to factor in all the other bullshit you may have in your compositing setup. All just to have a preview of what your bloom will look like.
It's a change for the sake of change without offering up anything better. I often times preferred the Eevee bloom even over most compositor versions.
Anonymous at Wed, 10 Jul 2024 01:27:40 UTC No. 989307
>>989306
>removed Shader RGB node
>completely broke stylized, NPR, and basically every rendering style that isn't Indian-tier PBR in a vain attempt to be Cycles' retarded cousin
Nothing about Eevee Next is a win.
Anonymous at Wed, 10 Jul 2024 01:36:49 UTC No. 989308
>>989307
You should do something about your porn addiction. go for a walk and clear your head at the very least.
Anonymous at Wed, 10 Jul 2024 02:11:39 UTC No. 989310
>>989307
>removed Shader RGB node
e....excuse me?
Fucking WHAT.
Yeah, never fuckin mind. Holy shit these devs are retarded.
All I've seen gone over was all the new PBR shit, so I had just figured old stuff like Shader 2 RGB was intact.
I rescind my statement.
Anonymous at Wed, 10 Jul 2024 02:32:41 UTC No. 989316
>>989310
>devs
Anon...
It's one guy.
One guy maintains Eevee and makes all the decisions regarding it. The open source meme doesn't work when an entire engine is one guy's pet project and no one else knows how it works.
If it makes you feel any better the Shader RGB node has been broken as far back as Blender 3.2 when he patched out screen space reflections.
Anonymous at Wed, 10 Jul 2024 02:38:04 UTC No. 989317
>>989316
Render is the 2th most important thing in 3D. Why in gods name is there only one person who works on it. I’m now believing the dev who got fired over at blender, the devs are officially crazy.
They removed the entire blender thread but they can’t erase anything from the internet: https://web.archive.org/web/2023072
Anonymous at Wed, 10 Jul 2024 02:40:36 UTC No. 989318
>>989317
it's actually the 3th, but if you didn't know that then you're ngmi
Anonymous at Wed, 10 Jul 2024 02:44:00 UTC No. 989321
>>989318
Texturing is optional, you don’t need it every time because game engines run in different environments and sometimes software like substance make it better than current 3D software.
Anonymous at Wed, 10 Jul 2024 03:31:20 UTC No. 989327
>>989283
what's with the reflections?
Anonymous at Wed, 10 Jul 2024 03:44:16 UTC No. 989328
I for one like that they removed bloom and make everyone use it via the compositor.
People were absolutely abusing bloom when using Eevee to the point where it became a fucking meme.
>Eevee in use? MASSIVE BLOOM EVERYWHERE EVEN IN CLEAR DAYLIGHT SITUATIONS
Anonymous at Wed, 10 Jul 2024 07:44:37 UTC No. 989337
It's interesting seeing a roughness override on the render settings. T bh they should have overrides for every shader parameter and stop pretending like shaders translate well between cycles and Eevee.
Anonymous at Wed, 10 Jul 2024 11:59:33 UTC No. 989348
>>989321
who said anything about texturing? It's actually the 7nd most important thing in 3D. didn't know that either? never. gonna. make. it.
Anonymous at Wed, 10 Jul 2024 23:44:33 UTC No. 989417
I just don't get why the fuck they couldn't just wait to release it in an actual finished state without compromising so many people's shit.
The way it's going, a lot of people are just gonna see it as a toy, but not ready for any real projects because it's unfinished. Likewise a lot of people who used to use Eevee for projects are going to wait until it actually has feature parity and doesn't gimp their shit.
So yeah, literally no reason to release it in this state. The people who actually use Eevee aren't going to fuckin use it.
That's not even mentioning that it'll probably NEVER be finished, because like a lot of Blender bullshit, they get one dude to work on it, then the dude fucks off and then no one knows how to update/upgrade the shit so they hire ANOTHER faggot to make an entire rewrite, he fucks off, and the cycle(s) (heh) continues.
The absolute fuckin state of Blender "development".
Anonymous at Sat, 13 Jul 2024 20:26:45 UTC No. 989711
>>989417
>I just don't get why the fuck they couldn't just wait to release it in an actual finished state without compromising so many people's shit.
boo hoo, your files are ruined, so many days work gone.
Or just don't update, or install two instances so you can have both. It's not a problem, I don't see why you're sperging out about it.
Anonymous at Sat, 13 Jul 2024 21:05:08 UTC No. 989716
>>989417
this >>989711
blenderfags are mostly amateurs or freelances but there's a good reason why studio pipes will stick to old versions until projects are done or their pipeline guys port everything over to the newer version.
that said, blender needs to adopt usd standards, implement hydra delegation, then port their renders to be hydra delegates. then you can decouple render engines entirely from the rest of blender dev.
they're never going to do it though because god forbid they actually participate in an industry-wide open source initiative.
Anonymous at Sun, 14 Jul 2024 07:53:27 UTC No. 989754
>>989417
I don't give a fuck about Eevee, it's never gonna get feature or quality parity with actualgame engines.
But don't forget they basically halted geonodes to work on their shitty grease pencil once more.
Anonymous at Sun, 14 Jul 2024 10:55:44 UTC No. 989765
>>989711
>spend months working on a project in the current build
>LMAO they removed a node you need, the whole thing is fucked
>try to revert to an older version
>LMAO they changed everything around, now all your shaders are broken
This is why no one is stupid enough to use Blender on an actual production except for me and the guys who make Blender.
Anonymous at Sun, 14 Jul 2024 18:39:21 UTC No. 989796
>>989765
That's literally what Blender LTS is for
Anonymous at Mon, 15 Jul 2024 07:19:47 UTC No. 989828
>>989765
I think I see your frustration. But this can be prevented by simply not upgrading in the first place. You should scale your project to the tools you currently have on hand. Not the tools you may have in the future. Therefore, you shouldn't go jumping onto the next Blender upgrade, just because they dangled a few new fancy looking features to entice you. Your project was planned without those new features, and so should be doable without them.
Anonymous at Thu, 18 Jul 2024 23:54:08 UTC No. 990142
>>989828
Good advice, thanks.
Anonymous at Fri, 19 Jul 2024 17:52:59 UTC No. 990190
>>989293
The compositor can't even factor in viewport resolution the last time I checked, it fucks up the intensity of the effects.
Anonymous at Fri, 19 Jul 2024 17:54:02 UTC No. 990191
eh Eevee next is really not that gamechanging, still no contact shadows for me and it lags more than before now, even on a Ryzen 7
Anonymous at Sat, 20 Jul 2024 14:35:23 UTC No. 990249
>>989307
>removed Shader RGB node
I fell out of the loop with Blender news and haven't done 3DCG for some months and now I come back to this. Damn.
I've used the Shader to RGB node in about half of my latest dozen or so Blender projects.
🗑️ Anonymous at Sat, 20 Jul 2024 19:37:53 UTC No. 990267
>>990249
>>990191
>>990190
>>990142
>>989828
>828>>990142>>989765
>>989796
>>989765
>>989754
>>989716
>>989711
>>989417
>>989369
>>989348
>>989337
>>989328
>>989327
>>989321
>>989318
>>989317
>>989316
>>989310
>>989308
>>989307
>>989306
>>989305
>>989304
>>989303
>>989302
>>989297
>>989296
>>989293
>>989289
>>989285
>>989283
just say you can't afford a pc for raytracing bro
Anonymous at Sat, 20 Jul 2024 20:56:46 UTC No. 990273
>>990267
>just say you can't afford a pc for raytracing bro
I've got a 4070ti, but you do you. Doesn't make Eevee next any less shit. I don't really give a fuck about viewport performance, as long as it's quicker than cycles. Bloom being fucked and Shader2RGB being fucked is all I care about.
Anonymous at Sat, 20 Jul 2024 21:10:49 UTC No. 990276
>>990249
I hope it's going to create new interest and resources for actual nPBR engines like https://malt3d.com/ instead of using Eevee as a workaround
Anonymous at Sat, 20 Jul 2024 21:31:07 UTC No. 990279
>>990273
Compositor bloom is 1 (one) extra step and shader to rgb didnt even get removed retard, yall don't use the program or make anything ever just scroll and complain
Anonymous at Sat, 20 Jul 2024 22:48:29 UTC No. 990289
>>990279
1 extra step for a worse bloom, several additional steps to try and compensate for still a worse bloom, and Shader 2 RGB is no longer working as it once did. Didn't say anything about it being removed.
kys zoomer.
Anonymous at Sat, 20 Jul 2024 23:57:26 UTC No. 990295
>>990267
wtf do fucked compositor effects in the viewport have to with raytracing
Anonymous at Sun, 21 Jul 2024 04:47:44 UTC No. 990319
>>990299
Yeah, it's a false alarm. The node is still there and materials that use it work the same as far as I can tell.
Light and shadows work differently, so if you transfer a project from an older version to 4.2 you will need to adjust your lighting setup.
Anonymous at Sun, 21 Jul 2024 04:53:12 UTC No. 990322
>>990319
Damn, how did you get shading like that? Teach me your ways.
Anonymous at Sun, 21 Jul 2024 06:57:18 UTC No. 990331
>>989318
>3th
bait or retard, call it
Anonymous at Sun, 21 Jul 2024 07:10:40 UTC No. 990333
>>990330
Can you take a screenshot of all the nodes in one image so I can see how they connect? Its okay if the names of the nodes are illegible since we have the close ups here.
Anonymous at Sun, 21 Jul 2024 07:45:38 UTC No. 990337
>>990335
I'm mentally challenged and couldn't tell, sorry. Thanks for the nodes!
Anonymous at Thu, 25 Jul 2024 09:47:20 UTC No. 990653
>>990497
nice how did you get the noise effect? I see you didn't reduce render samples
Anonymous at Thu, 25 Jul 2024 14:48:58 UTC No. 990674
>>990653
Turn up the distortion value of the noise texture node in >>990329 to like 50.
Anonymous at Sat, 27 Jul 2024 08:58:41 UTC No. 990766
>>990332
Cool stuff. Does it react to the light color? That's been my biggest issue with almost every NPR nodegroup I've found.
Anonymous at Wed, 31 Jul 2024 02:10:59 UTC No. 991109
>>990766
Not many toon shaders react to lamp colors, unfortunately
Anonymous at Wed, 31 Jul 2024 12:09:23 UTC No. 991135
>>989303
I already adapted to it and i still think its a downgrade.
Old EEVEE was convenient and had almost all the settings you need right there in the render menu. New one feels very tedious in comparison, especially with the compositor fickery which works like shit 70% of the time if you try to preview stuff like bloom. It's like a reverse QOL.
>Just use the old version lmao
Its an easy solution, but the thing is, it's not just projects that are dependant on it.
For example - I've been making an asset library for my atuff, and all those assets had shaders reliant on the old implementation. To redo it for the new one would take eons of work because its literally hundreds of different props, so i'm essentially locked on pre-4.2 versions because of it. I'm certain there are other cases where this was detrimental to users too.
I still don't understand why wouldn't they just leave legacy stay there like in beta.
Anonymous at Wed, 31 Jul 2024 14:35:58 UTC No. 991144
>>991109
Noooo!
Omg
Anonymous at Wed, 31 Jul 2024 17:00:27 UTC No. 991160
>>989283
>Eevee before: Stable, runs smooth like butter with tons of lights and effects, allows you to preview bloom easily and tweak it
>Eevee Next: Noisy shit that pretty much behaves like a slightly faster cycles whenever you move the frame, and performance is abysmal, especially with compositor. Bloom cannot be tweaked whatsoever unless you make compositor chains
Who fucking greenlit this shit?
Anonymous at Sat, 3 Aug 2024 14:09:10 UTC No. 991453
>>991160
me. you are shit.
Anonymous at Tue, 6 Aug 2024 02:20:25 UTC No. 991638
>>991135
>>991160
The thing that really grinds my gears about Eevee Next, is that it's packed with useful geometry nodes. So if I stick with 4.1 to avoid the shitty performance of Eevee next, then I can't use the new cool nodes.
Anonymous at Tue, 6 Aug 2024 04:17:17 UTC No. 991643
not enough bloom
Anonymous at Tue, 6 Aug 2024 16:52:10 UTC No. 991680
>>989283
The shadows in next look better. The lamp looks like it is floating in Eevee.
Anonymous at Tue, 6 Aug 2024 22:26:08 UTC No. 991697
>>989283
anyone mind mentioning what was so wrong with the original eevee that they had to rewrite it from yet again or is this just sirgay's latest excuse to avoid fixing the Multi-Res modifier