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

Signals & Couplers create FPS lag #1709

Closed
ImagineerDave opened this issue Feb 2, 2025 · 3 comments
Closed

Signals & Couplers create FPS lag #1709

ImagineerDave opened this issue Feb 2, 2025 · 3 comments
Labels
type: bug Issue where something isn't working type: upstream This is inherited from upstream Forge Create. It is highly unlikely we will change it.

Comments

@ImagineerDave
Copy link

Description

For a long while my area over at my SMP was lagging a lot. I always thought it was due to a lot of copycats+ but lagg doesnt seem to increase that much. After a while I started testing some other things like signals and couplers from Steam n rails.

In this setup I used 70 couplers and 115 signals. Outcome ; 98 fps with nothing (or well crap in the background), 47 fps with only the couplers, 43 with couplers and signals, 82 with signals only.

Image
Image
Image
Image

After stating this to IThunder he pointed me towards create where he said that signals wouldn't be instanced (no clue what it means really)

Game Log

none available, game didnt crash or report anything

Debug Information

No response

@ImagineerDave ImagineerDave added status: needs testing Issue needs testing type: bug Issue where something isn't working labels Feb 2, 2025
@IThundxr
Copy link
Member

IThundxr commented Feb 2, 2025

This should be on the create forge repo

@IThundxr IThundxr closed this as not planned Won't fix, can't repro, duplicate, stale Feb 2, 2025
@IThundxr IThundxr added type: upstream This is inherited from upstream Forge Create. It is highly unlikely we will change it. and removed status: needs testing Issue needs testing labels Feb 2, 2025
@ImagineerDave
Copy link
Author

@IThundxr why should it be on forge? I played on fabric?

@IThundxr
Copy link
Member

IThundxr commented Feb 2, 2025

Because the issue occurs on forge aswell, and create fabric does not make changes if the said issue happens on forge aswell, instead the fix from forge is pulled in, which in this case will be instances for signals

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Issue where something isn't working type: upstream This is inherited from upstream Forge Create. It is highly unlikely we will change it.
Projects
None yet
Development

No branches or pull requests

2 participants