right as you walk in, kick your feet up on the interviewer's desk and say "enough about me, why should i work for you?"

((((and out-of-core rendering with HLODs if i have time........ i just think it'd be cool........))))

might be shooting myself in the foot here by saying my plans before ive actually figured out if it'll be possible (this is for a school project so due in a couple months), but id like to try and get 3d physics, networking, and serialisation for saving/loading in before submission....
wish me luck :>

and it is indeed up-to-date with the graphics samples

here's a lil sample of the ECS in action, first in the user's code and second in the backend RenderSystem :>

the entrypoint is owned by the engine, and it gets linked to the user's code through those function declarations that the user is expected to define

(ignore overwatch in my taskbar that's not relevant to the demonstration)

is it IBL time chat?

testing this sample on my laptop running d3d12 at 4k did actually reveal some weird screen tearing issues so ill have to do some investigating there, doesn't happen on vulkan or 1080p dx12 though so probably just some weird dx12 quirk im not familiar with sdfjkhfsd

gonna take a break now from the backend stuff so i can spend a while doing fun shading i think :>

comms open

surprise !! if you made it this far, you get to see the Neki logo with the proper colours after my dumbass remembered to use srgb format for the swapchain

the GPUUploader class also has a EnqueueBufferDataUpload() function which is the same thing but for buffers instead of textures, so in the Texture sample, im batching my texture upload alongside the vertex and index buffer uploads

yap session concluded, thanks for reading :))

i make it sound more complicated than it is i think sdfjhkfsd
this is it !!

synchronisation is also handled quite nicely i think. when you call Flush() you pass in true/false depending on if you want to stall the calling thread until the flush is finished. If you set it to false, the function returns a fence that will be signalled when it's done so you know when to Reset()

this means that a bunch of uploads (like if you had 1000 textures to upload) would all get batched together into a single staging buffer and the transfer commands submitted all at once

once it's done flushing, you call Reset() to clear the staging buffer and reset the command buffer

more below :>