#BOBS TRACK BUILDER RFACTOR 2 HOW TO#

opened it in xpacker, loaded the new dds, replaced the jpg with them and deleted the unused textures. ground.jpg converted to ground.dds (DXT1, 6 mipmaps) There are tutorials for that procedure in BTB forum, this is general modding forum. The procedure for this is not intuitive, it's a workaround, BTB can't merge roads the right way. After you are satisfied with the start/pit area, you should merge the two tracks. Since you're still doing the basic layout work it's not yet necessary but it is before you can make the terrain around pits permanent.

#BOBS TRACK BUILDER RFACTOR 2 HOW TO#

Did some example of how to merge terrain anchors. But for sure dropping 2m in a span of 5m while turning 200 degrees does not fit to any road suitable for automobiles.

You need to wiggle the control arms, move nodes etc, there were un-naturally tight and too big elevation change at the same time, there's a limit of how radical changes you can do to a track in both gameplay and technical issues. Check the panel lengths in different sections. I did this only from start to the end of that long straight. With only one huge mesh, the game has to load it all in the memory at all times, with smaller sections, the game can load only the parts of the track shown on screen. It was 10km long, the preferred length of one section is 300-500m, about the size what you can see from the car. Splitted new sections to the road using material cross-section. Remember to change 'LeftsidePits = 0' to 1 in your AIW since your pits are on the left side. If you need to use positive bias, make the changes in your texture instead, make it smaller and blur it in photoshopĮDIT: The conflicting texture seems to be the pitroad. You can use positive mipmap biasses but that is basically just blurred texture then. We need to use even more negative bias to ensure we get the highest quality. Roads are difficult, they can be at the same time very close to viewport and extend quite a long way in the distance. gMotor2 has a tendency of using too low mipmap levels at default, that's why you see most textures to use mipmap bias of -2 or more. You can tell the game to use one mipmap level higher resolution (512x512), resulting in higher quality texture projection but more strain on the GPU. For ex, you would only need 256x256 size texture (it doesn't tak more than that area from your screen.) but it looks kind a fuzzy. Mipmap bias controls ahow much 'oversized' texture size we are using. Now you see why we need to use powers of two, it's fast to scale up and down, doubling and halving is very fast to do in binary systems. Each step smaller is called level and we can use the mipmap bias to control what level mipmap is used at what distance. They are smaller versions of the original image so the game don't have to scale 1024x1024 textures that appear on screen 5 km away, using only small number of pixels. They all reserve the same memory print while they are been processed by the GPU.ĮDIT: Forgot, te most important feature of DDS: mipmaps. It's a bitmap, supports alpha layer, fast to process but are slightly larger in filesize than JPGs. If you have to use something other than DDS, use PNG format. Also you can get the really important alpha layer in DDS. JPG compress the whole image so tiled patterns have lines in them (unless the opposite edge has the exact same color value, ie single color edges.). Use DDS format when ever possible, it's compression is fully supported by the GPU, it's fast and it doesn't suffer from the same faults: DDS won't diffuse the edges but keep them untouched. Your jpgs are 548x357 pixels, convert them to 512x256 or 512x512 DDS. Both jpgs in your pits xpack are wrong dimensions.

Bobs track builder rfactor 2