Wow, keep in mind that I'm on a pre-alpha version of dfhack for 43.05, I can't begin to figure out what is actually causing it due to the nature of the problem, but launching AV on arch linux, 64 bit, makes df go from using ~700 mb or so of ram to every bit available very very rapidly. First time it completely froze and I had to go around and hit the power button to reboot, this time I managed to kill it at ~3 GB used.
Edit to note, THIS time it printed a config.json, last time it wasn't able to do so, the numbers here are in the right ranges I assume?
{
"meshing": {
"meshingThreads": 4,
"queueLimit": 8
},
"rendering": {
"drawRangeSide": 4,
"drawRangeUp": 1,
"drawRangeDown": 5,
"maxBlocksToDraw": 460800,
"maxTextureSize": 512,
"textureAtlasSize": 2048,
"debugTextureAtlas": false,
"drawClouds": true,
"distantTerrainDetail": 2,
"drawShadows": true,
"vSyncCount": 0,
"targetFrameRate": 60,
"showHiddenTiles": false,
"fog": true
},
"units": {
"drawUnits": true,
"scaleUnits": true
},
"camera": {
"fieldOfView": 70.0,
"deferredRendering": true,
"SSAO": true
},
"game": {
"showDFScreen": false
},
"debug": {
"drawDebugInfo": false,
"saveBuildingList": false,
"saveCreatureList": false,
"saveItemList": false,
"saveMaterialList": false,
"savePlantList": false,
"saveTiletypeList": false
}
}
Also, the only reason it's a pre-alpha is due to some missing offsets, but I would expect that to just crash or not load or something rather than ram use*2n, but I can't figure out what it could be doing that would make the dwarf fortress process to shoot up so high, or is av incorporated in the dfhack process tree now?