Clay John comments

Results 411 comments of


                                            Clay John

trafficstars

Vulkan: SSIL produces undesirable distant occlusion when Half Size is enabled

May have been fixed by https://github.com/godotengine/godot/pull/72838

macOS Safari 16.1 (latest version) - all HTML5 exports crash on loading (even empty projects with default settings)

> In the upcoming days I'll try to reproduce it on linux, on older branches (corresponding to WebKit 605/604 the Safari uses) and if I succeed it will mean that...

Vulkan: Screen-space effects (SSAO, SSIL, SSR) sometimes break when the viewport is resized

Related: https://github.com/godotengine/godot/issues/62881 and https://github.com/godotengine/godot/issues/65987

Implement CAMERA_VISIBLE_LAYERS as built-in shader variable

Approved with respect to implementation

Vulkan canvas_item shader different to GLS3

I can't reproduce the issue on an intel integrated GPU with PopOS 22.04 and running current master f692b476869c14023b342c12efc21cb5cd6002b7 The result looks fine: ![Screenshot from 2022-12-08 12-13-37](https://user-images.githubusercontent.com/16521339/206558578-4608f782-bec0-461b-b3e3-a288bc0ce8b3.png)

Vulkan canvas_item shader different to GLS3

@Lippanon ![Screenshot from 2022-12-08 12-25-03](https://user-images.githubusercontent.com/16521339/206560391-82bf2885-ccfe-4da3-830d-b7251e1b37b7.png)

Vulkan canvas_item shader different to GLS3

It could be an issue from using sin in the hash function see e.g. https://www.shadertoy.com/view/4djSRW

Vulkan canvas_item shader different to GLS3

@Lippanon Can you test the same shader in shadertoy to see if you get the issue there as well? here is the code converted to shadertoy: ``` float hash12(vec2 p)...

Vulkan canvas_item shader different to GLS3

Just to update everyone on this issue. This is an NVidia Vulkan driver bug. I'm glad to here users have found a workaround, because there isn't really anything we can...

Blurred sprite after movement

> @Calinou should this be solved (even when using `move_and_slide`) when setting both the snap options? IMO the snap options should eliminate this artifact entirely.