Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

About FBO and getProgramInfoLog delay. #3434

Closed
state303 opened this issue Jan 20, 2025 · 0 comments
Closed

About FBO and getProgramInfoLog delay. #3434

state303 opened this issue Jan 20, 2025 · 0 comments

Comments

@state303
Copy link

state303 commented Jan 20, 2025

Hi everyone!
First of all, thank you all for this great framework. Been enjoying it ever since I found.

I have a simple question regarding the FBO and the 3.5 second long delay; which happens due to the 'getProgramInfoLog' process.

On Debian environment, the loading is significantly lower (like 200ms)

Packages

pkg version
Next 15.1.4
React 19.0.0
@react-three/fiber 9.0.0-rc.4
@react-three/drei https://pkg.csb.dev/pmndrs/drei/commit/d2d25601/@react-three/drei

Notes

Not using Next turbo thing, just a plain Web Pack setup (followed next-three-drei template)

Example (takes some time.. like 5 seconds..)

https://codesandbox.io/p/devbox/l49qhm

Is there any possible solution to asynchronously build the texture, such that UI doesn't get blocked?
Will write some detailed post on the solution over this problem, but it seems the block cannot be avoided in this scenario.

I tried suspend, dynamic import, etc, but none works without initial freeze on the browser's end, due to the WebGL being blocked with getProgramInfoLog.

Found some old issues that mentions disabling it with getContext().getProgramInfoLog=() => ''; , however, it won't help on this case.
Should I utilize web-worker in this case? or... is there any good references I could dig in?

Edit

There was a duplicate post on here.
And it seems to be related to the KHR_parallel_shader_compile support but closed on asyncCompile implementation PR.

@pmndrs pmndrs locked and limited conversation to collaborators Jan 20, 2025
@CodyJasonBennett CodyJasonBennett converted this issue into discussion #3435 Jan 20, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant