PuFu

your geo LOD seems not to be working

As a general rule, if you want to report something not working or some other issues (we recommend that everyone fills a ticket on our feedback tracker instead of writing here btw), always make sure you are testing that only with RHS. Otherwise, you are wasting both your time and ours.

what lods do you have done on that building?

why is there camoX in your model.cfg? does it serve any purpose as a bone? pretty sure there are shared vertices between camo selections and your other selections

parenting issue / meshes across multiple named selections. paste the entire model.cfg

you won't really get help for "i downloaded a model and trying to import" stuff here.

i don't think that is actually possible

and all these assumptions are based on your long term, first hand, modding experience ?

boys, please use feedback.rhsmods.org for bugs and other issues/

besides t-14 still being heavy wip, please direct all such reports towards - feedback.rhsmods.org

we only release on steam workshop, and that is precisely where we recommend people to get RHS from. your issues could be a number of things (corrupted download, corrupted upload) etc, none related to the current release

yes, it is possible to model some base meshes fatter to some degree, but no accessory will then fit, or in fact there will be clipping. You will also have to make all variations once again

again. nothing to do with RHS. we also do not actually take requests or "suggestions" either.

RHS in A2 was only russian oriented, so no

there was never such weapon in RHS.

can you pastebin the rvmat? and pboprefix?

glad you have it fixed. the config shouldn't matter whatsoever for an object to be packed with rvmat as well. No idea what HEMTT build system is, but atm, it feels like the software used to build the files is not packing the rvmat (it should spam the RPT with missing the RVMAT if the path is read correctly from the .p3d) or the path / P drive / work pipeline you have is not properly configured. My 2 cents, try another packing tool, also make sure the OB paths are pointing towards the P drive, and you P drive is configured properly inside OB.

well, both mikero and addon builder requires you to have the data on P: drive, and have unpacked A3 data (for things like external paths, such as environments etc) example this path: texture="Ammocan\textures\M2A1_nohq.paa"; should be on P drive as such P:\Ammocan\textures\M2A1_nohq.paa

can you try mikero's (free) tools instead? addon builder is something i have never used since it (at least used to) be shit. also, i assume you have your P drive setup correctly,same for the unpacked A3 data, yeah?

you packing with BI tools or mikeros?

the fact that most are using ripped content with zero regards to IP rights

you do not actually need either (detail or macro) for that ammo box. you can (sort of) work with metalness workflow, but you need to export for specular/gloss (SP can do that for you). on convert, the PNGs need to have proper suffixes - https://community.bistudio.com/wiki/ArmA:_Texture_Naming_Rules so that the converter knows how to and what to convert these to, no matter of what the SP outputs to (you can name these anyways directly from SP on export). the folder naming doesn't matter as long as the paths are correct. aslo in general, you should use a tag prefix for all of your file - example - pfu_ammocan etc etc Also, i assume the rvmat is assigned to the ammocan in OB builder, just bellow where you assign the _co file, because as it is, it seems the rvmat is simply not working at all. regarding that SMDI - it looks pretty flat somewhat, you will find that the specular and gloss needs to be in G and B channels respectively. R being full white (255/255/255). At a minimum for any sort of object in A3, you need a res lod, a geo lod and a SVlod properly configured.

you need to set arma properties for the objects you wanna export

if you made the asset in spec gloss, the result should be pretty similar - as in diffuse / spec / gloss workflow. have a look over - https://community.bistudio.com/wiki/Super_shader stage2 is wrong, you are also missing stage 7 also, how did you convert these files from whatever output you had in SP(ideally tga) to .paa? did you let buldozer do it for you? did you have the proper suffixes when you converted (be it via texview buldozer etc)?