Skip to content

Update develop with ForeverFPS #3634

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

Merged
merged 93 commits into from
Mar 1, 2025
Merged

Update develop with ForeverFPS #3634

merged 93 commits into from
Mar 1, 2025

Conversation

Geenz
Copy link
Collaborator

@Geenz Geenz commented Feb 28, 2025

No description provided.

RunitaiLinden and others added 30 commits December 18, 2024 13:45
…that our passed in ambient lighting is the only thing that gets applied. (#3327)
Try to handle this more gracefully, but primary purpose of this change
is to log wchars in case issue is reproducible.
…inimize vram usage and chance of probe nans (#2558)
Fix world going black and white on apple gpu
Instead of when there is any space.
if bias stays unchanged at 4.f, there is no reason to keep refreshing
at high rate.
Callstacks indicate that this happens only on shutdown.
No point to erase items one at a time, just clear the list beforehand.
Don't rely onto region for cleanup
Most crashes are related to LLStyle, log analysis suggests that it might
be a number of different issues, including memory and disk issues.
Just avoid recreating expensive LLStyle without reason.
akleshchev and others added 17 commits February 15, 2025 02:51
A workaround, hopefully temporary.
First test returns half the throughput, do two tests. May be caused by
driver, may be some 'energy saving', will need to be checked later.
It was working the same way prior to ExtraFPS, but viewer was running
an extra CPU test.
1. Cover reset with 'generation'
2. Fix lapse of judgement with mLastFontGlyphCount, it should have been
saved before render(), not after
- #3594 Adjustments to mitigate sun reflection being too narrow.
Copy link


Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.


I have read the CLA Document and I hereby sign the CLA


7 out of 8 committers have signed the CLA.
✅ (RunitaiLinden)[https://github.com/RunitaiLinden]
✅ (brad-linden)[https://github.com/brad-linden]
✅ (maxim-productengine)[https://github.com/maxim-productengine]
✅ (akleshchev)[https://github.com/akleshchev]
✅ (Geenz)[https://github.com/Geenz]
✅ (nat-goodspeed)[https://github.com/nat-goodspeed]
✅ (marchcat)[https://github.com/marchcat]
@rye
Rye seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

@Geenz Geenz merged commit 5d78ff4 into develop Mar 1, 2025
40 of 42 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Mar 1, 2025
@Geenz Geenz deleted the release/2024.12-ForeverFPS branch March 6, 2025 20:23
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants