fucnkn so I decided to vibecode version 6 and it’s kinda ok. go to https://t.co/7GOglaSBne to see. problem is the same as always, when I start moving into the content rather than the engine, I just utterly run out of steam .. very very sad
I just read through another twitter account that I used when I was sad. damn I used to be a lot sadder. maybe figuring out adhd helped.
my brother hung just over a month ago. it’s tragic to think about how bad it must have been in his head that he saw this as the only way
otoh I’m probably in the best place work wise, and my kids are 15/17 and such great kids. there’s potentially a lot of positives, I have a freedom I haven’t had for such a long time and certainly never as a decent wage earning adult
@ThePrimeagen I watched that video last night about open ai’s latest and I reckon it’s required watching for a lot of people, especially people who actually aren’t on the tools but managing them, to give them some realistic idea of what isn’t happening lmao
of course this info might be way off, but I wondered how much energy an ai uses compared to a human. there’s scaling that seems to improve this a lot, but an ai had be fuckin good to use close to ~30k times as much energy per hour as a human
luxcorerender : you can follow the webpage to a download of an alpha build that works on 4.1+ and tbh it slots in pretty nicely.
it can do bidirectional (only on cpu) which makes caustics show up very naturally and dispersion is built in
reason for this is that to evaluate the scene without this is very slow, this is a bit cheating.
you can use a noise threshold but unlike cycles it’s not per pixel, which would speed up renders on this super fast