Instalar o Steam
Iniciar sessão
|
Idioma
简体中文 (Chinês Simplificado)
繁體中文 (Chinês Tradicional)
日本語 (Japonês)
한국어 (Coreano)
ไทย (Tailandês)
Български (Búlgaro)
Čeština (Checo)
Dansk (Dinamarquês)
Deutsch (Alemão)
English (Inglês)
Español-España (Espanhol de Espanha)
Español-Latinoamérica (Espanhol da América Latina)
Ελληνικά (Grego)
Français (Francês)
Italiano (Italiano)
Bahasa Indonesia (Indonésio)
Magyar (Húngaro)
Nederlands (Holandês)
Norsk (Norueguês)
Polski (Polaco)
Português (Brasil)
Română (Romeno)
Русский (Russo)
Suomi (Finlandês)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Relatar problema de tradução
But yeah, would there be an issue?
(please let me edit comments some day steam)
I was concerned and had a look at the source. The only stuff that affects the game while running are here.
https://github.com/Syrchalis/LightRadius/blob/master/Source/SYR_LightRadius/HarmonyPatches.cs
The second harmony patch only affects when you are placing things blueprints for stuff so it should be relevant. The first runs when anything calls DrawExtraSelectionOverlays. I don't know if this always runs on any selected object, but even if so it immediately is doing some very low cost null checks then a low cost check to see if the thing has a light emitting component before it does any other work.
If you are not placing any blueprints and don't have anything selected there should be 0 performance impact, and from my reading of the code the impact otherwise should be very minor. It honestly doesn't seem like this mod would be a problem to me. Maybe you can experiment a bit more with this knowledge, see if it indeed slows down only when a bunch of things are selected?