Pocster

Nasty !

Yeah - mid life crisis purchase like we all have!. NEW TOY!. Also once the gpu AI is used I can expect maybe a 4 fold increase in local LLM speed.

Fuuuccckkkk! At the start of this thread refreshed Apple website every 55 seconds!. Missed this though!. M5 256Gb ordered!. Might keep might flip. Nice one @-rick- SERIOUSLY appreciate the heads up!. Also means it will always be 60fps!

You are SO right . Effectively on some things we’ve exceeded UE . But I cheated a bit . Mines a heightmap engine so I can’t do overhang / caves etc - fine for landscapes etc but not insides ( though I’m thinking about how you would do that with a ray marcher for a follow up project ) . But yes ! Everything UE does we attempt . Rain , snow , wind , lighting , explosions , lasers , ice , real big list . Put a video up on YouTube in the next few weeks . Expect Apple to offer me a billion dollars for it …. maybe …. or Mr.Beast ( I.e more money than sense ) . But I’ll take the cash from anyone ; not fussy !

Mike didn’t like his gun so now he’s upgraded to a plasma laser . Be kind . Don’t be like Mike and mow down the flora with your new found toy . In a world full of Mikes , don’t be a Mike .

now every blade of grass casts a shadow!. Mike (the robot) was happy in his tranquil world. But some mofo has now given him a gun.....

Fable is causing me to accelerate my requests! Mikes in; fully lit by environment and driven with IK. Scatter props like rocks, tree branches etc Trees with shadows. Full grass. All affected by wind/rain/snow Mikes eyes light at night so he can see where he is going. Some simpler creatures going in e.g. butterflies and fish. For the most part 60 FPS! - took sometime to get to that.

procedural generation does it itself also

Struggling to maintain 60fps and thats without Mike the robot, creatures and other goodies in. Even Fable is kicking back. TAA in was a big gain took some scenes from 200% GPU down to 120% (still over but considerable gain). Of course what's exactly on screen has a massive impact not just trees and imposters (tried those 3 times and gave up, after some thought 4th time worked good enough) but!, as essentially the terrain,sky,shadows,lighting,clouds,water is 1 massive shader (2Mb! as inline for speed) ray marching them from grazing angles can punish fps. I cant lie visuals are AAA - which is staggering. Still not looked at any code but tell it what to look for optimise wise and indeed it does and especially Fable goes off and find extra rabbit holes to explore which is good! A few more things to try though from a very empty bag of tricks. What do we have though? You can see maybe 10,000 trees on screen (yes most are a black pixel!), you can get right into the grass and it moves as you pass and each blade is vertex lit. Looks (expletive deleted)ing better than most of my holiday snaps!. Final push before rapier physics and Mike goes in. Then linking back to whisper and the local LLM - see we got there in the end just via a 3d engine! LOL!

I like Fable! it makes opus look like a 9 yr old!

Well! Been avoiding TAA as the visual artefacts annoy me and I want to get the best before I pull the big performance lever. But after some other smaller optimising this is the route we're going. Most major (if not all AAA ) games do this so it was always inevitable. 60fps is coming back!

Ok! Well Fable really is doing better than Opus 5 on high. Getting right down to the nitty gritty and understanding it. Not quite there yet but big optimisations on the way for trees and grass I think.

stuck. pushed the turbo "fable" button.... here's hoping...

Just a test so 1024 trees. All real meshes. Nearer ones move per branch with wind and have higher fidelity shadows. Take lighting from sun/cloud/terrain/atmosphere (froxel,fog etc etc). Lots to compute!. Been rethinking lots and applying every trick I can to get frame rate sane but still heavy. I'm now onto placement - so got to go and plant 10'000's of trees!

All day at it. Claude's now struggling to find optimisations. So I need to be extra creative on the method rather than the code. 1024 trees on screen kills frame rate. Tricks a plenty needed