| Age | Commit message (Collapse) | Author |
|---|
|
Setters and getters have been hidden from the documentation when the matching
properties have been exposed, but some of them are parametric and require the
name or index of a given parameter to be used. So they need to be properly
documented with the type and name of the arguments they take.
For example, CPUParticles' `set_param(Parameter param, float value)`.
|
|
|
|
Applying #30187.
|
|
They are now generated automatically by doctool.
|
|
Thanks to @bojidar-bg's impressive work in #29380.
|
|
- Document a few more properties and methods
- Add more information to many classes
- Fix lots of typos and gramar mistakes
- Use [code] tags for parameters consistently
- Use [b] and [i] tags consistently
- Put "Warning:" and "Note:" on their own line to be more visible,
and make them always bold
- Tweak formatting in code examples to be more readable
- Use double quotes consistently
- Add more links to third-party technologies
|
|
|
|
|
|
The relevant code was copied from (GPU) ParticlesMaterial but commented
out initially, and never ported.
Closes #29580.
|
|
|
|
|
|
It took me some hours of trying and wondering and one question with a very helpful answer in the facebook group to figure out that the color_ramp gradient actually modifies the vertex color of the particle mesh (but NOT the albedo). After knowing this enabling vertex_color_use_as_albedo in the SpatialMaterial led to success.
I hope adding this little hint:
"Each particle's vertex color will vary along this [GradientTexture]."
Might help other people which stumble upon this...
|
|
|
|
|
|
Fix various missing arguments in bindings.
|