| Rev | Author | Branch | Log Message | Date | SHA |
|---|---|---|---|---|---|
| r23661 | 1.7 | Fix texture mem leaks and performance issues |
8 December, 2025 | ||
| r23660 | 1.7 | Fix texture-mixing bug introduced by e317cc0 |
8 December, 2025 | ||
| r23659 | 1.7 | Fix shaders crash |
7 December, 2025 | ||
| r23658 | 1.7 | Fix streaming bugs and txd leak |
7 December, 2025 | ||
| r23657 | 1.7 | Improve texture/shader loading system |
6 December, 2025 | ||
| r23656 | 1.7 | Fix textures crash when restarting resource |
5 December, 2025 | ||
| 1.7 | Fix serveer crash |
5 December, 2025 | |||
| r23654 | 1.7 | Force rebuild |
4 December, 2025 | ||
| r23653 | 1.7 | Addendum #2 to 28ade16 |
4 December, 2025 | ||
| r23652 | 1.7 | Addendum to 28ade16 |
4 December, 2025 | ||
| 1.7 | Fix build error in certain configurations (custom builds) #2 |
4 December, 2025 | |||
| 1.7 | Fix build error in certain configurations (custom builds) |
4 December, 2025 | |||
| 1.7 | Update CEF to 142.0.17+g60aac24+chromium-142.0.7444.176 This brings some stability fixes in CEF itself. |
3 December, 2025 | |||
| r23648 | 1.7 | Fix SA crash at 0x00897C28 (dump name wrongly identifies it as 0x003F0090), likely 'caused' by VS2026 but a latent stack offsets bug since its introduction (736660bf2). Theory: VS2026 changed changed how inline assembly works. Probably something with different stack alignment, optimization choices, register allocation, calling convention optimizations, or code generation. (This can all be relevant to spot similar bugs manifesting now across hooks). The broken, now patched, assembly code was reading stack values from wrong offsets, and while the old compiler's code generation might have accidentally put "harmless" values at those wrong locations, the new compiler's different stack layout or register usage puts critical values (like 0xC97C28 - the address of _RwD3DDevice) at those locations. ... |
3 December, 2025 |