Revision as of 17:13, 4 September 2008

VIEW resources are the candidate Myst card representations, as they seem to glue other resources together like WDIB and MSND. In particular they seem to describe what to show on screen and what sound to play.

Original hints by Petroff Heroj.

Basic Format

Conditional Images

• u0 is unknown.
• image_count is the amount of images to check against.

• conditional_images is a count of these records:

• var is the variable to check against.
• num_states is the number of image id's.

Then, there are num_states unsigned shorts representing an image id. The variable is the index of what to use in the table.

Main Segment

Following that, is this structure:

• main_image is the main image to show on the screen. (Kind of like the default case).
• sound is the sound id to play. If it is less than 0, it acts like a flag to pause, continue sound (-1?), or stop the current sound (what means what still needs to be checked).
• flags appears to be flags.

Unknown Segment

TODO: I haven't completely figured this out. Petroff's guess was that it preloaded resources. However, it doesn't make sense that it is like that. It starts with an unsigned short representing the count. Then, following that is an unsigned short (which he believed to be the resource type to load). If it was 3 then there would be an array of WDIB's (an array of unsigned shorts, starting with a count and an unknown -- each unsigned shorts). A 1 would mean a single WDIB, a 2 would mean a single MSND (each represented by an unsigned short).

More Unknown

Following that is four unsigned shorts. Petroff's guess was that they represented RLST, HINT, EXIT, and INIT respectively. But, that doesn't line up with the resources that exist in the files. More likely, those resources are dependent upon the card id.

Old Case Studies

image name and sub-images (akin to Riven PLSTs)

• I think 3004 is the name of a sub-image (small image to be placed in another) of 3003 here.