As someone who's done the opposite ... gone from physics to coding ... I'd suggest the first thing to do is question your premise. What exactly does "getting into physics" mean for you? What actually comes to your mind if you imagine tasks a physicist might perform ? Which of those do you think you could do as a programmer, and which have you got no idea about how to approach ?
Such a questioning approach is typical for physics. Why are things the way they are? What predictions can one make ? etc....
Or do you even mean "physics" in the sense the word is used in computer game development ?
Which is "largely" (an over broad term) mechanics; how things move, flow, deform under external forces.
Can you give us more details? That would help with giving you pointers.
For that matter, graphics in computer games are informed by physics in the sense that many methods like rendering, raytracing, NeRF, Gaussian Splatting try to simulate light fields.
Or do you even mean "physics" in the sense the word is used in computer game development ? Which is "largely" (an over broad term) mechanics; how things move, flow, deform under external forces.
Can you give us more details? That would help with giving you pointers.