Gravis
Gravis
@JeodC If you compile [this code](https://gist.githubusercontent.com/GravisZro/8c3b44cae2c0526fba74cce5e0ac185e/raw/bc2597f01e542070b1d33a2f27e8e431e21be11e/savegameinfo.cpp) using the same MSVC that built the version of D3 that can load the demo file and paste the execution results then I should...
> Unfortunately, simply copy-pasting your gist caused the build to fail. Can you provide some more detailed instruction This not part of D3 project at all, it is a standalone...
> It's notably different, even when using the same compiler settings as the source, so I'm not sure 1280 is the correct expected size for the player struct. You are...
@jcoby I've looked over a bit of the code and noticed there are "canary values" that would trip if the loading was off, like this: ``` gs_ReadInt(fp, sig); ASSERT(sig ==...
Just FYI, I finally got a cross-compilation and execution environment and was able to make a build that would never go into graphics mode (I'm using non-graphic qemu) but would...
So, with a bit of dedication I was able to collect the [names and member names of almost all the structs in D3 as JSON data](https://gist.github.com/GravisZro/566ca82ae9be655adc49e1f5f453a562) (because I kept finding...
@winterheart Not all of these are socket initializations. As such, I consolidated the code into a single function in `networking.h`. Including `networking.h` in other headers lead to conflicting duplicate code...
Would someone please merge this? It's been reviewed by two people already.
Personally, I prefer the simplicity of `srand` and `rand`. Also, I found these when working on `RAND_MAX` overflow issue: - [qRandomChance](https://github.com/DescentDevelopers/Descent3/blob/8485cb0c4d0e5d80e5885850c5d6f69cade03202/scripts/DallasFuncs.cpp#L6125) - [qRandomValue](https://github.com/DescentDevelopers/Descent3/blob/8485cb0c4d0e5d80e5885850c5d6f69cade03202/scripts/DallasFuncs.cpp#L6145) If you can make the existing D3...
> Also, why not just statically link everything, if that's what we prefer? (It will definitely simplify packaging, having only a single EXE for Windows for example, but if we're...