config.cpp is not read unpacked

[alef]

http://community.bistudio.com/wiki/CMA:DevelopmentSetup#Develop_with_unpacked_data

My target for now is
tweaking config.cpp only
not going to binarize nor packing PBOs
not going to setup P: drive

My actual folders for unpacked data
H:\arma\2\1.02.58134
bin
ca
core
languagecore


Then, junctions are setup from these direcotries into my installation
E:\ArmA2
bin
ca
core
languagecore

With procmon (http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx), I can see arma2.exe reading the PBOs and the unpacked data (H:\arma\2\1.02.58134), but the unpacked config.cpp are not read.

My conclusion is the config.cpp, both at $PBOPREFIX$ root level or any other in subfolders, are not read unpacked.

Now, if I remove the relative .pbo file, for example E:\ArmA2\addons\air2.pbo, then the game doesn't use it at all, i.e I get the message"this mission can't be edited, was based on missing content bla bla", something like that.

Is there a way I can tweak unpacked config.cpp entries? It's something I've missed?

[Sickboy]

In my experience, you can only edit files which exist in the PBO that represents this folder.
In case of original arma pbo's, there is no config.cpp in the PBO's, there is only config.bin.
This is not a problem when you work on your own addons, unless you binarize them.

The only thing I can think of right now, is to unpack all arma addons with extractPBO by Mikero (with auto-derapification).
Then repbo them with another tool by Mikero (but disabling auto-rapification), thus your arma2 addons will actually contain config.cpp's instead of bin.

I have no experience with the PBO's available under the dta folder, but I think you override them correctly.

[alef]

The only thing I can think of right now, is to unpack all arma addons with extractPBO by Mikero (with auto-derapification).

I have forgot to say this is exactly how I got the unpacked data. extractallpbo.bat (+extractpbo.exe) from Mikero.


Then repbo them with another tool by Mikero (but disabling auto-rapification), thus your arma2 addons will actually contain config.cpp's instead of bin.
Ok. As I understood, config.cpp are not read because arma2.exe expect to see a config.bin, which is the one in the original .pbo.

------
binarizing edited config.cpp -> .bin works, thanks!