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

gfauto: add support for different framebuffer sizes #1089

Open
amakin-siru opened this issue Nov 4, 2020 · 3 comments
Open

gfauto: add support for different framebuffer sizes #1089

amakin-siru opened this issue Nov 4, 2020 · 3 comments

Comments

@amakin-siru
Copy link
Contributor

If a test carries out loads of calculations, it's sometimes necessary to reduce the framebuffer size to prevent timeout occurring. Gfauto should have an option for this.

@ghost
Copy link

ghost commented Nov 6, 2020

Hi would you please tell me more about this issue.

@prath06
Copy link

prath06 commented Nov 13, 2020

to make Optimal, I think reducing the framebuffer size will be better

@paulthomson
Copy link
Collaborator

I think we will need to add another field to the shader.json file e.g. $framebuffer: {width: 32, height: 32}. We need to update GraphicsFuzz (i.e. the Java code in the graphicsfuzz repo) so that it accepts the field (it could just ignore it, but it must not crash). And then we need to update gfauto to use the values when generating the AmberScript.

ghost and prath06: Apologies, but I don't think this is a good first issue; it is not well-documented, and we don't currently have the resources to mentor contributors outside Google Summer of Code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants