Editing Talk:Rocket launcher

From DoomWiki.org

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 5: Line 5:
 
also, has anyone ever noticed that projectiles which graze you seem to do less damage than those that hit you square in the face?  or am i just imagining things?
 
also, has anyone ever noticed that projectiles which graze you seem to do less damage than those that hit you square in the face?  or am i just imagining things?
  
:I'm sure the splash and direct damage are done seperately. And the projectile thing is probabally a coincedence since the only reason projectiles of the same type do different damage is because of a random chance. -- [[User:TheDarkArchon|TheDarkArchon]] 21:46, 13 Jan 2006 (UTC)
+
:The individual talk pages are there for a reason. Anyway, I'm sure the splash and direct damage are done seperately. And the projectile thing is probabally a coincedence since the only reason projectiles of the same type do different damage is because of a random chance. -- [[User:TheDarkArchon|TheDarkArchon]] 21:46, 13 Jan 2006 (UTC)
  
 
::It seems like it would be computationally more efficient to check for pain at the end of each tic, not every time a blow landed (especially since the "staggering" animation takes up multiple frames).  Coming from me, of course, that's just a guess, because I can never really tell what's going on in the source code.  But [[Doom#History and development|one does hear certain stories]] about how many things id had to do to shave clock cycles, so that their opus would actually run on a [http://www.homestarrunner.com/sbemail41.html 386].     [[User:Ryan W|Ryan W]] 23:32, 13 Jan 2006 (UTC)
 
::It seems like it would be computationally more efficient to check for pain at the end of each tic, not every time a blow landed (especially since the "staggering" animation takes up multiple frames).  Coming from me, of course, that's just a guess, because I can never really tell what's going on in the source code.  But [[Doom#History and development|one does hear certain stories]] about how many things id had to do to shave clock cycles, so that their opus would actually run on a [http://www.homestarrunner.com/sbemail41.html 386].     [[User:Ryan W|Ryan W]] 23:32, 13 Jan 2006 (UTC)
 
:::Painchance is handled in P_DamageMobj () in p_inter.c.  This is the generic "hurt something" code which is called for all damage events.  I'm not aware of any situations in the game where multiple seperate damage events are combined into one painchance check.  For rocket splashes, P_RadiusAttack () from p_map.c calls P_DamageMobj individually for each splash it makes, and the direct hit is also a separate call.  BFG tracers and shotgun pellets also call P_DamageMobj individually for each one, even if many hit one target. [[User:Goyuken|Goyuken]] 05:14, 20 October 2007 (UTC)
 
 
::::Heh, I suppose that's why shooting a cyberdemon with an SSG makes him flinch more often than not (a Leukart-style calculation says 80% of the time), even though his pain chance is so low.    [[User:Ryan W|Ryan W]] 14:50, 23 April 2008 (UTC)
 

All contributions to DoomWiki.org are considered to be released under the CC BY-SA 4.0 International (see Doom Wiki:Copyrights for details). By contributing, you agree to be bound by the Terms of Use.
Your changes will be visible immediately. Please enter a summary of your changes above.

Do not submit copyrighted images or text without permission! This includes text taken from in-game codices or logbooks, or from official instruction manuals, strategy guides, and other such books.

This project is not affiliated with id Software, Raven Software, ZeniMax Media, Bethesda SoftWorks, or any other commercial software developer or publisher. Use of trademarked logos and other protected intellectual property is solely for the purpose of analysis and critical commentary on the identified products and associated fan community activity, and does not imply any endorsement by any of these organizations or their employees, past or present.

Cancel | Editing help (opens in new window)