godot 4.3 beta 1 mobile is rendering inversely to the screen.

[Rpgdelve]

Tested versions

4.3 beta 1

System information

Android 10, opengl es 3.0, qualcomm snapdragon 425, Adreno (TM) 308, 32 bits, armeabi-v7

Issue description

When I open Godot 4.3 beta 1 the rendering window is inverted in relation to my screen. and this bug also occurs when creating games.

Steps to reproduce

1 example: the window renders inversely to my screen.

2 example: when I click on the "Remover Ausente" option, the "Criar" option is selected instead.

Minimal reproduction project (MRP)

I can't say specifically why this bug occurs.

[Calinou]

Can you reproduce this in 4.2.2?

[Rpgdelve]

Can you reproduce this in 4.2.2?

are you asking me if this bug occurs in Godot 4.2.2? If that's the case, no, this bug only occurs in this version.

[akien-mga]

I don't reproduce the issue on a Pixel 7a, it might be a driver specific issue.

[akien-mga]

CC @Alex2782 who has access to some older Adreno devices too.

[Rpgdelve]

Maybe this is the case, my cell phone is a Samsung J6+.

[Rpgdelve]

But is there any possibility of this bug being fixed?

[Alex2782]

my cell phone is a Samsung J6+.

SM-J610F ? (on Amazon: Samsung SM-J610F Galaxy J6+)

https://opengles.gpuinfo.org/
SM-J610F i can find there, but only Adreno 308.

---

But is there any possibility of this bug being fixed?

Yes (i think), 3 months ago we added some workarounds for Adreno 3xx, Flip-Y bugfix was also included.
#87352

I have LG Nexus 5X (Adreno 418), but Arm64 (Android 8).
I'll check later if the Y-Flip bug is now reproducible with version 4.3-beta 1. (no 3 month ago)

[Alex2782]

ok, the Snapdragon-425 has a Qualcomm® Adreno™ 308 GPU Link

I have also Nexus 7 (Adreno 320) and there are some devices on Firebase Test Lab

[Rpgdelve]

my cell phone is a Samsung J6+.

SM-J610F ? (on Amazon: Samsung SM-J610F Galaxy J6+)

https://opengles.gpuinfo.org/
SM-J610F i can find there, but only Adreno 308.

---

But is there any possibility of this bug being fixed?

Yes (i think), 3 months ago we added some workarounds for Adreno 3xx, Flip-Y bugfix was also included.
#87352

I have LG Nexus 5X (Adreno 418), but Arm64 (Android 8).
I'll check later if the Y-Flip bug is now reproducible with version 4.3-beta 1. (no 3 month ago)

Yes, it's an Adreno (TM) 308; sorry for not informing you correctly.

[Alex2782]

@joined72: Which Adreno 3xx devices can you test again? Maybe we need to check the driver version behind the OpenGL version.

@Rpgdelve: please try: OrientationTest.zip
If possible on PC via Remote Debug (USB cable) and adb logcat -s godot. (If the logs are not displayed in the editor)

Screenshots

---

What happens when you press 2 - REVERSE_LANDSCAPE?

func _on_button_reverse_landscape_pressed():
	DisplayServer.screen_set_orientation(DisplayServer.SCREEN_REVERSE_LANDSCAPE)
	pass # Replace with function body.

---

Please try also: https://github.com/godotengine/godot/releases

• 4.2.2-stable (only orientation bug?)
• 4.2.1-stable (no crash?)

---

I could not reproduce it, all Adreno 3xx devices we tested 3 months ago still need this bugfix.

godot/drivers/gles3/rasterizer_gles3.cpp

Line 201 in 705b7a0

flip_xy_bugfix = GLES3::Config::get_singleton()->adreno_3xx_compatibility;

GL_VERSION / video_adapter_api_version

---

gpuinfo: Nexus 7 vs. Samsung J6+

• OpenGL ES 3.0 V@127.0 AU@ (GIT@I96aee987eb)
• OpenGL ES 3.0 V@415.0 (GIT@d39f783, I79de86aa2c, 1591296226) (Date:06/04/20)

---

• moto e5 play: OpenGL ES 3.0 V@269.0 AU@ (GIT@I109c45a694)
• Moto G Play: OpenGL ES 3.0 V@140.0 AU@ (GIT@Ifd751822f5)
• Huawei Mediapad T3 AGS-W09 (Android 8): OpenGL ES 3.0 V@251.0 [email protected] (GIT@Ie4790512f3)

---

No Bugs

• LG Nexus 5X (Adreno 418): OpenGL ES 3.2 V@258.0 (GIT@8e59954, I0be83d0d26) (Date:09/22/17)
• Moto Z (Adreno 530): OpenGL ES 3.2 V@145.0 (GIT@I7ece6fe30d)
• Galaxy Tab S3 (Adreno 530): OpenGL API OpenGL ES 3.2 V@331.0 (GIT@7dbb41d, Iebf953a4a5) (Date:12/21/18)
• Samsung Tab S7 (Adreno 650): OpenGL ES 3.2 V@0502.0 (GIT@193b2ee, I593c16c433, 1633593732) (Date:10/07/21)

[Rpgdelve]

Ok, I'll check these versions.

[Rpgdelve]

Report Godot 4.2.2
screen rendering.
From what I see, the Godot 4.3 beta 1 bug only happens in this version. Because Godot 4.2.2 works normally. version.https://github.com/godotengine/godot/assets/171452240/dcddf9a8-4aa6-4180-84d7-93b58120f072

compilation.
When I run Godot, the screen is also not inverted.
https://github.com/godotengine/godot/assets/171452240/6ede2f90-81d4-4792-80db-2f85d8cedb12

bug.
There's a bug I forgot to mention: when I click to open a window, if I'm not careful, that window can end up being rendered outside of my screen.
https://github.com/godotengine/godot/assets/171452240/603b0c68-be72-42c1-b81c-5e9a9a758158
But I discovered a way to get around this problem, which was to increase the rendering screen.
Perhaps an important detail.

sorry.
Unfortunately, I don't have access to a computer and was unable to run the command to check further correctly.

[Rpgdelve]

Report Godot 4.2.2
screen rendering.
From what I see, the Godot 4.3 beta 1 bug only happens in this version. Because Godot 4.2.2 works normally. version.https://github.com/godotengine/godot/assets/171452240/dcddf9a8-4aa6-4180-84d7-93b58120f072

compilation.
When I run Godot, the screen is also not inverted.
https://github.com/godotengine/godot/assets/171452240/6ede2f90-81d4-4792-80db-2f85d8cedb12

@onready var mesh = $MeshInstante3D

Func _process(delta):
mesh.rotate_object_local(vector3(0, 0, 1,), 1.0 *delta)

bug.
There's a bug I forgot to mention: when I click to open a window, if I'm not careful, that window can end up being rendered outside of my screen.
https://github.com/godotengine/godot/assets/171452240/603b0c68-be72-42c1-b81c-5e9a9a758158
But I discovered a way to get around this problem, which was to increase the rendering screen.
Perhaps an important detail.

sorry.
Unfortunately, I don't have access to a computer and was unable to run the command to check further correctly.

summary.
For me this version is great and stable.

[Alex2782]

Unfortunately, I don't have access to a computer and was unable to run the command to check further correctly.

Thanks, this information is also sufficient, it is identical to the information on the homepage. I'll try to create a new 'PR' in the next few days. I will deactivate adreno_3xx_compatibility, starting with driver version 331.0

---

Android 10: https://opengles.gpuinfo.org/displayreport.php?id=4986
OpenGL ES 3.0 [email protected] (GIT@d39f783, I79de86aa2c, 1591296226) (Date:06/04/20)

Android 9: https://opengles.gpuinfo.org/displayreport.php?id=4696
OpenGL ES 3.0 [email protected] (GIT@35e467f, Ice9844a736) (Date:04/15/19)

[Rpgdelve]

Unfortunately, I don't have access to a computer and was unable to run the command to check further correctly.

Thanks, this information is also sufficient, it is identical to the information on the homepage. I'll try to create a new 'PR' in the next few days. I will deactivate adreno_3xx_compatibility, starting with driver version 331.0

---

Android 10: https://opengles.gpuinfo.org/displayreport.php?id=4986
OpenGL ES 3.0 [email protected] (GIT@d39f783, I79de86aa2c, 1591296226) (Date:06/04/20)

Android 9: https://opengles.gpuinfo.org/displayreport.php?id=4696
OpenGL ES 3.0 [email protected] (GIT@35e467f, Ice9844a736) (Date:04/15/19)

Thank you for your attention.

[Alex2782]

Because Godot 4.2.2 works normally.

@Rpgdelve could you please also test GPUParticles (Godot 4.2.2), crash?

Godot 4.3 beta 1 Should display an error message:"Due to driver bugs, GPUParticles are not supported on Adreno 3XX devices. Please use CPUParticles instead."
#92741 (comment)

If there is no crash on your device then we can reactivate it.

[Rpgdelve]

Okay, I'll do a test.

[Alex2782]

I tried it today, no crash but 'invisible' on Adreno 3xx and old driver
#92741 (comment)

[Rpgdelve]

_Godot report 4.2.2 GPUParticles _

CPUParticles2D
Test

After running the scene, I didn't identify any errors. The FPS seems stable.

Observation.

I ran all the scenes for 20 seconds.

FPS

GPUParticles2D

test

It also doesn't seem to have any issues with FPS drops, but there is a bug that occurs when editing GPUParticles, but when running it doesn't occur.

Bug

interface.

Test_gpu_2d_video.mp4

executed.

2_test_gpu_2d_video.mp4

FPS

CPUParticles3D

test

I also didn't identify any bugs, but the FPS ended up dropping.

FPS

GPUParticles3D

test

For some reason, GPUparticles has a bug that occurs in the layout and execution screen.

Bug

Test_gpu_3d_video.mp4

FPS

[Rpgdelve]

report update

I think I discovered the cause of the bug I reported earlier. This bug was caused by the fidex FPS, which was at 30 fps. Well, when I lowered it to 10 fps, the bug stopped happening.

GPUParticles2D

Test_Gpu_2D_video.mp4

GPUParticles3D

Test_gpu_3D_video.mp4