UnityCsReference VS astc-encoder

I've checked their CS reference code on their Github, both here and here, but I want to dive a little deeper - specifically, I want to know what they're actually doing when determining validity of the Matrix4x4.

Yep, but beyond just decompiling it, the c# layer of code is on GitHub: https://github.com/Unity-Technologies/UnityCsReference

https://github.com/Unity-Technologies/UnityCsReference/blob/master/Runtime/Export/Scripting/UnityEngineObject.bindings.cs (after 2019.1)

The code where the method filtering for the Animation Event Inspector is done, is here (line 190). Is it possible to do something like this? That repository explicitly says:

No reason, you can look at the source of encapsulate

There isn't really a straight forward way to do this, even the QualitySettings editor uses Serialised Properties to get at the data. (Line 343 in QualitySettingsEditor)

This is awesome, thank you! I'm most curious about their Runtime

I think if you want to get into graphics programming you do want to work with OpenGL and similar things, because at the very least you need to understand it all (and decide what parts of engines to use and what to ignore when you get to whole games). It's also worth saying that while you can only publicly get the references in Unity you do get source access at the higher subscription tiers you'd use at a game studio.

A1: The optimization suggestion in the original text is to remove the meaningless Alpha channel (defined in the original text that the Alpha channel has the value of 1). This is indeed helpful for memory optimization. In your test case, whether it is in png or tga format, after entering the engine, it will be converted to the internal format (RGBA, ETC, ASTC, etc.) by the engine. Imagine taking ETC2 as an example. If there is no Alpha channel and the compression quality is acceptable, RGB_Compressed_ETC2_4bits can be used. If this meaningless Alpha channel is added, then we will automatically select RGBA_Compressed_ETC2_8bits when importing the settings in batches. In this way, the memory is doubled. Regarding the ASTC in the question, the definition of the Texture import format (https://github.com/Unity-Technologies/UnityCsReference/blob/master/Editor/Mono/AssetPipeline/TextureImporterEnums.cs) in the Unity editor source code has this comment: // ASTC uses 128bit block of varying sizes (we use only square blocks). It does not distinguish RGB/RGBA. That is, it has nothing to do with whether the Alpha channel is included. For an introduction to the ASTC format, I recommend you to read the ASTC Format Overview on Github: https://github.com/ARM-software/astc-encoder/blob/main/Docs/FormatOverview.md Regarding the issue of the new version of Unity mentioned in your previous reply, you can look at this issue on the Unity forum: https://forum.unity.com/threads/is-astc-rgb-encode-gone.660622 Some people may think that if the format of all textures in the project is ASTC, the meaning of removing Alpha is not very significant. In fact, it cannot be generalized. Although the size is the same, according to the test in (https://zhuanlan.zhihu.com/p/158740249), Whether there is an Alpha channel will affect the compression quality to a certain extent. Therefore, it must be used reasonably in the project.