It is necessary to have the “building_textures” folder in the same folder as the fsCP airport files for the cultivation to show. The Elevation folder works best if it is directly below either Scenery folder and seems to be temperamental about having sub-folders. I also like to keep the fsCP airports in a totally separate folder due to the number of updates that I download. IN SHORT: it's totally unclear to me what parts of the folder structure are mandatory and what parts aren't.Īnd to keep you confused, all of the new Norway scenery could be in your personal “scenery” folder, not necessarily in the “add on” folder. Straight into 'places'? Or in that 'no' folder'? Should I keep or remove the other tsc and toc files? Q: I downloaded cultivation from IZ0JUB and have no clue where to put his tsc and toc file. In 'no' (the one directly in 'places') there is a folder called 10_lofoten: in that folder there is a folder called 'building_textures', one tsc file and two toc files. Q: are the subfolders 'fscloudport' and 'no' really needed or could I just as well put 'enlk' and 'ensh' straight into 'places'? In 'fscloudport' there is yet another folder called 'no' and within that one there are folders for 'enlk' and 'ensh'. In 'places' I have a folder called 'fscloudport' and 'no'. Q: or to take it even further: could I just as well put all files within those 4 folders straight into the 'images' folder? Q: is that folder 'no' really needed or could I as well put those 4 folders straight into 'images'? In 'elevation' I put all the Winther mesh files: no problem there. In that folder there are three folders: 'elevation', 'images' and 'places' I created the folder Documents > Aerofly FS 2 > addons > Norway I am trying to create a addon folder specifically for Hartman's Lofoten. A wiki would be great, I'm willing to help compile all the info and create a document for the wiki. I've seen some info here and there, some conflicting info, some dated info which we don't know if still true or not. Also so that we know what to expect of files or issues, where to look for an elevation issue for example etc.Ī structural graphic with colors (like red for mandatory structure, green for optional, etc.) would probably be the simplest and clearest. So that we can double check things are in the right place and of the right format. What content (type and file extension type) is expected in each folder. Which one are flexible (like I can have a USA folder and subfolders for each state, etc.) What folders are expected (scenery, elevation, image, aircraft, TMC, TMD, etc.), where (which one are not supposed to be interfered with) Structure of all three folders: C: game folder, C: game add-on folder User expansion folder At minima it would be nice to have a clear document (wiki) on the structure of folders for FS2. Last but not least, have you considered a de-activating prefix as proposed by Lenidcamper? something like : To remove or deactivate a scenery, you'll have to search for bits and pieces in various sub directories.Ĭould you please provide a quick guideline of possible/allowed structure and syntaxes? So far I was only able to replicate the SCENERY structure of the default game folder, which spreads constitutive parts of various sceneries into common folders, leading to a quickly growing mess : How can we successfully declare it on the external user-defined folder? What are the allowed structures and syntaxes? The same ADDON structure works well also in the Steam Library, which is not intended for home-made or manually installed sceneries. The ADDON structure works well on the default game folder, but it's on the C: drive which is to be avoided. What are now the allowed folder structures in the external user-defined folder?Īs already stated the aim is to replicate the ADDON structure, which is optimal for scenery management as illustrated below : all elements of a same scenery are gathered in a specific folder and substructure:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |