mikero

assuming ALL your rtms, (your p3d is irrelevant) ALL use ofp2_manskeleton, (eg they are ALL cargo poses) 1) create an anims subfolder and put ALL of them in there if you haven't done so already. 2) create a NameOfRtm.cfg file in the SAME folder. It doesn't matter which, of 20 different rtms, you have in there, just one of them needs a NameOfRtm.cfg This cfg file only contains a class cfgSkeletons.ofp2_manskeleton the 'right' skeleton to use is provided for you for arma1, arma2 and arma3 in the deRtm documentation folder

message deleted

and, as you've probably guessed already, addon breaker will do everything possible to make a pbo, with errors if present (but not bother to tell you there are in fact errors). PboProject and it's friends will do everything possible to NOT make a pbo. I invite you to think on the difference.

It's refreshing to see such detailed error reporting. It makes fixing it so much easier. Thank you for above. awes cargo rtm _probably_ contains 'bones' for the arma2 ofp2_manskeleton. Bis in their wisdom could not bring themselves to call a very different arma3 human skeleton ofp3_manskeleton. The logic behind that, clearly escaped them. as a result binarise has got itself in a knot. the other possibility, and a likely one, is you are expecting bis binarise to binarise two or more rtms which use different skeletons, one, the rather nice model.cfg you've shown above, which is clearly for a vehicle, and two, another rtm somewhere in the same pbo is a human static cargo pos. This, bis binarise cannot do. It can only crunch one skeleten type, per pbo

win10 does seem to have it's problems. the location of makepbo AND rapify have been set in the registry when they were installed. HKCU\Software\MIkero\Makepbo it's either there, or it's not. the exe 'key' in above for makepbo will say: C:\Program Files (x86)\Mikero\DePboTools\bin\MakePbo.exe if you are installing these tools AsAdmin, or running the tools AsAdmin, I have no further interest. The registry settings for an admin (as well as the pDrive) are different for admin vs mere mortals.

possibly the biggest mistake we at ofpec made was donating our knowledge base to the bis wiki when arma came out. It split the audience. 73% of people at the time voted ofp a far better game than arma1 in two separate polls, one by ofpec, and the other by the very good czech site that i can't now remember. The result was interest in the community collapsed with no migration path for the thousands of missions, hundreds of addons, and dozens of island. Ignorance is bliss. discord is not a 'secret' channel, nor is the equivalent in skype. But you need to google them.

yes. join the discord terrain makers channel

at least one, probably many, of the float values in the wrp have been corrupted. Den is a 'de' normalised value which cannot occur normally, and does not represent a float value per se. you _might_ be able to skip this warning by unchecking warnings are errors in the setup panel. But essentially, that wrp has been corrupted for reasons unknown. the error message is in fact a little vague. It lacks detail of what float value is actually faulty, and there's a small suspicion here that its a p3d causing the issue. .I will improve the message at some future date.

the error message is a warning to you that you have probably mis-used the same define. You must tell the compiler,. explicitly, that this isn't a mistake, and even then, it's an accident waiting to happen.

#ifdef THINGY #undef THINGY #endif #define THINGY new value

the 'O' drive error is also strange, check bistools\binMake\binmakerules.txt write permissions is often caused by running as admin. Each 'user' has their own P drive. 'admin' is just another user like everyone else.

An option to ignore the prefix that's not going to happen. re the linux/should/be/dos a release will happen with the fix when killswitch finds time to release it.

@proGreek if the pbo file entries contain / not, \ that is a mistake. i will look into it.

@asmodeus the dll has indeed put two more levels of obfuscation into the pbos to make it that much tougher for the thief to make any sense of the results of extraction. part of that is to increase size to pad them with garbage. > not possible. Finger trouble your end, reverting the dll will have same effect but don't forget to 'fulll build' that is correct and that is what compression is for, to reduce total size if possible. the 'apparent' obfuscation, is merely the compression encoding. that sounds about right. I have no plans to change it.

well I assume when you say you delete the line you actually just mean you delete the words access=anything; if you're wiping out other items on the same line, then of course that addon won't work anymore. removing access= should have not have had any serious effect to that addon, Serious, unpleasant consequences to the engine and other addons if left there, but not the addon itself. A classic case of 'my addon works fine' but it breaks other people's. The author may not give rat's arse about that, but his addon and mod very very soon get left with a reputation where people will not have it in their game and he wonders why he's unpopular. I've seen the same same story for over a decade. you really need to get the author of this code to get his act together, because backtracking to an earlier version, while fine, means you prevent yourself from ever being able to get new updates.

if you're a subscriber, the location of where old versions is kept is in the documentation that's supplied with the product. i don't remember, right now, where that is.

class RscListBox_infiSTAR { access=0; replace it with class RscListBox_infiSTAR {

unusually, the statement access=0 is embedded within a line of other text. it should be obvious to remove the words access=0 you can remove the whole page of text too and that will get rid of access=0 as well., but somewhere along the line common sense should have prevailed.

JOKE

if there are any remaining 'issues' i will throw rocks at you, in future, please post your support questions here:

yes ok, all good. by the time you read this the dll will have been updated.

please paste the cfgPatches section of ca\misc\config.cpp for me to look at

FREE TOOLS UPDATE The free version of my tool set has been updated to the latest subscriber snapshot of August 2017. Naturally and of course, not all tools are supplied, and naturally and of course, obfuscation has been disabled. Other than that these tools are now identical to those that the subscribers (currently) enjoy. (you can be certain with 1 update every week it won't stay that way) There has been 80+ updates since the last release, and chief among them are the ability to handle type 73 p3ds, and, make map making a far less painful experience. Further details, and where to get them are on the first page of this topic. Enjoy

well in order to reproduce the problem i'll need a full repo of what you have.

it is verboten for my tools to crash. this is a high priority fix needed. All you can do is keep removing sections of the build until it stops crashing, This, to establish what's causing it. Start with options such as disabling rebuild required addons, and notably the clutter check.