Fs13 make a road in gaints editor code#

For use in GiantsвЂ™ shader, all images need to be the same type, and the same resolution. A single DDS texture array can hold as many images as needed. The order of the images corresponds to the order of the UV tiles (1001, 1002, 1003 etc.). These texture arrays are special DDS image files that contain an array of images, in a certain order. These 3 texture files point to so called вЂtexture arraysвЂ™ for the diffuse, specular and normal textures. If you put your UVs in any of the regular UDIM tiles, where does the shader get the textures from? Texture arrays, or вЂGiants Material LibraryвЂ™ More about that special row in a bit, first letвЂ™s take a look at the вЂstandardвЂ™ tiles. The UDIM standard does not allow tiles with negative coordinates in both U and V directions, but fortunately, both Blender and Maya will still allow you to put your UVs there. And a special meaning is added to the row of tiles at V -1. The maximum number of tiles in the U-direction is set to 8. The implementation Giants used in the vehicleShader sets a few conditions for this. Based on the UV tiles you unwrapped your model parts in, the shader needs to figure out which texture to use. Use cases vary from tire deformation, to jiggling parts, and even tracks are fully implemented using the vertex shader.

There are cases though, where the vertex shader is used to change vertex positions. For the UDIM part, all the exciting stuff happens in the fragment shaders, as thatвЂ™s the shader that applies the textures, but just to make sure we covered everything, this is the vertex shader part of the vehicleShader, that simply sets the position to the position it has in your 3D model, unchanged. When we looked at the rendering pipeline earlier, I mentioned thereвЂ™s a vertex shader, and a fragment shader. The story of how a single shader abuses UDIM, in a non-standard way, to implement a flawed material library, and became the de facto standard for all vehicles and implements in FS19. Because most readers are probably here because they just want to know вЂhow to UDIM their tractor/truckвЂ™, weвЂ™ll have a detailed look at what they did, how they did it, and how you can use it first. This interpretation goes beyond the basic definition of UDIM, and it violates the UDIM standard. They used a very specific implementation for interpreting the UDIM tiles in a model. In the vehicleShader however, Giants did something more than just that. Now from the introduction about UDIM, you know that UDIM is basically nothing more than unwrapping parts of your model into different UV tiles, so you can assign different textures to them. For that, we need to take a closer look at the vehicleShader, because that is the shader that вЂsupports UDIMвЂ™. YouвЂ™re absolutely right, and weвЂ™re almost there. Shaders included in FS19 I thought this article was about UDIM?! ThereвЂ™s plenty of shaders included, the buildingShader and the vehicleShader probably being the most used for, as the name implies, buildings and vehicles. This is familiar territory for most modders, as you select these shader XML files in GIANTS editor. The way to specify these hooks, and tell the game engine how you would like to affect the way something is rendered, is through shader XML files. Giants actually provided us with an extensive and very open framework allowing us to affect almost every aspect of how the game looks, and behaves. This is something very few people are aware of.

Fs13 make a road in gaints editor code#

Hooks are moments in the execution of the shaders where you can insert your own code to be executed. The good news is, Giants included a huge number of so called вЂhooksвЂ™ in them. The actual shader code is part of the internals of FS19, so I canвЂ™t show you a fragment of it, but in case youвЂ™re curious and know your way around the game files, they are included in the shared/shader.gar archive.

The next one is the pixel shader, also called fragment shader, that colors them.ДЇS19 has implemented these shaders in Cg, a shader language based on the C programming language, developed by Nvidia. ItвЂ™s main purpose is to determine the position of your vertices. ThereвЂ™s two moments in the pipeline where we can control what the end result will look like. The bag of vertices on the left? ThatвЂ™s your 3D model. The diagram above shows a simplified view of the graphics rendering pipeline.