This has been brought up a few times on github (eg https://github.com/nesbox/TIC-80/issues/1839) - it seems to be fixed in the latest dev versions (at least on Linux) but not sure about Mac.
Not sure what the problem is there but I created this similar program and tested it natively and by uploading to itch.io. It reports the expected 60fps in both cases.
Maybe the python server is causing the issue? Note: I also didn't hear any music when running your code.
local t=0
local ts=tstamp()
function drawFps()
local tmp=tstamp()
if tmp==ts+1 then
ts=tmp
cls(0)
print(t,0,0)
t=0
end
end
function TIC()
t=t+1
drawFps()
end
I know but it's just not the same :D Programming on the CPC became less of a challenge compared to earlier home computers - at least you had a chance of saving your program successfully.
Yes, you could always use a viewport (clipping region) if the resolution is lower than TIC's - for example, my game for the last Low Rez jam was 64x64 (https://paul59.itch.io/crowd-sauce)
You can't change the resolution but you might be able to emulate a lower resolution in some way, eg drawing rects or small sprites to give the illusion of bigger pixels (I don't know anything about the Atari you mention I'm afraid).
The palette is easier - just use the colours you want and don't use the others :D
You could use this tool to set the desired colours and maybe set the ones you're not going to use to black or some other colour:
Hey, I tried the first three seasons and it was a nice chill experience that made me think... more content that I was expecting and I like the way you've incorporated real photos - well done!
The obvious workaround is to use 0 and 1 (or non-zero) to represent false/true but of course your code will need to be adapted to take that into account.
You could define (uppercase!) 'constants' at the start of your program and use them throughout:
local FALSE, TRUE = 0, 1
if flag==TRUE then...
Or you could just modify your 'if' statements: if flag==true then... becomes if flag==1 then...
Alternatively, you could create a function to examine the value and return true/false if that's essential for some reason. eg
function bool(i)
if i==0 return false else return true end
end
and use it in your 'if' statements... if bool(flag) then.... but this adds the overhead of a function call for every use.
The best solution really depends on how/how frequently the values are used. Hope that gives you some ideas , sorry if you know all this already and just wanted to a basic answer (which is 'No') :D
Despite the obvious issues it's a pretty good effort although I couldn't get away from the bugs and sometimes they just disappeared. Projectiles to give a clearer hint of fire direction would be useful!
