Jackal326

which can then be used with the hiddenSelectionsMaterials[] = {}; config parameter e.g. hiddenSelectionsTextures[] = {"\SSQN_Equipment\Data\crye_vests_mcm_co.paa"}; // defines the texture path ("\pboname\subfolder\texture.paa") hiddenSelectionsMaterials[] = {"\SSQN_Equipment\Data\crye_vests.rvmat"}; // defines the material path ("\pboname\subfolder\material.rvmat")

Maybe because its on your desktop... Unless you're packing the texture into the PBO along with your config.cpp or putting the texture within the mission folder itself, then of course the game can't find it...

Your texture resolutions should have dimensions that are to the power of 2 i.e. 128, 256, 512, 1024, 2048 etc.

I've been out of the ArmA3 mod-scene for quite some time, but its still good to see that some things haven't changed - "When will you include X?", "Why haven't you included Y yet?" etc. 😂

Why not make it using a texture that does exist and simply have it as a fully-transparent _ca.paa texture?

I've just had another thought. Depending on which model it is you're altering, provided it is compatible with hiddenSelections, you can use the HiddenSelectionsMaterials config parameter to simply change the rvmat relevant to that selection/texture. That way you don't need to go through the hex-edit route.

I've been out of the modding scene for quite some time and I'm trying to fall back in where I left off but I'll try to offer some advise as best as my (out of date) knowledge will allow. The thermal imagery textures are ending with the suffix *_ti_ca.paa These are defined in the rvmat file as such: class StageTI { texture = "a3\characters_f\opfor\data\clothing_ti_ca.paa"; }; To change these you would need to edit the relevant rvmat file and then point it to the new texture you've created. Thats where it (potentially) gets complicated as you'd have to now tell the model to use this new rvmat and the only way to do that (that I'm aware of/can think of) is via hex-editing the model. There may be some tutorials on that somewhere but the basic gist of it is to search for the rvmat that you're wanting to change - alter the hex code to your new path (but making sure you keep the hex path the same number of characters in length so as not to cause the p3d to be unreadable by the game) and then saving it as a new p3d file inside your addon pbo.

One large grid square in Object Builder (aka O2) is 1m (aka 100cm) as far as I can remember (going from memory isn't the best I'll admit).

Vague issue is vague. Do you have the correct named selections set up within the model? Do you have a correctly configured model.cfg and the correct entries for the model within the model.cfg? Is the model.cfg (that we're yet to establish actually exists) in the same directory as the p3d model? Are you Binarizing your addon?

Which of those weapons aren't showing up? Is it all of them or just select ones? The more specific you are with your problem then the more help we can be. Also, complaining about a lack of reply is a sure way to get no help what-so-ever...

Aren't you able to have separate Steam Library locations (in settings) for game installations? Just have ArmA3 installed on the SSD and have the mods installed on a different HDD...

Whoops! Misread the post 🙄 I'm surprised it isn't throwing an error on starting the game tbfh...

Also, form memory the "vanilla method" requires you expand on this part: discreteDistance[] = {100}; discreteDistanceInitIndex = 0; to something like this: discreteDistance[] = {100,200,300,400,500,600,700,800}; discreteDistanceInitIndex = 2; In the above example, the rifle can be zeroed from 100m up to 800m at 100m increments. It defaults to 300m (i.e. 100m is 0, 200m is 1, 300m is 2 etc.).

Go into the Geometry LOD and create a Property with the following info: Name: autocenter Value: 0 That should work...

Might need to refresh the normals etc by selecting everything and pressing F5 (in Oxygen). Might also need rvmats applied (or adjusting if you've already applied them).