Search the Community
Showing results for tags 'ImageToPAA'.
Found 2 results
So as of right now, I'm trying to do a faces mod similarly to what ASCZ Heads did with their custom mods, only, that the faces I'm trying to make wouldn't be able to be selected by the AI, exclusively player-decided. What I'm struggling with right now is the config.bin file and whether or not the base .paa file for the textures is suitable for use in the mod. All assistance is appreciated, but the last thing I want to hear is to just copy the config from another face mod and fill out the spaces as that does not help me in learning how to make a config.bin file from base.
Matthijs posted a topic in ARMA 3 - TERRAIN - (BUILDER)I'm following The Atlas - A Guide to ArmA 3 Terrain Making (v1.0), and I'm running into an interesting problem. My P:\ drive maps to "C:\Users\myname\Documents\ArmA3 - addon work" I set it up using arma3p.bat by Mikero When starting Buldozer, it tries to run ImageToPAA from o:\Arma3CommunityTools, instead of the normal steamapps directory. When I create an o:\Arma3CommunityTools with ImageToPAA in it, buldozer is functioning without errors. But I would like to to run without requiring the O: drive... What I tried: - Tried updating Buldozer through the Arma3Tools --> DevP --> update Buldozer - Going through the Terrainbuilder config, and found no reference to O: nor to Arma3CommunityTools - Going through the Buldozer config, and found no reference to O: nor to Arma3CommunityTools - Searched the registry, and found no reference to O: nor to Arma3CommunityTools - Tried creating a clean P:\ (remove all files, use DevP to set it up again) Update: - Tried running Ccleaner, cleaning all caches, and cleaning the registry until no issues appear. - Tried deleting buldozer.exe and replacing it with the retail arma.exe - Tried searching buldozer.exe and arma.exe for the string "O:\" -- both executables contain only a reference to O:\Arma3\Arma3Retail_DX11.pdb, but no reference to O:\ArmaCommunityTools Update 2: - Uninstalled Arma3 tools - Deleted Arma3 Tools directory - Reinstalled Arma3 Tools - Configured Arma3 Tools / P: drive Problem resolved, unable to reproduce the problem.