Rooba
/
ReC98
mirror of https://github.com/nmlgc/ReC98.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity
ReC98/th01/main_38.cpp

26 lines
596 B
C++
Raw Normal View History

[Decompilation] [th01] Pellet rendering So even TH01 wasn't 100% C++ after all. Turns out that this function was the only instance in all of REIIDEN.EXE where ReC98 previously had different encodings for identical x86 instructions. Part of P0096, funded by Ember2528.
2020-06-05 15:19:44 +00:00
/* ReC98
* -----
[Decompilation] [th01] Pellets: Manager class constructor Note how Turbo C++ auto-generates that call to `operator new`, which you don't see in the decompilation anymore. So yeah, as soon as you add a constructor, Turbo C++ enforces heap allocation for any instance of that class, even function-local ones that would otherwise be stack-allocated. That's where the bad reputation of C++ comes from, I guess? Part of P0102, funded by Yanga.
2020-07-04 11:52:53 +00:00
* Code segment #38 of TH01's REIIDEN.EXE
[Decompilation] [th01] Pellet rendering So even TH01 wasn't 100% C++ after all. Turns out that this function was the only instance in all of REIIDEN.EXE where ReC98 previously had different encodings for identical x86 instructions. Part of P0096, funded by Ember2528.
2020-06-05 15:19:44 +00:00
*/
[Decompilation] [th01] Player shots: Spawn function Continuing to learn new things about Turbo C++'s code generation! Part of P0098, funded by Yanga.
2020-06-10 20:45:56 +00:00
#pragma option -Z
[Decompilation] [th01] Pellet rendering So even TH01 wasn't 100% C++ after all. Turns out that this function was the only instance in all of REIIDEN.EXE where ReC98 previously had different encodings for identical x86 instructions. Part of P0096, funded by Ember2528.
2020-06-05 15:19:44 +00:00
[Decompilation] [th01] Player shots: Spawn function Continuing to learn new things about Turbo C++'s code generation! Part of P0098, funded by Yanga.
2020-06-10 20:45:56 +00:00
extern "C" {
[Decompilation] [th01] Pellets: Manager class constructor Note how Turbo C++ auto-generates that call to `operator new`, which you don't see in the decompilation anymore. So yeah, as soon as you add a constructor, Turbo C++ enforces heap allocation for any instance of that class, even function-local ones that would otherwise be stack-allocated. That's where the bad reputation of C++ comes from, I guess? Part of P0102, funded by Yanga.
2020-07-04 11:52:53 +00:00
#include "th01/th01.h"
#include "th01/ranks.h"
#include "th01/snd/mdrv2.h"
#include "th01/formats/ptn.hpp"
#include "th01/hardware/egc.h"
[Decompilation] [th01] Pellets: Shot/Orb/deflecting player collision First off: 👏 Just 👏 pass 👏 a 👏 reference 👏 to 👏 the 👏 currently 👏 iterated 👏 pellet 👏 if 👏 you 👏 need 👏 to 👏 modify 👏 it 👏 Second: Don't we hit-test pellets vs. shots already, in the CShots class? So what is this garbage…?! Completes P0101, funded by Yanga and Ember2528.
2020-07-03 20:19:17 +00:00
#include "th01/math/subpixel.hpp"
[Decompilation] [th01] Pellets: Manager class constructor Note how Turbo C++ auto-generates that call to `operator new`, which you don't see in the decompilation anymore. So yeah, as soon as you add a constructor, Turbo C++ enforces heap allocation for any instance of that class, even function-local ones that would otherwise be stack-allocated. That's where the bad reputation of C++ comes from, I guess? Part of P0102, funded by Yanga.
2020-07-04 11:52:53 +00:00
#include "th01/math/vector.hpp"
#include "th01/main/vars.hpp"
#include "th01/main/playfld.hpp"
#include "th01/main/player/player.hpp"
#include "th01/main/player/orb.hpp"
#include "th01/main/player/shots.hpp"
[Decompilation] [th01] Pellets: Unblit/update/render function … pellet unblitting uses a *doubly* sloppy 16×8 rectangle. 🤦 The resulting terrible flickering is probably why the Stage 15 and 20 battles enable this weird "interlace" mode that only renders and hit-tests half of the pellets each frame… except that player shots are still hit-tested every frame? So yeah, your eyes aren't deceiving you, the game does effectively drop its perceived frame rate in the Elis, Kikuri, Sariel, and Konngara fights, and it does so deliberately. And *then* you realize that those weird hit tests are actually a futile attempt to mitigate the disastrous effects of a way too large unblitting rectangle. Congratulations, you've found the most stupid piece of code in this game. Part of P0102, funded by Yanga.
2020-07-05 20:21:19 +00:00
#include "th01/main/bullet/pellet.hpp"
}
[Decompilation] [th01] Pellet rendering So even TH01 wasn't 100% C++ after all. Turns out that this function was the only instance in all of REIIDEN.EXE where ReC98 previously had different encodings for identical x86 instructions. Part of P0096, funded by Ember2528.
2020-06-05 15:19:44 +00:00
[Decompilation] [th01] Player shots: Spawn function Continuing to learn new things about Turbo C++'s code generation! Part of P0098, funded by Yanga.
2020-06-10 20:45:56 +00:00
#include "th01/main/player/shots.cpp"
[Decompilation] [th01] Pellets: Manager class constructor Note how Turbo C++ auto-generates that call to `operator new`, which you don't see in the decompilation anymore. So yeah, as soon as you add a constructor, Turbo C++ enforces heap allocation for any instance of that class, even function-local ones that would otherwise be stack-allocated. That's where the bad reputation of C++ comes from, I guess? Part of P0102, funded by Yanga.
2020-07-04 11:52:53 +00:00
#include "th01/main/bullet/pellet.cpp"