3/18/2024 0 Comments Gamebryo engine terribleIf you compile the dll with even just the 2005 compiler, then you are in for a mess if you allocate memory in the dll and free it in the exe or vice versa. This means we have to use the 2003 compiler. If you mix versions, you can quickly get weird bugs. It's the fact that with each generation of Microsoft Visual Studio, the compiler will use a different version of API for memory allocation. The biggest problem isn't even 32 vs 64 bit. I think that part of the answer to question (2) is that developers make hardcoded assumptions about available memory space inside the code, but I'm wondering if there's more to it. If someone here is patient enough to explain, and assuming that my conceptions are correct in the first place, I'm wondering (1) why it's impossible or very hard to replace the current Python interpreter with an 圆4 version or even a different Python version, and (2) how monumental a task it is to convert the x86 assembly of the Gamebryo-files to working 圆4 assembly. Civ4 uses a Python 2.4 interpreter compiled to x86.Source for Gamebryo's engine for Civ4 is not released.Firaxis has released all the source code for Civ4 which they exclusively own themselves. ![]() ![]() I've revisited this question sporadically the last couple of years, and if I remember it right, the situation is this: C++ and any other language statically compiled to assembly.Windows development (or desktop app development in general).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |