January 2019
Time control (0,1,2,3) is not working on the number pad. I have a Windows 10 and before had no problems using these shortcuts but now they will not work. 0 does nothing 1 takes all walls down 2 moves the camera 3 goes down a level. I am so use to using 0 to pause the game, 1 to use normal speed, 2 to go a little faster, and 3 to go the fastest. Please help me I don't know what to do. I have restarted the game and my computer multiple times. Also going ctrl + shift + c and typing help then hitting esc doesn't work.
January 2019
Try turning on/off num lock. It's a button right above the numbers. On my keyboard it just says NUM LK, so something like that.
January 2019
I have tried that.
January 2019
January 2019
I did do a system update a couple days ago. I do not have any impair accesibilty on I doubled checked to make sure (thank you for suggesting that I didn't think about it until you said something) I tried looking into my keyboard to see if there is anything that I can switch to help make it work but I don't see anything that jumps out. Any suggestions?
January 2019
January 2019
What you described is exactly what you get when Num Lock is turned off. 1, 2, 4, 6 and 8 move the camera and that's about it.
When Num Lock is turned on you are able to use 1, 2 and 3 to change the speed. Could you test in notepad if the buttons are still functional?
January 2019
so I double checked and I am able to use the numbers as they are suppose to be use in regular use but it still won't let me use it for the shortcut. I notice when the num Lock is turn off the pad does nothing.
January 2019
It's correct that you can turn the num pad off. Do you have any mods or CC in game that might be messing with the controls?
Could you test and rename your The Sims 4 folder in Documents\Electronic Arts? Just add a old to the end of it. When you start the game you'll get a clean game, test it, see if it has something to do with your folder. If it still doesn't work just delete the new folder and name the old one back to The Sims 4. If it does fix the issue start moving folders over one by one and testing in between to see where the problem is located.