Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Some) examples don't work #11

Closed
freder opened this issue Aug 5, 2018 · 1 comment
Closed

(Some) examples don't work #11

freder opened this issue Aug 5, 2018 · 1 comment
Assignees
Labels
bug Something isn't working vulkan Issues with the Vulkan backend

Comments

@freder
Copy link

freder commented Aug 5, 2018

./hellotriangle

FEngine (64 bits) created at 0x10a798000
FEngine resolved backend: Vulkan
[mvk-info] MoltenVK version 1.0.8. Vulkan version 1.0.73.
[mvk-info] GPU device:
		model: AMD Radeon Pro 450
		type: Discrete
		vendorID: 0x1002
		deviceID: 0x67ef
		pipelineCacheUUID: 00000000-0000-0000-0000-271300002718
	supports the following Metal Feature Sets:
		macOS GPU Family 1 v3
		macOS GPU Family 1 v2
		macOS GPU Family 1 v1
[mvk-info] GPU device:
		model: Intel(R) HD Graphics 530
		type: Integrated
		vendorID: 0x8086
		deviceID: 0x191b
		pipelineCacheUUID: 00000000-0000-0000-0000-271300002718
	supports the following Metal Feature Sets:
		macOS GPU Family 1 v3
		macOS GPU Family 1 v2
		macOS GPU Family 1 v1
Selected physical device: AMD Radeon Pro 450
[mvk-info] Created VkDevice to run on GPU AMD Radeon Pro 450
[mvk-info] Created 2 swapchain images with initial size (2048, 1280).
vkCreateSwapchain: 2048x1280, VK_FORMAT_B8G8R8A8_UNORM, VK_COLOR_SPACE_SRGB_NONLINEAR_KHR, 2
[***MoltenVK ERROR***] VK_ERROR_INITIALIZATION_FAILED: Shader library compile failed (error code 1):
Timeout after 125.000 milliseconds. Likely internal Metal compiler error.
froxel arena: High watermark 0 KiB (0%)
froxel arena: High watermark 0 KiB (0%)
Renderer: Commands High watermark 0 KiB (0%), 3 commands, 40 bytes/command
CircularBuffer: High watermark 5 KiB (0%)
cleaning up 1 leaked filament::details::FMaterial
Destroying 0 descriptor sets.
per-renderpass allocator arena: High watermark 1023 KiB (16%)

./hellopbr

[...]
Selected physical device: AMD Radeon Pro 450
[mvk-info] Created VkDevice to run on GPU AMD Radeon Pro 450
The specified IBL path does not exist: ../samples/envs/office
[1]    88881 segmentation fault  ./hellopbr

./shadowtest

[...]
Selected physical device: AMD Radeon Pro 450
[mvk-info] Created VkDevice to run on GPU AMD Radeon Pro 450
The specified IBL path does not exist: ../samples/envs/office
[1]    89676 segmentation fault  ./shadowtest

./texturedquad

[...]
Selected physical device: AMD Radeon Pro 450
[mvk-info] Created VkDevice to run on GPU AMD Radeon Pro 450
Loaded texture: 2048x2048
[mvk-info] Created 2 swapchain images with initial size (2048, 1280).
vkCreateSwapchain: 2048x1280, VK_FORMAT_B8G8R8A8_UNORM, VK_COLOR_SPACE_SRGB_NONLINEAR_KHR, 2
[1]    89815 segmentation fault  ./texturedquad

image

@prideout prideout self-assigned this Aug 5, 2018
@prideout
Copy link
Contributor

prideout commented Aug 5, 2018

The latter three Vulkan samples were launched from the wrong directory, I'll make this more friendly.

The shader failure in hellotriangle may be related to recent changes in our shader pipeline, I'll take a look.

The Vulkan backend is still in an experimental state.

@prideout prideout added the vulkan Issues with the Vulkan backend label Aug 5, 2018
@romainguy romainguy added the bug Something isn't working label Aug 5, 2018
prideout added a commit that referenced this issue Aug 23, 2018
This removes the build step where we copy a subset of assets, and makes
it so that FilamentApp hands out a "root path" for assets. For now this
is determined based on the location of the executable. This allows
developers to launch samples from any CWD.

Closes #11
prideout added a commit that referenced this issue Aug 23, 2018
This removes the build step where we copy a subset of assets, and makes
it so that FilamentApp hands out a "root path" for assets. For now this
is determined based on the location of the executable. This allows
developers to launch samples from any CWD.

Closes #11
prideout added a commit that referenced this issue Aug 23, 2018
* Try to clean up asset folders for sample apps.

This removes the build step where we copy a subset of assets, and makes
it so that FilamentApp hands out a "root path" for assets. For now this
is determined based on the location of the executable. This allows
developers to launch samples from any CWD.

Closes #11

* Restore asset copy to build.
rbsheth pushed a commit to rbsheth/filament that referenced this issue Jun 30, 2022
- add create and destroy callback to buffer object
- allow read pixels into buffer object without downloading from CPU
- allow upload textures data using buffer objects
- add gltf image extension for passing in buffer object pointer
- add gpu thread callback

note only the openGl api has been implemented for these
rbsheth pushed a commit to rbsheth/filament that referenced this issue Jun 30, 2022
- add create and destroy callback to buffer object
- allow read pixels into buffer object without downloading from CPU
- allow upload textures data using buffer objects
- add gltf image extension for passing in buffer object pointer
- add gpu thread callback

note only the openGl api has been implemented for these
zbai-sc added a commit to zbai-sc/filament that referenced this issue Nov 18, 2022
- add create and destroy callback to buffer object
- allow read pixels into buffer object without downloading from CPU
- allow upload textures data using buffer objects
- add gpu thread callback

note only the openGl api has been implemented for these
zbai-sc added a commit to zbai-sc/filament that referenced this issue Nov 20, 2022
- add create and destroy callback to buffer object
- allow read pixels into buffer object without downloading from CPU
- allow upload textures data using buffer objects
- add gpu thread callback

note only the openGl api has been implemented for these
zbai-sc added a commit to zbai-sc/filament that referenced this issue Nov 21, 2022
- add create and destroy callback to buffer object
- allow read pixels into buffer object without downloading from CPU
- allow upload textures data using buffer objects
- add gpu thread callback

note only the openGl api has been implemented for these
zbai-sc added a commit to zbai-sc/filament that referenced this issue Jan 17, 2023
- add create and destroy callback to buffer object
- allow read pixels into buffer object without downloading from CPU
- allow upload textures data using buffer objects
- add gpu thread callback

note only the openGl api has been implemented for these
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working vulkan Issues with the Vulkan backend
Projects
None yet
Development

No branches or pull requests

3 participants