Difference between revisions of "Creating Large Worldspaces"

3,619 bytes added ,  22:25, 25 January 2011
→‎Ready to Go: More additions - Cake Method and edited notes into rules and methods.
imported>Bruneauinfo
imported>Bruneauinfo
(→‎Ready to Go: More additions - Cake Method and edited notes into rules and methods.)
Line 106: Line 106:
*A simple conversion to remember is 32 units equals a yard. So divide by 32 and multiply by three to covert CS units to feet.  
*A simple conversion to remember is 32 units equals a yard. So divide by 32 and multiply by three to covert CS units to feet.  


====Using the Heightmap Editor Part 1====
Before getting too specific on a good method for generating your landmass a number of important methods and notes are included below for review. Keeping these firmly in mind will help make your new world space creation happen as efficiently as possible. The following have taken several weeks of testing and trials to discover and were written here to save you a lot of time. Keeping these points in mind will help get your mod finished with the least amount of time and frustration.
=====The 4 Quad Rule=====
You should know by now the heightmap editor only shows 4 quads at a time. Experience has proven there is a reason for this - during heightmap generation you should only work on 4 quads at a time. If your world space will be larger than 4 quads blending between sets of quads will be necessary but will be done at a later point. The world space graphic you created should be used to plan your work so that you can match your heightmap elevations between these 4-quad work sessions. One way to do this is to take notes on edge elevations when your heightmap extends beyond the edge of the current workspace. This includes things like where rivers will meet up in bordering quads and where mountain ranges begin and end. Perfection is not required at this point as errors can easily be resolved at a later step. Try to balance the care you take in these early steps of landmass creation with the amount of convenience such care will provide when you make these corrections later. You can waste time trying to make it perfect at the start. But you can also waste time if you're sloppy and have to do a lot of work fixing things later.
=====Sharp Elevation Change Rule=====
The greatest number of errors (rips) on a texture are created in the hightmap editor where land is not properly blended '''before''' saving the texture. Any large, abrupt changes in elevation are prone to tearing. These are indicated by hard lines between two colors. There should be no hard lines left on your texture in the hightmap editor '''before''' you save it. Make sure all hard lines are blended with either the blending tool or the noise tool. Your finished work should look more like it was applied with a paint sprayer than a paint roller. A good exercise is to look at the Tamriel world space in the heightmap editor. When all is finished with your new world space they should share a lot of similarities. Much of that finished look is the result of using the noise tool. 


Save this .esp. You will probably want to name this .esp something similar to the name of the new world space.  Although this may seem a bit redundant, some aspects of the heightmap editor (notorious for being problematic as you probably know) don't work particularly well when working on a world space which has not been saved (it's a memory thing); saving the mod records the definition of the world space within the .esp, so it is more stable (or something). Now you can begin within the heightmap editor.
=====The Edge Rule=====


====Using the Heightmap Editor Part 1====
In reference to the above rule tears can be prevented at the exterior perimeter of your New World by blending the last few cells into the water rather than having the land just suddenly stop and drop off. Blending can be done with the blending tool or with the noise tool depending on the terrain type you want at these locations.
It is true that if your world space is 4 quads or less you can hide the edges by leaving a buffer between the edge of your quads and playable regions. However, when working on your world space with the landscape editor you will notice decreased performance as the Render Window tries to load terrain at the edges of your world where there are rips and other errors. Region generation will also produce errors at these locations. It is well worth your time to prevent and fix any errors that occur outside your playable world space. The best way to prevent these errors is to blend your edges in the heightmap editor. And when they do occur you should repair them with the landscape editor (more on this later).
 
=====Glitches in the CS=====
 
There is a known glitch in the heightmap editor where errors are created when you save your heightmap. A common location for errors to occur in the heightmap is at 0,0 as well as at the centers - like 32,32 -32,-32 64,64 etc. These errors can regenerate themselves repeatedly '''each time their heightmap area is saved'''. Correcting these errors will be described shortly. Just know this phenomenon happens and can not be prevented. Also understand it's a pretty minor thing to fix.
 
=====Cake Method=====


Below are some notes and methods to help make your new world space creation happen as efficiently as possible. The following took several weeks of testing and trials to discover and was written here to save you a lot of time. Keeping these points in mind will help get your mod finished with the least amount of time and frustration.
With a graphic representing your new world space in hand it's time to start creating the landmass. A safe and efficient way to build your landmass is to think of your terrain as a large traditional layered wedding cake. With this type of cake the layer on the bottom is the largest. As the cake rises higher the layers get smaller and smaller in area. The method is simple, straightforward, and gets the job done.


*During heightmap generation only work on 4 quads at a time. If your world space will be larger than 4 quads the blending between sets of quads can be done later. Still you should try your best to plan your work as you go so that you can match your heightmap elevations between 4-quad work sessions. Take notes on edge elevations if your heightmap will extend beyond the edge of a quad, where rivers will meet up in bordering quads, and where mountain ranges begin and end. Perfection is not required at this point as most errors can be resolved later. But the more care you take now the easier it will be to make these corrections later.  
Working on your first quad you start by using the terrain raising tool, set its size to 150, and raise a patch of terrain anywhere in your workspace to use as a sample palette. Holding the mouse button down for a couple seconds should generate a spectrum of colors representing various elevations. Some will recommend changing the hight definitions of these colors. This isn't necessary using the cake method. Instead of focusing on color you will be focused on the 'Z' elevation value.  


*The greatest number of errors (rips) on a texture are created in the hightmap editor where land is not properly blended before saving the texture. Any large, abrupt changes in elevation are prone to tearing. These are indicated by hard lines between two colors. There should be no hard lines left on your texture in the hightmap editor when you save it. Make sure all hard lines are blended with either the blending tool or the noise tool. Your finished work should look like it was applied with a paint sprayer.
What your're looking for at first is an elevation slightly higher than the water - 4500 units or so will work perfectly. Using the Eyedropper tool hover over the color spectrum you created. You'll see the 'Z' value start to move up and down as you pass over the spectrum of colors. You want to get something close to 4500 units plus or minus a couple hundred. It really doesn't matter.  


*Additionally, in reference to the above note tears can be prevented at the exterior perimeter of your New World by blending the last few cells into the water rather than having the land just suddenly stop and drop off. Blending can be done with the blending tool or with the noise tool depending on the terrain type you want at these locations.
Once you get an acceptable elevation with the Eyedropper you can use the Paintbrush to spray out a swatch of color. Just spray enough out so you can sample it. You want to make sure the sample matches the elevation you thought you selected. It will rarely match exactly. If it's way off use the Eyedropper and try again.  


*If your world space is 4 quads or less you may not need to worry too much about blending the perimeter and so can neglect the edges of your world space. The edges can be hidden by leaving a buffer of about 3 cells between the edge of your quads and playable regions. However, you should still take note you may want to come back and generate dummy terrain so your world will have LOD terrain extending into the distance beyond your created world space. Also, when working on your world space with the landscape editor you may notice decreased performance as the Render Window tries to load terrain at the edges of your world where there are rips and other errors. It might be worth your time to go ahead and at least fix any errors that occur outside your playable world space with the Landscape Editor. So to prevent these errors altogether just follow the previous bullet note and blend those edges in the Heightmap editor.  
Using the Flatten tool set to a size of 100 - 150, hover over the color swatch. Once you are sure the Flatten tool will utilize this elevation color use it to spread this color-elevation all over the four quad section. Only leave out areas where you intend to have bodies of water. If you have a specific size and shape for the body of water shrink the Flatten tool and work from both the water elevation as well as the first dry land elevation layer and sculpt the body of water and land until they are the shape you desire. If you plan on having 4-quad sections bordering this one you should shrink the Flatten tool diameter further and get the first elevation color as close to the edges of the perimeter as possible.  


*A common location for errors to occur in the heightmap is at 0,0 as well as at the centers - like 32,32 -32,-32 64,64 etc. These errors can regenerate themselves repeatedly '''each time their heightmap area is saved'''.
Repeat the above steps with the next elevation. Each later should be smaller in area than the one below it. How you build these layers up will depend what you want your final terrain to look like. If you want a rough and mountainous terrain you may only need to build up half your elevations with this method and then switch to the noise tool. If your world will be smooth and rolling you will want to build all your elevation with this method and finish by smoothing your work out with the Smudge tool. No matter how you plan to build your world make sure before you save your work in the heightmap editor that you reference and follow the rules mentioned at the top of this section to prevent errors.


*After finishing work on your first 4 quad heightmap you should save your mod in the CS and follow the directions in the following two sections.  
After finishing work on your first 4 quad heightmap you should save your mod in the CS and follow the directions in the following two sections.  


====Converting Your ESP to an ESM====
====Converting Your ESP to an ESM====
Anonymous user