pop101

#NeverForget

Technically not the "first" as their was already 100 mods on the workshop but it is arguably one of the biggest mods to come along so far along with the Trader mod and Weapon Redux mod. They are the first few mods to have made a sizable impact in the community.

So i have been working on a few item mods for the game and one is a weapon case/crate for holding rifles. I have done the config, finished the LOD'S, applied textures/materials and everything looks fine in Object builders 3d view. When i go to pack my files it all works just fine like normally. i install the mod to my game launcher and run it with the community offline mode for testing. As soon as i run my game i get a crash resulting in a " Bad version 73 in .p3d file 'filename\filename.p3d' " error. The .p3d file/path it is referring to is my custom p3d item used in the "model="\filename\filename.p3d" line inside my .cfg ......(however the item works and looks fine inside OB) I have no idea what bad version 73 means or how to go about fixing it. Absolutely no clue. I have verified both my Dayz and Dayz tools. Removed and remounted my P: drive, restarted my pc, messed with LOD's and nothing has fixed it. Someone Please help! ***FIX/UPDATE*** So i have managed to track down the cause of my problem and i will explain it to help others if they run into the problem. Since Dayz modding is in its infancy most of the tools the last few months have been absent or broken therefore i have gotten used to working with arma tools instead. This is where my problem started. I was using arma 3's addon builder to pack my mods until now. Most of my other mods thus far have not used .p3d files until now and because of that i was not noticing compatibility issues with my other mods. Now that i have used a .p3d file there is obviously compatibility issues as i have ran into them. (not really surprising). With all that said, it seems to be compatible if your are not packing a .p3d which is what confused me the most since it worked up until now. Long Story short: Arma 3's Addon builder has a different .p3d version for packing the .pbo than Dayz's addon builder does which created this problem. Make sure you are using Dayz's Addon Builder if you run into this problem.