Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Cidward

Pages: [1] 2
And today, after I already installed the new versions, Substance Launcher has an update. I update, and it says that I need to install the new versions. Those are, of course, already installed on my PC since yesterday. Sigh.

Thank you, I'll give it a try!

ETA: Ok, so it turns out that you can't launch Substance Painter from the Substance Launcher anymore. Great. Got it to launch from my Adobe options in my startup menu. Also couldn't update it, as normal. Had to fully install the current version first (which wouldn't open at all), and then select the new version. Of course, wouldn't you know it, my project is no longer right there, and I've got to go and find it. Along with all the custom materials I created.

Headed into Substance Painter this morning to work on my project, and here's the new update. Installed it, and then opened it. It said "running" for a brief second, then right back to "update". Updated again (in case I did something wrong) and the same thing happened. Same for Alchemist and Designer. Really need to get back to work on this project, so if someone could help me figure out what's happening that would be great.

So I was texturing my model, when I discovered I had made a mistake (too many similar colors) in my ID map. I hopped back over to Blender, fixed the issue, and then baked out a nice new map. I imported that map into Substance just like I normally do, and sure enough, I can see the updated thumbnail right there in my project shelf. And it's there in my texture set settings tab too. But when I start texturing again, my model acts as if it's still got the old ID map loaded up, and is ignoring the new map. Can anyone tell me what I'm doing wrong, and how to fix it?

Thank you, will do!

Ok, so this is weird. It just stopped happening. Now meshes I load look normal when I bake their mesh maps. All I did was restart my PC.

I don't think so, as this happens on any model I try, including ones I didn't make.

Starting this morning, when I bake mesh maps, the resulting maps are bad, and have the UV map images spread across them like a texture. Not sure why this is happening. It happens on any mesh I try, even simple little ones, no matter if it's an OBJ or an FBX. Help! ETA: Something tells me, I'm going to miss my deadline. :(

When filling polygons, this happens:

Why is this happening, and how do I fix it? I've tried both the triangle (what you see here) and quad options, and still I get this ugly aliasing. I have also set seam padding to "UV space neighbor".

Ahh, ok, so it will require merging the texture sets first. That's...a bummer for a whole host of reasons. Strange this functionality doesn't exist.

I painted a mesh with a lot of texture sets. Can I now transfer all this work to the exact same mesh with only one texture set? I tried replacing the mesh in the project configuration tab, but all the texture sets got grayed out, and none of the textures transferred when I did this. It seems like this should be possible, since the mesh is exactly the same, but I can't figure out how.

SubstanceSubstance - Purchases & Licenses - Displacement use question
 on: February 18, 2021, 04:54:37 pm 
If I'm making a model of an old west town (to sell), is it acceptable to use a displacement map generated in Substance Alchemist to make the surface of the street by baking it out to a high poly physical mesh?

I've painted my model very simply, using just a fill layer with a black mask for all texture sets. With the mask selected, I right click and select: "Export mask to file". Works great, but for only two of my texture sets. All others, it exports a black square. What's happening?

I played around with the viewer settings tab pretty extensively, thinking I could just hit ctrl+z to undo the changes I had made, but it doesn't work. Is there a way to return to the default settings that were there when I first installed Alchemist?

Pages: [1] 2