Giel van Schijndel schreef: > Giel van Schijndel schreef: > >> Giel van Schijndel schreef: >> >>> When looking at the code I'm guessing that all you've changed is the >>> removal of all direct calls to the blockheap system throughout all src/ >>> files? >>> >>> Wen just scanning the diffs the modifications look quite nice to me. All >>> runtime that I've already had with the produced executable has had no >>> problems (in fact it had a few less problems). >>> >>> A huge difference I'm noticing is that now my FPS actually comes above >>> 25 on my laptop. Before using your patch I'd only have an FPS between >>> 18-25 (yes the FPS limit was set on 60 as well then), now it runs on 60 >>> while 60 currently is my set limit. >>> >> Seems that when applying your patch either an existing bug gets exposed >> or a new one created. >> >> For every time when I now encounter enemy units approaching me over a >> hill (or some other terrain that requires height checking for >> visibility) an assert gets fired from src/visibility.c:164 (in function: >> SDWORD visObjHeight(BASE_OBJECT *psObject)). It seems like the memory >> which contains psObject now somehow gets corrupted which causes >> psObject->type to be overwritten. I'm guessing this is now being exposed >> because the previous malloc allocated 32 bytes extra before and after >> the requested memspace as a safety zone. >> > PS It only seems to occur when I pass the --cheat parameter to WZ Uploaded a savegame and my own compilation (only diff to r591 is your mempatch) that cause the assert-loop here: http://wz-debug.mortis.eu/
-- Giel
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
