10-06-2013, 12:25 AM
The mesh uses a lot of memory when it gets bigger (seems to increase exponentially, but I've no way of measuring that). I had problems with recording new mesh in one zone as the existing mesh covered most of the zone (just not where I wanted). It would take a step forward, freeze while it dropped new triangles (for about 1 sec) then unfreeze, then take a step forward, freeze, etc. I've got 16gb of 1866mhz g.skill ram, a 4gb gtx770, and an i7 3770k @ 4.6ghz (too lazy to clock it higher, despite having the cooling for it), SSDs too (a given these days).
Once the mesh was recorded though, I had no issues. If you have problems just running a mesh (as opposed to recording), I suggest making a post about it and opening dialogue with the devs about it. Also, try lowering your gfx settings to minimum in-game. Should make a world of difference.
Once the mesh was recorded though, I had no issues. If you have problems just running a mesh (as opposed to recording), I suggest making a post about it and opening dialogue with the devs about it. Also, try lowering your gfx settings to minimum in-game. Should make a world of difference.