Use PAK explorer to extract files from “data.pak”.
Extract a file containing terrain height map data from ISDF mission 1 named “isdf01.ter“.
Use Terrain Explorer or ODL1WinterB4c to view the terrain file:
Extract the 512×512 px 8 bit grayscale height map and save as “isdf01Height8Bit.png”:
Use PhotoShop to save as a “isdf01Height8Bit.raw” file for improved compatibility with Unity.
Open Unity, create a 3D terrain object and in the settings scroll to the bottom where it says “Height Map: Import Raw…”
Note: When importing, use a height value of 15 and select ‘Flip Vertical’ option to match orientation with the original game. These settings are the result of some trial and error attempts.
Start Battlezone II ISDF mission 1
[CTRL]+[~] to open console.
[CTRL]+[E] to open editor.
sky.visibilityrange 5000 to increase visibility.
Use ‘+’ and ‘-‘ to zoom. Mouse touch edge of screen or use the minimap to pan.
For satellite view waypoint editor, press [SHIFT]+[F9] when in normal game view (not used here).
That is a pretty good match!
Important: Don’t bother trying to match up world units to meters. Just work with generic world units. If your objects and terrain are scaled too small, you will constantly find yourself working with decimal point values in translation, rotation and scale input fields. I had to ‘scale up ‘ my terrain from the default 500 x 500 width and height world units to 2500 x 2500 world units. Note that terrains don’t support scaling – you have to set an actual width and height in world units for the size of your terrain. If the Unity built-in icons for camera, lights, etc appear large it is an indication you are working on too small a scale; scale everything up to move away from decimal point input field values and nervous camera pan/zoom behaviour.