#4328 closed defect (wontfix)
WinCE: Simon1: Scene outfading very slow on VGA device
| Reported by: | SF/prontector | Owned by: | SF/knakos |
|---|---|---|---|
| Priority: | normal | Component: | Engine: AGOS |
| Version: | Keywords: | ||
| Cc: | Game: | Simon the Sorcerer 1 |
Description
scummvm-0.13.1-WinCE Simon The Sorcerer 1 Talkie German Windows Mobile 6.1 Eten Glofiish DX900
When using any of the 2x scaling options on a VGA device it takes up to 5 seconds for a scene to fade out (at the end of a cut scene or when leaving a level area) Tried sound_thread_priority=0, didn't help.
Ticket imported from: #2786637. Ticket imported from: bugs/4328.
Change History (8)
comment:1 by , 16 years ago
| Owner: | set to |
|---|---|
| Summary: | Scene outfading very slow on VGA → WinCE: Simon1: Scene outfading very slow on VGA device |
comment:2 by , 16 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:3 by , 16 years ago
comment:5 by , 16 years ago
I'd hate to do that: modify the source code to alter the faithful working mode to accomodate for something "slower" devices cannot handle.
Anyway, the real fix here would be to identify why agos is more demanding than other engines, and optimize it (if possible) instead of hacking away at the code.
comment:7 by , 16 years ago
Yeah, I did back then. Noone had reported any such thing, iirc, so I looked a bit into it with no results worth mentioning.
In the course of fixing an alignment bug later in agos, I snooped around for any calls which might hinder performance and had concluded with no results as well.
I may reiterate in the future :-)
comment:8 by , 15 years ago
I committed a new ARM version of the MameAdvx2 scaler the other day. Try a new build that includes this, and hopefully you should find it a lot faster.
Right, the AGOS engine is a little slower to execute in general. This is so for a long time, at least from when I took over the ce port. I had looked into this fact back then, but couldn't find anything that would seem to slow down the engine. So I guess we're stuck with this, as I don't have time to look at this.
Good idea about the priority though :-)
Thanks for the report, Kostas