3 ms·
Single-player fans can play Dwarf Fortress, which creates a custom 1000+ year history and has the most "realistic" damage formulas I've ever seen: http://dwarf
by dragontamer 13y ago
Single-player fans can play Dwarf Fortress, which creates a custom 1000+ year history and has the most "realistic" damage formulas I've ever seen:
http://dwarffortresswiki.org/index.php/DF2012:Combat http://dwarffortresswiki.org/index.php/DF2012:Combat
* Contact Area: Determines the surface area hit by the weapon. Likely in mm2.
* Velocity Multiplier: Effectively increases the velocity of the weapon swing.
* Blunt weapons are all about weapon mass, contact area, and velocity. Apply a large force to a small area for bone crushing goodness.
* Mass is likely material Density times weapon Size
* Momentum is Mass times Velocity
* Velocity is based on the Mass of the weapon, the Strength of the wielder, and the Velocity Multiplier of the weapon
* Any impact must have a conservation of momentum, and thusly, impart the weapon's momentum to the target
* Stress is the Force of the strike divided by the Contact Area
* Material Impact Yield determines the Stress required to dent the armor (likely not used)
etc. etc. etc.
Oh yeah, Dwarf Fortress runs quite slowly. Its an ASCII art game that bring computers to their knees.
- Dylan16807 13y agoIt's also quite badly coded. And there is absolutely no reason it couldn't do sim on one core (or more) and rendering on another core, there just happens to be no 3d coder on the team, let alone artists.
- NoodleIncident 13y agoBadly coded beats not coded every time. The pair of them tried the whole 3D thing with their previous game, Armok. They said that it limited their options too much, so they decided not to do it. I don't think the core rendering speed has anything to do with that decision. Besides, there are passable tilesets available by replacing the fonts, support for individual bitmaps for every creature, and if you don't mind directly accessing the memory, even an isometric renderer (Stonesense). All of these graphical enhancements are made by fans, freeing the two of them making it to just make the game. The development log for this game is fascinating and occasionally hilarious. Today he implemented a system that lets refugees from conquered sites turn to banditry if they 'choose' to. A long time back, to test thermal conductivity, he took control of a magma man, grabbed on to an adventurer's head with both hands, and waited for its various tissues to catch on fire / melt.
- dragontamer 13y agoDwarf Fortress is memory-limited, not CPU limited. Running DF on multiple cores won't change the fact that the simulator taxes memory extremely hard. Taxing memory even more by including 3d rendering or PCIe transfers to a graphics card will slow down the game. Its a known fact that Dwarf Fortress is mainly effected by memory latency (and not cache size or memory bandwidth). Each simulated agent takes up a lot of RAM, and lots of their information needs to be updated in every game tick. Cache-optimization is near impossible. When the single CPU that runs Dwarf Fortress is almost always stalled waiting for RAM, then adding more cores to the mix does NOTHING.
- Dylan16807 13y agoMultiple threads of execution means you can saturate memory instead of alternating between fetches and computations. But I thought pathfinding and fluid simulation were big CPU hogs, and those can cache very well.