Not completely consistent, but the pattern is still obvious. For example, a four-byte repeat pattern might look like etc, in ASCII. *Byte repeat pattern: My term for a repetitious pattern within a hex string. If anyone has an account at qhimm, please inquire there as to how one would go about viewing a Table of Contents / Index file from a Playstation CD. I'm still awaiting an account confirmation email from I think it doesn't like Yahoo. But I believe it may be what we're looking for. It is significantly different from its Xenogears counterpart for one thing, it's only 13 sectors long as opposed to 16, and secondly, the byte repeat pattern* happens every four bytes as opposed to every seven bytes. In other news, I'm attaching a hex string that might just be the Chrono Cross table of contents. I've linked to it already in this thread, but here it is again: Anyone who'd like to recapture Cross environments like what Zeality's doing, please see the tutorial on. I'm not going to have time to join in on the VRAM dumping frenzy this weekend after all, unfortunately. I wonder if the separate layers for each environment are stored as different files on the Cross CD? That would be sweet if so, because it would allow for slightly different or expanded environments to be made once the Compendium gets to the point of Cross fangames and hacks. I'd forgotten just how beautiful Cross' environments could be. If this works, then I'll move onto Cross and see if I can find a similar index file.
dat file, perhaps?) I'll return to the matter once I get a few things done outside the Chrono world. I'll leave it with the Community for a few hours to ponder how this can be viewed (as a. I didn't put a file extension on it yet it's raw hex. Okay, I've attached what I think is the Xenogears index file. Not sure what it'll be in Cross, though the PlayStation logo model is stored at the same offset in both Cross and Xeno.Īnyone familiar enough with disc sectors to tell me if 2048 sounds like a reasonable number of bytes per sector on a PlayStation CD, and if it's likely that Cross has the same number of bytes per sector? That makes the index file's starting offset in Xenogears C000, BTW.
If 2048 is the magic number, then everything seems to be shaping up with what's in the qhimm wiki reference on Xeno.
Chrono compendium pip iso#
It seems the disc sectors in Xenogears are 2048 bytes long, not 2352 (which I thought was the iso standard). Can anyone tell me if my understanding of the qhimm wiki entry Vehek posted is correct? I'll see if I can register at qhimm too and ask there for advice.ĮDIT: Oh-hoh- hoh. I *think* that means it should start on offset DC80 assuming each sector is 2352 bytes long (i.e., 2352 * 24 -> Hex). According to the info Vehek posted above, Xeno's index file starts on the 24 th disc sector and is 16 sectors long. Any ideas on what we would view a Table of Contents with? Just throw it into Notepad, maybe? Terminus Traductions' notes will help here.ĮDIT: Before I try to find Chrono Cross' index file, I'm going to try it with Xenogears first so I can get a sense of what I'm looking for. Others are welcome to try before I get to it, of course. I'll see if I can't rip some hex strings from the iso based on that wiki tonight.
Chrono compendium pip windows#
This could be a major breakthrough Chrono Cross definitely seems to have the same deal, what with the SLUS file and SYSTEM.CNF being the only things Windows can see.
0 kommentar(er)
