Jump to content

Szelf

Member
  • Content Count

    2
  • Joined

  • Last visited

  • Medals

Community Reputation

10 Good

About Szelf

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Szelf

    High resolution DEMs

    Confirm. For some areas ASTER GDEM is useless. But you should check it anyway - maybe you are lucky and this data will look acceptable. There is company that cleaned up ASTER data and sells it for 0.15$ / square kilometer ( Altis = Lemnos Island would cost about 180$ ) : http://www.intermap.com/data/nextmap-world-30 You may ask them for small sample to compare it with other DEM products. Or use this new SRTM ( you will not find anything better for free ). BTW: if someone is interested in HiRes DEMS from central Europe - Poland just published LIDAR data for almost the whole country ( resolution 1m ). Buildings, forests and bridges were removed - its just clean terrain. Here you may see WW2 artillery positions hidden in the forest ( along with trenches to the north east ) : http://mapy.geoportal.gov.pl/imap/?locale=en&gui=new&sessionID=1572976 This data costs about 0.5E / square kilometer and it may be great as a source for small detailed maps.
  2. Ahh, the good old floating point precision problem :) In short : object positions are (usually) represented using floating point data types ( google for IEEE-754 on wikipedia, this is my first post on the forum and I am not allowed to add any links at the moment ). The thing with floating point data type is that when the numbers are big, they lose precision. In computer graphics this starts to occur when object position coded in single precision floating point is more than 30 000 units ( usually meters ) from (0,0,0) point. And it starts to look like the position of the object is "quantified". Look at the video at 4:05 - the rifle looks like it moves for certain number of centimeters every frame - its movement is quantified. BIS should use double precision numbers to store the information about object position/rotation ( it looks like they do this for people in Arma 3 ). The problem for BIS is that they probably use single precision numbers in hundreds of places in their code ( rendering, networking, scripting, AI etc etc ). Big and painful code review is coming to poor developers :) EDIT : submitted as issue 19751 to feedback tracker. I also created a mission, that you can download from feedback tracker and check the issue yourself ( BTW : I found a small lake on a new VR map. It is located in NE corner ). I also checked that this problem touches only a soldier equipment. People ( and things that they carry on themselves ), vehicles and objects driven by physics are not affected by this issue. You can check it out by driving a kart in a mission and trying to push a chair.
×