#902 closed defect (invalid)
Slow draw on map/detail screens
| Reported by: | SF/bagobones | Owned by: | Kirben |
|---|---|---|---|
| Priority: | normal | Component: | Engine: SCUMM |
| Version: | Keywords: | ||
| Cc: | Game: | Sam and Max |
Description
In Sam & Max when new items are added to the map the appear VERY SLOWLY.
In Fate of Atlantis When detailed screens come up that transition from one to another such as at the beginning when the artifact is opened they draw very slowly.
Athlon 1.1 Ghz 512MB Ram
SCUMM VM 0.4.1
Ticket imported from: #756432. Ticket imported from: bugs/902.
Change History (7)
comment:1 by , 21 years ago
comment:2 by , 21 years ago
I agree with erik. The fades are in normal speed on my G3/500 and G4/400 machines, BTW (so I figure an Athlon 1.1 Ghz shouldn't have troubles.
comment:3 by , 21 years ago
| Status: | new → pending |
|---|
comment:4 by , 21 years ago
Sorry, I found the problem. There was a hidden background task hogging my CPU. Works fine now.
comment:5 by , 21 years ago
| Status: | pending → closed |
|---|
comment:6 by , 15 years ago
| Owner: | set to |
|---|---|
| Resolution: | → invalid |
comment:7 by , 6 years ago
| Component: | --Unset-- → Engine: SCUMM |
|---|---|
| Game: | → Sam and Max |
Note:
See TracTickets
for help on using tickets.
How slow is "very slowly"? There is a deliberate "dissolve" effect, so it isn't instantaneous if that's what you mean, but if it's taking more than a second something's seriously wrong. It shouldn't take much more time than the other transition effects, e.g. the "iris" effect when going from one room to another in some of the games.
In the case of Fate of Atlantis, I'm sure it was there in the original as well because I can see it when I run the original interpreter in DOSBox. (Last time I checked it wouldn't run Sam & Max, so I can't try that one.)
Of course, running it on DOSBox is probably the equivalent of running it on a 286 or 386. On modern hardware, the dissolve is so fast you won't even see it in the original interpreter. ScummVM deliberately tries to do it in constant time, regardless of CPU speed, since that was probably the original intention.