Vodhin's Big Idea

[Vodhin]

Hi all! There has been a lot of great scenery created lately and it seems that a whole gammut of new scenery makers are starting to get their feet wet. This is a great thing to help keep RCT3 popular, even as we approach the 2 year birthday of the game. Not many other games achieve this, ya know...

A while back, Potter began a campaign to try to set some standards for RCT3 custom scenery among other things. It didn't exactly take off, as I believe that it was too soon and more ambitious than need be.

I however, do agree that it might be better if custom scenery making had a few standards behind them. These are in no way rules, but helpful tips for all our newbies and even our veterans.

We really don't need to worry about much at the moment, but in the future we might see a huge, hard to figure out problem: conflicting file names. RCT3 scans its directories for usable files upon loading, and even though your theme might be named different, if you have one file that happens to be the same name as another, there probably will be problems. Imagine what might happen if a player downloads three or more sets that just happen to each have a "fish01.ovl" included...

My Big Idea involves Belgabor's improvements to Jonwil's importer, and may save us all from unwanted errors that stem from such a simple oversite. It also introduces the ability to share your unfinished work with others, in case you need help.

My Big Idea is simple enough, and can be implemented without any special programming. Of course, if Belgabor can hard code these options into his latest importer versions, then it will be even easier. So here are my suggestions for custom scenery makers both new and old:


A standard "Starting Folder" off the Root Drive C
A Prefix of your screenname (or something unique) added to all your files


This can be done now. This can help identify who created what. This can make your unfinished files shareable. Here's how:

1: Allways name your OVL files starting with your intiials or screename.

2: Make a default folder for your stuff that's the same as what would be on other's computers:

Open your "My Computer" icon and "Drive C" and make a new folder called "RCT3Models". For each new theme or set that you make, start a new subfolder (useing the set's name is best). It may be a bit messy, but have all your 3D model files, biturn'd files, and importer files in that one sub-folder for each set. Now you can share that set with other who have the same "C:\RCT3Models" starting point, creating the ability for group projects, or just sharing unfinished sets (either for help or just if you don't want to finish it yourself).

If Belgabor is up to the task, I ask that he create an (optional) mini-data registry: some way for the importer to remember a "File Prefix Name" that you choose and automatically adds it to any new OVL filename.

If he is also up to the task, I ask that he create an option to use default paths when saving ASE, theme, scenery, SID, and OVL files. Your original 3D model could be wherever you want, but the default folder for the aforesaid files would be C:\RCT3Models\[themename]. This default could be changed by the user if they wanted to. I've asked and he seems to know enough about the windows filesystem to be able to pull this off.

The filename prefix idea could be expanded to include an option to actually register your prefix on a server (which I'm willing to maintain) in a simple file that can be either downloaded into your copy of the importer or just have your entry checked against. This would be an option chosen by the user if they wished to double check. If the name prefix isn't at all viable for some reason, then at least a date-time prefix would be usefull for preventing duplicate filenames- for if two identicaly named files were created at the exact time, then we should all just give up and go find a corner to hide in...

So what say you all? Do these sound like a good idea? do you have any ideas to add to this or know a better way?

[marnetmar]

I always use the mnm prefix for my stuff, hopefully everyone else will use some sort of naming system & not just use generic names for their custom scenery.

[Belgabor]

I hadn't known that same filename in different dirs causes problems. I will keep all of this in mind for TNG. I will also put the prefix into the modified old importer.
Some of the problems will disappear automatically in TNG as it will certainly store filenames with paths relative to the theme file. Therefore if you keep all files in one dir (or subdirs) you can distribute the source without the necessity for a common directory like "c:\rct3models".

[CoasterSim.Fan]

Good ideas I know I always start off my files with my user name abbreviation and then set abbreviation. But then any way I really wonder if any one can figure out how I name m objects (its defiantly unique).

As for a cent folder it’s a good idea epically for grope products but not sure if that would work for every on I know I keep all my scenery on a septet hard drive (I have two internal hard drives) and I believe I am not the only one how does this.

[computertech82]

Another idea would be the creation of the objects itself. I'm from the old 2d graphics world, that should be used more often. I've noticed people making very complex structure items, but complain about it cannot be viewed except when you are close to the object. The solution should be simple really... use a extremely simple object, and use 2d graphics to give it an illusion of a more complex structure. Windows would be a good example. Many are made by very complex shapes and cannot be seen in a distance in the game. Making it a simple square or rectangle and giving it a complex 2d graphic (illusion) would allow it to be viewed from a much further distance.
I know the atari pieces are actually 2 pieces (one for up close and one for distance), but creating a simple structure item, could give it a longer range to still be viewed. Would be really nice if someone could finally create the library files so only one image is loaded for multiple items, instead of loading the image over and over for each item used.

[tedwardxp]

I already planned to make all my themes using the Prefix , TXP. I will start modifying the file names of the individual objects too.
Its a good thing you mentioned this. I am working on some planets on a larger scale then the ones JCat already has made. I am not sure what file names he is using but I have been simply using Mars.ovl, Earth.ovl and so on. I will go back and modify them.

About the 'C:/rtc3models' folder; does it really make a difference where the rtc3models folder is as long as the directory structure within it is consistent?
The directory structure I have developed starts in My Documents and looks a little like this;
+ RTC3CustomScenery
.... - Theme 1
.... - Theme 2
.... + Theme 3
...........theme name.thm
...........theme name icon texture map.png
........ - Model 1 folder
........ - Model 2 folder
........ + Model 3 folder
...............model name.ms3d
...............model name texture map.bmp
...............model name.ase
...............model name.scn
...............model name.ovl

The model folder may contain more then one version of each model, placed into a subfolder with a [model_name_version_#.#. ms3d] and copy of any texture maps.

Anyways, as I am new at this don't hesitate to tell me I make no sense at all :noob:

[StarRngr4.0]

Very good idea Vohd. I had something similar happen to me, where non original filenames messed up someone else's creations.

If I ever do rct3, I'll be using an SR4 prefix...

[Der Freak 00]

A standard "Starting Folder" off the Root Drive C


But it should be possible to change this directory (I, for example, have all custom scenery on "D:/JonWils SceneryImporter", since my C: Partition is NTFS (=>can't write on it from linux), D: is FAT32).

[Belgabor]

Currently it would be necessary to have a common folder (including drive) to make exchange of theme sources convenient, as jonwils importer stores absolute paths in the thm file. Depending on the theme size it can be a huge hassle to move a theme (I know what I'm talking about since I moved my Snowset from C to F for the reason Der Freak 00 mentioned).

[wabigbear]

While I am not a scenery designer, this is a great idea Vodin. I remember all the problems that would occasionally crop up in RCT2 with custom scenery sharing the same file name and the fact that many parks were ruined.

[Vodhin]

I guess that I should clarify the reasoning behind the standard starting directory: It isn't so much the model files, but the Scenry file (SCN) that the importer uses to assemble the different pieces into the OVL, and the theme file that assembles the OVLs into the theme. A standard directory for pieces, while not vital in general, would alow other scenery makers to be able to share or finish a set.

[marnetmar]

I don't see a big need for this actually, not that many people are "sharing" themes & if they did, they only have to make sure to send all the files to the other person & everything will be fine.

[Belgabor]

I don't see a big need for this actually, not that many people are "sharing" themes & if they did, they only have to make sure to send all the files to the other person & everything will be fine.

Actually it probably won't be ok. Ever tried to move a complete theme? The full paths in every file make this a nightmare... I'm not even sure if you can load scn files at all if you moved the ase...

@Vodhin: for TNG, to what should the prefix be applied? Is the theme directory and object ovl flies enough or do the subdirectories also need it?