Thursday, March 29, 2018

ono sendai

On the tile front my next generation of .gltf terrain tiles feature matching 1K rgb and height maps.

The vertex per texel counts means no urgent need for bump map.

Recently Windows10 updgrade cycle began failing daily so I finally purchased new system drive, unplugged others and did a clean install.

With a basic development environment we begin baking tiles and find virtual memory configured as suspected in an unconfigured highly crashable state.

After several more crashes and restarts we end up hardcoding 100GB of new high performance SSD for swap space or in windows lingo minumum - maximum fixed virtual memory advanced performance settings

After only 1 day the old SSD feels sluggish and slow and the HD completely retarded. Never mind.

half baked tile cache configured with large virtual memory footprint

the more things change

As was made evident in March 2015 - I love monkey.

I am also continuing to support steamstub for BlitzMax - the unattributed 2D game compiler of champions.


Recent additions to the steamstub user group include:

The popular 2D counterstrike game CS2D

And the very cool 3030 Deathwar Redux

It is very humbling to see BlitzMax continue to shine as a development platform, it's completely anonymous presence glowing in the corner...

With very little notice the blitz archives moved from to where interestingly, they were indexed by googlebot in record time.

The good news this week is the available of amazon linux 2 instances featuring gcc 7.2.1 a big step up from the default instances featuring version 4.8.5.

My AWS linux2 instance recipe uses a small instance with 2GB and is now compiling my primary work binary pipelines and django server:

   sudo yum groupinstall "Development Tools"
   sudo amazon-linux-extras install python3
   sudo pip3 install django

The bad news is the free tier nano instance has too little memory and no swap space so after last months spend up on EC2 experiments a separate build machine is instanced to run on demand.\

As reference the following history represents basics of setting up an amazon linux 2 environment.

fresh ec2 history

[ec2-user@ip-172-31-6-102 build]$ history
    1  sudo yum update
    2  git
    3  sudo yum install git
    4  git clone
    5  ls aws-sdk-cpp/
    6  mkdir build
    7  cd build
    8  cmake ../aws-sdk-cpp/
    9  cmake ../aws-sdk-cpp/CMakeLists.txt
   10  sudo yum groupinstall "Development Tools"
   11  cmake
   12  sudo amazon-linux-extras install cmake
   13  cd ..
   14  pwd
   15  wget
   16  tarr -xvf cmake-3.11.0-rc3.tar.gz
   17  tar -xvf cmake-3.11.0-rc3.tar.gz
   18  cd cmake-3.11.0-rc3/
   19  ls
   20  ./bootstrap & make & make install
   21  ./bootstrap  &make -j8 & make install
   22  sudo make install
   23  cd ..
   24  cmake --version
   25  pwd
   26  cd build
   27  ls
   28  dir
   29  ls
   30  pwd
   31  cmake ../aws-sdk-cpp/
   32  sudo yum install zlib-devel
   33  sudo yum install openssl-devel
   34  sudo yum install curl-devel
   35  cmake ../aws-sdk-cpp/
   36  sudo yum install libpulse-devel
   37  make -j8
   38  history