Default value of 'bUseUObjectArrayCache' is now false in non-zDev #747
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
UE4SS
force-pushed
the
disable-buseobjectarraycache-for-nondev
branch
from
da18d77 to
4200921
Compare
|
I wouldn't say this Fixes #315, it's more of a workaround for now. |
Okay. |
Buckminsterfullerene02
approved these changes
Jan 9, 2025
|
Oh, that's how it's done. Makes sense, default value is always |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The
bUseUObjectArrayCacheoption doesn't work as intended, and fixing it seems unlikely so this PR disables it for non-zDev releases by default.It still needs to be enabled for zDev releases because the live view search feature relies on it.
Workaround for #315
Type of change
How Has This Been Tested?
Locally ran the release.py srcipt and verified that the value of the option is correct.
Checklist