-
-
Notifications
You must be signed in to change notification settings - Fork 157
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
godot4.3.dev5 headless profile not good #434
Comments
Did you try hiding the node? |
I just hide the window,and make no camera is current(I create each room as a window by use its own world3d,and the hterrain is the child of a node on the window)
…---Original---
From: ***@***.***>
Date: Wed, Apr 17, 2024 02:04 AM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [Zylann/godot_heightmap_plugin] godot4.3.dev5 headless profilenot good (Issue #434)
Did you try hiding the node?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Hiding the node and/or calling |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In my Godot project, I separated the server code and client code to implement a PVP room game. However, after testing, in scenes with similar objects, the FPS of the server differs greatly between using an hterrain map scene and using a regular glb object scene imported.
Both were tested under the headless display server mode (for the server, rendering is unnecessary, the purpose is to improve computational performance).
When there was only one room, the difference between the two was negligible, the server could reach 75FPS.
When the number of rooms reached 50 (4 people), the FPS of hterrain dropped to between 4-6, while the regular scene could maintain 9-12FPS.
Is there a way to disable unnecessary rendering calculations in headless mode?(not create any hterrain detail layer)
I only want it to effect collide on th server app side.visible is not important
other:
![image](https://private-user-images.githubusercontent.com/33251075/322795547-435657f8-6f47-4e70-ba31-a4cd6b676382.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjExODYyMjgsIm5iZiI6MTcyMTE4NTkyOCwicGF0aCI6Ii8zMzI1MTA3NS8zMjI3OTU1NDctNDM1NjU3ZjgtNmY0Ny00ZTcwLWJhMzEtYTRjZDZiNjc2MzgyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzE3VDAzMTIwOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWE0MzM0MGY1MDUzMzJmZWVmYTBmNjY1NTgzNWFmOWQ0ZTgwZTMxM2U5MTlhNmQwMTI0YTA3MWUwM2EyZWNjZGYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.kaWbBSBcpb02HLhuH1-Pk8e7nM83A6yR3AuXvDkbMCA)
The text was updated successfully, but these errors were encountered: