Closed Amateur-God closed 1 year ago
Bug is here.
And not only that, but most sniper scopes and many non-sniper optics arbitrarily don't support NVG/TI although there's no reason they wouldn't. Not sure I'd even call it game balance either.
That sounds like a lot of config changes and maintenance hell.
And there are reasons why optics wouldn't support NV/TI, mostly to do with light reception through the optic into the goggles and eye relief.
That sounds like a lot of config changes and maintenance hell.
Yeah, shoulda been done since the start, so not now.
And there are reasons why optics wouldn't support NV/TI, mostly to do with light reception through the optic into the goggles and eye relief.
Surely those are the exception, though ? I dunno if the game (or the file formats) is even able to account for those, either, but if it can it's up to the Players to decide what to use.
@LinkIsGrim can you lock this thread since it's resolved, this is like the 2nd bot to post a link to malware on the thread as a "fix for the issue"
Mods (complete and add to the following information):
Stable
[e.g. 1.00 stable, rc, dev]stable
[e.g. 3.0.0 stable, commit hash] (Current steam version)stable
[eg. 3.0.0 stable, commit hash] (Current steam version)Description: as discussed with "BaerMitUmlaut" in Discord Message linked, the Script that is supposed to detect whether or not a scope supports NVGs isn't working properly,
I have a Scope with the following class config
However, as can be seen here
it shows as not having NVG support from what i can tell from the script its suppose to detect the contents of
visionMode[] = {};
and set the text to primary supported if there's no content between the{}