RCT Discussion / What spacek531 looks for in official title sequence candidate parks

  • spacek531%s's Photo

    Hello all,

     

    This thread is something I should have published a long time ago, but here it is finally: the criteria that I use to determine which parks to include in the official title sequence. There's a huge number of things I take into account when actually making the title sequence, but this thread is all about the parks featured in official title sequences. The most important criteria are presented in descending order of importance:

     

    1. Park size: Shots should not show any blacktile when viewed on a 1920x1080 canvas.

     

    This means that for any particular view of park in the title sequence, all pixels are part of the environment or part of the subject. This does not mean cordoning is disallowed, as The Bayou and Nin's SFOT have cordoning, and Nin's SFOT has a lot of it, but it means that potential subject matter by the edges must be passed over.

     

    There is no magic single answer for how large a park should be; the required size is completely dependent on potential subject matter:

     

    Attached Image: example pic 3.png

    Cordoning is relaxed enough for the subject

     

    Attached Image: example pic 2.png

    Cordoning is too tight for the subject

     

    2. No custom objects: Parks shall not have custom objects nor expansion pack objects.

     

    There are a few reasons for this:

     

     - The most pertinent to title sequences is that there are a limited set of vanilla objects while there are nigh infinite custom ones. Objects take time to load and unload, which creates freeze frames while the objects are loaded. Objects that are the same between parks are free, so no time is spent loading or unloading them. By limiting the objects to vanilla objects only, the number of objects that repeat between parks can increase, and in fact in the 1.2 sequence all parks share identical object selections.

     

     - Expansion pack objects are not allowed. Sorry Julow! Not everyone owns the expansion packs, and they're ugly to boot. Not much to say on this.

     

     - OpenRCT2 has not been given permission to distribute custom objects. I know NE has been doing this for years but my understanding is that Ted John does not want to because even if objects are released with permissive licenses most of them have been lost to the sands of time.

     

     - Objects have to be packed or distributed in some fashion with every download. These inflate filesize a considerable amount and bandwidth costs money. I am not hosting the sequence or in charge of hosting the sequence, but I find it only courteous to try to limit the impact of downloading the sequences on the host.

     

    3. Style: Parks should have a decently pleasing style to them that is above the level of Chris Sawyer's RCT1 parks.

     

    The only park I can think of that has this issue on the site (and meets the criteria above) is Six Flags Hoosier Station. I'm not a fan of its grid-based layout, its foliage, or its monochrome architecture.

     

    Parks should be peeped. Guests add life to parks and many look unusual without them. The degree of peeping depends on the purpose of the park in the sequence.

     

    4. Framerate: Parks should have reasonable framerate when viewed on a 1920x1080 canvas.

     

    This isn't a huge issue because OpenRCT2 has gotten a number of optimizations over RCT2 (as far as I know). Shots should get 30 frames per second or better when viewed on a 1920x1080 canvas. For reference, Nin's SFOT gets 32 frames per second consistently around the water coaster.

     

     

    Hopefully this post helps create a better understanding of what I am looking for in title sequence parks. This is not an end-all be-all list, but it is very important and are the primary qualities I look for in title sequence candidate parks.

  • Cocoa%s's Photo

    awesome work dude

Tags

  • No Tags

Members Reading