Code Zone Episode 69: Bug Squashing and New Polygon Editor Features

• 0:00-0:02 Introduction: The stream focuses on debugging a polygon editor.
• 0:01:05 The Bug: The main issue is a bug where, after drawing multiple shapes, the ability to select and move vertices of older shapes is lost.
• 0:02:00 Polygon Editor Features: The streamer has added features to draw and select shapes, and edit their corners. The hover effect is a nice visual cue.
• 0:02:57 Lua Error: When attempting to move vertices on an affected shape, a Lua error occurs: attempt to index a nil value. This indicates the Lua script is losing the link to the C++ node object.
• 0:03:50 Unique Lure States: Each shape has a unique Lua State machine, which should have its own local data, leading the streamer to question the cause of the issue.
• 0:06:08 Smart Lines: The streamer demos smart lines. These lines generate radiuses automatically with vertex point edits. It utilizes triangles and doesn't get overdraw.
• 0:07:59 The Nodes Are There: The core issue is a breakage in the link between the nodes in the C++ code and the Lua state, not the absence of the nodes themselves.
• 0:10:35 Inhaled a Fly: A fly is inhaled.
• 0:12:00 Tooth Issues: Personal details shared about a dentist appointment for a crown replacement leading to some speaking difficulty
• 0:16:37 C++ Crashing: The debugger revealed that C++ is crashing because the vector is not there.
• 0:17:10 Stale References: A concern exists about stale references causing a memory leak
• 0:17:56 Solution: The chat suggests that the same name on global values may be an issue.
• 0:21:05 STL Library Dive: Sol's way of accessing internal values is explored, and an attempt to find nulled values is conducted.
• 0:27:15 The Heap is Corrupted: The memory may be corrupt.
• 0:29:00 Recent Shapes Work The most recently created shape never runs into the same problem.
• 0:30:01 Linking Lure: The current linking process is explored.
• 0:30:19 Temporary Vectors It is suggested the node may be taking address of temporary vector.
• 0:33:13 Pointers At this point it was reiterated no pointers are being used.
• 0:33:55 Mouse Hover is Good: The hover highlight on collision detection is good.
• 0:34:27 S's Role S is described to handle linking with standard vectors.
• 0:37:18 Real Problems Surface: As things begin to function as expected again, the limitations of current systems are revisited.
• 0:40:01 Model Types: Several model types are discussed.
• 0:40:59 Try - Catch As they continue to fail, it is suspected try catch may be to blame.
• 0:41:53 Iterator Debugging: The chat proposes to enable iterator debugging.
• 0:43:07 Crash in Lure: It is identified that the lure is Legitimately failing,
• 0:43:14 Need a Sol Spurt: Sol expert desperately needed to help with the situation
• 0:43:53 Isolate Problem: Isolated it was found that a single shape never runs into this problem.
• 0:45:35 Shouting out shout show or shout out, is proposed.
• 0:45:50 S All Safeties Safety net settings are described.
• 0:46:49 Push Back Push back was a red flag and could potentially be to blame.
• 0:53:00 L Side is Fine They prove even at this later point L side is still great.
• 0:57:00 VC Shapes VC shapes are described to never change during this section of code.
• 0:57:54 Vector Decks and Fixes A solution is presented to change a vector to a deck which they say for a point this simple problem it would remedy.
• 0:58:35 V Shapes is Invalidated Reiterations that if they push back into VC shapes you invalidate references from LURE on existing shapes.
• 0:59:00 Yes It Clicked As they began to draw shapes the chat discovered the invalid reference is indeed to blame and offered solutions.
• 1:03:00 Next Steps - It's All Down Hill: It is suggested that the design needs to shift.
• 1:03:45 More Chat Wisdom: The team reflects on the discovery that the chat just identified.
• 1:04:00 Reallocation Caused The Chaos: Reallocation of vectors and references moving causing problems was the real reason for the situation.
• 1:05:30 Deck Fixes All :D Indeed deck made everything work
• 1:07:33 S Code Deep Dive Code files and methods were presented with the intent of explaining how to solve or the cause of problems.
• 1:15:30 Performance Issues: Geometry is generated live and comes at the cost of performance and increased geometry numbers.
• 1:18:00 Release Mode Release mode drastically improved speed.
• 1:23:20 Wrap Up: The team was excited to continue and fix some code and thanked people who subscribed.