tacedit - import/export

F4Browse, CATE, Tacedit, Terrainview & TheaterMaker etc utility related

Moderators: Snake Man, Lone Wolf

Post Reply
User avatar
Luk
Brig. General
Posts: 455
Joined: 2007-04-23, 09:59:36 AM

tacedit - import/export

Post by Luk » 2010-06-29, 10:29:42 PM

Hi, I have quite noob question.
Is it possible to import previously exported objectives back into the tacedit? (I changed some settings/flags)

I have tried it, but I think it does not work.
Perhaps the "csv file for import" should have very different structure compared to "export type csv".
But there is some info in tacedit help - I catch on to it is possible to import previously exported file (exactly the same).

This is from tacedit help :

Code: Select all

Objective Import format
There are two forms of import for objectives. The first is aimed at preserving all the details, and is the format output by the export command. The other is aimed at programs that generate lists of objectives, and take the minimum details, and fill in the rest. They are distinguished by the first line of the file. Both are in comma separated variable (CSV) format. The first line being the type, the 2nd line being a list of field names (which is ignored by the import process). 

1.0 Objective Export 
Name, 
Type, 
Subtype 
ID, 
Objective, 
X, 
Y, 
Z, 
STime, 
SFlag, 
BFlags, 
Owner, 
XID, 
LastRep, 
OFlags, 
Supply, 
Fuel, 
Losses, 
FCount, 
Priority, 
Parent, 
FOwner, 
LCount, 
Features, 
Links, 
Radar, 
2.0 Objective GenerateThis format covers the minimum range more used for generation. The fields are in order: 
name - either a string, or a number. If a number it is an index into the theater strings directly. A string is looked up in the list of theater strings, and if present is used, else a new string is added to the list. 
id - what F4 Id this object will have. 
objid - which objective ID this is - a reference to the CT table. 
x - x location 
y - y location 
z - elevation (usually 0) 
owner - current owner of the objective - a team numer 0-7 
campid - campain ID - usually same as F4Id 
parent - the F4Id of the parent object - use 0 if no parent. 
priority - the priority of this - range 0-100. 
This is info from PMC wiki:
Objectives → Export Objectives
Exports all objectives into a CSV file.

Objectives → Import Objectives
Imports new set of objectives from a CSV file. Make sure your campaign is empty if you are importing fresh full CSV file, or if you only import partial new objects then you can proceed with existing objectives loaded.
-------------------------------------------
BTW: what does mean this tacedit warning : "Warning - objectives in this file as well as base file!"

Thanks.
Luk

Snake Man
Commander-In-Chief
Posts: 8561
Joined: 2000-07-31, 10:01:01 PM
Gaming Interests: ArmA, ArmA 2, Falcon 4.0 and OFP.
Editing Interests: All, I (try) to edit everything.
Location: PMC

Re: tacedit - import/export

Post by Snake Man » 2010-06-30, 09:56:40 AM

Yes you can import back the objectives you exported earlier. Of course you need to delete the objectives in tacedit first, so you don't import them on top of the existing ones.

Can you show like 3-4 lines of this CSV file you edited?
PMC since 1984

Editing knowledge, visit PMC Editing Wiki
Addon manuals, visit PMC addons/mods online manuals
View our videos in PMC Youtube channel.

PMC Tactical forum Advanced Search is power.

User avatar
Luk
Brig. General
Posts: 455
Joined: 2007-04-23, 09:59:36 AM

Re: tacedit - import/export

Post by Luk » 2010-06-30, 02:10:15 PM

Of course you need to delete the objectives in tacedit first, so you don't import them on top of the existing ones.
Yes, of course I deleted them.
Can you show like 3-4 lines of this CSV file you edited?
Some few upper rows of csv to import:

Code: Select all

1.0 Objective Export Tue Jun 29 11:50:30 2010
Name, Type, Subtype, ID, Objective, X, Y, Z, STime, SFlag, BFlags, Owner, XID, LastRep, OFlags, Supply, Fuel, Losses, FCount, Priority, Parent, FOwner, LCount, Features, Links, Radar, More-Field27, Field-Field28, Header-Field29, Names-Field30, To-Field31, Keep-Field32, Access-Field33, And-Field34, Others-Field35, Happy-Field36, Field37, Field38, Field39, Field40, Field41, Field42, Field43, Field44, Field45, Field46, Field47, Field48, Field49, Field50, Field51, Field52, Field53, Field54, Field55, Field56, Field57, Field58, Field59, Field60, Field61, Field62, Field63, Field64, Field65, Field66, Field67, Field68, Field69, Field70, Field71, Field72, Field73, Field74, Field75, Field76, Field77, Field78, Field79, Field80, Field81, Field82, Field83, Field84, Field85, Field86, Field87, Field88, Field89, Field90, Field91, Field92, Field93, Field94, Field95, Field96, Field97, Field98, Field99, Field100, 
Tampere Pirkkala, Airbase, 08_26 Airbase Rvr, 15331, 1774, 1801, 1959, 0, 0, 0, 0, 2, 15331, 0, 4310272, 235, 235, 0, 39, 50, 66, 2, 1, 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff, 20, 30, 30, 21, 12, 12, 255, 255, 66, 0.022, 0.022, 0.022, 0.022, 0.022, 0.022, 0.022, 0.022, 
Utti, Airbase, 08_26 Airbase Rvr, 15336, 1774, 1994, 1902, 0, 0, 0, 0, 2, 15336, 0, 4310272, 235, 235, 0, 39, 50, 155, 2, 2, 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff, 11, 23, 23, 15, 12, 12, 255, 255, 129, 26, 60, 60, 40, 34, 34, 255, 255, 125, 0.022, 0.022, 0.022, 0.022, 0.022, 0.022, 0.022, 0.022, 
Linz, Airbase, 08_26 Airbase Rvr, 15346, 1774, 1408, 493, 0, 0, 0, 0, 3, 15346, 0, 4310272, 235, 235, 0, 39, 50, 292, 3, 2, 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff, 11, 19, 19, 13, 7, 7, 255, 255, 327, 6, 19, 19, 14, 8, 8, 255, 255, 294, 0.09928, 0.13651, 0.156011, 0.109208, 0.0260164, 0.0390246, 0.0420265, 0.028755, 
Zeltweg AB, Airbase, 01_19 Airbase, 15351, 1772, 1458, 379, 0, 0, 0, 0, 3, 15351, 0, 4310272, 235, 235, 0, 37, 50, 533, 3, 3, 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff, 24, 140, 140, 93, 35, 32, 255, 255, 2718, 4, 4, 4, 2, 1, 1, 139, 139, 2871, 10, 21, 21, 14, 5, 5, 255, 255, 536, 0.108173, 0.118475, 0.165865, 0.118475, 0.0501431, 0.0966172, 0.0990327, 0.0707376, 
Graz, Airbase, 34_16 Airbase Rvr, 15352, 1783, 1512, 355, 0, 0, 0, 0, 3, 15352, 0, 4310272, 235, 235, 0, 46, 50, 559, 3, 5, 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff, 21, 60, 60, 40, 24, 23, 255, 255, 563, 8, 12, 12, 10, 5, 5, 255, 255, 561, 146, 157, 157, 151, 10, 10, 255, 255, 2711, 19, 54, 54, 36, 24, 23, 255, 255, 552, 18, 42, 42, 28, 16, 15, 255, 255, 2684, 0.042857, 0.0611426, 0.0849203, 0.0611426, 0.148794, 0.210062, 0.238071, 0.162321, 
You can see "ff" instead "0" in above sample. It was a purpose of this operation - export an unchecked portion (most of) of European ABs and set them to "destroyed". I supposed this export also destroy the linking (at least normal links). So unchecked imported ABs will be all destroyed and unlinked. Then I will go through these dump objectives and fix/change + "unlock"(repair) them.
It would be perhaps easier for me to add them as new objectives, but I want to respect your wish to not loose the old ones. Next thing is, it will also save "idx/wch" strings space. Non-essential ABs I can preserve for eventually future use. Some really bad/wrong(for example some club grassfield) airbases I can convert to willage/town with identical name - save names again.
Post edited: It would be better, convert them to forrest(hilltop) objectives. It is becouse they are not connected to the road network (I had to built a road throught 2 segments sometimes, when added new bases). Such a type of objective is just for apperance, no matter you cannot capture it - the Elfes still own the forrest, independently of the humans hassles anyway :wink: .
note: I tried to import unmodified csv as well. I did not see any imported objectives neither after tacedit restart...

BTW:
There is my substitution TXT file. Each AB objective type has its own amount of "0"/"ff". So I had to make the same number of substitution strings as is the number of AB subtypes:

Code: Select all

80x
Linz, Airbase, 08_26 Airbase Rvr,
 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0,
 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff,

15x
Zeltweg AB, Airbase, 01_19 Airbase,
 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0,
 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff,

19x
Graz, Airbase, 34_16 Airbase Rvr,
 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0,
 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff,

28x
Klagenfurt, Airbase, 11_29 Airbase,
 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0,
 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff,

45x
Brussels National, Airbase, 05_23 Airbase 2 Rvr,
 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0,
 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff,

11x
Bierset, Airbase, 23_05 Airbase 2 Rvr,
 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0,
 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff,

16x
Prague Ruzyne, Airbase, 02_20 Airbase 2 Rvr,
 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0,
 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff,

11x
Caslav (CENTOGRAF), Airbase, 32_14 Airbase Rvr,
 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0,
 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff,

7x
Brno-Turany (BOLERO), Airbase, 12_30 Airbase Rvr,
 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0,
 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff,

6x
Malacky, Airbase, 02_20 Airbase Rvr,
 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0,
 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff,

2x
Kastrup, Airbase, 20_02 Airbase 2 Rvr,
 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0,
 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff,

5x
Schiphol, Airbase, SEOUL AFB, 15515,
 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0,
 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff,

8x
Valkenburg, Airbase, 34_16 Airbase 2 Rvr, 15517
 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0,
 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff,

14x
Fritzlar, Airbase, 30_12 Airbase Rvr, 15812
 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0,
 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff,

7x
Sembach AB, Airstrip, Highway Strip EW, 15865,
 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0,
 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff,

2x
Szeged, Airstrip, Highway Strip NS, 15973
 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0,
 1 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff,

.....

Of course it would be easier to select the objectives by window in tacedit and push the "destroy" button for all of them. But it is not possible in my opinion. Perhaps there is some elegant way to do it by "tcl" script. But I dont handle this powerful language at the moment :mrgreen:
The positive thing is, that used subtitutions led me to leave the club of "sick women" - I used windows notepad before. But I was not able to substitute longer strings used by some ABs. I had convert to notepad ++ and it is really good.

Luk
Last edited by Luk on 2010-07-02, 10:20:11 AM, edited 2 times in total.

User avatar
Luk
Brig. General
Posts: 455
Joined: 2007-04-23, 09:59:36 AM

Re: tacedit - import/export

Post by Luk » 2010-06-30, 06:41:55 PM

note:
I tried to import just one row - Linz AB
It worked fine.
Import of "type no.1 CSV file (complex one)" does not destroy links. Links among objectives are preserved, also parent links are preserved - all informations are saved in CSV.

I also tried big file import again and it did nothing.
I tried 20 ABs import and it worked fine (Objective have all flags + links and are "destroyed").

It looks 289 rows file is too big for some reason. Or there is another unknow problem.
I will experiment with it.
-----------
It looks, before mentioned report "Warning - objectives in this file as well as base file!" has nothing to do with my imports.
It also occured when I just deleted some objectives by hand (used window created by mouse for selection).
I will take a look at it.
Luk

User avatar
Sherlock
Lt. General
Posts: 1167
Joined: 2006-05-24, 10:01:01 PM
Gaming Interests: Falcon 4.0
Editing Interests: All, I (try) to edit everything.
Location: Arizona, USA

Re: tacedit - import/export

Post by Sherlock » 2010-06-30, 10:05:43 PM

Wild thought Luk but could it be a bad objective in the exported csv data that is messing up everything after it?
Sherlock
Victurous te Saluto

User avatar
Luk
Brig. General
Posts: 455
Joined: 2007-04-23, 09:59:36 AM

Re: tacedit - import/export

Post by Luk » 2010-07-01, 10:33:48 AM

Wild thought Luk but could it be a bad objective in the exported csv data that is messing up everything after it?
It is possible Sherlock. I can try and noose loop around it. :twisted:

--------
I still try to understand and also to find, how the links are stored. Parent links are clear - there is a "Parent" field in csv file (stores ID of the parent objective). It was not big suprize for me. But what about the object linking?

This is part of CSV file - legend/description + stored values (Links starts 11 IMHO ...etc):

..Features, Links, Radar, More-Field27, Field-Field28, Header-Field29, Names-Field30, To-Field31, Keep-Field32, Access-Field33, And-Field34, Others-Field35, Happy-Field36,..

..destroyed features .. ff, 11, 19, 19, 13, 7, 7, 255, 255, 327, 6, 19, 19, 14, 8, 8, 255, 255, 294, 0.09928, ...nonintegral numbers continue..
(I posted very long legend - just becouse Happy-Field36 sounds funny to me...?)

The only linked objectives are:
Wels factory ID 327
Linz factory ID 294

So it looks each linked objective has its own chain of values
Wels factory ID 327
Static,Foot,Wheel,Track,Low Air,Air,Naval,Rail,Objective id
11, 19, 19, 13, 7, 7, 255, 255, 327
Linz factory ID 294
6, 19, 19, 14, 8, 8, 255, 255, 294

It looks all linkage info is stored in CSV. The most important is to do not mess objectives IDs. It would be possible to work on separated CAMs when respected some simple rules (since some stage when all objects are placed OR only 1 person is authorized to add new objectives OR each worker has its own range of objectives ID) separated by 100 for example(you can set it by base objective id). CAMs can be merged together than. This is a good new for me.

Luk

User avatar
Luk
Brig. General
Posts: 455
Joined: 2007-04-23, 09:59:36 AM

Re: tacedit - import/export

Post by Luk » 2010-07-01, 12:33:42 PM

Think I solved it. The key was mentioned warning/report. It looks, the name of CAM file is very very important for tacedit.
I guess all CAMs with different names, than "save0.cam" are handeled in different way. Some things are managed by objectives deltas and so on. Such a CAMs are handled as a difference between base CAM and its derivate.
I must make all backup in different directories/zips, not renaming the file.
It was a noob misstake.

The import was done in a second and everything looks fine.

Luk

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest