Welcome to Steelbeasts.com

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

DarkAngel

Members
  • Content count

    1,636
  • Joined

  • Last visited

4 Followers

About DarkAngel

  • Rank
    Senior Member
  • Birthday 09/01/1965

Personal Information

  • Location
    NE Tasmania
  • Interests
    Models, Reading, Computer games
  • Occupation
    Computer Tech
  1. Not I as I still have it installed.
  2. Best moment for me with cold waters so far was wiping it off my HDD.
  3. I'm not exactly sure why you are quoting me here. I was just explaining to Nike Ajax why its unlikely you will see LIDAR data based maps (for the community), at least in the short term. I'm not going to be making anymore community request maps until the New Terrain engine is closer to release. Partly because I don't have the time at the moment. The other factor is that there is little point making maps for 4.x, with the NTE they will all need converting to new formats. I have enough of those to do without making more work for myself. For me the map making process is this:- Accumulate Data. For a standard map I go and collect the data I need Height data from SRTM or NED/NEMA (10M US data). For Vector data my first stop tends to be Open street map or one of its data access sites. Process data. This is to make sure it is all in the right projection also to separate the data types into their relevant categories (Roads, rail, buildings, terrain types). I remove any extraneous data and then aggregate the data into similar types (SB types that is). Create the Heightmap in SB Pro, Load a theme and import the basic terrain types ( separated in stage 2) Load the map as created in stage 3 into my SB mapper Pro program. In there I can import Roads and have them automatically join sections together. This is a necessary step which used to be a long and tedious task. In SB mapper Pro I can also import walls and, if the data contains suitable data, import building files. Various tweaks and effects can be added too if i want, again using SB mapper pro.
  4. Hmmm LIDAR is sort of a mixed bag. It takes quite a bit of grunt to process it (preparing for an sb map). There is not a lot of it available in the public domain, some countries make the data available (Sweden and a couple of others). The map sizes are going to be HUGE unless it is a very small map.
  5. One thing you might want to check too. When using a jump to end route which ends in a battle position it is best to make the route multi node and have the last leg in the direction you want the unit facing. This may have been fixed but it always used to be the case. Because instead of spawning at that BP they are Arriving at it.
  6. no it generates a new number for each route check
  7. You need to make one of them conditioned so it will always work. You don't need to put the different numbers in them. You just need 0 < new <25. Butt you will always need one route which it will default to.
  8. Noob. Slap yourself!!!. Each route has its own new variable
  9. alt-T to retrieve.
  10. Should be fixed for next version.
  11. The second one is known. First one may be... I will check thanks!.
  12. OK thanks... we will look into it.
  13. Is this in 4.019?.
  14. OK thanks
  15. isn't this the one you have reported before?.