Substance - Bug Reports and Feature Requests
interpolator
There are currently 2 ways to report bugs:
but going through one of these paths will ensure that your bug lands in our bug tracking system as quickly as possible.
Feel free to use this thread to post feature requests for both Substance Painter and Designer too.
- In Substance Painter, through the Help > Report Bug menu.
- For every other Allegorithmic tool, the little green tab on the right of this page allows you to report bugs too.
but going through one of these paths will ensure that your bug lands in our bug tracking system as quickly as possible.Feel free to use this thread to post feature requests for both Substance Painter and Designer too.
Replies
While we are consolidating things into sub forums and sticky's a Roadmap or maybe a public Trello board may be a good idea.
Already in:
Ctrl + right click resizes your brush
Ctrl + left click changes the brush flow
heheheh that teaches me for not reading the doc's then....thanks for the heads up
Loving Painter though. It can fall under the "where have you been all my life" categories.
Hey, I realize this is probably a pain because of the projection, but is there anyway to paint where that brush is... or just straight up switch off the uv mask ?
Its making it tricky to paint gently a long the edge and push in.
The program itself is freaking awesome XD
Or am I just being blind and there is a button already for me like my last question.
Are you guys thinking about supporting another type of compression inside unreal 4, I find that I get some nasty artifacts working with it now, might not be to visible in a game but since I am working on a scene I want the highest quality.
Something I asked on the other thread, not sure if it got overlooked:
"Also I would be able to tell substance to default to tga for bakes, so I don't have to switch it from png each time and being setting the to default to linked instead of embedded.
One more thing, be able to chose the bake folder inside substance, cause now I have created my own folders inside my graph, but when I bake it makes a new one with the mesh name and all that."
Edit: also a way to align the brush mask with the direction of the stroke would be nice to have.
For example if two float value nodes are added together, seeing the result in the addition node would help.
Some sample FX graphs do some very interesting things but it's very hard to understand the maths without seeing the graph do it's magic.
This. Sometimes when I'm doing some simple math stuff I need to recheck everything I'm doing because this isn't a thing yet. Also, it would be cool if the picture in the math nodes were like, math stuff instead of just white. Like if you're using an addition node thing, instead of having a white square for it, having a plus sign instead. Maybe it's just me but I think it would be easier for people.
I'm having some problems in Substance Designer with some of my normal maps:
I'm trying to combine multiple bakes into one map using my own versions on the Normal Combine nodes (it still shows the errors with them nodes too).
When I drag them from the Explorer view into the 3D view they work fine. However, when I "view in 3D" from within my graph then they show up with some strange artifacts.
I tried them in a brand new graph but still the same results.
I've tried changing the output format of the graph and individual nodes to 16bits but still the same result.
I've also tried changing the engine from Direct3D to SSE2 and baking in them to see if that fixed it. It didn't.
I've also tried masking out the areas where the affected areas but same results.
I've even tried using a cage or increasing the raycast distance to see if that fixed it. It didn't.
I've tried changing the shader itself to see if it was that but that didn't fix it either.
In order to try and reproduce the errors, I exported a plane and a high poly version (a plane slicing through a sphere) and baked that within SD without a cage and it works perfectly fine!
I'm at a stumbling block here so any help would be much appreciated
Can you try to bake your normal map in PNG (as this format allows 16 bits)?
If you process your normal map in the graph, be sure the next filters are also in 16 Bits per channel (the yellow link is bigger in 16b).
I've just tried baking out my normal map as a PNG but it still shows artifacts (although different from before) and I made sure the graph/node was in 16bits too.
Be sure to use the normal on your low poly mesh to get a correct preview, as the baking was based on it.
This kind of artifact can be due to the difference between your high/low poly (maybe you already read it but here is a good thread about the subject: http://www.polycount.com/forum/showthread.php?t=81154).
This is the only workaround for the moment.
I'm in something of a panic, because all of my materials DID have graphs before, and I rely on the dozens I created for projects.
I've tried restoring the default paths, and changing the engine. What's going on here?
Current version is v4.4.1 (Steam).
[EDIT - SOLVED] Right, I figured it out. Apparently one of the updates changed how you access the graphs; I kept clicking and dragging to the window expecting the graph to show up like it used to, but you can't do that any more. Doubleclicking also didn't work. You have to select the graph and hit enter.
[Edit 2] ....aaaand the doubleclicking issue was actually a problem with something else, ffs. So problem was a combination of user error and a mouse setting, not SD.
lol you were accidentaly trying to open the published SBSAR file inside SD weren't you?. I killed an entire day until i finally realised how stupid i was.
Hey
That is a great read that thread. I've made sure my low poly matches my high poly as close as possible.
I went back and made sure it wasn't due to not having a cage however I'm still getting artifacts.
In another attempt to track down the problem I also exported my meshes as OBJs (to see if FBX was causing problems). Interestingly, I still get artifacts but they are a bit different:
OBJ is on the left and FBX is on the right:
However (as I've said previously), if you drag the normal maps from the Explorer and apply them to the 3D view (in the normal slot) then they work great!
I've also found that if I export them out from SD, I get the same artifacts in Marmoset Toolbag 2 too.
I can send you a link to my meshes if you would like too.
About the differences between OBJ/FBX: with FBX format, you have the possibility to export the "Tangents and Binormals".
If you do so, SD will use them and it can leads to some differences between the ones you provide versus the ones "created" by SD (that will be used with OBJ format, or FBX if you didn't export them).
Regarding the difference between the explorer and the graph:
- if you use "jpg" compression for your bitmap (in the resource properties), your graph node will necessary output 8bits even if the node/graph is set on 16b per channel.
When you use the compression, the preview will only be available in the graph (not from the explorer). You can change the "Bitmap Compression Quality" value (to something around 0.99 ), and use "F5" shortcut in SD to clear the cache of the graph; then you'll be able to have a correct preview of your normal.
- if your bitmap is set on "raw": could you please check the engine you use using "F9" shortcut: to know if you use the CPU (SSE2) or GPU (Direct3D10) engine?
Thanks
Ever since it crashes whenever I create new substance or whenever 3d view loads.
The crash error looks like this :
I have checked and updated the video driver, tried restarting , reinstalling and removing the Relief files from the Shader folder.
Update : I unchecked the "View outputs when opening a graph" option and it works fine up until the view port opens when I double click the mesh. What is strange is that it worked fine before...even when it had a mesh loaded and I was UV mapping in Maya.
Update 2 : I can even bake maps ....without 3d view port and once I try open it , in 1 sec it crashes after it loads.
Hey,
Not sure exacly what u mean but I created new substance , dragged&dropped from library into the graph an image from enviroments and right clicked on it > view in 3d view.
The 3d view started loading, I can see the mesh , the image and then it crashes.( just like before)
I am using a GT 540M graphic card. I even tried reinstalling the previous version of the driver.
Here is a bit of the console :
Okay, this crash is "kinda" normal (I got it too, it will be fixed), but does the 3D View load now when you restart Designer once you did this manipulation ?
If this still doesn't work could you also try to remove/move your preferences too ? (They are located in C:\Users\*usernamme*\AppData\Local\Allegorithmic\Substance-Designer\4 )
A bit more of the console , should see the all the errors now:
Maybe you default graphic card switched to the integrated Intel chipset instead of the nVidia GPU. The best way to avoid that is to create a profile for Designer in the nVidia drivers settings and set the type of GPU manually.
Sent PM. Thank you for helping!
We found the problem when talking in PM, so I'm pasting the solution for everyone.
The problem was because designer was able to load the PBR shader, but for some reason the GPU switched to the integrated chipset of the laptop and therefor Designer was not able to load the shader and crashed. We have a check for this case normally when the user click in the menu of the viewport, but we didn't expected the GPU can change later. this will be fixed in a next update.
Anyway, to workaround this problem do just do these steps :
I just wanted to ask again, if this feature is planned?
However, what we plan to add is a gradient node with a secondary input and coordinate parameter: the gradient node will sample the pixel values in 1 dimension in the image at the given coordinate. Can't give any date for when it'll be implemented though..
That's fine, hearing that you guys have this issue on the agenda is already great. Cause the gradient maps are a great feature, I'm glad that you have some love for it.
If you have some bitmaps in the Resources folder and for some reason you move them around, the PKG Resource Path gets broken and it becomes a blank image. Would it be possible to have it properly reassign the paths as you move?