thats fine, but its a small bit of code and itd be very easy if we show you a picture.
for some of us, liking means “i read your post”, unlike other platforms where it means “your post is funny”
I’ve kind of asked for a picture from the beginning but no one showed me a picture
I was still a bit too confused to how this works
basically the double food has a probability of \frac{1}{10} of being chosen. if it’s not chosen, each other food has a \frac{3}{10} chance to be chosen.
this is called probability and i think schools teach this in 4 or 5 grade :))
Hmm ok interesting
do you understand?
No not really
Does it happen with every project when you enter it?
lets say theres a giant wheel that you have to spin. on the wheel are ten sections. if it lands on section three, something will happen- but if it lands on 4, 5 or 6, something else will happen.
It seems it only happens if you tap the + button and try to delete the image. If you do it after tapping a set image parameter, the image deletes successfully.
There is something that is preventing the image from being deleted.
And yes it does. It happened to me too.
Interesting but I think I might make the burger and fries a item in the shop
As like a combo maybe
I only tested this on IPhone, and that’s the only custom project I have
whats the max objects in a HS editor and do clones count?
4096, and clones do count I believe :))
okay thank you! i think i’ll be ok haha
more blocks = more frames
l
Most frame drops are caused by objects running a complex piece of code at the same time every frame.
@Awesome_E if only you were able to make a tool that can calculate which block(s) caused the most frame drops in a project. It would give us an idea of why our projects are sometimes laggy, and could also give us a clue on how to optimize our projects to run smoother.
@t1_hopscotch here’s every bug / annoyances I could find in the public version (3.54.2):
- Deleting a block via dragging can cause the code window to scroll down
- Trying to delete an image after tapping the + button always fails (discovered by @RoadOcean)
- Sometimes entering values in parameters causes the block to scroll all the way to the beginning instead of remaining where it was. This makes editing large parameters more difficult, and it takes much more time to do so.
- Large projects have a chance of womping after some time (larger projects womp faster than smaller projects). It doesn’t even show the error message, it just displays a white screen (even though the code says not to do so).
- When downloading a project, if you go back before it finishes / opens the project, or it returns an error, you are unable to choose another project in your drafts until you quit the app.