I'm still stuck, even after following the official guide. I'm now getting the following error message when importing the ASC files; LoginId:f8e07850429b515690df0499ee908b04 EpicAccountId:64bbbb73d8094af2a55979c591a8eed3 Unhandled Exception: EXCEPTION_ACCESS_VIOLATION writing address 0xffffffffa12313f9 TrainSimWorldPublicEditor_UnrealEd TrainSimWorldPublicEditor_UnrealEd TrainSimWorldPublicEditor_AssetTools TrainSimWorldPublicEditor_AssetTools TrainSimWorldPublicEditor_UnrealEd TrainSimWorldPublicEditor_UnrealEd TrainSimWorldPublicEditor_Engine TrainSimWorldPublicEditor_Engine TrainSimWorldPublicEditor_UnrealEd TrainSimWorldPublicEditor_UnrealEd TrainSimWorldPublicEditor_TS2PrototypeEditor TrainSimWorldPublicEditor TrainSimWorldPublicEditor TrainSimWorldPublicEditor TrainSimWorldPublicEditor TrainSimWorldPublicEditor kernel32 ntdll Now I probably know the issue and it could be the file sizes but this is how QGIS created them and I have no idea if I can compress the file size. The route is (Totton) Southampton Central to Portsmouth Harbour via Netley currently 29.1miles (46.9Km), with a planned extension of Southampton to Portsmouth Harbour via Eastleigh. Any advice on how I can get around this error message? I have tried Googling it but it's not offering much as this is a cut down or edited version of UE4.
You need to split this into (many!!) tiles. I think you forgot to click on create VRT or so? Please have a look at Lukas stream again.
I had the VRT ticked, however I had it set to 30,000 tiles instead of 3,000 . Just changed it to 3000 tiles and now importing. Thank you
I watched the stream carefully and worked accordingly. To my surprise, it worked... Terrain around Prague - Zbraslav, Czech Republic... ;-)
OK, I'm very much close now to pulling out my remaining hair, I just can't understand what is going on! I've followed this video three times this weekend and still cannot import anything correctly. I imported the KML file but it was just sea level flat so I thought, OK, must be another step along the way but nope, is there something I missed no height what so ever? Imported the Lidar data and still it rises up in squares even though everything is around Southampton. I'm still using Defra (UK Gov) LIDAR COMPOSIT DTM 1m 2022 KML File KML Route in Google Earth Lidar data My selected LIDAR areas and saved as ASC I might get to the point of just paying someone to do this bit for me because I have no idea anymore?!?!
It's weird that in the explorer the file extension is .asc and not .uasset. Did you import the asc files by drag and dropping them in the editor or by just moving them in windows explorer?
But they weren't in the same folder before? I mean you didn't drag them from the source folder in windows explorer to the source folder in the editor which represents the same folder? Because my tiles are all .uasset files. I don't know if that's the problem.
I may of done... I told QGIS to save to F:\Program Files\Epic\TrainSimWorld4MOD\TS2Prototype\Content\Developers\Zeo2113\SouthamptonPortsmouth\lidar\source and then imported by drop/drag into the source folder in Editor, which is also the same pathway.
I first noticed the huge blocks after I had loaded several tiles correctly but I had restarted the editor in the meantime. When you close the editor it doesn't save the Lidar data in the source files in the route building tab so I was applying blank data to the landscape. Once you have the LIdar data in the folder you have to select all of the files in that folder m and then Click on the "Use selected assets" button. I had 236 lidar tiles so it takes a long time to load but they will appear in the "Lidar Source Data" on the left hand side. Then you can "Apply Lidar data to selected tiles". I've found you have to repeat this step if you lay more tiles after leaving and re-entering the editor otherwise you get the thousand foot tall blocks. In fact once I reload the data I can click on the tall block and it will apply the correct tile. Don't know if this will help Zeo 2113's problem but that's when I experienced the huge blocks.
Right, I've gone back through the whole process and managed to get the editor to convert them to UASSET files (Including the KML) but still getting the blocks. I'm starting to think this could just be an unlucky bug for me and that I might just uninstall it all, remove EVERYTHING and try again, at least I have a week off after next weekend so I can spend more time on it. Below should be Southampton Central to St Denys but looks like nothing like it! lol.
@Zeo I think it's a projecting issue, either like the post above suggest or your process in qgis. And since you are close to the sea, also be aware, there is a sealevelbug atm, I believe its on a fix list as Matt have talked about in on stream. It will give high rise of terrain where Lidar data gives sealevel.
Some good news on the horizon everyone approx 18 hours later, and 54 pages (with Pics) The guide i'm working on is nearing completion, I've just finished my Qgis section and starting my Importing of Lidar to the editor section. Once that's done I'll have a quick scan through then post a link on the forums (probably make a new thread). Over the next week I'll be tweaking it up a bit with any feedback I get, adding an Index page, Dedication page and Glossary. I'll be Adding headers and sub headers to help with finding specific sections, checking for grammar and spelling errors and then post a link to the updated version.
Got my Guide ready to Share I can't upload the file here as it says its too large in .pdf format. My wife tried the link i had to the document on my google drive but couldn't access it because she doesn't have google docs Is there anyone that can help
Hi, I followed the stream, tested it, and it works. But I have a problem with my source files. My tiles, instead of just displaying the terrain, are a mixed point cloud. I probably didn't do the conversion well at first. I used COPC (Cloud Optimized Point Cloud) files which are in .LAZ (downloadable LIDAR data in France). Does anyone know if there is a simple method in QGIS to convert just the terrain to a .tif file to achieve the result as Lukas shows in the video?
You can convert .laz to .tif using Lastools in QGIS. You need to download Lastools first and google how to install it as it isn't as straight forward if I remember right. Then you can convert the files. Lastools will put a diagonal through your tif files if the laz file contains too many points unless you pay. To circumvent this, I use the lasgrid tool. For some reason it doesn't put the diagonal there then. But how you need to use the tools depends on your data.
Thank you for your answer. Yes I did my conversion with Lastools, but for sure, I had to follow a wrong way by converting all the layers of the original file. I tested another technic using Lasground to just isolate the terrain and indeed the results I get are a .tif file with a diagonal. I didn't know about Lasgrid, I'm going to see if it can remove this diagonal.
Well I've found what I had forgotten, I didn't add the "-keep_class 2" parameter, whether on lasground or las2dem, to isolate only the ground. Lulon : according to the information I was able to find, to avoid the diagonal, you must limit the size to "1 million points". I haven't tried lasgrid tool, but there is also blast2dem which accepts a size up to 6 million points. This is my next step. Another possible method with QGIS, but I don't recommend it at the moment, because I have some rendering issues. I converted my .LAZ tiles (depends on the format of your LIDAR source, in France they are classified into several classes; ground, water, folliages, buildings...) using the QGIS tool "Point Cloud conversion/Export to raster", add the classification parameter = 2 (ground), you obtain a tile in .tif format. You then have to fill the holes with "fillNodata", but here I have some display bugs. Once all the tiles are assembled, Lukas' tutorial works well, but as said, when putting 3000 per 3000 for the tiles size "FillNodata" gives a bad rendering at some corners...which generates distortions of the ground once imported into the editor.
Another 6 hours, another 2 times of following this guide TO THE T! This time, I just did Salisbury to Romsey 19.5 Miles (31.4Km), a brand new route after reinstalling the world editor, avoiding the costal areas at all costs and still not getting any height data into the game from Google Earth Pro via the KML file. Can someone else try the Salisbury, Southampton or Portsmouth area? I just want to see if it's me or if it's a bug in this area of the map that height data doesn't exist or something. Which is rather silly to be honest as I managed to get height data in before but now I can't do it at all.
DonnyDave, your guide for UK routes is amazing! Followed it step by step and I've finally got Southampton Central in. You legend and thank you everyone for your help as well
My F Drive just bloated and can no longer open or save anything. Do I have to keep the LIDAR folder, Merged.tif and Reprojected.tif? Can I save them to an external drive in case I need them for the future? Just FYI, this is a 500GB SSD with nothing on it other than TSW4 and TSW4 editor.
No, you don't have to keep any data. You can delete the reprojected and merged files. They are only useful if you want to repeat the process for example with different parameters without merging and reprojecting again. You can also delete the tiled tif files as they are copied anyway when you import them into the editor. You can even delete the imported tiles if they have been applied to the landscape already because they actually have nothing to do with the landscape (AFAIK). It's just for applying. But I prefer keeping them in case I want to reset the terrain.
Hi all, As the native LiDAR files are well sized for my needs (1000x1000), I managed to simplify the workflow and avoid the merging and tiling steps. It even seems to generate less severe artifacts at boundaries, easily evened out with the smoothing tool. The only step I couldn't manage to bypass (apart of selecting the right native tiles) is the reprojection from the native CRS to WGS 84 Pseudo Mercator. QGIS handles this quite nicely, yet feels a bit bloatware-ish for just batch reprojections. I wonder if lighter, command-line alternatives exist – in case someone finds the drive to create a lighweight, portable & efficient utility for us simmers. Cheers, Mat
You could do the whole re-projection in GDAL. With just the comand line only. Using a Batch File. I would need to figure it all out first. I just know it is possible.
What you would do, is install the latest GDAL Library and tools, from https://gdal.org/download.html And follow the instructions to get it onto your command line. They made it pretty complex to set up, to get it set up right you almost have to compile it from source. Thst why its better to use QGIS. But there is a way to automate the whole process with or without QGIS using batch script(s) I need to loook into it a bit more.
So after fooling around with the editor for the last 10 hours, I finally managed to get the lidar working somewhat. My route is in a city, but I have all these random blobs, spikes and walls thats going to make it impossible to get the actual landscape down. Does anyone have any ideas? I know someone here said to put a select command in QGIS to remove everything but elevation data, but would that even fix this?
up to now a lot of of time I wasted was trying to find easier ways of doing things. so now I just go along with tried and tested. when it comes to qgis I just follow my guide, but I've done lidar for 4 different routes I want to do and it don't seem much of a drag anymore.
just go through the process of getting your lidar, and add that. The kml for my second route terrain seemed flat but after adding lidar it all changed showing hills and the valley
I'd try your route but it won't be till Friday night cos its 2.43 am now goin bed soon, out all day and out tomorrow most of the day too
Looks like the buildings are included in the LIDAR? When you download LIDAR tiles, there are usually two download options: DEM (Digital Elevation Model) which is only the landscape DSM (Digital Surface Model) which is the landscape and also buildings
The only options I see for my area (in New Jersey) is the LiDAR data I used for this. Is there another site I’m suppose to be using?
I don't know which site you're using or what the data you're using is called. If it's called DEM, then it should be right. You could check in QGIS whether your heightmap looks like it has buildings and trees. If it doesn't look like it has buildings in QGIS then I don't know why there are those bumps in your landscape. But because your roads and rails are flat I thought maybe it's because your LIDAR data contains buildings and trees. Still wouldn't explain the spikes...
Hi, I am not an expert in the matter, but I got the same issue at first, this is because you have probably use QGIS to make an average of your source file, which is probably a multi-rasters of Point Cloud Datas. So the buildings and other stuff like the trees are merged together. If your original format is a file with the .LAZ extension, you have to first split them to reduce the size (6000000 points is the max in QGIS without getting the license). After you convert the LAZ/LAS to a Geotiff, make sure you selected the Class 2 in order to have the ground only. Thus, ones you have a .tif file with just the ground (DEM), you can follow the procedure as mentioned in the tutorial. In my situation, I followed the stream : Also, don't hesitate to look for tutorials on the principles of conversions with QGIS, you will definitely find what you are looking for. Hope it helps
in what step of the tutorial do I select Class 2 only, if you can also point me to the tool I have to use.
This step isn't in TSW tutorial, it is part of the process from QGIS or other tools, to convert your source files. In my case I used Lastools, but you have to install this Plugin into QGIS first. Then I used lassplit to reduce the size of one tile which convert the .LAZ into a .LAS, after that, the tool blast2demPro or las2demPro (depending of the size of your tile) will convert the .LAS in TIF, where you put here the Class filter "keep_class 2". See this video, it gives a good example of the process :
Once you have successfully converted your source files, isolated the terrain to tiles in ".tif" format, you can now follow the tutorial from Lulon starting at step 3. I mean; merge all your tiles, modify the CRS... Always make sure your tiles are in the correct position compared to the world map.
For LASSplit & LAS2DemPro, what were the parameters you used? And how do you run it as a batch for 40 tiles?
Thanks for the suggestion! I tried this afternoon but for some reason the output .asc files are shifted a few hundred metres to the West, despite the use of the exact same EPSG codes at those I've set in QGIS. I'm quite sure the files converted from QGIS are the correct ones thanks to the GMaps overlay and to the lower-res SRTM terrain. It's a pity because the whole package would have only weighted about 60 MB. [New thought] I can't see why but it may be caused by the output resolution which is 1.404something instead of 1.000000. I'll try to figure this out. Sure. [EDIT: the following method still ends up in boundary glitches, so the main method may be preferable for you.] Make sure you know for certain the Coordinate Reference System of your LiDAR data. This shoud be provided with the LiDAR dataset you've retrieved. For instance, if you are interested in French RGE ALTI data, appendix C of the corresponding content description manual says: EPSG code 2154 for continental France. You don't need to have your LiDAR files loaded in QGIS. You just need to know in which folder they are stored. Go to the Raster menu > Projections > Warp (Reprojects)..., then click the Run as Batch Process... button at the bottom of the window. In the Input layer column, click Autofill... > Select Files... (or Add All Files from a Directory... depending on what you plan on doing, just keep in mind that it will also include the contents of all subfolders). Select the LiDAR file(s) (or their folder), then click OK. One row is then created for each of the files you wish to convert. Now we will only need to set the parameters of the first row, as it will be possible to apply them to all other rows afterwards. In the Source CRS column, click the Select CRS icon. The window now shows the CRS selection tool. In the drop-down menu at the top, select Predefined CRS. Find the source CRS of your LiDAR dataset in the list; you may want to use the Filter text field as you know for sure the identifiers for the CRS of your dataset (see step 1). Following my example I can type "2154" to find the CRS valid for continental France. Click the blue triangle in the upper left corner to get back to the file list. Do the same for the Target CRS but now you'll have to choose the EPSG:3857 (WGS 84 / Pseudo Mercator) GPS for the converted files to be compatible with the TSW4 editor. In column Resampling method to use, you may want to replace Nearest Neighbour with something more refined e.g. Cubic – I've read that it's a good compromise between conversion speed and quality. Again, no need to change more than just the first row. Column Nodata value for output bands can be left as is. In column Output file resolution (etc.), type 1 and press Enter. In the last column (Reprojected), click the "..." button, navigate to the destination folder of the converted files, type a short prefix you would like to see appended to the name of your files, select the .asc format, and then click Save. An Autofill settings window pops out. Select Fill with parameter values in the first drop-down menu and click OK. For all columns but the first and last ones, click the Autofill... header > Fill Down. It should do as it says. Now everything's looking nice and ready, click the Run button. Once the conversion process is finished, look for all your TSW4 ready LiDAR files in the destination folder set at step 11. All .prj files may be deleted. Cheers, Mat
