https://forums.uberent.com/threads/wip-papa-texture-editor-v0-3-1.56309/ DeathByDenim made a texture editor/extractor there's the link
I tried using that, but I get an error message saying: "The program can't start because libstdc++-6.dll is missing from your computer. Try reinstalling the program to fix this problem." Obviously reinstalling it won't solve that problem, and Google searching it hasn't really brought up any useful information.
Thanks, however I think you're getting it wrong. According to the post, Papatran is used to turn things into papa files. Not the other way around.
Papatran exports files into .papas, the file system used for models, textures, and animtions. (And maybe particles too, can't remember atm.)
I'll ask DeathByDenim to recompile the program with the -static-libgcc and -static-libstdc++ argument's it should link the library's and remove the need to put them in the folder.. It's a part of MinGW I also have the .dll's on my pc in the MinGW bin folder if you want me to upload them for you, but it's better if DeathByDenim recompiles the program with the command line to link the dependencies
Trying to import the aeson commander I don't seem to get any textures loaded, just the raw grey mesh. what am I doing wrong? I simply loaded the tank-aeson.papa file into blender (Sorry, I'm totally noob at 3d editing, just want the commander exported in a different format for 3d printing.) Very kind regards, Johannes
The textures for units are not contained in the same file as the model. The blender importer/export can't load them either. But there's a tool to extract the textures as images, which can then load into blender if you wish.
Why do you need the textures for 3D printing by the way? 3D printers don't print colour, do they? (Just curious, I've never printed 3D before)
Terrain is set up slightly differently. Textures are referenced rather occupying the same folder. Unless raevn does more wizzard stuff, your only hope is to get hold of 3DS Max.
I wasn't actually aware of that. I was aware it used a different vertex format, but I already accounted for that during import. It should still export fine, I just expect it then wouldn't work in-game. Also, @rancor47, the actual issue you have is to do with vertex groups, it appears you either have verticies that aren't assigned a group, or haven't set up groups for all the bones that need them.
Thx for the reply! I made a vertex group and the error is gone! Now I have another question. When I import a terrain .papa I get three bones, two for textures. Should they all be connected to the vertex group? or just the non texture ones?
You can get the error to go away, but it won't work like that. You won't be able to get any terrain meshes working via raevn's papa exporter (for now).