[video member=nothings stream_platform=twitch stream_username=nothings2 project=obbg title="Open Block Building Game Development #42" vod_platform=youtube id=FNL-4wnsSCo annotator=Miblo]
[1:15][:Run the game to :demo the current status, hit the assert in visit() and investigate why]
[2:47][Fix that assert and consider natural things to do]
[8:12][Determine to thread the :simulation][:threading :rant]
[9:19][@kelimion][@nothings2 Might you also split up the :simulation of discontinuous parts of the factory (not connected by belts / pipe, but by trains / drones instead) so it can be processed by several threads?][:threading]
[12:45][Delete stale code and commit "minor cleanup"]
[15:28][The strategy for :threading the :simulation][:blackboard]
[19:48][Using a copy of the game state to enable effective :threading][:blackboard]
[24:03][@norad91][How feasible is it to use thread 2 to calculate the info needed interleaved with thread 1 so it isn't idle until after the first complete update?][:threading]
[24:22][Infeasible copying as you calculate][:blackboard]
[26:50][@norad91][I mean instead of thread 1 copying the game state for thread 2 to use, thread 2 builds its copy while the state is built, interlocked with thread 1. So more fine-grained. Or is that too much work for too little gain][:threading]
[29:42][@enemymouse][How about instead of copying state every frame, maintain two states one for even frames one for odd, then the frame data ready to render is read only already][:threading]
[30:03][Performance considerations in a pure functional :language][:blackboard]
[31:55][Performance considerations in an imperative :language][:blackboard]
[33:56][Double-buffering your :simulation][:blackboard :threading]
[37:44][@happylittlerat][I try to avoid in-place operations except locally, so if any system requires intermediate states, it'll make a local copy]
[38:54][:Threading the :simulation for ~OBBG][:blackboard :physics]
[1:53:55][Organise the logistics :simulation function declarations]
[1:56:10][Break]
[1:57:01][Return and start by creating logistics_render.c to house the existing logistics :rendering code]
[2:02:53][What happens when belts meet][:blackboard]
[2:05:00][Our three options: 1) Preserve the chunk structure; 2) Never look at the belt IDs and just copy the data without worrying; 3) Don't preserve the structure, but add more tags][:blackboard]
[2:07:17][Determine to copy into a new render_belt_run format]
[2:09:43][:Run the game to make sure it's working]
[2:10:15][Remove :"input handling" from the belt_run struct and commit "get rid of 'input_id' field in belts"][:simulation]
[2:12:15][Move the logistics :rendering code back into logistics_render.c and write the render_belt_run struct][:simulation]
[2:39:24][Introduce copy_belt(), copy_machine(), copy_belt_machine() and copy_picker()][:simulation]
[2:46:52][Put the item directly in the render_belt_run struct and make the copy_*() functions take a belt_run][:simulation]
[2:48:44][@edelknecht][Was / is there a good reason for old C not to allow declarations anywhere other than at the head of a block?][:experience :language]
[2:52:45][Make copy_logi_chunk() handle the new versions of the copy_*() functions, complete with sound effects][:simulation :trivia :audio]
[2:53:46][@insofaras][I like keeping the scope of declarations as small as possible][:language]
[2:55:46][@ginger_bill][Do you think function overloading is ever "really needed"? Or are default parameters and / or parametric polymorphic functions better?][:language :experience :rant]
[3:11:43][@vavassor][I hadn't even considered grep-ability. My IDE just lets you "open declaration" on operators and overloaded functions to search for them. Of course that offloads the problem onto the editor]
[3:14:43][@type_null][What kind of C abuses do you think are the most common?][:language :experience]
[3:27:45][Make logistics_do_long_tick() more readable][:simulation]
[3:30:20][@mathk_][Did you read the Doom16 rendering article?]
[3:30:32][@palebluezebra]["what is this doing?" That alone justifies the extra lines]
[3:31:03][Carmack loop][:trivia :demo]
[3:33:22][@mathk_][What do you think about modern :rendering tech?][:experience]
[3:41:52][@norad91][@nothings2, is there a good reason for the bitfield-representation not to be defined, when designing / thinking about a new :language?][:demo]
[3:49:22][@corralx][I believe @mathk_ was talking about this article: [ref
[3:51:29][Return with pseudo-lunch and find the bottle]
[3:52:06][@aka9900][That's a very sad post right there]
[3:52:15][@ginger_bill][I have SIMD vectors already in my :language too! And swizzle works too. swizzle(v, 2, 0, 1) will work][:experience]
[3:55:24][@corralx][That is what they did with padding. The compiler can pad the fields but you have a way of preventing that. But I still feel like rearranging fields is too obscure, padding is less dangerous. To me actually I would prevent padding too and let the programmer pad its own things if he needs / wants to][:language]
[3:58:46][Resume implementing the copy_*() functions][:simulation]
[4:02:22][@corralx][To me padding is dangerous too, as a graphics programmer, so I tend to avoid it, but I feel like rearranging would be even worse. I've spend quite a few hours in the past debugging bad memory layout while passing data to the GPU][:language]
[4:04:55][:Demo the need to be explicit when writing out to disk][:language]
[4:09:15][@ginger_bill][ARM is big-endian!]
[4:09:51][@rastapharao][misunderestimate?]
[4:10:01][Continue implementing the copy_*() functions][:simulation]
[4:19:15][Remove logistics_animation_offset() and continue working on logistics_copy_and_render(), renamed to logistics_render()][:rendering :simulation]
[4:20:53][Enable copy_logistics_database() to perform the copy][:simulation]
[4:23:28][@corralx][Yeah, that is exactly why I don't see it worth it. You need to define precise and fixed rules to rearrange in the language standard, otherwise it wouldn't work. But this prevents really any real optimization and is not worth it][:language :demo]
[4:28:15][@minixmex][What's being programmed?]
[4:30:03][@norad91][JAI has that in some ways with the hot-cold stuff, I think?]
[4:30:14][@falseparklocation][@nothings2 Hey! typedef vs struct?]
[4:31:05][Continue working on the newly renamed logistics_render_from_copy()][:rendering :simulation]
[4:34:20][Disable logistics_debug_render() for now and work through compile errors][:rendering :simulation]
[4:37:22][@falseparklocation][Linus is really hate typedef]
[4:37:38][Annoyances in the C standard: Arithmetic on variable data in structs][:rant]
[4:41:41][Forward declared arrays][:rant]
[4:44:41][Continue working through compile errors][:rendering :simulation]
[4:46:57][@enemymouse][People asking "why would you do that?" on stackoverflow are the worst][:rant :experience]
[4:48:45][Finish working through compile errors][:rendering :simulation]
[4:51:31][:Run the game and do not crash]
[4:52:19][@popcorn0x90][This is why [@cmuratori Casey] doesn't read the chat]
[4:53:04][@shadyshroomz][I just got here. If you could explain stuff that would be awesome]
[4:53:08][@happylittlerat][Video freeze?]
[4:53:37][@aka9900][It's the webcam]
[4:53:58][:Run the game to :demo the current state]
[4:57:58][@heroickatora][So this is kind of Factorio meets Minecraft?]
[4:58:05][The intent of ~OBBG]
[5:00:08][Clean up and commit "render logistics from a copy"]
[5:02:02][Make logistics_render() only copy the database on a longtick][:simulation :rendering]
[5:02:44][:Run the game to try that]
[5:04:34][Make logistics_render() only copy the database when it changes, :run the game and consider gathering data]
[5:05:23][Introduce logistics_update_block_core_queue() to enable :threading logistics_tick()][:simulation]
[5:09:30][@ginger_bill][xs and ys are the sizes of elements for qsort. xs < ys will return 0 or 1 so -1, 0, 1 are the values needed to sort][:language :sorting]
[5:11:47][:Demo stb_intcmp() and wish for qsort() to take a SORT_REVERSED parameter][:sorting]
[5:15:09][@ginger_bill][Okay, I'll do alphabetical then][:sorting]
[5:16:18][Determine to let the :animation stutter if it can't keep up with the :simulation][:rendering :threading]
[5:17:38][Introduce trigger_logistics_database_copy() which creates a semaphore][:simulation :threading]
[5:22:37][Make logistics_render() and logistics_thread_main() work in tandem using the semaphores][:threading :simulation]
[5:26:10][@ginger_bill][I've just found a problem with non-ordered structs: Imagine Thing{a, b, c}; Without reorder the order matches the layout, with reorder it may not. Where Thing{a, b, c} is a compound literal][:language :sorting :experience]
[5:27:45][Make the threadsafe_queue struct and related functions public][:threading]
[5:29:44][Introduce and make logistics_init() initiate a block_update_queue][:threading :simulation]
[5:54:15][@furroy][Can you pick up the pink dots from the belt and they appear in inventory?]
[5:54:30][Rename inventory to item_chooser in preparation for implementing a real :inventory][:ui]
[5:58:39][Enable mouse_down() to handle UI_SCREEN_inventory][:"input handling"]
[5:59:26][Make the actionbar and :inventory use the same data structure][:ui]
[6:03:32][@furroy][I'm used to holding down whole time]
[6:03:34][@zilarrezko][Yeah, click and hold and drag]
[6:04:52][@furroy][Mwahahaha, you know what the peanut gallery will choose...]
[6:05:02][@edelknecht][Won't it hurt to stand for hours?][:trivia]
[6:05:37][@happylittlerat][If you have something already held, then don't pick]
[6:05:46][@happylittlerat][Support both]
[6:05:47][@djmonkey64][It pushes it forward a slot from memory]
[6:05:53][Determine to support both kinds of dragging][:"input handling" :ui]
[6:06:30][Introduce hit_detect_grid() for mouse_down() to use and][:ui]
[6:16:31][Make the :inventory start non-empty][:ui]
[6:17:15][@zilarrezko][There's also hover over an item and pressing 1-0 and then Shift + Left Click]
[6:17:24][@furroy][Won't the drag on self trigger instantly? Seems like you would need to see if it went off first and then back]
[6:17:49][Introduce inventory_mode_drop_item() for mouse_down() and mouse_up() to use][:inventory :ui]
[6:21:03][@hekmedia][@nothings: How / where are 3D models stored, like pickers? Are the .crn files models?][:rendering :animation]
[6:22:26][Draw the actionbar if we are in creative mode, otherwise draw the whole :inventory][:ui]
[6:25:04][Introduce compute_drag_shape() for inventory_mode_drop_item() and do_ui_rendering_2d() to call][:ui]
[6:30:04][@zilarrezko][If I wanted to pack :font data, or some type of bitmap into my executable (to have like a default font or bitmap that I didn't want to keep an external part), how would you personally approach achieving this? [ref
site="the Nothing itself nothings"
page="Bitmap fonts for C/C++ 3D programmers"
url=https://nothings.org/stb/font/]]
[6:33:15][Add blocks to the items enum and clean up compile errors][:ui :inventory]
[6:38:16][:Run the game to see how this goes]
[6:38:42][Enable draw_ui_row() to handle blockcodes and itemcodes and init_ui_render() to populate the sprite_for_itemtype array][:ui :inventory]
[6:44:30][Fix all call sites of draw_ui_row()]
[6:45:18][:Run the game and do not see the :inventory being drawn]
[6:45:56][Only do compute_ui_inventory() in init_ui_render()][:ui]
[6:46:57][:Run the game and correctly see an empty action bar]
[6:47:05][Enable do_ui_rendering_2d() to draw the :inventory]
[6:55:01][Explain how hide works][:ui]
[6:56:03][@furroy][You left out the break at end of case ui_screen_inv]
[6:57:20][Make draw_ui_row() correctly advance the row, and :run]
[6:58:06][Break into inventory_mode_drop() and inspect what happens]
[6:59:52][Make do_ui_rendering_2d() pass the correct data to draw_ui_row()][:ui]
[7:01:10][:Run the game and try dragging :inventory items]
[7:01:41][Fix do_ui_rendering_2d() to render sprites correctly while dragging][:ui]
[7:04:42][:Run the game and try dragging :inventory items]
[7:05:23][Fix inventory_mode_drop_item() to correctly swap items, and :run]
[7:06:35][Introduce did_drag() in order to enable process_mouse_move() to handle click-and-hold dragging][:ui :"input handling"]
[7:10:27][:Run the game and try dragging]
[7:12:04][Set the threshold really high and :run again to see what's going on]
[7:14:22][@internal_static_void][Would you recommend using raw winapi for a windows build and X11 for a Linux build, or use a library to try to keep one application cross platform?]
[7:14:52][@sandwichmaster5000][Hello! I hope you are doing well! I was wondering if you knew of any good tutorial videos, I need to code a timed street light but I am pretty lost]
[7:15:16][Motivational advice][:experience]
[7:19:49][:Demo an implementation of a random number guesser]
[7:22:27][:Run the game and consider what we need next]
[7:22:56][Enable item placing to use the action bar][:ui]
[7:27:15][:Run the game and find that the ghost is not using the bar]
[7:27:29][Enable do_ui_rendering_3d() to draw the ghost based on the action bar][:ui]
[7:27:57][:Run the game to try out the ghost, and commit "inventory ui"]
[7:30:21][@soysaucethekid][I have a question about compiling the ~stb library (on a Raspberry Pi). I'm trying to compile the truetype test and it's complaining about undefined references the math functions, though looking at the source it looks like that ifndef STBTT_ifloor, it should use <math.h>, I don't see it STBTT_ifloor defined... compiling: gcc test_trueype.c -D TT_TEST]
[7:30:34][@furroy][Does the swap work on the bottom bar?]
[7:32:13][@popcorn0x90][Math required -lm in Linux?]
[7:32:27][@furroy][Pick off the belts]
[7:32:42][Consider the problem of picking off belts][:inventory :simulation]
[7:33:57][@hekmedia][Yeah, hit key to pick stuff up]
[7:36:19][Introduce non_logistics_interactions() and player_vacuum()][:simulation]
[7:41:49][Enable non_logistics_interactions() to vacuum nearby items into the player's :inventory]
[7:50:25][@hekmedia][Just an idea maybe look at a block / conveyor and hold the vacuum key, and everything passing into the block is picked up? Could look above you, etc. and "select" where to pick stuff up. It would be chunk aligned too then. Maybe even more intuitive instead of stuff from all around being picked up]
[7:51:51][Consider the separate case of picking out of machines][:inventory]
[7:52:48][Continue implementing vacuuming items off belts][:inventory]
[8:02:09][Reflect on the terribleness of this giant non_logistics_interactions() function][:inventory]
[8:02:50][Introduce should_vacuum() and vacuum_item()][:inventory]
[8:05:42][Add "vector lib" to the TODO list and introduce axis_overlap()][:inventory]
[8:09:13][Bind vacuuming to a key and fix compile errors][:"input handling" :inventory]
[8:13:17][@emanuallan][What is he programming right now?]
