The reason that these values are defined in xml files is to make it possible to tweak them without having to compile the dll each time.
The bug is that the event is executed multiple times until the movement costs become negative. It should only be executed once.
How are the lazy dll programmers to blame for design choices made by xml modders?
I only made that change in the save compatiblility fixes branch because it breaks saves! Is that change now also present in the master branch?
After doing a 1.2GB dummy memory allocation I finally got the game to crash while panning the map.
But the crash was in the visual c++ runtime dll...
My laptop has a 1050Ti with of 4GB VRAM.
I always limit games like CivIV to 30fps when using the laptop because more fps aren't necessary for...
I finally got an error but the ram usage was still below 2GB:
Wrapper dll using the code from https://github.com/elishacloud/DirectX-Wrappers/tree/master/d3d9 with some logging code added.
I added some very simple logging to Direct3DDevice9Ex::SetLight and when you move around the map you can see new lights being added up to the...
Have you looked at the properties of the lights which are added but not removed are they all the same?
That's how it started but they actually added it in the september update.
I'am going to play CivVI for a while the last updates really improved it and they even added a free battle royale Mode
I made the OOSLogger match the checksum calculation in CvGame::calculateSyncChecksum it doesn't help to log things which aren't included in that...
@Whisperr is using a older version of C2C as you are. The python error in OOSLogger.writeLog on your side should be fixed now.
Could you post a save showing that corruption it's something that should be fixed before v40.
On these zoomed out screenshots you can also see some missing graphics like roads. That's caused by the graphics paging changes.
Another thing that helps a bit is this ini setting it should be set to 1 to save some memory.
Disable PAK memory mapping (May affect performance)...
Viewports displays a smaller viewport into the full map instead of the full map to save graphics memory.
About saving memory.
There are some broken unused Features in C2C like the
GAMEOPTION_STRENGTH_IN_NUMBERS. That option alone uses ~140 byte per...
When playing on big maps the Viewports feature should be enabled to reduce the memory usage.
The paging can't do more then it already does...
Separate names with a comma.