mikero

firstly. welcome to hell, and secondly welcome to a set of tools that actually work, and tell you when you've got errors. a unique experience. For 'paramflles' (mission.sqm. config.cpp, desc.ext, rvmats. blah blah) there is no such thing as 'true' or 'false'. If you have not done so for yourself using #defines, then bis provide you with #include "commondefs_a3.hpp" for this exact purpose. Bottom line: for a desc.ext you need to explicitly state, before anything else. #define true 1 #define false 0 this is _only_ required in a description.ext btw, because all other paramfiles can be binarised, And my dll transparently adds these defines without you having to fuss about them. --- for other folks reading this, the above does not apply to sqf files or sqf syntax. In sqf syntax "true" and "false" (note the quotes) are valid.

i sent you the details by email. As far as i can tell, your email address is correct above, which means you did not type the password correctyl copy and paste it from the email I sent, it works here. and 'crash' is a very silly word to use. clearly,. it has not.

That's a nice, informative post by Vovo folks. the only discrepancy in this discussion is that Eliteness will not convert wrps. It only views them. the correct syntax is convertwrp NameOf.wrp 60 this will produce an arma TWO pew file convertwrp NameOf.wrp 60 some.cfg will use the details contained in 'some.cfg' to: give you vegetation(green) versus 'artificial' (red) object icons in visitor, make the icon-objects round or square the cfg supplied in the documentation is generally more than good enough. convertwrp NameOf.wrp 8 will produce and arma2 unbinarised wrp which looks identical to the one created by visitor or Terrain Breaker. When importing into Terrain Breaker It is your choice to use either the pew, or the unbinarised.wrp

missing land classes are caused by bis binarise unable to find a land_class for a p3d whose geolod contains class=house this happens when it doesn't know where to look for the config containing that land_class (if there is one) you tell binarise where to look in pboProject's->Setup->island builds only if you haven't extracted the relevant pbo, you're out to lunch, or if, in fact, there is *no* land_class configured: make one. land_classes mean animations, and lack of one baked into the wrp means animations (such as doors) won't work IN the map. https://community.bistudio.com/wiki/The_Land_xx_class

FREE TOOLS UPDATE A snapshot of the basic toolset that subscribers enjoy is now available on dev heaven. It replaces the ones already there, handles type70 p3ds, and will enable you to make high quality maps. https://dev.withsix.com/projects/mikero-pbodll/files Compression and/or obfuscation have been disabled. Just like the previous free tools, I have no plans to maintain or update them. It just happens if it happens. Note that this is the basic toolset in order that you can make and extract pbos. For a full list of all the tools, visit here https://community.bistudio.com/wiki/Mikero_Tools

Hi Johno When bis binarise crashes it doesn't actually report good or bad status the above messages are simply that pboProject noticed it. Half the time, the crash(es) appear to be irrelevant and occur when binarise is simply closing down, hence pboPro lets the processing carry on. It should not do that really, and subsequent versions do in fact stop. No one knows the cause of any of the different crashes we get with binarise because there's no progress information of what it's doing at the time. The best people have noticed is that it _appears_ to be caused by a p3d it doesn't like. (as opposed to say a bad config, paa, or rvmat) --- As others have commented, pboProject builds pbos plural, and addons plural (all-in-one-go. (if you let it). The definition of an addon is that it has a config.cpp. It is quite legal, to have addons within addons, eg multiple configs in the same pbo. PboProject considers the first config.cpp it disccovers to be the boundary of the pbo. Hence subsequent configs in the child folders are merely addons in the same pbo. --- sorry, but there is no easy answer for you re the binarise crash. You will have to do what everyone else has to do, and use the 'halve and halve again' rule. This simply means start taking out large chunks of data out of your pbo until it packs successfully, then progressively add things back, to locate the problem.

Not good enough? I doubt it. Like many, you've been brainwashed into using tools that don't work, and now, have to rethink your workflow. It's only ever after that fact, when things start working that it's all so obvious. The only good news is getting it right, each time, every time, becomes second nature. Ask anyone using my tool set how much easier, predictable, and confidence building, that is. if your lazy (which i doubt), and expect everything done for you at the touch of a button (which i doubt), go play with addon builder, I not only can't, i won't, help you, My money says you simply weren't paying attention (which is being human). My tools take no prisoners, one misstep and they expect you to fix it. And the reason why they are so vicious, is the tools are vicious to your pc. The one thing no-one can afford is a misstep that results in destroying your OS or file system. Something bis have yet to understand, since their tools will wipe out your entire p drive if you let them. My tools just won't let the causes of that to happen, and you are (currently) suffering.

you either ignored the warning when installing depbo.dll that it could not set your environ path. OR, you are running as admin with uac enabled. There's extensive documentation for all my tools in start->programs->mikero\blah blah they tell you you how i set the registry,and where my tools are.

Thank you for your comments folks. They make any person feel it's worth the effort. @scottg, stop wasting your time with tools that don't work.

Arma3P will not tolerate buldozer.exe on YOUR p drive and neither should you. Arma3p removes it and the one billion dll's needed to use it. Simply point your buldozer activation in both TB and OB to steam\arma3.exe directly and be rid of this issue forever. no more missing dlls no more tetrahedron bug no more missing bin\config.bin\whatevers no more shader mismatches no more 'works in buldozer but not in game' no more steam can't log in with invalid user It's always your choice folks to keep filling forums with 'why doesn't blah work', or improve the quality of your workflow. forever. There is NO relationship between where\ever\buldozer.exe is and p:\bin\config.cpp There is NO relationship between 'pinkelephant,exe' and arma3\dta\bin.pbo There is 1:1 correspondence between arma3.exe , it's shaders in bin.bpo, and config.cpp there is only ONE 'buidozer' on your pc. it's not buried in devel tools, not buried in stable tools, it's your copy of arma3.exe use it.

I only check geolods. The lack of one, in my code means, effectively, there is no class=, hence there is no problem. I don't intend changing that even tho you are correct Auss. Also folks, be aware that dep3d allows you to change the geolod properties of any p3d. This may save you agony. And finally, i have changed pboProject for you folks so that if you build a pbo with a *pre-binarised* wrp coming directly out of arma2, these checks are disabled. The check now, only applies if you create an arma3 wrp. This change is wrong, in the sense that the engine insists on land classes, but there is a point where common sense has to apply.

>The weird thing is - in this case, all the objects are A3 - so, while I had CUP issues before, this time it can't be CUP. Strange indeed. :) then it's up to bis to get their act together, they make the rules.

yes. that error msg is admittedly a little misleading unless you read it carefully (I will reword it on next release) what it is complaining about is that the p3d has geolod class=house and bis binarise (not pboPro) was unable to find a corresponding class land_nameOfP3d unlike arma2 (which prolly also needed it), arma3 insists that any and all p3d's with geolod class=house have a corresponding land_class in a config.cpp some\where the some\where is literal, it can be any\where\ in one of the pbos making up the game (not necessarily THE pbo that contains the p3d) binarise spends most of it's processing time in a desperate hunt to find it. either: the land class genuinely does not exist (in which case make one) or you didn't tell bis binarise (via pboPro) where it could find it. (look in setup->island builds only) The cup team are aware of these issues and this requirement. To the best of my knowledge they are fixing thier config.cpp's accordingly. as and when they discover a problem. further reading: https://community.bistudio.com/wiki/The_Land_xx_class

firstly, your ca_misc config.cpp is wrong (being empty) the *real* config contains class CfgPatches { class CAMisc { it is this class which identifies the pbo to the engine. pboProject will not continue if it knows lack of one will cause issues. (the reason for your first error above) either: provide the 'correct' config.cpp OR delete that config.cpp altogether (pboProject will then search backwards, find, and use, CAdata as the addon for that file\reference) ---- i am not aware of any issues with aIa2p (which is not to say there aren't any). However aia was brillian at the time (past tense) and you are 1000% better off using cup, which is also, and a2 drop in replacement, and is designed to replace AiA

the insistence on K is simply to ensure that the user has, actually, read the warning message. far too often in the past, users simply let arma3p do it's thing and ignored all errors (or warnings) and THEN posted forum or skype messages asking why bla bla doesn't work! yes, indeed, arma3p finished successfully, but what it cannot do is alter the registry settings for OB and TB respectively (not quite true), to change them to the 'real' buldozer called arma3.exe and the reason for this change is that buldozer.exe is not necessarily identical to arma3.exe but it must be. and the reason for not making an identical copy in the p: drive is that a mountain of ever changing crud must also be copied over to P as well. finally, putting bis executables, (tools, or arma3), or even my tools on the p:drive is a disaster waiting to happen. indeed it has happened in the past where bis assumed the entire contents of p: was theirs and wiped you out when they updated. (quickly fixed, but you;'d never want a repeat) as the dos screen advises you, you simply have to point the respective TB OB tools using the tools own 'options' to point to arma3.exe rather than P; anything. I do not know how bis tools you mention achieve this. they can, as stated in the dos screen, be done by you anyway. I am only aware of the tetrahedron bug being mentioned some time ago and can't answer whether it's related to using bi's Devp or not. personally, i'd recommend not using it at all.

The free versions of my tools don't support bi's newly introduced type70 p3d's I have no plans to update them. Subscribers get the benefit of a never ending stream of updates as bis move goalposts.

I have given up on Dev Heaven and now run my own server and website. I have sent messages out to all skype groups about this. and now, here :) if you are a current subscriber you need to download the NEW updater by using the OLD updater. if you wish to become a subscriber, the same mechanics are involved as before. Essentially, $35/year via paypal to sloompie16@gmail.com the NEW updater is available to everyone in the free tools section of Dev Heaven, https://dev.withsix.com/projects/mikero-pbodll/files In all cases, the dev heaven login (or lack of one) is irrelevant. your login is the email address you send me in the paypal request. to which, i will reply with a password existing subscribers *also* require a new login and password and they can contact me via skype or email direct. while an apology is in order here for messing all of you about. I hope you understand the necessity of getting away from dev-heaven, and hence, the temporary wrinkles.

doesn't work for me i did similar to you taking the tetrahedron.p3d from the already extracted game assets using arma3p and putting it in p;\core\etc note that _this_ tetrahedron bug displays an armaTWO gui there is an almost identical bug where buldozer cannot find a3\data\f\tetrahedron.p3d eg: https://forums.bistudio.com/topic/182105-buldozer-cannot-open-object-a3data-ftetrahedronp3d/

killswitch and i need to check the code, there's a definite mistake at my end that slipped thru, we will find it. In the meantime, your choice is to alter the \ to / by hand wherever you encounter it causing problems. Windows is smart enough to treat either character as a file separator so you aren't upsetting the same files built on windows platforms.

i'll check the code and get back to you, the linux versions are compiled with automatic '\' replacement, something may have gone bang. In the meantime, since windows has no issues with either / or \ you could change the source to / (even tho it's not your code)

as stated to you the latest toolsets do exactly as you describe, 1) they check if already entered and 2) check there's enbough space if not. and 3) they warn you I don't know what a 'community tools updater' is, if it bit me. https://dev.withsix.com/projects/mikero-pbodll/files

this is a known issue with winamp's nsis installer. the latest tool sets (both free and subscriber) are failry succesful at avoiding it. basically you have too many apps installed on your pc, all of them wanting to swamp the environpath which, for nsis, has a 1k buffer limitation. 1k of paths to hunt is normally more than ample for an unstressed pc. more than that and your pc slows down in reaction time to find and load any given exe. i don't have any answer for you re recovery and am sorry to hear it happened to you, but, as mentioned, the later toolsets amost certainly prevent it happening.

there is no such file or folder as c: drive anything. for whatever reason your wrp is looking for it's files in the wrong place. They *must* be on p:\

In over ten years of providing tools, missions, and addons, that's the first time i'm accused of that :) My daughter in law was on holidays this past week and i have only just recieved your emails today I do realise your frustration, I live on Norfolk Island which cannot recieve paypal, so I have to do it thru a proxy. Hence the intolerable delays. As noted in the how-to-subcribe, you can always contact me directly via my profile settings here on the forum with email or skype here you go: https://dev.withsix.com/projects/kmp-dpbodll-up/files

>Do you offer any support? I think you need to start using the free versions to get an idea of what my tools actually do. No one actually using them would ever ask that question. https://dev.withsix.com/projects/mikero-pbodll/files