Problem with dragging parts

Recently I have opened a new baseplate and decided to build some stuff on it. But something weird happened. When I decide to drag the part the part goes completely into the void of the game. I don’t what I’ve turned on or off. Can someone tell me please what I have done?

Here’s what I mean:

robloxapp-20230505-1559479.wmv (1.2 MB)

Note: the same thing happens when I specifically use move tool in the home tab; when I try all the ways possible to move a part it simply locks itself into this y axis position → -340282346638528859811704183484516925440

7 Likes

I dont know, maybe reinstall roblox studio?

2 Likes

Well, I’ve tried moving something but this time in the output it says:

The Parent property of VirtualInputManager is locked, current parent: Place1, new parent NULL

What does it mean?

2 Likes

Is it only for that place or everywhere

2 Likes

I’ve experienced this issue on all of my places.

By the way I tried reinstalling studio and even restarting my computer; none seemed to work.

Sorry for late response…

I dont know if its fixable yet… The Parent property of VirtualInputManager is locked - Bug Reports / Studio Bugs - DevForum | Roblox

2 Likes

Looks like I am one of the “lucky” people to encounter this warning.

My studio is going crazy. I reinstalled the second time and when I opened random white particles were fetching into my studio screen. At this point I clearly don’t know what to do. And the same warning pops up when I try to do something… Wow.

I really dont know either i have never encountered this my entire life

1 Like

Change the grid snap move value to something non zero or anything close to it, something like 0.125

you can find it in the model tab

2 Likes

There is a different method, you can use the transform tool in the model section, but it’ll take a bit more time for stuff like modeling

1 Like

Guys that thing is gone. But the the warning is still popping up sometimes though, but it doesn’t seem to have some kind of effect in my work. Turns out something was up with my computer (like it was an unfinished task or something) and after turning off and then turning the computer on again after some time, had proven to be working just as regularly. I think that it was due to a Windows scan or something.

But anyway, glad the issue is gone, thanks for all the advices that you guys have given me.

2 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.