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

Text_Debug example #1170

Closed
sigten opened this issue Dec 30, 2020 · 2 comments
Closed

Text_Debug example #1170

sigten opened this issue Dec 30, 2020 · 2 comments

Comments

@sigten
Copy link

sigten commented Dec 30, 2020

Bevy version

0.4.0

Operating system & version

Windows 10

What you did

Cloned the Bevy repo, navigated to the Bevy directory, and ran:
cargo run --example text_debug --release

What you expected to happen

text_layout
(from the Bevy 0.4.0 release notes)

What actually happened

Screenshot
(screenshot)

Additional information

  • Perhaps there is an issue with the size and/or max_size fields in TextBundle?
  • I seem to be seeing the infamous wavy text bug (wasn't this resolved in 0.4.0?)
  • I am also getting very poor rendering quality with text (this could from the known issue with regard to the HiDPI changes made in 0.4.0)
  • My frame rate seems to be limited to 30 fps, despite vsync being disabled in the example. I tried adding
.add_resource(ScheduleRunnerSettings::run_loop(Duration::from_secs_f64(
            1.0 / 60.0,
        )))

to the app builder in the example, but it didn't change anything

Thank you all for your fine work and great discussions on this project! I apologize in advance if this is a coding error on my part or if more information is necessary. I am a hobbyist coder and this is my very first Github post.

@sigten
Copy link
Author

sigten commented Dec 31, 2020

update: while I was writing this issue, a commit came out that fixed most of the issues I was having (#1132).

New_Screenshot
I appear to be only having the odd frame limiting issue now. The text looks great!

@sigten
Copy link
Author

sigten commented Dec 31, 2020

Okay, I am now realizing that this issue is just me, sorry for the mistake! Enabling vsync does what it should and stops the frame limiting.

@sigten sigten closed this as completed Dec 31, 2020
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

1 participant