121 lines
9.7 KiB
Plaintext
121 lines
9.7 KiB
Plaintext
THANKS for your support!
|
|
|
|
Thank you for purchasing Castle Valley Collection #1! These rock formations were scanned in the San Rafael Swell, a heavily eroded upwelling of Jurrasic sandstone in central Utah, not far from Moab. Thanks goes out to the folks at 3DF Zephyr and 3D Coat and Unity for their great software. Thanks also goes to my pack goats Shelby GT, Woodstock, Bacchus, Vincent VanGoat, Barry Goatalo, and also Luna the German Shep, for their assistance carrying equipment out in the desert. If Collection #1 is successful, Collection #2 will be complimentary and compatible, containing more of the most useful building blocks for amazing scenery.
|
|
|
|
----------------------------
|
|
|
|
SUPPORT
|
|
|
|
Web Page: http://www.goatogrammetry.com/
|
|
Email: goatogrammetry@gmail.com
|
|
|
|
----------------------------
|
|
|
|
SETUP
|
|
|
|
This version of Castle Valley Collection #1 is meant for Unity's default standard render pipeline. Because there are no scripts or settings that will override or interfere with any of your existing work, it should be safe to install it directly into your current project.
|
|
|
|
A scene in the Demo directory "Castle Valley Layout Scene" will show all of the prefabs and tiling textures in this pack lined up in rows. In order to keep the size down and not clutter your project its very basic, with no baked lighting, no baked reflection probes, no camera scripts, and no skybox. Feel free to delete it when you've finished looking it over.
|
|
|
|
Thats it for setup!
|
|
|
|
-----------------------------
|
|
|
|
TIPS:
|
|
|
|
* PBR shaders require reflection probes to work. If you don't have probes added (and also baked), your cliffs and rocks will look too glossy or plastic-like as they reflect the skybox rather than what is actually around them. Often the skybox has bright colors even on the lower half, which will reflect upwards onto the undersides of shadowy overhangs, giving weird "plastic" looking results. If you drop some cliffs from this pack into a new, empty scene, and the shadows are harsh and very black, its because there is no ambient lighting at all. Once the scene has correct lighting, you'll be pleasantly surprised at the improved realism of these scanned assets.
|
|
|
|
* Some of the tiniest rocks and plants get their ambient lighting from light probes rather than baked lightmaps. If you do not have your light probes set up, you may find these prefabs are rendering too dark or bright. When you add light probes, be sure to place them near any prefabs that need them, especially if there is a strong shadow boundary in the area.
|
|
|
|
* Keep in mind that prefabs that use the "Cliff" prefix are very large and look best with a little distance, even though they use a 2nd 'detail texture' to enhance the micro-surface. Because of their large size, their pixel density is lower than the other, smaller prefabs. They look fine up close, but due to their scale there's no reasonable way to make them look quite as detailed as some of the other, smaller items when the camera is very close to the surface.
|
|
|
|
-----------------------------
|
|
|
|
|
|
LOD (Level Of Detail) or "LOD Group" component:
|
|
|
|
* All meshes come with 4 or more hand-adjusted LODs built in.
|
|
|
|
* As a rule, LOD1 has half the triangle count as LOD0, etc.
|
|
|
|
* Remember that you can adjust global LOD distance ratio in your project settings (LOD bias).
|
|
|
|
* Special Note: As of this writing (Unity 2019.3b) Progressive GPU (Not CPU) light baker malfunctions on meshes with LODs, causing blurry, blotchy bakes with glowing and missing black zones. There's nothing wrong with these meshes-- Its just that Progressive GPU is still in preview beta. I suggest Bakery GPU Lightmapper (Unity Asset Store) for great results, or using Progressive GPU only for rough-draft light baking, and using the slower CPU version for the final bake. If you use Progressive CPU, I suggest using 5 or 6 texels for indirect, and dropping the samples from 100 to 16 or so activating the de-noising options to smooth it out. These rocks are forgiving and imperfections/low resolution in the indirect lighting looks fine. The demo map took me about 20-30 minutes to bake in 2019.3 but in 2018.4 it takes a miserable 5 hours, so it looks like Progressive CPU had a big improvement at some point in between!
|
|
|
|
|
|
-----------------------------
|
|
|
|
COLLIDERS
|
|
|
|
* All prefabs contain custom-made low poly, but accurate, convex mesh colliders.
|
|
|
|
* The colliders are not contained within the rock's .fbx file, but rather in Meshes/Colliders.
|
|
|
|
* The physics material for Sandstone is in Meshes/Colliders. I just guessed on the values, so adjust as you see fit.
|
|
|
|
-----------------------------
|
|
|
|
MATERIALS AND TEXTURES
|
|
|
|
* Sometimes different meshes share the same material's bitmap for optimization.
|
|
|
|
* Mesh filenames have a naming convention that links them to their matching material.
|
|
|
|
* An example: Mesh_Boulder_01_AJ.FBX uses Material_AJ_01.mat which gets its colors from AJ_Color_01.png (Note the AJ in each)
|
|
|
|
* Color & Normal textures are generally 4096x4096. The "smoothness" grayscale is in the color(albedo) alpha channel.
|
|
|
|
* Occlusion maps are generally lower resolution to save video memory, since occlusion isn't usually ultra detailed.
|
|
|
|
* All the rock materials use a detail texture.
|
|
|
|
-----------------------------
|
|
|
|
LIGHT MAPS
|
|
|
|
* Any meshes that share the same texture have a 2nd UV set for light maps. This 2nd UV set fills the whole UV space to prevent wasted texels in the lightmaps.
|
|
|
|
* Special Note: As of this writing (Unity 2019.3b) Progressive GPU (Not CPU) light baker malfunctions on meshes with LODs, causing blurry, blotchy bakes with glowing and missing black zones. There's nothing wrong with these meshes-- Its just that Progressive GPU is still in preview beta. I suggest Bakery GPU Lightmapper (Unity Asset Store) for great results, or using Progressive GPU only for rough-draft light baking, and using the slower CPU version for the final bake. If you use Progressive CPU, I suggest using 5 or 6 texels for indirect, and dropping the samples from 100 to 16 or so activating the de-noising options to smooth it out. These rocks are forgiving and imperfections/low resolution in the indirect lighting looks fine. The demo map took me about 20-30 minutes to bake in 2019.3 but in 2018.4 it takes a miserable 5 hours, so it looks like Progressive CPU had a big improvement at some point in between!
|
|
|
|
* Some of the tiniest rocks, plants, and the tree are set to take their lighting from the light probes rather than light maps. Its easy to change, but they're set this way to prevent crazy-long bake times and huge lightmap data.
|
|
|
|
* All of the "Cliff" prefabs have their light mapping scale set to 1/3 normal texel density due to their large size. Because you're dealing with large meshes, its safe to reduce this to even smaller fractions and still have a great looking final light-bake!
|
|
|
|
* "Cliff" prefabs often have "Cap" meshes on the top and back. These do not bake light maps and use light probes instead.
|
|
|
|
* "Cap" meshes on cliffs are meant to help cast shadows but are not really made to be seen. Hide them with capstones etc if necessary.
|
|
|
|
* Sometimes the cliff's cap meshes will throw warnings from the light baker, saying they have overlapping UVs. Ignore this, since the UV size is set to 0 (not meant to be seen) and is thus ignored by the indirect light baking algorithm entirely.
|
|
-----------------------------
|
|
|
|
TERRAIN
|
|
|
|
* When adding "Terrain Layers" (materials) to paint on the terrain, you'll find them in the Materials/Tiling directory.
|
|
|
|
-----------------------------
|
|
|
|
Version 1.1
|
|
|
|
Converted from 2019.3 to be compatible with 2018.4
|
|
|
|
Cliff_Corner_03's prefab somehow had the mesh offset from the colliders by .4 meters. Its fixed, but you'll want to make sure it didnt introduce a gap in your own maps. If so, just move it a bit.
|
|
|
|
Special Note: If you're converting from the Standard 1.0 to 1.1+, or to HDRP or back, you may have to change the meta ID# for the vulture, obstacle1, rabbit brush, and living tree prefabs to match. I had to rebuild them from scratch and I forgot to paste-in the right prefab ID, and now people have been using the new patch, so its kinda out of hand. Sorry about that!
|
|
|
|
-----------------------------
|
|
|
|
All prefabs with problems with the UV2 (baked lighting) problems are fixed. But since UVs got changed, you'll have to re-bake your maps :( Sorry!
|
|
|
|
By popular demand, I added an example scene (sort of a PVP deathmatch map) found in the demo directory. I suggest adding the simple camera controller script that comes with HDRP so you can move around in play mode. Progressive lightmapper choked and died so I used Bakery.
|
|
|
|
The sage brush and trees have been changed to NOT be static. I found out static terrain trees are a no-no. All plants will take their lighting from probes. Also Sage's most distant LOD3 no longer casts shadows just for optimization's sake.
|
|
|
|
I added a version of the sage brush with the vertex normals pointing upward. This evens out the shading on the branches. It may or may not be an improvement for your scenes, so try it out! Also, I've added more shader options for the sage brush. There's now a version that randomizes the tint between 2 colors based on location, and also a transmission shader (based on the example Amplify Shader with my branch movement added). Some of these shaders cause some artifacting with the forward render path's ambient occlusion post FX, but I guess thats normal and you can try them out and see which work best for your project.
|
|
|
|
Obstacle 10-13's albedo texture was slightly too bright and didn't match the rest perfectly. Its been adjusted.
|
|
|
|
I've turned off the vulture script's debug message flag. I left it on originally-- Annoying!
|
|
|
|
Baked occlusion sliders for the ledge and rock pile materials has been lowered slightly-- It was too intense originally.
|
|
|
|
Remember to leave a review! Thanks!!! |