5)Save the images in a folder (c:\example_folder) with the desired splitting (5x3 in this example):Operations -> Select -> Previous Selection -> Stick -> Start YOU MUST select .dat file bindings6)Now we add the grid to joined.geo:

Código:

> add_dat_to_geo('c:\example_folder')

7)Open joined.geo and you will see the limits of the downloaded images you have inside c:\example_folder

If you use the lines of the new grid for splitting the non-driveable zone, may be you can then map the textures easily.

The intersection with grid and splines of the track will create automatically? It is important to apply materials to meshes, I was do manually but it is a hard work.

After my experience I was thinking about texturing all terrain, and I think that I found a better solution. So it is easy, fast and practical. Better than do materials for each texture in BTB is add background images and fit on each rectangle, it is fast and give you the opportunity to mix some faces selected with a new material. I do that for a 5x5 grid succesfully.

Napalm Candy escribió:The intersection with grid and splines of the track will create automatically? It is important to apply materials to meshes, I was do manually but it is a hard work.

After my experience I was thinking about texturing all terrain, and I think that I found a better solution. So it is easy, fast and practical. Better than do materials for each texture in BTB is add background images and fit on each rectangle, it is fast and give you the opportunity to mix some faces selected with a new material. I do that for a 5x5 grid succesfully.

It is impossible (or really difficult) to create automatically that intersection.But it is not so difficult for the user to create points by hand that rest on the grid lines (for example, for the vertical lines those new points must have the same x coordinate as the points that define the line). Create those points for the intersection spline-grid, delete the spline and then just join the points with straight lines so you can use them and the grid lines to define small surfaces for the non-driveable zone.

Note: add_dat_to_geo calls addgrid internally, so when you call add_dat_to_geo, a backup of addgrid.hlg is made before it is overwritten. It should be better changing the name of addgrid.hlg each time we create it, so it is more descriptive, or copying it to another folder so we don't lose it.

strsplit is not one of my scripts. May be you need octave 3.2.3.You can install 3.2.3 and have both installed on the same system. Or remove 3.0.5 as we are working with 3.2.3.I hope that will fix the problem

dont know..Im doing everything right...I hope. I made sure to include all the scripts from 240410 for the projectDo I have to add the salida folder? I noticed when I did that it called for the mapeo.txt

I can't follow you (probably because I have no expertise with SASPlanet)

Now add_dat_to_geo also creates a list of all the background images, with the format needed by BTB.It is called list_bi.txt. It must be inserted by hand inside the Venue.xml (really easy, the list of background images islocated on the 3rd line of this file).

Images should be named sat_X-Y.jpg and should be located inside My Project\XPacks\Common\Textures.

Just trying some things:I batch converted all the sat_x-y.jpg images to dds after resizing them to proper multiples for game use prior to opening btb.If you do the same, you need to edit the list_bi.txt and find replace all .jpg to .dds before adding to Venue.xml.

Don't do the simplification process with MeshLab.I have an idea: I can split the non-driveable mesh, nonconducibles.ply, into squares (one in its own .ply file). For each of them simplification is straightforward, as you don't have to "select the square". Instead you just open the .ply file for that square (when I say square, I mean "grid cell"). MeshLab has the option to open multiple meshes at Tte same time and joining them into just one: n.ply. That should work.I will try it in a couple of hours.

To reduce an image and save to DDS you can use photoshop and the plugin from nvidia DDS (Freeware).

So you create an action, doing the reduction, saving in DDS format and closing the file. After record the action, if you have opened all images at the same time, only need to play the action (1 click) one time for each image, it is very fast.

Open s4_terrain\salida\nc_splitted\*.ply with MeshLab (you can open all in the same operation)View-> Show Layer Dialog

Select one mesh with the layer dialog, simplify it. Repeat until all the meshes have been processed. Then Filters->Layer and ... -> Flatten visible layers. This combines all the grid cell's meshes. Save result as salida\n.ply