Is it possible to disable this rescaling algorithm for V6 game other than Infocom’s games?
Not at present, no.
To expand that answer a bit, the simple rescale used for Infocom’s V6 games generally doesn’t produce good results, except on 8/16-bit style pixel art. What I’d generally imagined people would do with the ‘Reso’ chunk is provide artwork that is larger than the display, so that it gets scaled down, not up, to the required size, which generally produces much better results.
It’s true that I wanted to use it in a way that doesn’t make much sense, and the result wasn’t very good indeed. Thank you.
Another small update to Windows Frotz, which is now at version 1.22:
-
There is a flaw in the Infocom game Arthur: if the screen is too wide, then the game corrupts its internal state. As a result, Frotz tries to limit the initial size of its window when running Arthur to prevent this.
-
Font substitution, which attempts to find font characters in other fonts when the characters are not in the current font, has been turned off for fixed-width fonts, as it caused more problems than it solved.
-
The print_table opcode now interprets the string passed to it as ZSCII, rather than ASCII.
The new version is available as ever from:
https://ifarchive.org/indexes/if-archive/infocom/interpreters/frotz/
https://github.com/DavidKinder/Windows-Frotz/releases
2 Likes
For 2022, a small update to Windows Frotz, version 1.23:
If the number of columns or rows in the window is greater than 255, the appropriate field in the Z-Machine header is set to 255, rather than the actual value modulo 256.
The new version is available as ever from:
https://ifarchive.org/indexes/if-archive/infocom/interpreters/frotz/
https://github.com/DavidKinder/Windows-Frotz/releases
2 Likes