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

On Windows, F3D is very laggy when resizing the window IF the cheatsheet is shown #1013

Open
Tracked by #1243
mwestphal opened this issue Sep 30, 2023 · 7 comments
Open
Tracked by #1243
Labels
os:windows type:bug Something isn't working
Milestone

Comments

@mwestphal
Copy link
Contributor

Describe the bug
On Windows, F3D is very laggy when resizing the window IF the cheatsheet is shown

To Reproduce
Steps to reproduce the behavior:

  1. Open the file using f3d --dry-run example.glb
  2. Press H to show cheatsheet
  3. Resize window using the edge of the window
  4. Very laggy

Expected behavior
Showing the cheatsheet should not impact the performance of F3D during resize

System Information:

  • OS: Windows
@mwestphal mwestphal added this to the 2.3.0 milestone Sep 30, 2023
@Meakk
Copy link
Contributor

Meakk commented Sep 30, 2023

Just tried, cannot see any difference with or without the cheatsheet.

@Meakk
Copy link
Contributor

Meakk commented Sep 30, 2023

Actually, I reproduce. It happens when the font inside the cheatsheet (or the metadata) window is changed because of the resizing.

@mwestphal
Copy link
Contributor Author

Then it should happen with the filename too ?

@jspanchu
Copy link
Contributor

jspanchu commented Oct 22, 2023

@mwestphal I'm noticing this even on macOS. When the cheatsheet is shown, resizing is slow. Also, toggling any feature takes too much time. Ex: try turning on/off the grid or increase light intensity. With the cheatsheet, it takes about 1-2 seconds for the feature to actually get toggled. Maybe something unintendedly introduces a delay in the interactor event processing loop?

@mwestphal
Copy link
Contributor Author

Sounds like a different issue ?

@jspanchu
Copy link
Contributor

unsure, Could it be that an improper configuration of the interactor (event observers, etc) causes similar behavior on both mac and windows?

@mwestphal
Copy link
Contributor Author

I've seen similar things on Linux as well. Lets loop back on it once we have #1077

@mwestphal mwestphal self-assigned this Dec 21, 2023
@mwestphal mwestphal added the help wanted Please help with this issue! label Jan 7, 2024
@mwestphal mwestphal modified the milestones: 2.3.0, 2.4.0 Jan 7, 2024
@mwestphal mwestphal removed the help wanted Please help with this issue! label Jan 26, 2024
@Meakk Meakk added this to F3D Feb 2, 2024
@mwestphal mwestphal removed this from the 2.4.0 milestone Feb 3, 2024
@mwestphal mwestphal moved this to Investigate in F3D Feb 10, 2024
@mwestphal mwestphal added the type:bug Something isn't working label Feb 10, 2024
@mwestphal mwestphal removed their assignment Feb 10, 2024
@mwestphal mwestphal added this to the 3.0.0 milestone Jul 5, 2024
@mwestphal mwestphal mentioned this issue Jul 13, 2024
23 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
os:windows type:bug Something isn't working
Projects
Status: Investigate
Development

No branches or pull requests

3 participants