New Roblox Update Error (Promise340)

I’m using a custom StarterCharacter and it IS happening.

3 Likes

I’ve been encountering the same issue too, but I’ve never payed attention to it and just assumed it was a bug with Roblox’s facial animation.

Another weird thing I have been experiencing is that when playtesting, my face, instead of being the normal Chill face with no facial animation, is replaced with a more neutral face with facial animation.

1 Like

Don’t know why everyone’s being so freaked out by it. It’s simply just an error an employee made that managed to get past their update screening (wondering how effective that is lol) and was released to the public. It shouldn’t affect your game since it looks like an unreleased feature.

2 Likes

No @TestyLike3 it is not just an error because my local script doesn’t work correctly now. Don’t ask me how it doesn’t work, but after the latest Roblox Studio update, it doesn’t work; it only works for half of it. If you don’t experience the bug, please don’t start saying things that are wrong. It is a serious bug that made me wonder if I should quit developing on Roblox because the script works perfectly, but with the new update it stopped working. Thank you for your understanding!
Sincerely,
@Katastro5 :cool:

4 Likes

Hello @SpiritualSonicdash just to let you know they have changed all classic faces to their new ugly in my opinion animated faces. Do you remember our favorite builderman? Our favorite player on Roblox when we were kids. Yeah, they have changed his default face to the new animated face. :skull:
Sincerely,
@Katastro5 :cool:

1 Like

Yeah, I know about the change to animated faces, but the weird part about my case (and something I forgot to leave out in the last post) is that I don’t have an animated face equipped.

I’ve even checked to confirm, and sure enough, I don’t have one equipped.

1 Like

Any proof it is because of an error, or did you just write crappy code, and the only thing to justify it not working is the error?

It’s an internal error caused by Roblox’s CoreScripts. There’s nothing you can do about it.

1 Like

finally im not the only one who’s getting this

1 Like

Yeah same, Roblox should fix this asap its really annoying especially while testing and using WaitForChild or FindFirstChild or just a normal path to a part in workspace and whenever (during testing) I check for that part I don’t find it and look at output it says “Model is not a valid member of Workspace.Folder” knowing that before testing that part was already there

1 Like

Hello @BLOXBOT105! :wave:
First of all, I am not a clown, specifically in the Roblox Developer Forum. Also, my local script stopped working, but I rewrote it, and now it works. To be honest, my code was bogus, but I fixed it now, and it works perfectly. Right now, I don’t have any proof that it is not working because of the new error. Before it was a warning (the new Roblox Studio bug) and the bug (my local script), but now it is only a simple warning (the new Roblox Studio bug). To be honest, thank you for saying that because I forgot to edit my reply. Now I won’t edit it, but I will leave that reply to you.
Sincerely,
@Katastro5 :cool:

You are right. Roblox must fix this as soon as possible because it is getting very exhausting (at least for me).

Are You Encountering the New Roblox Update Bug?

  • Yes
  • No

0 voters

I believe this is happening beacuase the Promise340 module script is empty, CoreGUI is trying to request assets that dont exist at least thats my assumption.

Am glad am having the same issue! When I press play the camera stays still but the player spawns! I even hear noise and everything, so annoying!

Hi Everyone, so i also have the same problem and i think its a problem handling with the permission for Face View and VC. You can access Core Gui In studio settings if u want to see the script itself (Pretty much useless since its empty). I believe theres actually no way to fix this and also this error may only come for people with VC (I Think)

Roblox glitch, not your fault. Your games will work fine.

This somehow turned into an entire “Development Discussion” topic. Wow. :no_mouth:

1 Like

Issue seems to be fixed for me now, I’m not seeing it anymore.

1 Like

It does harm your game when you are trying to build up players and they get binned randomly with no way to handle the error. Likely they will move on ?