[FF7PC-98] The Big Bug List (OLD)

  • Thread starter Thread starter White Wind
  • Start date Start date
Status
Not open for further replies.
The bug that causes the enemy to show as normal for a single frame right after death seems to be fixed by nopping function at 5BBEBD. What this function does I don't know... since nopping appears to have no ill effects other than fixing this issue.  But I am sure there will be some sort of problem.
Click to expand...
Try reviving the dead enemy with Angel Whisper and that function nopped. I'll bet that something will look weird.
 
Seems to be ok.

Although there are several other smaller issues to fix (unrelated to that function).  For some reason, the screen shakes at the start of Bahamut Zero while the Earth is showing.  Weird.


So what's hot and what's not?

Hot
1. All flickering seems to be gone, apart from Bahamut Zero, which still has an issue.
2. Any hanging bugs that happened due to older method are gone too.
3. This method may be easily adapted to allow for interpolation in choice areas, like model movement.
4. Tifa's reels, battle numbers, boss and enemy death speed, and various other issues are fixed.
5. All death animations corrected.

Not
1. Still working on shrinking / Growing being 4x too fast when using Minimum.  This shouldn't be too difficult to fix and I have the function locked down. The highest value is 32767 - values higher will make the model go the other direction and sink into the ground head first. Now fixed.

2. There may be some nasty surprises not yet discovered.

3. The fade-in needs some work. Again shouldn't be too much of an issue, since I have the functions (Kramner had the main one located already). Tbh it was broken in the original PC release too.

4. Bahamut Zero issue.

5. One enemy death type is still too fast. NFITC1 helped fix.
 
Last edited:
You were right that sound effects in battle are always centred, Kaldarasha.  It's by design. At 430D08, 40(centre) is forced.

Edit.  Seems it depends.

Like at call 00745160.  Still centred, but that one can take any value.
 
Last edited:
I guess they did this way to use the stereo sound files for the summons without losing the stereo pan of them. Either way for me are mono calculated sound effects better than wrong stereo calculated ones. However, I have no hopes that this can be fixed easily.
 
OK so melting bug and minimum bug are fixed. So is Cait Sith's reels playing the sound effect after menu is cancelled.  Seems other menus initiate a "stop effects" function.  I've just added a "play effect 0 on looped effect" on the cancel.
 
To fix melting issue
5BC39D = 90 90 90 90 90 90 90

To fix minimum issue
42C112 = 66 C7 80 7E 11 BE 00 00 00
This must actually be nopped or any part revived (like Hojo's monsters) will be 0 size.

Although, the X Y Z you found probably should be zeroed also.  But I didn't need to as the issue still went away with just the above.
 
Last edited:
To fix melting issue
5BC39D = 90 90 90 90 90 90 90
Click to expand...
What does that bit do that was cleared before you nopped the reassignment? Do you know?

[/quote]To fix minimum issue
42C112 = 66 C7 80 7E 11 BE 00 00 00
[/quote]

But this forces EVERY enemy to be minimized on death. That doesn't jive with Pollensalta and other bosses which can revive dead limbs/allies. Wouldn't those cause problems too?
 
I don't see any issue with what has changed?  They die the same way as they always did.  If minimized they just don't regrow on death. That function is only called on the last part of death - where it's already faded out. You can't see it with any of the deaths - only when minimum is active.

Not sure about the melting nop.  The change above is specific to the melting animation though, as that's the melting death function. I think it's simply the size of the model - It gets placed back to full size at that point (which is where melt has ended and the model is at its lowest 'melt size' - and about to disappear).

Actually, while we're at it - it should probably be the case that enemies stop moving when killed.  At the moment, they carry on even as they are fading out.  Looks v ridiculous with Midgardsormr.  Always thought it did on PSX too. But maybe it would look silly with enemies swinging a ball and so on.
 
Last edited:
I'm talking about enemy revival. If they melt and aren't returned to their original size then they'd be revived all weird. In practice it may be a non-issue, but I'm going to give it a try.
 
Enemy revival is itself a bug that needs plugging (angel whisper etc). It may be an issue with enemies that have their parts revived, though.  But I suspect it gets reset again on revival.  Keep me posted.

None of the normal parts that return to screen after death use the melt death iirc.

Edit.  It doesn't get reset on revival, so you have to nop the resize and not zero it.
 
Last edited:
{change key-held to key-press
6D8D3A = A1 E0 85 9A 00 25 00 01 00 00 90 90 90
6D94C2 = A1 E0 85 9A 00 83 E0 20 90 90
6DB39C = A1 E0 85 9A 00 83 E0 20 90 90

This changes the battle keys so that you cannot hold Action to continually attack - and stops the help menu flicking on and off repeatedly when holding select, which irritated the life out of me.

I had a look at Quake 3 issue with the bad texture, but this doesn't happen for me with Aali's driver.  Either it's caused by the option in Aali's driver not using more texture memory, or a similar issue with Steam version.  If Steam, it won't be getting fixed.
 
World Map colour is wrong. Additionally, Aali's driver messes up the markers (indicating where your chocobo etc. is) on the World Map...map. The markers are way too faint.

Here is an actual comparison between PSX and PC. Note, the colour in Battle / Menu / Field appears to be fine.  It's the World Map where this issue lies.

https://s18.postimg.org/gnd2lyc4p/world_map_colour.png

This isn't just a gamma problem. The colour/lighting itself is wrong. Most noticeable on the ranch model.

Aali:

The minimap markers being too faint is because of the whole alpha blending transparency issue which also affects the savepoints and other stuff. The issue is that the PC renderer has two different alpha values (vertex alpha, texture alpha) and the game doesn't specify which one to use (AFAIK), so sometimes the correct thing to do is to just use texture alpha, sometimes vertex alpha and sometimes the two should be combined to produce the correct result. The way it works now is correct most of the time but not always.

As for the world map color, lighting on the world map is already completely broken (shadows follow the rotation of the camera instead of being fixed in the world) but I would suggest looking at the world map textures to see if they match the colors on the screen. You could also check the textures from the PSX version to see if there's any difference.
Click to expand...
It definitely isn't the files.  The PC map files can be replaced by PSX straight off the disc... and no change.
 
Last edited:
I've fixed the marker issue in a different way. Just increase the colour for each marker...

Table starts: 0096DEF0

For example, 00 00 80 80  (main red marker) = 00 00 F0 F0

fixedmarker.jpg


I am gonna compare to PSX.

PSX:  https://s17.postimg.org/t8u332fr3/psxmarkers.jpg

#World map marker fix
96DEF0 = 00 00 F0 F0 00 D0 00 F0 D0 D0 00 F0 D0 D0 D0 F0 D0 00 D0 F0 00 D0 D0 F0 00
 
Last edited:
The Omnislash sound issue (where the sound effect fails to play as the beam arrives on the end of the sword) is fixed. So, too, will most/all errors of this nature be when I am done. For whatever reason Aali's driver / original game does not properly deal with certain functions the way it should.  But by creating my own sound replacement, the effect is called - and then played correctly.  The sound effect is not missing - and it is being called. It simply isn't initiating with the original game.

Also, sound effects will no longer play at all when the effect volume is 0. So no more silly rogue effects.

The music will v likely work better than with Aali's driver too soon.
 
Last edited:

Never picked up on it before.  Alarm music and ambient sfx in reactors etc are being told to play on every field load. (You can hear this clearly at 15:24) Either someone was meant to add code to stop repeated calls to a playing music being obeyed, or the script programmer made an error.  I will add the PSX functionality to the PC - and correct the field script.  The PC game, oddly, does not restart a sfx that is being played, but this will likely break other things.
 
Edit.  I was wrong.

The Submarine minigame does use the Hurry music for the story


55:17

However, there is another bug here.  The music fades out from 100 to 1 (at  0077D9D1)  in a rather long period of time (17 seconds).  I think some sort of cock-up has happened here. Either they meant the music to play and not fade out - or the music should be the water sound effect, like the Gold Saucer. I think it's the former. 

Code: [Select]
Code: 
push 00 { 0 }push 00 { 0 }push 00 { 0 }push 00 { 0 }push 00 { 0 }push 00 { 0 }push 00 { 0 }push 7F { 127 }push 000000C0call 00740D80
That will fix it.

It's also possible that they intended to fade it out to a higher volume, like 0x40 (half), rather than 1.
 
Last edited:
Finally making progress cleaning this up. Sega Chief has also joined the project to fix whatever he can.  Quite a lot of bugs have been fixed.
 
Status
Not open for further replies.
Back
Top