@info-creaticode ece19161-3a4d-404a-af45-6ea26fdba841-image.png I have found out, it still works, but after changing and going back into it didn’t error crash so I’m just going to remove and remake the list
Never mind it’s still an option be47ead1-7e9c-4377-b06e-28762ce70886-image.png
Thanks for sharing. There are 2 small adjustments you need to make:
The box that sometimes shows up around your car is the last box added to the targets. It happens sometimes that when you add the car, the box has not been moved to its own position in time. To solve this issue, the best solution is to move the code for the targets and the car into 2 new sprites, as suggested in the tutorial steps 7 and 11 above
The plane can not be too big. The size given in the tutorial has y of 15000, and your project has 150000, which is 10 times larger. Although this seems to be a small difference, the physics engine can not find a solution when you try to drive the car. So try 15000 or some other smaller value. If you do need to have a larger map, you can add more planes, but keep each of them relatively small.
@info-creaticode I just figured out my error. Sadly, it is embarrassing but something my students do more than I like. I was coding my sprite under the stage section not with the sprite. I’ve moved the code and now it works. I am eye rolling myself while laughing. Thank you for reaching out (also, I am not sure why my screenshots did not post originally).
Hi there, one way to work together remotely is to use the “co-editing” feature, which is part of the premium subscription. It allows 2 users to work on the same project on 2 computers at the same time. Please check out question 17 on this tutorial page:
If you are not looking for such a real-time collaboration tool, I suggest you and your friend work on different parts of this project, such as different sprites in it, then you can merge your sprites into one project, using the export/import functions of sprites.
Hi, the wait block simply waits some time, and the time period can be specified by different units, where a frame is assumed to be 1/60 seconds. It does not account for the actual number of frames since it does not have that information.
If you need to run some code at fixed intervals, a better choice might be this block:
This block will try to run a new iteration by the fixed time interval, no matter how long it takes to finish each iteration.
If that does not work for your project, please share the project with us, and we can probably figure out a working solution for you.