[15:43][Modify lighting_solution to remove LightBoxTargetP and add RootLightBoxIndex, and begin to make BuildSpatialPartitionForLighting() build trees of occluders and lights][:"data structure" :lighting]
[25:16][Walk through SplitBox()][:lighting :research]
[27:46][Fix compile errors in BuildSpatialPartitionForLighting()][:"data structure" :lighting]
[28:18][Consider using the root light box to cast against, and continue to walk through SplitBox()][:lighting :research]
[30:32][Make SplitBox() set an accumulated RefC][:lighting]
[33:22][Consider initialising the root occluder and light boxes' RefC][:lighting :research]
[35:42][Introduce CalculateRefC() for BuildSpatialPartitionForLighting() to initialise the root boxes' RefC][:lighting]
[38:57][Rename GetSpatialLeafForP() to GetLightLeafForP() and make it query for the (not guaranteed) closest light source][:geometry :lighting]
[44:57][Introduce GetDistanceToBoxSq() and GetClosestPointInBox()][:geometry :lighting]
[54:57][See that our light is kind of busted][:lighting :run]
[56:25][Step in to TestCastFromProbes() and inspect our Solution][:lighting :run]
[57:05][Step through GetLightLeafForP() and watch what it does][:lighting :run]
[57:33][Fix BuildSpatialPartitionForLighting() to pass ActualLightCount to the lights' SplitBox()][:lighting]
[58:31][Step back in to GetLightLeafForP() and still see a ChildCount of 2][:lighting :run]
[58:50][Step through BuildSpatialPartitionForLighting() with an ActualLightCount of 8, and on through GetLightLeafForP()][:lighting :run]
[1:02:54][Stop BuildSpatialPartitionForLighting() from setting RootBoxIndex from AddBoxReference(), and +1 to the Source in light boxes' SplitBox() call][:lighting]
[1:03:35][See that we're still busted][:lighting :run]
[1:03:50][Make GetLightLeafForP() draw its spatial hierarchy walk][:"debug visualisation" :geometry :lighting]
[1:06:42][See that our box spatial query is wrong][:"debug visualisation" :geometry :lighting :run]
[1:07:01][Consider our problem to be in GetClosestPointInBox()][:geometry :lighting :research]
[1:09:07][Getting the closest point in a box][:blackboard :geometry]
[1:11:19][Make GetLightLeafForP() call GetClosestPointInBox() directly, before itself then calling LengthSq()][:geometry :lighting]
[1:15:51][Fix BuildSpatialPartitionForLighting() to loop over the ActualBoxCount][:geometry :lighting]
[1:16:46][See that our spatial hierarchy remains misplaced][:geometry :lighting :research]
[1:17:08][Continue to scrutinise BuildSpatialPartitionForLighting() and SplitBox()][:geometry :lighting :research]
[1:22:05][Augment lighting_solution with a ScratchC for BuildSpatialPartitionForLighting() to use][:"data structure" :geometry :lighting]
[1:22:53][See that our spatial hierarchy is now correctly placed and queried][:"debug visualisation" :geometry :lighting :run]
[1:23:37][Prevent CompileZBiasProgram() from disabling the :lighting]
[1:24:00][Admire our :lighting][:run]
[1:25:21][Work on reading our test sphere, removing CubeSideWeight from light_sampling_sphere and Weights from sphere_store, and related code][:"data structure" :lighting]
[1:27:45][Prepare to invoke hhsphere][:lighting :research]
[1:29:06][Invoke hhsphere][:admin :lighting]
[1:32:45][Invoke hhsphere in release mode][:admin :lighting]
[1:33:37][Determine to implement ComputeVoxelIrradianceAt() and make BuildSpatialPartitionForLighting() preserve voxel contents][:lighting]
[1:38:06][Set up ComputeLightPropagationWork() to read from our light sphere, picking one random point on a light source][:lighting]
[1:44:08][Determine to figure out how to update our voxel field][:lighting :speech]
[1:44:56][Q&A][:speech]
[1:47:02][@x13pixels][Q: What is the go to assembler for 64-bit code on Windows these days? Is MASM still maintained, people moving to NASM, something else?[ref
site=NASM
url=https://nasm.us][ref
site="The Yasm Modular Assembler Project"
url=https://yasm.tortall.net]][:asm]
[1:51:07][@leachleach][Q: If I buy ~RemedyBG now, will I also get access to upcoming versions of it or just the current and past ones?]
[1:51:16][@steamymcfly][Q: Do you think with all recent processor vulnerabilities being found that future processors will use a fundamentally different optimizing architecture?][:hardware]
[1:54:24][@letambourinroyal][Q: What's the go to thing for learning assembly][:asm]
[1:54:53][@lucid_frost][Q: If assemblers were better would you consider programming in x86 / ARM directly (which ever you are trying to target primarily) for everything? Maybe it would auto translate on the backend and you could rewrite critical sections for secondary platforms][:language]
[1:56:59][@vtlmks][@cmuratori Do you know of a write-up similar to 'How to avoid C/C++ runtime on Windows' by [@mmozeiko Mārtiņš Možeiko] on the Handmade Hero forum,[ref
site="Handmade Hero Forums"
page="Guide - How to avoid C/C++ runtime on Windows"
url=https://hero.handmade.network/forums/code-discussion/t/94-guide_-_how_to_avoid_c_c++_runtime_on_windows/] but for Linux?]
