Paste image is nice.
I never use sprites.
I would rearrange the code as such:
Sync on `Don't delete this. It's saying that YOU are taking control of how the video refreshes
Sync rate 60 `A value of 60 will tell it to update the screen ~60 times per second. 0 will tell it to go as fast as possible.
Autocam off `Otherwise, the camera will always move to the newest created object.
Load Image "TestImage1.jpg", 1 `Always set up your screen before you load any assets.
Load Image "TestImage2.png", 2 `Otherwise, Load assets->setup screen(flush vRAM) ->no objects!
Make Object Cube 1, 50
Do
`You don't need to CLS clear the screen. It'll slow it down/flash.
`Plus, I'm pretty sure everything is flushed after the sync anyway.
UpdateLogic()
Update3d()
Update2d()
Sync
Loop
Function UpdateLogic()
A = 1
B = 1
C = A + B
Endfunction
Function Update3d()
Position Object 1, 0,0,0
Position Camera 0,0,-150
Point Camera 0, 0, 0
`Anytime you move the camera, it's good practice to point it where it needs to look.
`Otherwise the camera angles stay the same, while the position moves.
`Since Autocam was on, the camera's position might have been 0, 0, -100.
`When you move it to 0,0,-150 it will now be pointing at 0, 0, -50. So, Point Camera 0, 0, 0.
Endfunction
Function Update2d()
Paste Image 1, 0,0
Paste Image 2, 200, 250
Endfunction
Sprites definitely have benefits such as animation. I'm pretty sure they are just 3d textured plains aligned to the camera internally by using a projection matrix and world coordinates, etc.
Everybody is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid.