You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please also see the 3.80 Change Log for details about the major 3.80 release.
Bug Fixes
Fix RenderTexture crashing in the presence of a light.
Fix failure to restore compressed textures after WebGL context loss.
Fix a single WebGL error, with no visual side-effects, from occurring while calling Shader.setRenderToTexture() after the game has started running. Actually, the root cause was leaving new WebGL textures bound after creation.
Ensure that TextureSource.setFlipY always updates the texture.
Remove unsynced flipY from render textures in Shader and DynamicTexture.
Modified onMouseUpWindow and onMouseDownWindow in the MouseManager so they now check for sourceCapabilities.firesTouchEvents and if found, abort registering the event. This new browser event property is designed to prevent you accidentally registering a Mouse Event when a Touch Event has just occurred (see https://developer.mozilla.org/en-US/docs/Web/API/InputDeviceCapabilities/firesTouchEvents)
This discussion was created from the release Phaser v3.80.1.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Please also see the 3.80 Change Log for details about the major 3.80 release.
Bug Fixes
RenderTexture
crashing in the presence of a light.Shader.setRenderToTexture()
after the game has started running. Actually, the root cause was leaving new WebGL textures bound after creation.TextureSource.setFlipY
always updates the texture.flipY
from render textures inShader
andDynamicTexture
.TouchManager
that would prevent clicks from outside the game window from being registered. Fix After updating to Phaser 3.80 using Capacitor and Ionic #6747 (thanks @ulsoftnaver @jaxtheking)Updates
onMouseUpWindow
andonMouseDownWindow
in theMouseManager
so they now check forsourceCapabilities.firesTouchEvents
and if found, abort registering the event. This new browser event property is designed to prevent you accidentally registering a Mouse Event when a Touch Event has just occurred (see https://developer.mozilla.org/en-US/docs/Web/API/InputDeviceCapabilities/firesTouchEvents)This discussion was created from the release Phaser v3.80.1.
Beta Was this translation helpful? Give feedback.
All reactions