asgardius/virtualx-engine
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge pull request #92719 from lawnjelly/doc_mipmap_warning

Browse source 
[3.x] `ImageTexture` - document workaround for mipmap generation
This commit is contained in:
lawnjelly 2024-06-30 12:13:52 +01:00 committed by GitHub
commit e2c7073b4e
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
doc/classes/ImageTexture.xml
View file

@ -26,6 +26,7 @@
[/codeblock] [/codeblock]
An [ImageTexture] is not meant to be operated from within the editor interface directly, and is mostly useful for rendering images on screen dynamically via code. If you need to generate images procedurally from within the editor, consider saving and importing images as custom texture resources implementing a new [EditorImportPlugin]. An [ImageTexture] is not meant to be operated from within the editor interface directly, and is mostly useful for rendering images on screen dynamically via code. If you need to generate images procedurally from within the editor, consider saving and importing images as custom texture resources implementing a new [EditorImportPlugin].
[b]Note:[/b] The maximum texture size is 16384×16384 pixels due to graphics hardware limitations. [b]Note:[/b] The maximum texture size is 16384×16384 pixels due to graphics hardware limitations.
[b]Note:[/b] Mipmap generation can fail with some graphics drivers (especially on Android), resulting in black textures. In these cases, consider either calling [method Image.generate_mipmaps], or creating an [ImageTexture] without [constant Texture.FLAG_MIPMAPS].
</description> </description>
<tutorials> <tutorials>
<link title="Importing images">$DOCS_URL/tutorials/assets_pipeline/importing_images.html</link> <link title="Importing images">$DOCS_URL/tutorials/assets_pipeline/importing_images.html</link>