processing / processing/p5.js

[p5.js 2.0+ Bug Report]: frameBuffer causes warning in Safari

Open
#9,138 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area:WebGL p5.js 2.0+
Dominant language
JavaScript
Stars
24k
Forks
3.8k
Avg merge
3d 16h
Merged PRs (30d)
25

Description

Most appropriate sub-area of p5.js?
  • Accessibility
  • Color
  • Core/Environment/Rendering
  • Data
  • DOM
  • Events
  • Image
  • IO
  • Math
  • Typography
  • Utilities
  • WebGL
  • WebGPU
  • p5.strands
  • Build process
  • Unit testing
  • Internationalization
  • Friendly errors
  • Other (specify if possible)
p5.js version

2.1.1

Web browser and version

About Safari

Operating system

macOS Tahoe 26.6.2

Steps to reproduce this
Steps:
  1. Error occurs trying to initialize the frame buffer
Snippet:
let cnv = createCanvas(windowWidth, windowHeight, WEBGL)
let  fbA = createFramebuffer({
		width,
		height,
		format: FLOAT,
		textureFiltering: NEAREST
	});

Error message:
Warning: The requested width/height exceeds hardware limits. Adjusting dimensions to width: 0, height: 0.
This environment does not support FLOAT textures. Falling back to UNSIGNED_BYTE.
This environment does not support FLOAT depth textures. Falling back to UNSIGNED_INT.

This sketch was operational in Safari when I submitted it to #WCCChallenge on openProcessing last week. I have checked other sketches and I think all the ones that use a frame buffer are broken. https://openprocessing.org/@kfahn/2997648

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in Safari using the supplied WEBGL and createFramebuffer snippet, and compare it with the linked openProcessing sketch. Start by tracing frameBuffer initialization and the reported hardware and texture warnings; done means frame buffers initialize without these warnings and the affected sketch remains operational.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
computer-graphics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.