Horrible update a lot of 3rd person game developers don’t want to see through your character and most brick based weapons now lag you near a wall or corners with MouseLock on.
We’d like to have it so we don’t have to see through our characters and when fighting start to glitch like crazy when fighting with a gun and or sword for most games that use it which is pretty much every game on ROBLOX.
Pic of one of the problems and the other can’t be a screenshot due to it having to move around while doing it to see it.
Doesn’t it just change your character’s transparency locally when you zoom in? For a temp fix, can’t you just forcefully change the transparency? (never tried before. Just suggesting.)
[size=2](also, why would you bump a thread 25 minutes after you posted it)[/size]
Well to be honest I have tried it but it still does nothing and it messes up the players shadows also when a player holds a tool it lags them near a wall or corner no matter how many bricks they’re holding it also stops them from moving.
[quote] Doesn’t it just change your character’s transparency locally when you zoom in? For a temp fix, can’t you just forcefully change the transparency? (never tried before. Just suggesting.)
[size=2](also, why would you bump a thread 25 minutes after you posted it)[/size] [/quote]
Well to be honest I have tried it but it still does nothing and it messes up the players shadows also when a player holds a tool it lags them near a wall or corner no matter how many bricks they’re holding it also stops them from moving.[/quote]
I have no response to the player lagging, since I don’t use mouse lock. I’ll try to do something with transparency when I get the chance, though.
@Tiger: There was a bug where the player jitters around when using mouselock – I assume it isn’t restricted to just mouselock and it’s related to locked mouse positions + moving, and that is what OP is talking about
And normally I would be inclined to say some not-so-nice things about the lack of depth in the explanation of the issue, but I’ve seen so many “umg playerscripts broke everything revert it revert it useless update!” threads (on the main site) that I just don’t have any words left for anyone who calls it a “Horrible update” on the developer forums. For future reference, take the time to explain the issue when you post bug reports. The only reason I knew about the “lag” you were talking about is because there was another thread on it, and anyone who hadn’t seen one of those threads (i.e. the staff, assuming it hasn’t been fixed because they don’t know about it), won’t know what you’re talking about. “start to glitch like crazy when fighting” is also wonderfully specific, and needs to be elaborated on further. And I’ll tell you what I told the people complaining about playerscripts on the main site. Playerscripts are not a “Horrible update”, and ROBLOX is not out to get you. Playerscripts allows developers to to modify the camera and humanoid control code to their liking, and there will no doubt be bugs since ROBLOX is converting the existing code to an entirely different language. If there is a bug, you report it and help them squash it – not call the update horrible as if they intentionally put it in there.
And also, Juriaan wasn’t referring to bumping in general. Bumping old, relevant threads instead of creating new ones is perfectly fine, but I find it hard to believe that after 24 minutes of posting the OP your post was even off of the first page of recent. There was no need for you to bump it.
Exactly as Echo says. If you’re going to say something dumb don’t say anything at all.
P.S: Don’t bump your own threads on here unless it’s a nice wall of meaningful text.
Also I bumped it by accident I did not know if you could delete post so I left it, the bump was for another forum on the actual website I had misplaced my paste onto here while not wearing my reading glasses, and yes I understand it takes time for these to be fixed but my words as I quote are"The camera is becoming a problem for 3RD person shooters" I said it was horrible due to it being well horrible, I never said it was useless the bug came due to something that has to do with the new tool selector that ROBLOX created due to tools coming out far from the character themselves and not right in the players hand.
I have my problems with these things due to the mishap of many weapons I have for a 3RD person horror shooter.
Again my apologies for the random bump that was not needed.
alright, so because nobody else really answered it.
you can solve the transparency issues with the new CameraScript. Hit play solo, copy the script from StarterPlayerScripts, and paste it back into StarterPlayerScripts in edit mode. hit Ctrl+shift+f and seach for “.LocalTransparencyModifier =” . comment out all the lines it shows up in on the scripts, and your character shouldn’t turn invisible anymore.
You can customize a great deal with the new CameraScript and ControlScript, I’d highly recommend digging around inside them.
Thanks man that helped a lot!