falcon4:terrain:cateairbases
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
falcon4:terrain:cateairbases [2017/10/06 14:08] – http to https switch. snakeman | falcon4:terrain:cateairbases [2024/07/31 09:10] (current) – links added. snakeman | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Airbase Background Tiling and Leveling with CATE ====== | + | ====== |
+ | |||
+ | [[https:// | ||
This section instructs you to automatically tile airbase background tiles and level them by using [[falcon4: | This section instructs you to automatically tile airbase background tiles and level them by using [[falcon4: | ||
- | First you must export Airfields from Tacedit into a CSV file. Go to the Map View, then select the menu item **View -> View Objectives -> None**. Also I'm going with **View -> View Units -> None**. Then select one more time **View -> View Objectives -> Airfields**. Now zoom out to get ALL the airbases into the view screen. Then just use left mouse button to drag a box around ALL of the airbase objectives. Select Operation dialog pops up and click **Export Viewed** and save the list. | + | First you must export Airfields from Tacedit into a CSV file. Go to the Map View, then select the menu item **View -> View Objectives -> None**. Also I'm going with **View -> View Units -> None**. Then select one more time **View -> View Objectives -> Airfields**. Now zoom out to get ALL the airbases into the view screen. Then just use left mouse button to drag a box around ALL of the airbase objectives. Select Operation dialog pops up and click **Export Viewed** and save the list. |
Okay now you got CSV file with airbases. Feed this baby to CATE dir (or where ever) and fire up CATE, select the airbase rules (more on this later I think), load theater.L2 file and select new L2 file which you want to save. Now click Read data which time it should take few seconds to load the stuff up (time is relative to theater size, rule complexity and your computer speed), then click Update data and CATE updates the L2 data in memory. After its done (takes another while) click Save data. Done. | Okay now you got CSV file with airbases. Feed this baby to CATE dir (or where ever) and fire up CATE, select the airbase rules (more on this later I think), load theater.L2 file and select new L2 file which you want to save. Now click Read data which time it should take few seconds to load the stuff up (time is relative to theater size, rule complexity and your computer speed), then click Update data and CATE updates the L2 data in memory. After its done (takes another while) click Save data. Done. | ||
- | ====== Default Korean | + | ====== Default Korean |
The airbase coordinates comes from Tacedit exported CSV file, simple X/Y coordinate. In our example images we have marked the coordinate with X and the other airbase tiles with O's. Lets begin. | The airbase coordinates comes from Tacedit exported CSV file, simple X/Y coordinate. In our example images we have marked the coordinate with X and the other airbase tiles with O's. Lets begin. | ||
Line 17: | Line 19: | ||
< | < | ||
OO | OO | ||
- | XOO | + | XOO |
OO | OO | ||
</ | </ | ||
Line 114: | Line 116: | ||
====== 21_03 ====== | ====== 21_03 ====== | ||
- | Airbase subtype **21_03** - tiles: 848-853 (coord tile: 850). | + | Airbase subtype **21_03** - tiles: 848-853 (coord tile: 850). |
< | < | ||
Line 405: | Line 407: | ||
If you want to use these airbases in Tacedit after getting datas from Dem2Terrain CSV creation, just export the airbase list and edit the csv file with text editor, change the Airbase substrings and OCD ID's to your theater specifications. | If you want to use these airbases in Tacedit after getting datas from Dem2Terrain CSV creation, just export the airbase list and edit the csv file with text editor, change the Airbase substrings and OCD ID's to your theater specifications. | ||
+ |
falcon4/terrain/cateairbases.1507298934.txt.gz · Last modified: 2017/10/06 14:08 by snakeman