I just bought Black Mesa on Steam today and couldn’t help but notice that almost all of the scientist’s ties were bugging out. They would spaz out, then stretch into the unknown void of Xen. I don’t know, but so far this is happening in the beginning, in Sector C.
I have the same issue with the retail version. While in itself a minor bug, it projects itself on every scientist throughout the game so really comes off as a major minor bug in my opinion. I really hope this bug will be fixed in time for the upcoming update!
Lucky you. I get the version where the ties are still visible, just spinning around like some kind of neck-mounted propeller.
Ridiculous ties, indeed…
I’ve actually never had this problem. Or maybe I just haven’t noticed…
You probably just don’t experience the bug. I can say from my encounters with the bug that it is a hard (at least for me) to ignore, the reason being that it isn’t a one-place bug but a bug that affects all the scientists’ ties. This is the only bug that I really have any sort of significant issue with. Hopefully there is a way of fixing the bug, even if it means turning off the tie physics.
So now that I’ve went further in the game, everybody does it. Either their tie will spin around or it will glitch off into who knows where.
When you say “everybody”, do you mean everybody with a tie, including security guards? The way you’ve worded it makes it seem as though more in-game characters are affected by the tie bug as you proceed through the game (more than earlier on). I noticed that security guards were unaffected for me (presumably because of the vests covering most of the ties).
This is a WELL KNOWN issue and gas been discussed MANY times. Wait for the December update
No need to shout. I was just trying to help the poster.
Now that it’s (apparently) going away in the December update, I almost want a console variable added to toggle it on and off so that future players can experience the majesty of Turbo Ties.
I still have the propellor necktie glitch
To fix the tie glitch;
Type cl_jiggle_bone_framerate_cutoff 0 in the console.
Thank you. I will try when I get home tonight