Substance Painter Tutorialをやってみる⑩

Substance Painter Tutorial ? Fundamentals 10: Particle brush


要点まとめ

パーティクルブラシ

SPの目玉機能！として紹介されるパーティクルブラシ！
便利ですが、設定が多くあってちょっとめんどくさいです。




パーティクルブラシの項目

とりあえず、"heavy_leaking"のパーティクルブラシの項目を確認

dt…DistanceTime?パーティクルの間隔を指定してくれるみたいです。

Emitter…エミッターのタイプを設定

SpawnRateFactor…パーティクルの発生量？
SpawnSpeed…パーティクルの発生スピード？
SpawnSpread…パーティクルの拡散量

Receiver…よくわからない。

DrowOnBumpSensityvity…よくわからない
DrowOnGeomSensityvity…よくわからない

FadeOpacity
FadeOpacityRand…のランダマイズ
FadeSize
FadeSizeRand…のランダマイズ
Friction

GlobalWindX…風向き(X方向)
GlobalWindY…風向き(Y方向)
GlobalWindZ…風向き(Z方向)

GravityFactor…重力度

InheritVelocity…法線方向を加味するかどうか。
InheritVelocityRand…上記のランダマイズ

NormalFactor…ノーマルマップへの影響度を指定
ParticleLife…パーティクルの生存時間
ParticleLifeRand…パーティクルの生存時間のランダマイズ
Spread…パーティクルの飛び散り具合?

TurbulencePower…パーティクルの乱れるパワー
TurbulenceScale…パーティクルの乱流のサイズ


ざっとみて赤文字のところが大切そうなところ。
この項目もブラシと同じで、自分でプリセット化が可能。
必要に応じてライブラリ化してね！みたいなかんじです。

Comments

Post a Comment

Popular posts from this blog

Calling Python from Substance Painter

Here is a quick code snippet for calling a Python script from Substance Painter and parsing the results. The in/out is very simple, but serves as an example of using the alg.subprocess.check_output function to bridge the JS api and your own Python scripts. // This can be called from the QML UI, or elsewhere in the plugin code. function GetAllFilesInDirectory(root) { if (root == undefined) return; // I put my scripts in a relative path to keep my plugin tidy. var script_path = "Scripts/FileUtils.py"; // Gathering files var ret = "NOSTRING"; try { // The arguments are used as parameter inputs to the Python script. This requires some planning // and well communicated conventions, but works well enough. ret = alg.subprocess.check_output( [ pypath, // Absolute path to interpreter. script_path, // Relative path to the py script. "log_files_of_type", // sys.argv[1], in this case the python ...
Read more

A Quick Checkin- Clion, Unreal and Mac

Image
Super quick check-in. Hello world! For the last year or so, I've been working with Echtra Inc. on a great project as a Tools Engineer/Technical Artist guy. The project is using the Unreal Engine, which I like more and more every day. On Windows, C++ plus Visual Studio Pro and Visual Assist is a great combo, and I happily churn through my daily tasks without fighting the tools too much. Not so on my Mac at home. Programming in Unity on a Mac is great! Mono Develop isn't amazing, but it isn't terrible. But Unreal on a Mac. I want it to be fun, I want it to be possible, but I just can't get myself to like, let alone enjoy, XCode. On that, for anyone thinking "well, you could just use blueprints..." etc, I feel it's too much of a shackle to not be able to just dive into the guts of it. C++ or bust. So anyway, I recently adopted PyCharm at work and really enjoyed using it for my Python tools. I noticed that JetBrains also made an IDE called CLion , and they ...
Read more