yeah you could use an overlay that makes the view go tho the left or right.
This might help
your actual player that can be shot
typing some calculations for memory
Uhh, your actual player can still be shot and move
I don’t rlly care that much about memory, the rest of the game wont take that much memory.
I think that’s the OP’s goal. Is it not?
version 1
memory calculations
zone = 200 memory
placement limit: 64
12800 memory for the zones (12.8%)
camera point = 100 memory
6400 memory (6.4%)
overlay = 175 memory
175 (0.175%)
property = 10 memory
10 memory (0.01%)
notification = 15 memory
15 memory (0.015)
block code = 500 memory
500+ memory (0.5%+)
If you really want I can type you a guide for a cheaper version
well it could be more memory, that’s not the worst.
still will take a lot of memory just cheaper to detect which camera point to use
Why not a Coordinate device?
you can that’s my plan for a different version just needs a lot more converting in block code
@wait.what.626Youtube do you want me to make that guide? If not I’m going back to inventory expanding
sure, you can make a guide if you want.
(I’ll mark it as the solution)
will make a new post just mark me later I guess
How smooth do you want it to be?
I need to decide how many camera points to use
map has 500x500 needs to be dived into a decent number
- the number needs to be a multiple of 500
- will not accept anything lower than 20
the transition dosent have to be that smooth. as long as its not too choppy, its fine.
its not the transition
its how many different views there are depending on where you are
so how many units between each camera view
here are your options
20 units = 625 camera points
25 units = 400 camera points
50 units(pretty choppy) = 100 camera points
how about 25 units, that will be fine.