Warlock87 0 Posted May 6, 2022 It seems that .gob mass vis is bugged, if you use -1 for radius in .gob mass vis VisRange GobID Radius setup, it not only goes for -1 in the range but also seems to assume -1 in the GobID slot. Aka if you .gob mass vis -1 BigWallID -1 EVERY item in range of -1 vis is set to -1 vis. Share this post Link to post Share on other sites
cindy 2 Posted May 7, 2022 This is currently affecting *all* gob mass commands. Also if this is a known issue I have absolutely no idea why there wasn’t a public notice like previously noteworthy bugs bc this has happened to multiple people and has fucked their phases (my own included) and it really sucks. Share this post Link to post Share on other sites
Warlock87 0 Posted May 8, 2022 Yeah my own phase was hit quite heavy by this, I simply wanted set -1 vis on a few rather large trees that looked really weird popping into existance very close to them. Instead I took about 20-30 FPS off the phase because every gob was hit, not just the trees. A PSA or a fix, or both, would probably be good ? Share this post Link to post Share on other sites
Razmataz 14 Posted May 20, 2022 I think this is fixed. Sorry for the lack of announcement about it. I applied the fix on the 7th. Please re-open if this is not the case. Share this post Link to post Share on other sites