Jump to content

DarkAngel

Members
  • Posts

    2,098
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by DarkAngel

  1. I t might be nice also to aggregate PC carried infantry kills into the PC kill if it died with it's infantry on board.
  2. Think it may be interesting to narrow things down further. So for example with Kills on tanks he may be interesting to see this broken down further into "what" caused the kill ie Infantry (rpg), Infantry ATGM, Tank, APC etc Also you may want to check the totals... I'm not convinced there were 158 kills in that mission (I could be wrong). Are you sure you aren't getting hits on things which are already dead?.
  3. Played this scenario (a lot), we often play them during testing. There are a couple of really good positions. First is there is a small hill near the ( bracket of Matzmed (North) text . There is another one near your waypoint 20 but on the road in a hull down position.
  4. Your best bet with a map is to start with a generic theme of the type of map you want ( Woodland, desert, tropical, arid etc). Then to tailor the theme to how you want the base map to look. Then if you want things like "Winter", "Autumn", "Summer" etc themes for it create those based on the base theme and upload the themes with the map.
  5. I can probably do some of it for you. As long as you are not in a rush. You would have to group the buildings shape files into categories of SB buildings with maybe some indications of what actual buildings to use. The only bit i couldn't do is import the Lidar data, my internet is terrible and I couldn't deal with downloading and uploading 20gb of data. If I made a base map at 12m resolution maybe DK could import the LIDAR data for you as he has a fast internet connection.
  6. I thought there was a difference between canister and Beehive. Beehive explodes at a set distance.
  7. Don't forget that TGIF is an hour earlier if you are in EU or Australia!!
  8. I wouldn't trust an auto join system in any of the GIS programs i've used. Maybe what you are using is better that what i've tried, all of those use a first pass connect system which does a woefully inadequate job of joining lines for roads. Terrain from landsat is ok if you like pixelated edges to everything, not worth bothering with in my estimation which is why I made my own system for doing it. So the only thing you are going to save time on is the bocage and you would want to hope your GIS software has a good join and simplify routine if you want the game to run with that data imported. The real issue with map creation is buildings and there is no easy, quick way to do that with the SB import tools.
  9. I really don't know where you get this idea that the work could be done in a "Mere fraction of the time" from. I did try to explain that the Pro editor is exactly the same as the Pro PE editor apart from the import tools. I can assure you the import tools do not open the door to maps in a "Mere fraction of the time". As I previously said the point data for building import does not contain building type or orientation unless someone puts it in there, manually, in a GIS program. On a big map area that could mean manually editing 500,000 point objects. You think this is quicker than the way you do it in the map editor?. Now maybe some data sets do contain this information, I have certainly not seen such in the public domain!. What about joining all the little road segments up into contiguous lines.. You think that is trivial?. I did a hell of a lot of it (and manual digitizing) before I came up with my own tools to make it easier. Pro import tools certainly won't do that for you either. So you have to manually do that in a GIS program, that does not happen in a "Mere fraction of the time". If you think LIDAR data (from the public domain) is going to fix all your issues think again. You have obviously not seen the amount of noise that is in it, nor how badly it lines up with public domain vector data!.
  10. I love how this topic started as a thank you to map makers and turned into complaining about the import functions not being in Pro PE
  11. Most of the lidar data I've seen isn't worth using TBH, it is terribly noisy. Even the DTM Lidar data which cuts "most" of the trees and vegetation out does not cut out the noise from buildings, bridges and parked vehicles.
  12. It definitely isn't that simple. For a lot of functions the pro editor and the Basic editor are the same apart from the import tools. I can assure you the import tools do not do everything for you. In your example all you could get for building data is points. These do not set the orientation of the buildings. Plus you would have to go through and manually set types to them all. In regards to roads, a straight output to SB is not a good idea. Most of the datasets split roads at every junction. To make this SB compatible you would have to spend hundreds of hours joining all the segments up to make contiguous roads for SB. The maps I make for requests are made using a piece of software I wrote myself which does a lot of the heavy lifting from what i said above. I wrote into it a double check road joining routine. I also wrote a very complex piece of code which takes building shape files (as areas) and tries to determine the orientation and closest match building type based on these shapes. This software took me many thousands of hours to write.
×
×
  • Create New...