Selecciona tu lenguaje de programación favorito. Todos los fragmentos de código serán mostrados en este lenguaje.
Gracias por ayudarnos a mejorar la calidad de la documentación de Unity. A pesar de que no podemos aceptar todas las sugerencias, leemos cada cambio propuesto por nuestros usuarios y actualizaremos los que sean aplicables.
CerrarPor alguna razón su cambio sugerido no pudo ser enviado. Por favor <a>intente nuevamente</a> en unos minutos. Gracias por tomarse un tiempo para ayudarnos a mejorar la calidad de la documentación de Unity.
Cerrar| eventID | User defined id to send to the callback. |
| callback | Native code callback to queue for Unity's renderer to invoke. |
Send a user-defined event to a native code plugin.
Rendering in Unity can be multithreaded if the platform and number
of available CPUs will allow for it. When multithreaded rendering is
used, the rendering API commands happen on a thread which is
completely separate from the one that runs the scripts. Consequently,
it is not possible for your plugin to start rendering immediately,
since it might interfere with what the render thread is doing at the time.
In order to do any rendering from the plugin, you should call
GL.IssuePluginEvent from your script, which will cause your native
plugin to be called from the render thread. For example, if you
call GL.IssuePluginEvent from the camera's OnPostRender function, you'll
get a plugin callback immediately after the camera has finished rendering.
Callback must be a native function of "void UNITY_INTERFACE_API UnityRenderingEvent(int eventId)" signature.
See Native Plugin Interface for more details
and an example.
See Also: SystemInfo.graphicsMultiThreaded.