1
Releases / Re: [REL] Final Fantasy VII - Retranslation Project With Documentation
« on: 2012-09-24 11:45:17 »
There's usually a simpler explanation to these issues: plot ≠ gameplay.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Negative; rather than choosing Save after making modifications, I chose Save As, and created a new image.You don't need to use Save, changes are instantly applied no matter what command you use after import. With Save As all you do is creating yet another identical copy of the ISO.
Actually, not quite - LBA values are always 150 lower than the corresponding sector IDs, because the first 150 sectors of a PSX disc are used for license data. That means if you're hunting look ups, you have to account for the numeric difference.There's no difference to be taken into account, you were probably mislead by CDMage's sector scroller (in which sector 150=LBA 0=beginning of the ISO). Let's go by examples: LBA=0 means something is located at sector 0, byte 0; LBA=23 means the sector you need to seek to is the 23rd, byte 54188 (23*2352=54096, where 2352 is the size in bytes of each sector). Licensing data is much smaller than 150 sectors.
What do you mean by same position? If they are the same size as they originally were, if they have the original name, and if they are in the original directory?No, I mean they must share the same LBA and size on all three disks. There's no point in retaining the original size (and whatever other crap) if you're planning on regenerating an expanded ISO.
Probably due to different gzip implementations, my file was 2 KB smaller than the originalCheck if the gzip signature is correct and if the header contains any extra information like time stamps and file names (FFVII doesn't like 'em), just in case.
It successfully imported the file (to the same LBA/sector as the original), and I saved the new image as a new file (in the same format I loaded it as, Mode 2/2352-byte image;You don't save a new image after injecting a file, it's unnecessary. The ISO is already changed as soon as you confirm the injection.
Still, I think Hack7 should be able to open the files, and complain about issues afterward if desired...Or Makou could regenerate jumps automatically. I'm not sure why it's still working internally with byte positions:
X was a great game and last great FF.... after that with FFX-2 (the first main cash in), it was over. It has never recovered.Dull cast, embarrassing story, incredibly boring battle system based on a growth system that simply doesn't exist and ends up making your characters identical in pretty much every aspect (with the exception of Yuna, she has the Summon command after all ;O ). And Nomura, oh for the love of god, NOMURA ALL OVER THE PLACE. FFX killed the series for me: so many terrible choices for just one game. No wonder the same team created XIII, another gigantic pile of flaming sh*t.
Final Fantasy series Died with Final Fantasy 10.Fixed.
The PSX had no direct access to VRAM and the transfer is slow.DMA transfers from/to VRAM are actually fast, very fast, way faster than regular RAM access from the cpu.
I bothered to check it. The same as "Glass hairpin" is made clear in Ultimania. These things are intended by the designers. A way around this is for me to do both. I can call it Omamori and in description "An amulet" but this may just be silly. Either way I am keeping Omamori because Ultimania and the bonus disk make it clear that is what it is. An Omamori is an amulet, but an amulet is not always an Omamori.Ultimania and the bonus disk were not created by the team that worked on FFVII, it was outsourced and most assets were created for just the purpose defined by said disk (notice the models for the Buggy and the Highwind, definitively not coming from game assets). In other words, it's not exactly something you'd want to refer to as accurate information as it's probably something coming from Famitsu or whoever took care of assembling all the data to create the guide and the disk. The original designers, programmers, producers, etc. had barely any role in the material you're basing your nomenclature off. Fun fact: I've never seen a sketch of the regular items coming from Nomura of whoever was assigned to additional designs.
Says here they are specifically a certain culture/religion. They are certainly not regular western items. Using "Amulet" or something else completely destroys the connection to Buddhism and Shinto. Edit. I understand the Japanese translates as "Amulet" but Ultimania makes it clear that Omamori is intended.The ones in FFVII aren't Shintoist or Buddhist amulets, considering they aren't based on either religion (neither exists in the FFVII world, after all). Not to mention using "omamori" is totally clueless to the player; there isn't a thing lost when you translate it to amulet, as there aren't real pictures in game other than an extra disk nobody ever bothered to check (and even in that case people would still understand it's a japanese amulet, it's not rocket science). Leaving omamori is just like leaving Barret's "Cloud-san!", no more no less. Plus, they're usually called amulets anyways and the reference would still make sense with a non japophile term.
Think about it. If the executable listed filenames, the console would have to seek the file every time a resource was called. On a CD-ROM, that would be immensely slow. Direct block addresses are much faster.That's quite far for the real reason why some games don't use TOC filenames (libraries would still cache TOC data in order to locate files in an efficient manner, so it's not a matter of speed). PlayStation games do so because libcd is bugged and cannot access directory records longer than one sector, causing all the data in the extended sectors to be totally invisible to the system. With direct LBA+size references you can overcome this limitation and access very large directory records.
Why would a kernel cause memory alignment issues?Because of the 16 bit pointers in each text section.
Does the game require uncompressed kernel data to include alignment padding?Yes, it's gonna make the hardware crash otherwise.