RepJunkieJr

Niiice

How come I've never seen your work before, my man? Fantastic stuff! I'll be watching your workshop with great interest!

Great work, Zel! I will watch over your career with great interest!

You might try For The Republic. If I recall correctly, it uses two different types of blasters, one for the clones and one for the droids. If you want I can scour the files and find out what makes it possible.

Hey there! Hit me up in DMs and we can talk.

So, to summarize so I understand correctly: you're looking for a way to add multiple different types of weapons to the game. More than one weapon for pistol, more than one for rifle, so on and so forth. I've actually seen this done in other mods, though I can't remember off the top of my head which ones. I agree, this would be a wicked idea and allow for new types of mods that require an array of weaponry.

Hey. So just an update. I was able to get it to import the bsp data. It created shaders for each texture in Blender, but it did not actually make any efforts to retrieve them and set them to the shaders, forcing me to do it manually. I run 2.81 and I can't exactly update to 2.83 due to addons that I can't go without, and I already have three different installations of Blender in different versions, so getting 2.83 is not ideal. It's a hell of a grind, but in the end, with the work I'm making, I think it's worth it.

I was hoping I could get some help here. I made a directory, extracted the contents of a map pk3, and imported the bsp, but I'm getting zero textures. The textures are extracted as well, but nevertheless I'm getting nothing here. Can I get a hand?

I'm working on a new model, and I can't export because it says UV Seam found. Split Meshes at UV Seams. I know how to fix this issue. Select the Seams from Islands, select one, Shift+G > Seams, then edge split, but this isn't working. It still gives the same error however, as if I didn't even split them, when I clearly did, as when I select Seams from Islands, it shows that they're all gone. This wouldn't be an issue if it was just one object on the model. I could easily delete it, name it an anomaly, and move on. I can't do that though, since the entire model has this issue. Can someone please help me?