So when a player loads into the game, since there is so much terrain, it takes a few moments to load it all in, but by the time it loads, the parts have already loaded. So without the box there (which is collidable), the rover falls through the area where the terrain would be, and keeps falling until it hits the part destroy height or gets stuck in an underground cave. It doesn’t always happen, but sometimes depending on how slow the player’s computer loads the terrain, it can be an issue.
So the box is there to hold the rover until the terrain loads, then it gets deleted, which is why the rover drops onto the ground.
I hope that makes it a bit easier to understand.
However in-game the terrain is procedurally generated on top of this (hence why you don’t see the canyons/canals/whatever you want to call them in-game) and past this, so you can never fall off or out of the world unless the generated terrain does something funky.
Well now I think I found out why that happens. It seems I forgot to move the rover back into the box when I was fixing something on it a while back. Whoops!
That’s weird. I have no idea why it’s not working for you. It’s worked for all other people who have tested the game. Are you sure there’s nothing on the client side that may be affecting it?
No im fine… i wonder if the system you use to move the rover is not compatible with my Mac or something… ill test it from my sons pc and see if any issue.
I’m not sure if this is still relevant, as it was 8 years ago, but it might be the cause of this issue if it still exists and roblox didn’t fix/did a poor job at fixing it.
i just tested on my sons pc computer and same issue, cannot move forward or turn or backwards… only can move the articulating arms and head, all the controls listed in the Controls work… i just cant move the rover around the terrain.
The scripts for moving the rover with WASD and moving the other parts on the rover work a little differently, which may be why. I adjusted the WASD one a little now and hopefully it should work. If not, then I really have no clue
EDIT: Okay so I somehow broke it for myself now too. It works in Studio but not in-game.
EDIT 2: Alright now it’s fixed for me. Hopefully it is for you too now.
No not for me unfortunately … also, when i use WASD at the start, the arms and head move slightly, but then stops, so i think the two scripts or the two movements are somehow miscommunicating.
Darn. Well unfortunately I don’t know what else I could do. If I ever figure it out I’ll let you know, but until then, there’s nothing I can do, sadly.
Just wondering, could you just make the robot a starter character to prevent the movement issue? If my knowledge is correct I think this will go ahead and make the moving for you with Roblox’s scripts. Although I could be wrong as I’m not as experienced as you
The moving is done by a script that is way different from the Roblox animate local script, so the roblox one wouldn’t work for this. I’ll try making the rover the startercharacter though. I’ll let you know if it changes anything.
Alright so I experienced the problem too again, and so did another person, and I published another fix and now I can move the rover again and so could he, so fingers crossed it’ll work for you too now.
Woohoo it works!!! finally i can enjoy it properly!
But i see what people mean now about the touchy wheels, any little thing makes them bug out… but its ok, thats how it really happens on different planets when we explore… it was truly immersive.
Good job for sticking to the issue and resolving it!
I’m so glad it finally worked out! This project has been brain-hurting problem after brain-hurting problem, but I’ve always been able to solve them with some time and work put in. I’m glad that you’re able to play it now. Thanks for the feedback, too.
