benu 1 Posted June 11, 2004 After one ugly failure and CTDs using a-lone-wolfs config.cpp i tried to use BIS commented config 191 for a "modding ecp project". It seems there is a manVehActions.hpp in there that does not get included at all in BIS config.cpp?!? And manActions.hpp gets included twice, once in cfgMoves.hpp and once in cfgVehicles.hpp, as does woundsFace.hpp. Is this correct and as it should be? I'd also like to know which config.cpp the mod teams are using. As i had no problem generating a patch file with the unix diff command and applying it to a-l-ws config.cpp, but applying it to BIS' config.cpp fails and i have to edit most of the changes manually now. Wouldn't it be better if there was one official config.cpp that all modders would base their projects on so that comparing/changing/integrating them could be helped by automated processes? And something else i asked myself along those lines is: why is there no bin2cpp tool that is actually working with flaws? Or is there? Can't be too hard to get the last errors out off eg unpbo 1.3, or can it? I would be happy if anyone could point me to some info about what cpp2bin does or even a working bin2cpp tool. Share this post Link to post Share on other sites