mikero

hi kivi i haven't a clue what namespace is, it's bandied about a lot and means just about anything anyone wants it to mean. i rarely use binpbo for anything these days. it's a good proggie, but it's a little too clever by half, and can be a total pig because it spends most of it's time binarising EVERY config it can find on and in p:\everywhere as for p:\, the bottom line is that you MUST, repeat, MUST set it up to reflect *every* pbo of the arma2/oa/ or co / and or beta patches of the 'game' that you have. half measures will fail in frustrating ways. quite a few pbo's overclass the base configs that come with personal tools. Building without the full kitchen sink will generally produce 'interesting' results. firstly and obviously p:\ca\everything but what's not 'obvious' are the following p:\core (from dta) p:\bin (from dta) p:\langaugecore from dta i think p:\@ion_rte p:\@ion_rte_data p:\dta with a copy of product.bin (for buldozer) p:\anything\else bis suddenly decide to add to their current folder names and, you *must* copy languagecore.xml to \bin because binarise (not binpbo) get's it's knickers in a twist the *garanteed* way of setting up p: 'properly' for *any* engine is to use arma2p.cmd http://dev-heaven.net/projects/mikero-pbodll/files most of the hard work in there has been done by Dwarden, with a little contribution or two from me, mostly in providing deRapped rvmats and configs. and yes, ok, you have all your stuff on p: and aren't happy you have to pentruple disk size to accommodate all bis pbos but tuff and too bad. that's bis 'namespace' or in proper context \pboPrefix for you. i know i haven't properly answered your query re binpbo, but the above is first step. *most* other issues become obvious after the above has been done. hope that helpz

http://dev-heaven.net/projects/mikero-pbodll/files ConvertP3D.exe AnyOA.p3d 48 reverts operation arrowhead p3d files to Arma2 type 48 for use in bulldozer This is a FULL fix, not a patch from one signature to another. There are no known differences between 48 (arma2) and 49 (oa), except for some very minor architectural re-arrangments. This re-arrangement, may have resulted in an improved speed or efficiency of the model, or it may not. Regardless, the above exe creates a fully compatible p3d Enjoy ---------- Post added at 02:41 AM ---------- Previous post was at 02:36 AM ---------- MoveObject.exe AnyOA.p3d From\Here To\There revised exe corrects small issues with Arrowhead P3ds that have stagecounts so that it can be moved into any folder of choice

extractpbo/makepbo http://dev-heaven.net/projects/mikero-pbodll/files come with their own regkeys to get over this problem any time it occurs.

for examples structures_e.pbo? extractpbo.exe then, look at the config.cpp.cfgPatches for the name they use. pay particular attention to the $prefix$ it aint necessarily in the same pathways as arma2 ca

depbodll version 3.10 fixes this issue, along with associated problems with ConvertP3d.exe thanks for spotting this blunder Itax

moveobject has been around for some time now and pretty stable. i'd need a copy of that, specific p3d before it got changed, to proceed any further with this mike.andrew on skype

http://dev-heaven.net/projects/cwr2editor/files one thing you are forgetting is that missions from ofp require ofp islands. I would call that, a total mod, any way you look at it. however, in regards to ofp models ONLY (buildings, plants, etc) see above link

The venerable Editor103 for Operation Flashpoint has been released for ArmA2 CWR2Editor is fully compatible with all previous versions of this (almost mandatory) addon for flashpoint missions. you do not need the CWR2 mod nor any other flashpoint sensitive addons to start using the 500++ models from Resistance and ColdWarCrisis in your A2 missions. Note that Editor103 alias CWR2Editor does NOT include genuine vehicles or soldiers and never did. http://dev-heaven.net/projects/cwr2editor/files Mirror: http://213.245.0.237/mikero/ Enjoy

the mirror mentioned above contains un-split files. LST addons for ofp are just that. They are unique models not in the original games. the editor103 on the other hand exposes the 500+ models that ARE in the official game but were never made available via config.cpp. I am unaware of anyone having converted lst pbo's to arma. the tools to do so however exist at http://dev-heaven.net/projects/mikero-pbodll/files

this is a DOS CONSOLE APPLICATION you need to be in dos (the command prompt window) for any magic to happen.

1) install the dll in the same folder as the exe OR put it, the dll, in windows\system32 2)use a command prompt dos console 3) \wherever\you\put\moveobject.exe \whatever\p3d\you\want.p3d voila NB: there is a fairly active 'bug-report' for this and the other dostools at dev-heaven. t_d or myself are likely to respond very quickly if you post a message in there

Mission 'voices' as i understand it, it is not so much the 'voice' or the 'voice' quality you are mentioning, it is the voice 'phrases' that are missing. As an example, the fact is, even if, the original phrase 'you're late armstrong' was provided, from ofp, there is nowhere in this mission (or campaign) where it is used! we converted elite missions and campaigns for cwr rather than use the oiginal ofp missions and campaigns. Hindsight being that marvellous thing, we now know that was a mistake, but, at the time of what has turnned out to be a huge devel effort, we took path of least resistance. What i am saying is, it's not just a question of providing (access to) a phrase.wss file, but inserting it in the mission itself so that it's useable. If there's no context (anymore) in the mission to 'say' "you're late armstrong" we would either have to 1) create one by re-writing the mission or 2) simply covert the original ofp mission. Duh! oh and btw , Wolle mentions cpbo, my ego demands that i mention ExtractPbo as an alternative, since it, and it's sister MakePbo are what is used on the cwr devel site, so it probably works a little better. :cool:

http://andrew.nf/ofp/tools new versions of eliteness2.23 dostools1.42 depbodll 1.62 Major improvements above are (mostly) to do with ArmA better include path statements (very different to ofp) arma sensitive #defines (not quite as powerful as ofp, in cpp mode) more aggressive lint checking (arma *loves* semicolons) will now create bisignatures for MP play rapified (binarised) rvmat files and lintchecking among other things ....

the bottom line is you will have to write c# code to extract, at the very least, the header information of a pbo. the header contains filename and file size for each data block in the pbo the way to do that, is of course up to you in C# code, but the structure of the pbo, and what you're needing to fread() is at the above link. alternatively. you can use my depbo.dll. which as the name suggests does it for you and you just use API calls into the dll to get at what you want. mikero@norfolk.nf if you need further info (the dll's header file eg)

the bottom line is you will have to write c# code to extract, at the very least, the header information of a pbo. the header contains filename and file size for each data block in the pbo the way to do that, is of course up to you in C# code, but the structure of the pbo, and what you're needing to fread() is at the above link. alternatively. you can use my depbo.dll. which as the name suggests does it for you and you just use API calls into the dll to get at what you want. mikero@norfolk.nf if you need further info (the dll's header file eg)

as far as i am aware my depbo.dll is the only pbo tool 'out there' that can handle our russian komrade's zzz files, along with a nasty encryption used in amalfi's unpbo tool, along with a very unpleasant crash from any pbo's made using Flea's fleabomb (it makes wrong assumptions about the header content and consequently scribbles some 'interesting' files) if you want arma comatibility, then either mine or keg's equivalent is the only reasonable way to go. compression as such is not used for arma pbo's as the file content is streamed in-situ (the pbo becomes part of the virtual file path, un-extracted) as far as dll's in general are concerned, i agree with the sentiment, however they are the only reasonable course of action to employ when you are using multiple tools to achieve same end's. eg a dos based or gui based, binariser, and, pbo maker. Elsewise exe files become bloatware, and, you are *garanteed* to have incompatible libraries between the two. the latest batch of dos based tools is here http://andrew.nf/ofp/tools/index.htm along with Eliteness 2.18 which is the one shoe fits all gui based equivalent of above.

at some stage i will upgrade the source to linux compatibility for arma. The major difference toolwise is to deRapify the newer style encoding of bin files. It should be a non-issue unpboing addons. however, recreating them for arma requires a new header to be totally correct (but most resistance style headers are 'ok)

http://andrew.nf/ofp/tools/eliteness2.18.rar is now available for your viewing pleasure fixes bug where arma style pbo's could not be created DUH! (Thankx Planck)

grab a copy of Eliteness from http://andrew.nf/ofp/tools/eliteness2.17.rar it has a lint checker _specifically_ intended to detect the above issues. Enjoy

Thanks for that http://andrew.nf/ofp/tools/Eliteness2.17.rar

http://andrew.nf/ofp/tools/DePbo1.55.rar fixes the 'delete' problem with Eliteness 2.15 download and replace the dll contained in the above rar file with that supplied in in the eliteness package (http://andrew.nf/ofp/tools/Eliteness2.15.rar) --- also, http://andrew.nf/ofp/tools/MikeroDosTools1.41.rar now contains an improved patch pbo that allows you to set the prefix header (rather than assume it's name is one of the patched, pbo's) syntax patchPbo -APrefix\Folder\Name this.pbo that.pbo output is to that.patched.pbo but the prefix header contains "Prefix\Folder\Name" --- all further notices regarding Eliteness and / or Depbo upgradess will be posted here http://www.flashpoint1985.com/cgi-bin....1132810

http://andrew.nf/ofp/tools/DePbo1.55.rar fixes the 'delete' problem with Eliteness 2.15 download and replace the dll contained in the above rar file with that supplied in in the eliteness package (http://andrew.nf/ofp/tools/Eliteness2.15.rar) --- also, http://andrew.nf/ofp/tools/MikeroDosTools1.41.rar now contains an improved patch pbo that allows you to set the prefix header (rather than assume it's name is one of the patched, pbo's) syntax patchPbo -APrefix\Folder\Name this.pbo that.pbo output is to that.patched.pbo but the prefix header contains "Prefix\Folder\Name"

http://andrew.nf/ofp/tools/DePbo1.55.rar fixes the 'delete' problem with Eliteness 2.15 download and replace the dll contained in the above rar file with that supplied in in the eliteness package (http://andrew.nf/ofp/tools/Eliteness2.15.rar) --- also, http://andrew.nf/ofp/tools/MikeroDosTools1.41.rar now contains an improved patch pbo that allows you to set the prefix header (rather than assume it's name is one of the patched, pbo's) syntax patchPbo -APrefix\Folder\Name this.pbo that.pbo output is to that.patched.pbo but the prefix header contains "Prefix\Folder\Name" any further notices on eliteness/depbo will be found here http://www.flashpoint1985.com/cgi-bin....1132810

Hi there,,, looking at, or for, the problem with eliteness right now..... to confirm: eliteness2.15 is the latest 'n greatest and should work with the delete calls (Kegs does not yet) you should however be able to use the config.cpp as a config.cpp text file, (no reRap) for the interim pls let me know if at least THAT (a text file), works

http://andrew.nf/ofp/tools/eliteness2.15.rar and also http://andrew.nf/ofp/tools/MikeroDosTools1.4.rar the dos tools are a dos console version of the functions available in the Gui (Eliteness) and now also include an updated version of patchpbo that will merge two Arma (or elite) pbo files together (or any other pbo file for that matter). dos tool makepbo now raPifies (binarizes) the relevant file(s) such as config.cpp such as description.ext if allowed to. see documentation inside rars Enjoy