Wait, it should be another Cyberpunk pic today...?Well, let's me explain my horrible week with Blender.Like I said last week, I wanted to start learn Eevee to have faster rendering and start animation again. And I was really serious this time, really! So I indeed start to learn, watch video, training. Eevee is really cool because you can see all your lights directly without a lot of noise and navigate inside the viewport quickly. I was quite happy with it and start doing that Cyberpunk pic as intended. For sure, the pic would be quite meh, because it was my first Eevee pic after a long time and the engine change drastically. Then, I press Render Image.
It didn't work. No of term of light or else, just, Blender just give me a crash.txt, and keep crashing. And when it's not crash, Blender doesn't respond, so just another way of crash. Okay okay, so maybe the cyberpunk scene was to heavy, so I decided to change the pic for the week, as you can see above.But it's crash too. So I look into a solution. Finally found that was an object who cause the crash. So render it again and ... Blender didn't respond... Okay, that was maybe the 5.0 who still very unstable and go into 4.5... I need to redo some things, then press Render Image again ... And after some blender who still didn't respond, Eevee finally works ... but the render time ... I expect to see just seconds, and I see a minute, just a bit less against Cycles.So fuck it, and reswitch to Cycles, to make that Cyberpunk pic again. But this time, some model just doesn't work, probably because it wasn't updated since a long time. I was close to the burn out yesterday, still seeing what was the problem. So I decided to reswitch to the pic above, and do it with Cycles...
Thanks for reading my story about me who wanted to break my entire rig and Blender! x) Hope I can fix that cyberpunk pic for next week.