Differences between saving during endurance races or not.

  • Thread starter Thread starter Track_Veteran
  • 5 comments
  • 1,058 views
Messages
223
Messages
mungusCREEP
I didn't locate any search results in regards to this topic.
I noticed some differences between racing a continous endurance event and racing an endurance event and saving in the middle of it.

1. Any damage to the car is reset after loading up your save.
2. Any dirt accumulation is reset after loading your save.
3. Any track obstacles like cones are reset after loading your save.
4. Your fastest lap is changed to the lap previous to your current save state.
For instance: your fastest lap is on lap #20. You save the race on lap 50. Your fastest lap will be changed to lap #49 instead of #20.


Has anyone noticed anything else?
 
I had to wreck my car all over again, and then beat my best lap again so it showed the right lap I got it on. :p
 
Small things but also resets you driving position and my custom playlist starts all over with the same song every time which I would expect that last one since it does every time you reload the game.

I didnt have this issue with the LeMan track but when I loaded the Nurburgring race today its now playing the GT5 music not my custom list. It was playing my custom list before hand so not sure what happend
 
Since damage doesn't have an actual effect in A-Spec offline races yet, it makes sense that it wouldn't save that deformation. Unnecessary data to save. Likewise with dirt or track cones. The fastest lap is probably set up to avoid any potential glitches from an improperly saved time. Don't know how the game handles fast-lap tracking, but if it somehow saved your fast lap as occurring on a later lap than you actually are (say you're on lap 60, but for some reason it loaded your fast lap as lap 70), then something might happen. Better safe than glitchy.

As for the playlist, since that's saved on your playstation and is irrelevant to the game, I'm sure that's just as much glitch prevention as well. The playlist updates automatically as songs are added or removed from your harddrive, so by not saving which song you're on and instead merely queuing up Playlist.NextSong(), it doesn't have to worry about trying to load a song that isn't there. Again, better safe than glitchy.
 
I've noticed the following in addition to what's already been raised:

1: You can no longer watch/save a replay
2: The lap-time for the in-lap is slightly different than what it would've been had you not suspended (by a few hundreths - 0.010's)
3: Not sure if this is the case or not, but I'm not sure if suspending 'often' reduces the possibility of the weather changing (for better or worse)
4: Suspending can cause the AI to follow a different strategy for what they were about to do, or could result in different outcomes for AI (AI spins etc). E.g. I suspended a race, saved and exited. I re-loaded and within 2 mins had to lap the McLaren F1 (NRing 24h). A couple more laps and then I suffered a power-cut. On re-loading, and re-starting from the last save point, the McLaren F1 was no longer ahead to be lapped (I haven't yet worked out whether he just didn't pass the pit, whether he pitted with me or whether he was much further up the road)
 
Back