Search results

  1. L

    WC2 Cinematics reverse-engineering thread

    My friends, I'm still looking for a legal way to get all the MuchowVision code into the public domain.
  2. L

    WC2 Cinematics reverse-engineering thread

    Isn't this just a question of limiting the DosBox framerates? I don't think changing the scripts would be productive... of course I only have a disassembler, not an assembler and packer to create modified files (SERIES.xxxx INCIDENTS.xxxx CAMPAIGN.xxxx AND gameflow.xxxxx which would of course...
  3. L

    WC2 Cinematics reverse-engineering thread

    Problem: In practice, SERIES does not call the the WIPE opcode directly, but uses it indirectly through the standard library. SERIES doesn't even call doshow directly, but rather some other higher-level things (INCIDENT does call doshow directly). When doing it this way, you set global 388 (and...
  4. L

    WC2 Cinematics reverse-engineering thread

    I'll just paste in my opcode list, as of today. A few things are recent and uncertain. This doesn't cover the opcode formats which are ostensibly the second parameter here, but some of these are actually deferred to the main loop code, so this doesn't tell the full story. One important opcode...
  5. L

    WC2 Cinematics reverse-engineering thread

    There are 186 opcodes in total, but you also need to know the encoding of each, which isn't consistent. A disassembler is pretty much a prerequisite; trying to investigate these files as data is pretty much doomed. The offsets in my disassemblies seem to be off by a bit compared to your...
  6. L

    Wing Commander Toolbox

    Hi everyone, I'm new here. I've been spending some time writing a disassembler for the SERIES.xxx, INCIDENT.xxx, GAMEFLOW.xxx and CAMPAIGN.xxx files in WC2, and it actually works pretty well at this point. I wanted to try out the WC Toolbox to make sure we're on the same page regarding...
Back
Top