Jump to content

Search the Community

Showing results for tags 'roads'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


    • Vigor
    • DAYZ
    • ARMA 3
    • ARMA 2
    • YLANDS
    • ARGO
  • ArmA Toolmakers's Releases
  • ArmA Toolmakers's General
  • Die Hard OFP Lovers' Club's Topics
  • Japan in Arma's Topics
  • Arma 3 Photography Club's Discussions
  • The Order Of the Wolfs- Unit's Topics
  • 4th Infantry Brigade's Recruitment
  • 11th Marine Expeditionary Unit OFFICIAL | 11th MEU(SOC)'s 11th MEU(SOC) Recruitment Status - OPEN
  • Legion latina semper fi's New Server Legion latina next wick
  • Legion latina semper fi's https://www.facebook.com/groups/legionlatinasemperfidelis/
  • Legion latina semper fi's Server VPN LEGION LATINA SEMPER FI
  • Team Nederland's Welkom bij ons club
  • Team Nederland's Facebook
  • [H.S.O.] Hellenic Special Operations's Infos


PlayStation PSN














Found 15 results

  1. Hi map/terrain/environment/world… makers, this is, after working at BI/BISim for almost 10 years, my first topic created here at BI forums. In my defense, I’m mostly active in Arma 3 Maps Terrains Skype’s group, but the topic I want to share with you deserves to be discuss here(skype has short memory and is not as comfortable as forums, for such kind of discussion). The Topic? It’s of course the bLandscapeTools(bLT), an addon for Blender I’ve been already working on for the last 8 years. The main reason I started this addon was: already knew Blender wanted to improve my python scripting skills, as I like to automate or at least speed up processes many handy world creation features were not available back then, are not available now and will never be implemented in BI/BISim world creation tools Necessary to note that I never intended to write a tool which would take over the world BI/BISim tools, but rather try to fill gaps(small/large) in terrain development. Blender is a 3D modeling tool(and much more), but you can’t expect fancy features which can handle big chunks of terrains with millions of objects on it, it has its own bottlenecks and limits, but even back then I could see, that the advantage of having possibility to import terrain mesh and its textures to Blender and start placing environment content much more easier way(comparing to Buldozer) or even modeling content over a terrain is a feature that will never come into Terrain Builder/Buldozer. By sticking together Blender’s default features like sculpting, painting + powerfull API I was basically able to add many time consuming and “Visitor4/TerrainBuilder hard to get implemented” features into Blender. Let’s stop talking for now… check out my talk at BlenderConference2016 about the Blender Terrain Tools(Edit: just currently I changed the name to bLandscapeTools) so you guys can make an image of what I’ve been working on. There are some features which will be really hard(almost impossible) to release because they are closely bound to BI dev content like raw(non-binarized) P3Ds, but on the positive note bLT has some handy features not even mentioned in the video(like quality assurance tools) Why now? After the conference I got contacted by individuals and even teams, asking me where they can download the addon as they would like to have their hands on it and give it a try. So I decided to start releasing the tool bits by bits to people so they, hopefully, can have a fun time play around with bLT. Also, the fact that this year(2017) it's going to be 10 years at BI/BISim or in other words working with the RVengine, as well as, Paul Pelosi(bushlurker) suddenly passing away, made me to do this decision and release the tool. It’s also going to be a challenge and something new to me, releasing my tool to other people, it needs a change of thinking about the tool, fix some parts of the pipeline..etc. and that may take some time. How? There’s plenty of how in the front of me. I need to figure out a way how to share the tool with you guys. Github, Blender market I have in my mind right now. As mentioned already, there are features hard to release(raw P3Ds). In this case I’ll have to ask someone here in BI, if company would be willing to release let’s say at least last LODs of assets so they could be imported into Blender and used within bLT. I use Blender for over 10 years, so I’m pretty comfortable with its workflow, but this doesn’t have to apply to a newcomer. Therefore, I’ll have to take some steps to make bLT even more user friendly than it is right now. I plan to make quite some tutorials how to use Blender and bLT to user’s satisfaction. Currently, Blender development is at the stage where quite a big major changes are being implemented and to be released with Blender 2.8. There’s going to be plenty of great new features such Viewport update(supporting PBR shaders), new Layers, Workflow system and much more. This means that I’ll have to re-think some of the bLT features to support all these new improvements once they’re released. Therefore I don’t want to do any major touches into what exists in bLT now. I hope that the improvements done for 2.8 will take bLT a few steps further again, as it already happened with the transition from Blender 2.4 to 2.5+. So once again, I’d like to ask you to have a look at my talk, if you have any questions please don’t hesitate to ask. It will help me to move on with releasing the tool as well as to know how the features should be done to help you create a map for any RV engine related project. When? Release of the '0-th' or 'Introduction' version is planned on the end of summer holidays. Progress will be tracked here. Subscribe to bLT youtube's channel here. Tools Github's here. Cheers, Miro
  2. https://feedback.bistudio.com/T128144 The small dirt roads around Mount Tanoa have a very short rendering distance. The road used around Mount Tanoa and the wo Comms bases disappears after a few hundred meters. Did not happen with version 1.80 its a 1.82 issue.
  3. Hello Community, I would like to make a Lakeside Life Server. To solve this I downloaded the Jackson County source files, mounted my P drive and unpacked my needed Mod pbos to the P drive . Terrain Builder and Bulldozer are working fine. BUT. Some of the roads were placed as shape roads and other as Object from E76. The Bridge on Jackson County doesnt work. I can delete the Objects from the bridge and the Road objects . Buit under the Bridge is also a shape road. If i delete the shape and export the layers, then the street is still there in Bulldozer and Arma 3. And I have also a issue with placing roads . I can place roads as objects but I cant place them as road shapes.If I place them as road shapes, I dont see them in Bulldozer and Arma 3.I made all like in the Tutorials on Youtube or like tutorials on forums. I hope somebody can help me to delete road shapes so i can´t see them in Bulldozer and Arma 3. I hope somebody can help me. Greetings from Germany Tom
  4. Im tried to add Roads to my map, but they are not displayed in Terrain Builder/Ingame. I draw Polylines, right clicked them and added the Database Properties ID,ORDER,__LAYER. Then I pressed File -> Export -> Shapes... and selected current Layer(also tried with Selection and Selection of Layers). The files are in the data/roads where they belong. The roadslib.cfg is copy n' pasted from the data of Stratis. I also tried to make the Shapefiles with Global Mapper and QGIS but it still don't works. When I just copied the road data from Altis and Stratis it was working fine in TerrainBuilder and Ingame. roadslib.cfg: In the config.cpp I added: Screenshot of my map and the database Properties: Screenshot of my folder structure: I hope someone can help me. Best regards, Tim
  5. I am aware of TB's ability to export a shape file to imagery etc. (I have done this) and therefore have a very rough layout of my roads as part of my fictitious island's sat map. I have spent countless hours tweaking curves to try and get a 'near perfect' rendition of the final roads, anyone who has generated any size of terrain will appreciate how long this takes. I am trying to get my road shape file (and therefore my sat map roads) to follow more precisely (if not exactly!) the actual road curves produced by TB. Other than simplifying my proposed mountain switchback, which I am loathe to do (though I may have to at this rate), is there anyway to export from TB an exact shape file for the actually generated in-game roads? What is annoying is when flying and/or viewing roads from a distance the sat map doesn't quite match up with the curves. This doesn't bother the guys who have play tested the map, and it wouldn't be TOO noticeable whilst in battle etc. but it drives me crazy. If there is no other way than tweaking each curve until it matches then so be it, but rather than pull my hair out I thought I'd ask here.
  6. I'm looking to use mask line in terrain processor to remove trees on roads. I add the shape file with roads but I think I'm missing something. Some how it has to be linked to the the objects to remove. How do I do that? Thanks.
  7. Dear all, Those of you who have tried importing roads from real data might have experienced the pain. There are multiple tutorials out there, but most of them give bits and pieces and it's hard to understand the exact workflow that needs to be followed. FYI, reference is mainly from these tutorials: Terrain Processor PMC Editing Software that you'll need: Terrain Builder Global Mapper QGIS SAS Planet Photoshop / Gimp Some of these software are not free, however there are trial versions that you may consider using. Let's get started. SETTING UP TERRAIN BUILDER & EXPORTING THE REFERENCE HEIGHT MAP Fire up Terrain Builder. Click on "Mapframes > Add mapframe": Leave the default Zone 31N selected and click OK: Set the name of the Mapframe, the output root folder (in your P drive), Easting to 200000 and Northing to 0: Click on the "Samplers tab" and choose your map size. I've set everything to have a map size of 10,240Km: Click on the "Processing" tab: Then click on "Rebuild Terrain": Confirm, and you will now have an empty terrain layer in Terrain Builder. We are going to export it so that we will be able to use it as a reference, further down in the tutorial: We're going to save it as reference-terrain.asc. DOWNLOADING ROADS There are multiple ways that you can get the roads shapefiles from Open Street Map. You can go on the https://www.openstreetmap.org/ website and export a specific area if you'd like, but we're going to download the data from http://download.geofabrik.de/ Head there, and select the country of your interest. In our case, we're going to need the data from Afghanistan: Download the .shp.zip format, and unpack it somewhere on your drive. SELECTING A PRECISE AREA Open Global Mapper and start a new project by selecting "Load Default Data": Click on Find address: Enter the name / coordinates of the area you're interested in (in this case Feyzabad, the map I'm currently working on): Click to center map on result: Let's now add some visual reference by clicking on the icon to connect to online data: Select "World Imagery" and click on "Connect": Use the zoom tool to zoom on your area. You can now enable the Control Center from the menu: So you can enable / disable the layers to view either the world imagery or the countries default data. We are now going to select our precise area of interest. Click on the "Create rectangle/Square area" tool: Draw an area (doesn't need to be precise) on the terrain where you want your area to be. In the menu that pops up when you release the mouse button, enter the name of your reference area (I've called it "border"): We can now better move the selection to your area of interest. Click on the Digitizer Tool: Select your area, then on the move tool: This allows you to move your area of interest around: Once you're satisfied with the position, we're going to adjust this area to be a perfect square in terms of meters. Right click on the area and select "Vertex Editing > Edit Feature Vertices": In the menu that pops up, we're going to change all of the vertices distances so that they reflect our map size, i.e. 10,240m. To do so, click on the first vertex, then on the "Edit Length" button, and enter the value 10240 meters: Once you're done, you will have a perfect square of 10,240m x 10,240m (look at the "Length" column): Click on "Copy to clipboard" to be able to access these references later: These are my coordinates: Idx,Longitude,Latitude,Length,Total Length,Heading 1,70° 30' 01.1798" E,37° 09' 41.4202" N,10.24 km,---,90.0° 2,70° 36' 56.2072" E,37° 09' 41.4496" N,10.24 km,10.24 km,180.0° 3,70° 36' 56.2072" E,37° 04' 09.2811" N,10.24 km,20.48 km,270.0° 4,70° 30' 01.6831" E,37° 04' 09.3107" N,10.24 km,30.72 km,0.0° 5,70° 30' 01.6831" E,37° 09' 41.4793" N,---,40.96 km,--- Use a converter tool to convert these coordinates in UTM. I used this online converter tool to do so: http://home.hiwaay.net/~taylorc/toolbox/geography/geoutm.html The result of my conversion is to have the following 4 points: top left 37.0692447463377,70.5003277260268 UTM: 4103606.716118635,633376.3161381673 top right 37.0692447463377,70.6156131229525 UTM: 4103774.7515539424,643625.6939804782 bottom left 37.1615056060246,70.5003277260268 UTM: 4113842.6755561405,633214.540454661 bottom right 37.1615056060246,70.6156131229525 UTM: 4114010.864559334,643451.4784080114 Note that the UTM zone of my area is 42N. Now it's time to import the roads downloaded from Geofabrik. For the purpose of this tutorial (importing roads) we're only interested in the gis.osm_roads_free_1.* files: Import the gis.osm_roads_free_1.shp file to Global Mapper (a simple drag & drop will do), and you will see the roads surrounding your selection: Now we need to convert the project to use UTM. Click on "Configure": In the resulting popup, set the Projection to UTM (the correct zone should already be set for you, if not just use the one that resulted from your computations here above): You might see your areas tilting a bit. Now, let's crop the roads to our area of interest. With the Digitizer Tool active, and only the roads and your border layer visible, select your border, and right click to select "CROP - Crop Loaded Features to Selected Area(s)": Ensure that you consider only lines and that you create a new layer: Name your layer: Verify that the projection of your new layer is correct: and then click on OK. You can now hide the layer with the full roads, and if you visualize only the newly created "roads_clipped" layer and the border you'll see only the roads you're interested in: We can now export those clipped roads: Export them as "shapefile": Specify your destination file for your lines (in my case, roads_exported.shp) and that "Generate Projection" is selected. PREPARING ROADS FOR IMPORT Open up QGIS. Open the options: Ensure that your projection is set to WGS 84 / UTM zone 31N by default: Click on OK and start a new project. Now import (drag & drop will suffice): The reference height map that you exported here above from terrain builder (reference-terrain.asc). The roads_exported.shp that you exported from Global Mapper. Right click on roads_exported and select "Zoom to Layer": You will see: Ensure that both layers are set to the proper CRS: right click on both layers, select "Set Layer CRS" and select "WGS 84 / UTM Zone 31N": Do this for both layers. If you don't see roads anymore, just right click on the layer, "Zoom to Layer" again. Now it's time that we move the roads to the appropriate place, which is Easting 200000 and Northing 0, as per the data we entered when creating our Mapframe in Terrain Builder. let's compute how much our roads are off, in terms of UTM: Our top left corner UTM coordinates are (see computations above): 4103606.716118635, 633376.3161381673 We need to make them become: 0, 200000 Hence we need to shift the coordinates: X shift: 200000 - 633376.3161381673 = -433376,3161381673 Y shift: 0 - 4103606.716118635 = -4103606,716118635 Bring up the Processing Toolbox with CTRL+ALT+T, and search for the v.transform algorithm. Once it appears, double-click on it, which will bring up the dialog. Enter the shifting values that we just computed: Clic on "Run". This will create a new layer "Transformed". Right-click on this layer, and select "Zoom to Layer". You will see: The black square is our reference-terrain level, so the roads are now in the right position for Terrain Builder. Great! However, you can notice that the roads are slightly rotated in comparison to the reference terrain. We can fix that by applying some rotation. I'm going to choose -1 and apply it with v.tramsform again: This results in roads being rotated but also shifted southwards: Right click on the upper "Transformed" layer and select "Toggle Editing": Now use the Move Tool to move your roads so that they are fully contained in the black area (the reference terrain): Repeat if necessary. When you're done, we can export those roads to be used in Terrain Builder. Right-click in the uppermost "Transformed" layer, and select "Save as:" Export the layer as ESRI Shapefile (ensure that the proper CRS is set, which should be the default): Here I've saved the file as roads_final.shp. We now need to set the appropriates attributes for roads. In the resulting excel-like table, toggle editing mode: Click to create a new field: Create a new numerical field called ID: Now we need to populate this field. Click on "Open field calculator": and fill the data to look like this: The ID field needs to contain the roads reference as specified in your roadslib.cfg file of your terrain project. Basically, we are populating the newly created ID field based on the values contained in the fclass field by using this expression: CASE WHEN fclass is 'primary' THEN 1 WHEN fclass is 'secondary' THEN 2 WHEN fclass is 'tertiary' THEN 3 WHEN fclass is 'residential' THEN 4 WHEN fclass is 'service' THEN 4 ELSE 5 END Click on OK. You ID field will now be properly populated: Now let's remove the unneeded fields. Click on the delete field icon: Select all the fields except the newly created ID: Click OK. Save Edits: Quit the Attributes Table and If prompted, save the layer. PREPARING THE SATELLITE IMAGE Open SAS Planet, and click to enter a selection area by coordinates: Enter the coordinates as exported by Global Mapper: This will bring up the selection manager. Select "Bing Maps - satellite" (or your preferred satellite source) and then click on the first zoom level that has a resolution higher than your terrain size (in this case, you can see that with zoom level of 18 the resulting image size is greater than 10,240 x 10,240): Click on "Start" to download the tiles: Once the process is finished, click to select the last area: Move to the "Stitch" tab: Ensure to select the same Map source (in this case, "Bing Maps - satellite") and level of zoom (here, 18), select where to save your file and click on "Start". This will save your satellite image as a single JPG file. Open up this image in Photoshop (or other editor of choice) and change the size of the satellite image to match the size of your terrain (you will have to un-tick "Constrain Proportions"), in this case 10240: Save your resulting satellite image as a BMP file. Do not save it in other formats, as those might take significantly longer when imported in Terrain Builder (we're talking about hours in comparison to few seconds). IMPORTING EVERYTHING BACK IN TERRAIN BUILDER Back in Terrain Builder, import the newly created satellite image: Now import your roads (roads_final.shp): When prompted, leave unchanged: And there you have it. Enjoy your freshly imported roads: And if you select them and open up the Database Properties: You are going to see the correct road ids: Many thanks to the various tutorial writers that originally helped me, and to W4lly63 for his great support. Best, _SCAR.
  8. All, I am building a terrain and am already pretty far in the process (we are finalizing the objects on the map). When I first started, I imported the PNG file of the height map, and I have levelled the roads by hand. It has been a painful process and I often still see some roads that need adjustments. Unfortunately until recently I had no idea that there was a Heightmap Road Integration for Terrain Processor, my bad. However, I would still like to give it a try and see if it can solve some issues that I'm seeing. Can I do that? I only have the original height map in PNG format (not .ASC, which is what is required by the plugin) that I imported when I first created the terrain. Since I modified the terrain quite a lot, I see that there are new layers for the heigh map in Terrain Builder. I don't think that the original PNG file that I imported contains the information of all the changes that I've done since then. I found that I can export the terrain information as an .ASC file, but how would I go to reimport it in Terrain Builder? Any information would be greatly appreciated! Thank you, _SCAR,
  9. Hallo, I need help with the function BIS_fnc_nearestRoad. I use it for several scripts for example spawn vehiculars or roadblocks. I know the function of the first 2 parameters: Parameter(s): _this select 0: ARRAY - The center position _this select 1: NUMBER - The distance from center position _posStreet = [_position, _radiusSearchForRoads, []] call BIS_fnc_nearestRoad; but when I want to work with the third parameter blacklisted road object it doesn´t work. _this select 2: ARRAY - List of blacklisted road objects I know that the Function BIS_fnc_nearestRoad with parameter _list work as an Array. like _array = _array - _list So my main problem is, what kind of format is allowed in the array _list (3 parameter of function BIS_fnc_nearestRoad)? I need a restriction for a lot of roads on the map Taunus. On this map are a lot of Paving paths, Concrete slabs and other road objects (mostley Objects from the Addon CUP terrain), they are sometimes under houses. So I want to restrict these objects. What I done: 1. nearestTerrainObjects ( "MAIN ROAD", "TRACK", "ROAD", "TRAIL" ) for the array _list, its a "STRING", 1.1_posStreet = [_position, _radiusStreet, ["ROAD"]] call BIS_fnc_nearestRoad; <----- no result 2. className (CUP_A1_Road_kos6konec,CUP_A1_Road_kr_new_kos_sil_t) again for the array _list, 2.1 example as "STRING", _posStreet = [_position, _radiusStreet, ["CUP_A1_Road_kos6konec"]] call BIS_fnc_nearestRoad; <----- no result 2.2 example not as "STRING", _posStreet = [_position, _radiusStreet, [CUP_A1_Road_kos6konec]] call BIS_fnc_nearestRoad; <----- no result 3.Then I watched in the array _posStreet what for comments are in there, _posStreet = [2730105: ,1780867: pflaster_hex_9m.p3d,1780868: kos6konec.p3d,1736475: ,1780869: ,1780105: , ], 2730105: this is the ID number but with : , every CUP road object has the ID number and the P3D Name 1780867: pflaster_hex_9m.p3d the not CUP road objects has only the ID number with that fuc... double point (tested on Altis and Stratis) -----> Its can be a STRING ----> I attempt again with 3.1 _posStreet = [_position, _radiusStreet, [1780867: pflaster_hex_9m.p3d]] call BIS_fnc_nearestRoad; <----bad format : double point 3.2 _posStreet = [_position, _radiusStreet, [pflaster_hex_9m.p3d]] call BIS_fnc_nearestRoad; <---- no function 3.3 _posStreet = [_position, _radiusStreet, [1780867]] call BIS_fnc_nearestRoad; <---- no function I work lot of hours on it, but I have no idea now, I hope someone can help me pls. Maybe there is a other way? p.s. I want to spawn compositions and vehiculars on the normal roads not on the CUP road objects on Taunus
  10. Buldozer Tools

    Buldozer Tools by Lappihuan This is a successor to the Improved editor.sqs I’m pretty sure most of you know the following scenarios: “You work for several hours in Buldozer, the rain that is dropping since the last 20 mins is already annoying but the productivity and creativity is on fire. It keeps getting darker and darker and you think that it’s time to restart buldozer but you quickly want to finish the composition you are working on. BOOM! Out of nowhere TB crashes and your adrenalin rushes through the whole body, you didn’t save the project for the last 4 hours!!!†Result: things like this can throw your motivation off for several weeks. “While working on a town, you feel like there is a road missing or would like to move an existing one to fit your object placement better.†Result: you need to restart Buldozer every time you change your roads.shp which is a waste of time! “Players report that AI can’t properly use the awesome bridge you placed on the map, and you can’t figure out why they won’t use it.†Result: you spent many hours to tweak the road and bridge model with a eventual success or use a hacky solution like place an invisible road below the bridge. I hope to eliminate or at least reduce most of the above issues with the Buldozer Tools. Features: Reload roadsDefault key “1†Reset weather and timeDefault key “2†Toggle road diagnosticDefault key “3†Be aware, it can cause Buldozer to crash! DebugDefault key “4†execute the debug.sqf while buldozer is running (helps R&D) NVG and IR modeDefault key “N†Help DialogDefault key “0†Save notificationCustomaisable time in userconfig.sqf While the list is still quite small, I feel like it already has a big impact on the workflow in Buldozer. Installation For the sake of easiness I provide a scripts folder with everything needed in there. Drop the script folder into your P drive so it has the structure: P:\scripts\initBuldozer.sqf You can customize everything in there, but the config.sqf is the most important part for you. If something is unclear / could be made easier, let me know. IMPORTANT: delete or rename your current editor.sqs, so it won't conflict with this. Download Link Feel free to contact me on Skype/discord or here about suggestions, bugs or whatever. I hope you guys enjoy! Thanks to Pennyworth for the help!
  11. Hi there, I am having some trouble with my roads. I can no longer See them in buldozer (Yes I am using editor.sqs in 'scripts' folder) and I can't see them in Arma 3 either. I do not know what has happend but yesterday I could see my roads in Buldozer perfectly fine however now (the day after) For some reason they just don't Appear? Here is my Roads.lib: /* 1 - Main Road 2 - City Road 3 - Dirt Road 4 - Highway 5 - Path 6 - City Road 7 - E76 Highway 8 - sentiero 9 - pista */ class RoadTypesLibrary { class Road0001 { width = 12; mainStrTex = "a3\roads_f\roads_ae\data\surf_roadtarmac_main_road_ca.paa"; // lowercase! mainTerTex = "a3\roads_f\roads_ae\data\surf_roadtarmac_main_road_end_ca.paa"; mainMat = "a3\roads_f\roads_ae\data\surf_roadtarmac_main_road.rvmat"; map = "road"; order=1; }; class Road0002 { width = 8; mainStrTex = "a3\roads_f\roads_ae\data\surf_roadconcrete_city_road_ca"; // lowercase! mainTerTex = "a3\roads_f\roads_ae\data\surf_roadconcrete_city_road_end_ca.paa"; mainMat = "a3\roads_f\roads_ae\data\surf_roadconcrete_city_road.rvmat"; map = "road"; AIpathOffset = 2.5; order=2; }; class Road0003 { width = 8; mainStrTex = "a3\roads_f\roads_ae\data\surf_roaddirt_road_ca.paa"; // lowercase! mainTerTex = "a3\roads_f\roads_ae\data\surf_roaddirt_road_end_ca.paa"; mainMat = "a3\roads_f\roads_ae\data\surf_roaddirt_road.rvmat"; map = "track"; AIpathOffset = 0; order=3; }; class Road0004 { width = 12; mainStrTex = "a3\roads_f\roads_ae\data\surf_roadtarmac_highway_ca.paa"; // lowercase! mainTerTex = "a3\roads_f\roads_ae\data\surf_roadtarmac_highway_end_ca.paa"; mainMat = "a3\roads_f\roads_ae\data\surf_roadtarmac_highway.rvmat"; map = "main road"; AIpathOffset = 3; order=4; }; class Road0005 { width = 5; mainStrTex = "a3\roads_f\roads_ae\data\surf_roaddirt_path_ca.paa"; // lowercase! mainTerTex = "a3\roads_f\roads_ae\data\surf_roaddirt_path_end_ca.paa"; mainMat = "a3\roads_f\roads_ae\data\surf_roaddirt_path.rvmat"; map = "track"; AIpathOffset = 0; order=5; }; class Road0006 { width = 10; mainStrTex = "a3\roads_f\roads_ae\data\surf_roadconcrete_city_road_ca.paa"; // lowercase! mainTerTex = "a3\roads_f\roads_ae\data\surf_roadconcrete_city_road_end_ca.paa"; mainMat = "a3\roads_f\roads_ae\data\surf_roadconcrete_city_road.rvmat"; map = "track"; AIpathOffset = 2.5; order=6; }; class Road0007 { width = 12; mainStrTex = "a3\roads2\Data\asf1_dashedline_ca.paa"; // lowercase! mainTerTex = "a3\roads2\Data\asf1_dashedline_ca.paa"; mainMat = "a3\roads2\Data\asf1_dashedline.rvmat"; map = "road"; AIpathOffset = 2.5; order=7; }; }; Here are some Screenshots (In case you need to check something) https://gyazo.com/5a5da79580fac72f4e8d1a8768558231 - My Terrain Builder with Project Loaded https://gyazo.com/0a12c500f0a49751fcc175545f2f71b0 - My P: Drive Directory https://gyazo.com/deed7472caece8da14f2da91520e7582 - My Project Folder Please Let me know if there is any other files / Information that you need! Thank you very much!
  12. Make sure to use the new version called Buldozer Tools Improved editor.sqs This is an Improved version of the editor.sqs which can be used to execute code within buldozer. You can load and reload roads.shp while being in buldozer, additionaly it removes rain and sets the time to midday. This means, no more buldozer restarting for road adjustments and for the addicts no more rain and night. The key to execute the script is * on the NUMPAD, you can change the DIK in the script by editing the key variable. 1. Paste the code in your P:\scripts\editor.sqs 2. Make sure to set your path to your roads directory correctly 3. Make sure your road files are in the respective directory 4. Load up your buldozer and wait until you see your map 5. Press * [NUM], the reload should be quick but can get longer with extremely big and complex road networks P:\scripts\editor.sqs ; editor.sqs by Lappihuan and Sumrak ; due to sqs syntax the single line must be kept! https://community.bistudio.com/wiki/SQS_syntax ; key to execute the script is * [NUM] ; roadpath: is the path to your roads directory in your project. ; dateArray: https://community.bistudio.com/wiki/setDate ; key: https://resources.bisimulations.com/wiki/DIK_KeyCodes roadpath = "P:/mytag/mymap/data/roads/"; dateArray = [2001, 06, 22, 12, 0]; key = 55; _bulKeybinds = [] spawn {keyBind = (findDisplay -1) displayAddEventHandler['KeyDown','if(_this select 1 == key)then{result = buldozer_LoadNewRoads roadpath;setDate dateArray;0 setRain 0;0 setOvercast 0;}']}; You are free to use and edit this script how you like. If you have any bugs, suggestions or improvements please post them here. If you have or are about to make a tutorial, feel free to include the script in the source data. Thanks to Sumrak for pointing me out that display event handlers work in buldozer and providing a example code. I'm happy to see what you guys can come up with. Kind regards, Lappihuan
  13. So, i am working on a small bridge of my own, and i am having problems with road textures. Ill upload my project here, so someone can have a look at it. Would be nice if someone could have a tutorial for me on how to make roads and bridges. Thanks ;) Model Here
  14. So I'm building this island with a completely custom heightmap. The roads are on the map and I used Terrain Processors road integration but the result is not what I want.. Let me give some examples: http://imgur.com/c0xui9m http://imgur.com/18L1sgg http://imgur.com/Ny5597j http://imgur.com/cTgpyIO Don't mind the bright colours because thats far from final:D But as you can see the edges of the roads angle very agressively. I know I can up the "affected terrain" parameter in TPP but the results remain rather chunky... My own theory is that the roads.shp file looks very pixelated and because of that the result are not smooth (while TB is prfectly capable of smoothing!) Or maybe it has something to do with the "side maximal slope" parameter because I have no clue of its function.. I also tried trippeling the islands size allong with the shape file but the results remain the same. Can it have anything to do with cell size? So basically if someone knows what to do I'll glady hear it. Or if someone can fix it for me I can give you the .shp and .asc