{"id":2180,"date":"2011-09-01T00:12:55","date_gmt":"2011-08-31T14:12:55","guid":{"rendered":"http:\/\/www.vectorstorm.org\/?p=2180"},"modified":"2011-09-01T00:12:55","modified_gmt":"2011-08-31T14:12:55","slug":"the-last-multithreading-post-for-now","status":"publish","type":"post","link":"https:\/\/www.vectorstorm.com.au\/2011\/09\/01\/the-last-multithreading-post-for-now\/","title":{"rendered":"The last multithreading post (for now)"},"content":{"rendered":"<p>Setting up multithreading code is complicated!<\/p>\n<p>Here&#8217;s what&#8217;s new:<\/p>\n<ul>\n<li>Set up a generic &#8220;task management&#8221; system for MMORPG Tycoon 2. \u00a0Systems generate &#8220;tasks&#8221;, and tasks are assigned out to worker threads, which work on those tasks, and then let the main game know when the tasks finish. \u00a0Heightmap building now uses these generic worker threads, instead of having their own threads. \u00a0Right now, there are eight worker threads. \u00a0But in theory, it&#8217;s probably best to have the same number of threads as the user&#8217;s CPU has cores, potentially plus one.<\/li>\n<li>Clutter generation stuff occurs using dedicated threads. \u00a0I need to convert these over to use the new generic worker threads.<\/li>\n<li>The game now waits for all queued up tasks to complete, before rendering the next frame. \u00a0This fixes some problems I was having before, where different blocks of terrain were updating at different times and not matching each other, just due to how long they took to calculate in the background threads.<\/li>\n<li>Fixed some issues with my OS X semaphore implementation (since OS X doesn&#8217;t support unnamed semaphores, for unknowable reasons).<\/li>\n<li>Worked around a renderer bug, where anything which had no texture was being drawn opaque, regardless of its material settings. \u00a0This affects the live trunk, too; \u00a0I&#8217;ll bring the fix across at the same time as the various threading fixes I&#8217;ve mentioned in the past week or so. \u00a0(If anyone needs a quick workaround in the meantime, just remove the line &#8220;m_state_SetBool( vsRendererState::Bool_Blend, false );&#8221; from vsRendererSimple::SetMaterial() on VS_RendererSimple.cpp, line 958.)<\/li>\n<\/ul>\n<p>And now, I&#8217;m completely sick of dealing with the complexity of threads, and so the next thing on my list will be more player AI. \u00a0I think I&#8217;m going to work on making players assemble into parties that do quests together. \u00a0That ought to be entertaining.<\/p>\n<p>And it raises some interesting questions, which actually come up in the development of real MMORPGs; how to handle characters who are of differing levels, but who want to team up &#8212; ignore it? \u00a0Boost the level of the lower character? \u00a0Lower the level of the higher player? \u00a0Not allow teaming between those characters? \u00a0And worse, what do we do when a character completes a quest multiple times, accompanying different party members. \u00a0Do they get the reward multiple times?<\/p>\n<p>My understanding is that most modern MMORPGs now give credit for completing a quest again in this sort of situation, but older MMORPGs often will not give repeated completion XP. \u00a0I wonder whether I need to make this configurable for players, or whether I should just take the modern approach and assume that that&#8217;s what everyone will want.<\/p>\n<p>Lots of stuff to think about!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Setting up multithreading code is complicated! Here&#8217;s what&#8217;s new: Set up a generic &#8220;task management&#8221; system for MMORPG Tycoon 2. \u00a0Systems generate &#8220;tasks&#8221;, and tasks are assigned out to worker threads, which work on those tasks, and then let the main game know when the tasks finish. \u00a0Heightmap building now uses these generic worker threads,&hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":""},"categories":[24,25],"tags":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/po9WK-za","_links":{"self":[{"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/posts\/2180"}],"collection":[{"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/comments?post=2180"}],"version-history":[{"count":0,"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/posts\/2180\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/media?parent=2180"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/categories?post=2180"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vectorstorm.com.au\/wp-json\/wp\/v2\/tags?post=2180"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}