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

Jabba performance adjust #5

Merged
merged 4 commits into from
Aug 10, 2020
Merged

Conversation

jahtim
Copy link
Contributor

@jahtim jahtim commented Aug 10, 2020

5% fps increase if you have 50 jabba barrels in your render distance. This change actually makes the item and text on the barrel not rendering when the player is far (4m default). and this could be configurable.

@draknyte1
Copy link
Contributor

4M is far too low for a new default.
Suggest 4m is the comment, leave default as default.

Copy link
Contributor

@draknyte1 draknyte1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As above.

@jahtim
Copy link
Contributor Author

jahtim commented Aug 10, 2020

Changed to distance of 100 as default

1 similar comment
@jahtim
Copy link
Contributor Author

jahtim commented Aug 10, 2020

Changed to distance of 100 as default

@@ -129,7 +129,7 @@ public void preInit(FMLPreInitializationEvent event) {

allowOreDictUnification = config.getBoolean("allowOreDictUnification", Configuration.CATEGORY_GENERAL, true, "If true, Jabba will try unificate 'ingot' 'ore' 'dust' and 'nugget' using oredict");

renderDistance = config.getFloat("renderDistance", Configuration.CATEGORY_GENERAL, 16f, 0f, 10000f, "Render Distance (square) for stack and text on barrel.");
renderDistance = config.getFloat("renderDistance", Configuration.CATEGORY_GENERAL, 10000f, 0f, 10000f, "Render Distance (square) for stack and text on barrel.");
Copy link

@hazzal hazzal Aug 10, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we change the text for the config to describe that it is actually cubed (not squared) distance.
Please disregard, thankfully Glease corrected my wrong interpretation.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No. Check the code again. It is indeed squared.

Copy link

@hazzal hazzal Aug 10, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apologies in that case. Please disregard my initial comment and thanks for correcting me Glease

@Dream-Master
Copy link
Member

@TataTawa @draknyte1 @hazzal can we merge it ?

@draknyte1
Copy link
Contributor

Yes.

@Dream-Master Dream-Master merged commit 3e27c34 into GTNewHorizons:master Aug 10, 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

Successfully merging this pull request may close these issues.

None yet

5 participants