Open j-baxter2 opened 1 month ago
Could you please run python -m arcade
and paste the output here?
This command will give you a few lines of information, including your Arcade and pyglet version numbers. We need both of these version numbers because:
The output should look something like this:
$ python -m arcade
Arcade 3.0.0.dev32
------------------
vendor: Intel
renderer: Mesa Intel(R) UHD Graphics 620 (KBL GT2)
version: (4, 6)
python: 3.10.12+ (heads/3.10:f91dfdf5ff, Jul 20 2023, 21:32:15) [GCC 10.2.1 20210110]
platform: linux
pyglet version: 2.1.dev5
PIL version: 10.2.0
Hi Paul,
I get this output:
vendor: Apple renderer: Apple M1 version: (4, 1) python: 3.9.6 (v3.9.6:db3ff76da1, Jun 28 2021, 11:14:58) [Clang 12.0.5 (clang-1205.0.22.9)] platform: darwin
Jamie
From: Paul @.> Sent: 29 July 2024 11:40 To: pythonarcade/arcade @.> Cc: j-baxter2 @.>; Author @.> Subject: Re: [pythonarcade/arcade] Crashing, but I fixed with source code modification, but would like this to be added to source code so I can distribute my game (Issue #2328)
Could you please run python -m arcade and paste the output here?
This command will give you a few lines of information, including your Arcade and pyglet version numbers. We need both of these version numbers because:
The output should look something like this:
$ python -m arcade
vendor: Intel renderer: Mesa Intel(R) UHD Graphics 620 (KBL GT2) version: (4, 6) python: 3.10.12+ (heads/3.10:f91dfdf5ff, Jul 20 2023, 21:32:15) [GCC 10.2.1 20210110] platform: linux pyglet version: 2.1.dev5 PIL version: 10.2.0
— Reply to this email directly, view it on GitHubhttps://github.com/pythonarcade/arcade/issues/2328#issuecomment-2255588140, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BJN2DIJC5XHRG7DJBIAZGATZOYL2VAVCNFSM6AAAAABLT4NS7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJVGU4DQMJUGA. You are receiving this because you authored the thread.Message ID: @.***>
This is probably fixed in 3.0 dev versions. I believe we fixed most(maybe all) of the apple silicon problems in pyglet
Definitely fixed in 3.0. This was a problem 2 years ago in pyglet 2.0dev versions. We are now on pyglet 2.1.
I added the code that is selected in this image and it fixed the issue, see error message in terminal.