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

ram usage when editing goes up rapidly #260

Closed
RogerRandomDev opened this issue Nov 30, 2023 · 4 comments
Closed

ram usage when editing goes up rapidly #260

RogerRandomDev opened this issue Nov 30, 2023 · 4 comments
Labels
duplicate This issue or pull request already exists

Comments

@RogerRandomDev
Copy link

Terrain3D version

0.8.3

Godot version

4.2 beta6

System information

linux xubuntu

Is the issue reproducable in the demo?

Yes

Issue description

my ram goes up rapidly whenever updating the terrain. i do have it saved as a .res file, which made it slower, but the ram increase is extreme, sometimes more than 100 mb in a second

Logs

No response

@TokisanGames
Copy link
Owner

TokisanGames commented Nov 30, 2023

How many regions do you have?

Use your monitors to display exactly how much ram is used, or at least your system process monitor. We can't do anything with anecdotal evidence, and 100mb is nothing. Get specific. You are allocating memory when you allocate regions. If ram usage isn't going up that would be a problem.

Disable collision and check ram usage. Maybe a duplicate of #161 or #165.

@TokisanGames
Copy link
Owner

There is a version for 4.2 linked in the latest release notes. You can try that.

Saving the storage resource file to binary .res as opposed to leaving it in the scene to be saved as text most certainly would not make it slower. Saving the data as text requires writing 10-40x more data, which is not possible to be faster.

Much more observation and testing from you is needed to take any action on this. However if I don't get any responses or further information, I will close this issue in a few days as it's not reproducible.

@RogerRandomDev
Copy link
Author

How many regions do you have?

Disable collision and check ram usage. Maybe a duplicate of #161 or #165.

I'm only using 4 regions, and i have collision disabled. the 100 mb i list is per change, I.E. any time the mouse gets moved. I've noticed it most when the height of the entire map is changing the most.

@TokisanGames TokisanGames added the duplicate This issue or pull request already exists label Dec 4, 2023
@TokisanGames
Copy link
Owner

Thanks for the response. OK. That's working normally then. The maps are duplicated so that undo and redo works. We either increase ram usage or no undo. #165 will reduce this consumption, so I'll mark this as a duplicate.

@TokisanGames TokisanGames closed this as not planned Won't fix, can't repro, duplicate, stale Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants