Layout Directory Structure

[slickturtle_gamer]

Can someone provide a breakdown of the sub-directories contianed in a layout? I have seen images, Sound, Themes, and Video. Each of those have folders which contain specific items. I am trying to understand how attract mode reads and loads from those directories. I assumed the Wiki would have this, but I cannot seem to track it down. Troubleshooting is a nightmare without this information.

I am working with a Hyperspin layout.

Any help appreciated.

[bundangdon]

I'm far from being an expert on this subject but I have been playing around with some of the layouts in attractmode and customized them to my own personal preference. The subdirectories in the layout folders all have various purposes, depending on how the (original) designer put the layout together. For example, in my layout .nut file, I have this code:
//TV Background
local bg = fe.add_image("tv.png", flw*0.18, flh*0.270, flw*0.34, flh*0.470);

that means the "tv.png" is in the same layout folder (no subfolder) but if I wanted to, I could write the code like this

//TV Background
local bg = fe.add_image("images/tv.png", flw*0.18, flh*0.270, flw*0.34, flh*0.470);

In this case, the purpose and design is exactly the same, but that "tv.png" is not in the layout folder but it's now in a subfolder within it titled "images" which has been done to just to keep things a little more organized. This is a very very basic explanation but hope that it helps somehow

[slickturtle_gamer]

It does. I have a degree in Computer Science so I should be able to figure this out now that you explained the nut file controls relative paths and the directory structure is subject to the person who coded the layout. Appreciate the help.

[liquid8d]

AM doesn't have any requirements on folders in a layout folder. There doesn't need to be any at all, it can just be a layout.nut file. As mentioned, if you do decide to use folders, references to those files in the layout.nut are relative so fe.add_image("images/bg.png", 0, 0, fe.layout.width, fe.layout.height) - you can also specify a full path, something like fe.script_dir + "images/bg.png" could be used.

Hyperspin, however, did have specific folders it used if I recall correctly - so for AM to read the Hyperspin layout, they will probably need to be in the same folders as they were for that frontend.