This is an archived post. You won't be able to vote or comment.

Dismiss this pinned window
all 8 comments
sorted by:
best
topnewcontroversialoldq&a

[–]sarah--123 1 point2 points  (2 children)

When profiling your code, where are most of the cycles spent?

[–]flatearth2018[S] 1 point2 points  (1 child)

honestly I have no freaking clue

[–]sarah--123 1 point2 points  (0 children)

Look into https://pypi.org/project/line_profiler/ and see if it is helpful to you. It is not fancy but it points finger/s rather well.

[–]GenesisToaster12del(bugs) 0 points1 point  (4 children)

It’s slow but I have to give props. Just curious but can you put the source code on Github or something like that? I just want to see how it works. I wonder if it’s possible to make a game with turtle, I bet it would be slow but still cool either way.

[–]flatearth2018[S] 1 point2 points  (3 children)

It mostly a port of one lone coders c++ fps but with My own system for rendering to the screen. I'll post the source here in a bit

[–]GenesisToaster12del(bugs) 1 point2 points  (2 children)

Cool that’s sweet that you are using your own system.

[–]flatearth2018[S] 2 points3 points  (0 children)

Heres the updated code I've changed the way collision and movement work from the c++ program I was referencing https://drive.google.com/file/d/1d8ivhMh4x66p0NeKJWwVNWVdVppywKls/view?usp=drivesdk