I find that I don't get a replay of an entire race (I have been practicing
passing so I have all 33 cars turned on). I presume this is because I have
only 8 MB memory? I get about 12-14 minutes of replay with all cars turned
on at New Hampshire. How much memory do I need to get a full replay at, say
Michigan?
Alternatively, I suppose I can escape in the middle and save things out,
but that's a pain.
---
Brian Wong Product Marketing Engineering
415-336-0082 Palo Alto, CA 94303
Quoted text (8 lines)
>Engineering) >Subject: Replays >Date: 12 Sep 1994 19:34:21 GMT >I find that I don't get a replay of an entire race (I have been practicing >passing so I have all 33 cars turned on). I presume this is because I have >only 8 MB memory? I get about 12-14 minutes of replay with all cars turned >on at New Hampshire. How much memory do I need to get a full replay at, say >Michigan?|> I find that I don't get a replay of an entire race (I have been practicing
|> passing so I have all 33 cars turned on). I presume this is because I have
|> only 8 MB memory? I get about 12-14 minutes of replay with all cars turned
|> on at New Hampshire. How much memory do I need to get a full replay at, say
|> Michigan?
The amount of memory required for replays is highly dependent on how much dirt
and smoke gets generated. I've seen replay files where more than 3/4 of the
file is associated with dirt and smoke (and that didn't require running in the
dirt very much).
Here is a formula for the size of a replay file assuming you have no dirt, smoke
or crash sounds.
File size = 16 + ( ( 7 + ( 10 * NumCars ) ) * 15 * seconds )
The File size is in bytes.
Basically, there is a six*** byte header, 15 records per second with each
record having 7 bytes of fixed overhead and 10 bytes per car. The smoke and
dirt can easily add several hundred bytes PER RECORD.
--
Mike Corrigan
