nmlgc / rec98 Goto Github PK

The th04_marisa4_crash_warp branch's code is looks to be identical to the code in the th04_marisa4_crash_still one.

$ git checkout th04_marisa4_crash_warp 
$ git log|head
commit 96ca88f6299629973165ed0d7b5a82dc8e26b71d
Author: nmlgc <[email protected]>
Date:   Fri Apr 15 03:06:49 2022 +0200

    [Mod] [th04] Stage 4 Marisa: Replace the Divide Error with no movement at all
...

$ git log|head
commit 79a78cac7448ab7f8ce178387c493f61783cdf51
Author: nmlgc <[email protected]>
Date:   Fri Apr 15 03:06:49 2022 +0200

    [Mod] [th04] Stage 4 Marisa: Replace the Divide Error with no movement at all
    ...

I found this while trying to find if there would be a way to patch my English translated binary in a hex editor to avoid having to try setting up a cross compilation/assembly environment in Linux. I do not have windows on anything at all. I already successfully did this for the EMS crash (for the RHDN patches: change 204E to 1A4F at address 0xBD10).

I did this because I don't think the community fixes are in English.

Hello, i'm a member of touhou online and we would like to translate to french the pc98 touhou games, so i've been interested in your decompilation method of the games in order to translate them, could you tell me if it's usable and how ?

TH01 pellets are coming up next, and for the first time, we'll have the chance to move hardcoded sprite data from ASM land to C land. This raises the question of when we are going to do this The Right And Moddable Way, by auto-converting actual image files into ASM or C arrays during the build process. This converter would also automatically generate pre-shifted versions of any sprites that need them, without requiring modders to store the 8 versions of those sprites manually.

Such a minor thing is currently not covered by any of the subscriptions, probably to this missing option in the order form. Since it requires no RE skills and also collides with nothing else, it would be the perfect thing to be done by an outside contributor who is merely familiar with C/C++… if we still have any left, that is.
Any backers with outstanding contributions in the backlog might also choose to put their contribution towards that, in case they think that this is more valuable than more reverse-engineering at this point. Otherwise, I'll just hardcode TH01's pellets directly, for the time being.

Since TH05's gaiji are also stored in this hardcoded 1bpp form, I also consider this converter as a prerequisite for fully rebuilding TH05's ZUN.COM, as mentioned in the 2020-02-23 blog post. As it turns out though, the OMF .OBJ output mentioned in that post won't be necessary after all. Most of these sprite declarations lie in the middle of a translation unit anyway, and therefore need to be #included. Same for ASM land.

Some more, unsorted details I had in mind - everything here is still up for discussion though:

• Ideally, we'd only have to read 1bpp ("monochrome") .BMP files, as saved by MS Paint – any non-1bpp formats are handled by other, non-hardcoded image formats, and are out of scope here. However, Paint is pretty much deprecated, and has a quite nasty rendering bug in 1bpp mode on my system:

  
  (It's the exact spark sprite sheet from below, but some dots just aren't rendered?)

  It's also been getting more and more difficult to save this format from other tools. Therefore, the converter should also accept all other common uncompressed .BMP bit depths – but, of course, error out whenever any color other than #000000 or #ffffff is found.

• This should simultaneously compile into a 16- and 32-bit binary, right from the start. The 32-bit build step already requires the ASM arrays to be present, as does the 16-bit build step for C arrays.

• Yes, technically it wouldn't be necessary to compile this into a 16-bit Real Mode DOS program, since we could already output the C arrays during ReC98's 32-bit build step. However, people are looking forward to the eventual 16-bit-only build process, and I agree that it makes no sense to have the PC-98-only master depend on a 32-bit C++ compiler just for things like these.

• Therefore, aim for maximum portability right from the start - the converter should compile with anything from Turbo C++ 4.0J up to modern Visual Studio and GCC/Clang compilers, so that future port authors have one less thing to worry about. Now, I could force C89 onto people now, but I really don't see why I should 🙂

  ReC98 itself is going to use the freeware Borland C++ 5.5 (from the infamous freecommandLinetools.exe) as its default 32-bit Windows compiler; I've just added that one to the DevKit. Turbo C++ 4.0J defines the subset of allowed C++ features anyway, and BCC55 still happens to be the most hassle- and bloat-free way to get any sort of 32-bit Windows C++ compiler to people. (Open Watcom unfortunately only comes second here.)

• Rely on platform.h in the top level of this repo, adding new things there as necessary. For modern, sane compilers, we'd ideally only need to #include <stdint.h> there? I hope.

• For integration into the future build system, the converter should be written as a library with a C/C++ API.

• My original plan would have involved parsing sprite dimensions from a C header, recognizing the dots*_t types, as well as macros like PRESHIFT to figure out where to put the pre-shifted data, or *_H to indicate the height. However, that would not only significantly raise the complexity of this, it also can't communicate all necessary information: TH03's in-game score sprites have their dots stored upside down, but we'd obviously like to have them the right way around in the .BMP file. (Not to mention the fact that TH05's zun -G is written completely in ASM and doesn't need a C header anyway.)

• 💡 And then you notice that having a C++ build system allows you to just #include the sprite declarations from their actual header, and then pass the necessary numbers to the converter via sizeof(). So, the converter is free to only output raw numbers for the array definition. Adding per-dimension initializer lists will catch even more errors at compile-time, and mzdiff will catch the rest 🙂

• 💡 And then you notice that this doesn't depend on the build system at all. We can simply use the converter's main() function to call the conversion API for every sprite sheet in ReC98, with "hardcoded" paths, and run that from the Makefile. Then, we don't even need to design a command-line frontend.

• No further dependencies – yes, no master.lib, but also no win32_utf8. The only encoding-sensitive call should be fopen(), so let's just handle Win32 Unicode via an overload for wchar_t.

• The dots*_t types limit the width of individual sprites to 8, 16, or 32 dots, you don't need to support any other sprite widths. Pre-shifted sprites can even be restricted to 8 dots.

• Inside the .BMP files, cels can be arranged in any left-to-right, top-to-bottom order. Their individual positions are then derived according to the dimensions of the input file. An example from TH05's gaiji sprite sheet:

  • Sprite size: 16×16
  • Sprite count: 256
  • Input .BMP size: 256×256
  • → Top-left corner of sprite #174 (0xAE) is at position ((0xAE % 16) * 16, ⌊0xAE / 16⌋ * 16) = (224, 160)

• Preliminary file extensions for the generated files could be .csp and .asp. The future build system mandates that those are different from regular .cpp or .asm, because that's how it selects the compiler. Having distinct extensions also works well with .gitignore.

• Whoever writes it gets to name it. (Within reason, of course…) 6 letters max, since we need to suffix it with 16 and 32 – if a directory contains both a .COM and a .EXE with the same name, even modern 64-bit Windows runs the .COM binary by default…

• And, of course, it should output the obligatory // Generated by ??? from ???.bmp, do not modify directly comment in the first line of the file.

Currently, the converter would have to work correctly with the following sprites, and output the same arrays we currently got in the repo:

Game	.BMP file	C declaration / data layout	Note
1		dots16_t sPELLET[3][PRESHIFT][8];
2/4/5		dots16_t sPELLET[PRESHIFT][8];	Reusing TH01's bitmap is probably not worth the complication of somehow getting rid of TH01's two decay sprites, which are no longer used in later games?
2/4/5		dots16_t sSPARKS[PRESHIFT][8][8];
2		dots16_t sPOINTNUMS[13][8];	Yes, there's a 13th empty 8×8 sprite at the end. It's actually used in place of the multiplier, if the multiplier would be ×1. :zunpet:
3		dots8_t sSCORE[10][8];	Emitted data needs to be stored upside-down.
4/5		dots16_t sPELLET_BOTTOM[PRESHIFT][4];	Bottom gray part of pellets.
4/5		dots16_t sPOINTNUMS[12][PRESHIFT][8];	Also not worth reusing the first 10 sprites of TH02's bitmap.
5		dots16_t sGAIJI[256][16];
5		dots8_t sPIANO_LABEL[9][8];

(Technically, we'd also have to add the piano sprites for TH05's Music Room, but these are stored and used in such a compressed way that it defeats the purpose of storing them as bitmaps.)

I'm wondering if this reconstruction of the old Touhou games will work on IBM-compatible/standard MS-DOS.

I recently did a project to re-create the th2 ~ 5 music room. However, I encountered a problem, I do not know ZUN the use of the polygon background (which is the polygon inside the star image) where. So I'd like to ask you, where do you find those pictures from these data? thank you very much!

(@Shinmera, would you be up for doing artwork for this project as well? I've even got a more detailed description this time around.)

Now that all the doubts about the feasibility of this project have been removed and I'm slowly starting promotion, it would be nice to have some custom artwork to go along with it.

The basic concept I've been having in mind is Richard Stallman cosplaying PC-98 characters (or the other way round, whichever you think looks better or funnier). There would be 6 main versions in total: one with Reimu or Marisa (again, up to the artist) to represent the project as a whole, as well as the final boss of each game (Sariel, Mima, Yumemi, Yuuka and Shinki) to represent that specific game.

Stylistically, I'm looking for something similar to Touhoumon sprites, that is, a whole-body drawing of the given character striking a random pose. Bonus points if the 5 Magic Stones are included in the artwork, since I just love using them to mock Touhou character discussions. ☺

I'm not asking for entirely separate images per game. It's completely fine if the costumes of the 6 characters are merely layers on top of a shared base pose.

Since these will be mainly used as icons, you should be going for a square aspect ratio. Apart from that, draw as high-res as you like. (Of course, SVG is always preferred, but it's not too important.)

That said, the future ports will also introduce new in-game menus for mod selection, and I'd like to reuse some of the character artwork as message box or status icons. I think I should be able to create low-res sprites from the high-res promotional images by myself, but it would be great if I could get some help there as well. In that case, we could even add a small waiting animation or different expressions for the various types of message boxes (information, warnings and errors).

Just note that these images need to match the constraints of the PC-98 graphics hardware, and can thus only use a maximum of 16 different colors.

However, we're still about one year away from that point, so I can't give any more specifics on that right now.

I'm doing a remake of PoDD with ReC98 (when I actually get to doing it) and I need help! I need someone who can draw in the PC-98 style, composers who can make PMD music, and people who can make more stages and cutscenes for the game. I'm writing the dialogue and music comments, as well as translating stuff. Here's a TV Tropes darth wiki page on what's gonna go on in the game: http://tvtropes.org/pmwiki/pmwiki.php/DarthWiki/PhantasmagoriaOfDimDreamRemake