Those of you who have been following the comments on the Ultima 9 in Widescreen Resolutions article may have noticed Iceblade, from the Forgotten World team, contributing to the very fruitful discussion taking place there. Indeed, he and Kirinn made some very interesting discoveries about how Ultima 9 handles field-of-view, and about how it displays the in-game journal and other books to screen.

Because, you see…by default, on higher-resolution monitors, the journal and other books scale up too much, and all but block out the entirety of the interface. What Kirinn and Iceblade worked out was a way to correct this. Like so:

It was delightful to see a fruitful, lengthy comments thread here at the Codex again; these were fairly commonplace at Old Aiera, but haven’t been quite as prevalent here. Iceblade, too, seems to have been quite positively affected by the event; he recently posted a news update to the long-dormant Forgotten World website, announcing that work had resumed on that project:

…I did my rewriting/reorganizing of the activity editor back in March and it is effectively finished apart from a bit of polishing and maybe a minor side feature or two.

More recently, I’ve attempted to do some reverse engineering with the executable and I helped Kirinn a bit with widescreen corrections. We ended up finding a few bytes in the executable (largely by coincidence) that govern the scale of all book GUMPs in the game. Pretty useful; especially for those that find the spellbook overlaps with the toolbar. For more details, check out the comments section below this post at the Codex.

Unfortunately, I’ve not had much luck in finding other useful bytes; however, I did find out that savegames store snapshots of various on-going in-game processes. These are largely spells, animation, and movement controller processes as well as a few special trigger processes like fade-in. This might prove somewhat useful at some point, but the processes are largely about stuff we don’t intend to change. I’ll probably do some more executable reverse engineering over the next few months.

On the programming front, I’m slowly advancing the triggers editor; reusing much of my GUI interface and internal code from the activity editor. Unfortunately, filling in the necessary details for 150 trigger commands will be quite time consuming even with the modular code I wrote for the activity editor, so it will be a little while before I’ll have more news about this editor.

And finally, I’ve decided to start work on the types editor. The groundwork for this will help with the trigger editor’s target type field (a parameter that selects the trigger target based on Usecode ID) by allowing me to quickly generate a drop-down list via the types database and typename flex file. At this point, I have created the code to read in and write out the types database. Typename is next on my list; followed by an editor for these two files.

He also suggests that we might possibly expect to hear some news about Beautiful Britannia next month.