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

When computing prop_staics vrad only uses one thread of the cpu. #6121

Open
Unusuario2 opened this issue Dec 16, 2024 · 0 comments
Open

When computing prop_staics vrad only uses one thread of the cpu. #6121

Unusuario2 opened this issue Dec 16, 2024 · 0 comments
Labels
Tools The issue relates to the modding and development tools.

Comments

@Unusuario2
Copy link

Unusuario2 commented Dec 16, 2024

When computing prop_satic vrad only uses about 7-8% of the cpu (one thread), this happends in the "ThreadComputeStaticPropLighting:" phase.
Image
Image
This behaviour happedns also with maps that have a ton of prop_static besides of the vrad command line.
the command line in this case :
-threads 16 -bounce 320 -final -smooth 45 -StaticPropLighting -extrasky 128 -both -LargeDispSampleRadius -maxdispsamplesize 256 -softsun 0 -chop 2 -maxchop 2 -StaticPropBounce 32 -softenCosine -textureshadows -StaticPropSampleScale 32 -StaticPropPolys

Details

Steps to reproduce

  1. Try to compile a map with the command line provided above (compile a big map with a lot of prop_static)
  2. See how slow vrad is in the ThreadComputeStaticPropLighting: phase.
@robotboy655 robotboy655 added the Tools The issue relates to the modding and development tools. label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Tools The issue relates to the modding and development tools.
Projects
None yet
Development

No branches or pull requests

2 participants