The above video goes away if you are a member and logged in, so log in now!
HD Loader Timestamp Problem
HD Loader Timestamp Problem –
Does anyone know how to fix/patch the timestamp problem with the HD Loader? I have a feeling it may be the cause of some incompatible games. Any ideas?
I think there isn't any fix for this. I noticed that it's caused to "old" games like SH2,ICO,Contra and not new ones like Spiderman2, GT4P and others...
i get this also with some new games for example FFX2 for me does the same problem and star ocean don't do this problem so it vary by game to game
Am I missing something important ?
What timestamp ? Where ?
And why is it a problem ?
Best regards: dlanor
do you know on memory card the ps2 store also the date when a save was saved? with hdloader and some games happen that this date is messed up (ie: 31 october 2000 when we are in the 2004)
some games can have problems (rarely) and it's a bit annoying having the last save showed like the earlier
I see. I thought you meant some timestamp on the HDD, which should matter very little
as the games never see that stuff. But on the MC it does matter more, as it will affect
which save gets to be selected by default in the in-game browsers of many games.
But are you sure that the bug is caused by HDLoader and never strikes without it ?
It's very odd if HDLoader affects data read from the real-time clock.
Best regards: dlanor
yes games that i played from a year before hdloader (from when i have the mod) i don't have any problem. when i use hdloader with some of these games all the times it write the wrong date, hour (for example these are the hours 00:00:00) for some games this don't happen, but in any case all the games from dvd don't do anything like what hdloader do to the saves
From what I've experienced, HDLoader can't read data from the real-time clock in at least 2 games. I have the japanese version of star ocean dc installed and it is playable except that the enemies don't drop any random items after battles; my guess is that the luck factor affecting item drop is based on the system clock. The other is wild arms 3 where the giant clock in one of the guardian dungeons don't show the correct time and you can't talk to Armengard, an npc which says different things on different days depending on the system clock. It didn't break the games, just annoying.
It could be because the cdvd-library has commands to read the system time and while HDL patches this library to use HDD as the media the commands for the time are discarded. Propably those games that can still handle time are using different means to read it.
--- Signatures are just lame excuse to waste bandwidth ---
I have tested this for a while now, and found that many games are affected by it, though some are not. For example, all my Squaresoft games are affected, whereas the ones from Nippon-Ichi have no problem at all. This makes it very likely that there is some difference in the development libs of the various game companies, which causes this difference.
Your report increases the urgency of the matter, as it's no longer a case of losing only the correct dating of game saves. Instead it can also affect gameplay, possibly to the extent of making some games impossible to complete, or at least malfunction in serious ways, both as you describe and in other ways.
eg.1: Minigame timeouts becoming eternal , removing challenge
eg.2: Clock-based randomization yielding constant repitition of events
eg.3: Clock-based tasks/delays locking up, preventing completion
These possibilities give a high priority to finding a fix for this bug.
(It is no longer a 'feature' but a definite BUG.)
That is my conclusion too, so the question is whether or not we can modify that lib, somehow, as you did for the 48-bit LBA patches etc. We need to know where to 'hook' in the functions, and we need some place in the code for the new functions to reside. This will probably require a master at 'minimalist' programming, space-optimizing the code like crazy...
Originally Posted by Zer0-X
Btw: This inability to access the real-time clock correctly may also be responsible for the incompatibility of some games with HDLoader, causing them to lock up on launching.
All it would take is for that program to have a clock-based delay loop in part of its initialization code. If the 'clock' access gives the same faulty data each time (which the bug does), then such a delay loop will lock up for ever.
We can't know that this is happening of course, so we just blame it on some IRX driver conflict (or whatever) and try to live without that game on HD. And of course, that explanation may be true for some of the cases too, but I no longer believe that it is true for all of them. Some of the 'incompatible' games are probably just locking up in eternal delay loops, due to this clock access bug.
Best regards: dlanor
PS: The faulty dates on my game saves are always the same:
--- "30/12/1999 16:00:00"
--- This does NOT match what some others have described, but that may
--- be due to BIOS standards differing between PS2 versions and regions.