You are using the 2019 version of sat, the api changed in 2020. is it possible for you to use the 2020 version? If not, I will try to make a 2019 compatible sublender(but it may take one or two days )
(Since we both speaks Chinese, why don’t we use Chinese )
Yes I reinstalled and it seems to be correct right now, maybe was a cache problem or something. Really nice update and thank you for my name in credits
I Was wondering, at this moment it’s possible to create a custom profile? I noticed you made a cool presets system using JSON
It’s possible, but it is hard~~, I’m planning a feature to generate template based on Blender Material, thus we can edit as we like and generate it automatically.
If you want to try make one yourself, you can extend an existing template. The sublender will load the template while blender starting.
And here is how to get the type of a node with python console:
after I tested this add-on, I’m wondering, by any chance using the “real procedure” parameters nodes from substance to blender rather than exporting textures and using them? Like substance to Unreal engine.
In my case, I’m working on a large scale scene project. The textures cost lots of ram or Vram when rendering. If I can use real procedure like substance node really into blender that will very low ram cost, any idea?
I don’t understand you, here is what I got after loading a sbsar into unreal engine, it seems that it’ using the textures directly rendered after importing.
There’s not. The procedural generation from SD uses own Substance engine and Substance didn’t release an official plugin for Blender, due Blender’s license.UE4 however has. This is a Workaround using the Substance Automation Tool which is a HUGE time saver. These limitations are not bonded to xVanTuring addon. But this is the faster and better workflow with SD and Blender.