Open samdev-7 opened 2 years ago
Sorry just saw this ( I re-added notifications so if you respond I'll see it faster now). It should work, the post you linked to the guy was able to get it working on Xbox series X.
Can you run it on your CPU? If not what is the output from CPU?
Also keep in mind that it may be setup to run immediately ( ie testing mode which doesnt show a UI) . If so it isnt crashing, check the running section on what to comment out, get it running with UI on your CPU then send over to XBOX to run
Sorry for the late reply. I tried running it locally. It produced a similar crash at the same breakpoint.
How do I run it with CPU? It seems to be erroring before the UI loads.
When I said CPU I really meant run locally. Although you would still need a GPU on your PC to run (nvidia or arm gpu with at least 8gb VRAM). Since that’s also breaking, I’ll see what’s going on today and send you more info
On Feb 5, 2022, at 10:20 AM, SamDev7 @.***> wrote:
Sorry for the late reply. I tried running it locally. It produced a similar crash at the same breakpoint.
How do I run it with CPU? It seems to be erroring before the UI loads.
— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you commented.
It seems the current version should be working. Is it set to debug mode and x64? Do you have a GPU to run locally? Try enabling lines 231 and 232 of
miner.set_test_vars();
miner.mine_forever();
This will start running without the UI. Someone got it running on the One X, but not sure the one S is compatible
Also is the mode set to games? Otherwise you wont get full GPU access which explains the crash.
The logs get to "generate dataset" which is the Ethereum DAG. then crashes. If you dont have a GPU to run locally, I'm going to guess the One S isnt compatible
Builds successfully, but crashes on startup on the Xbox One, the app is set to 'Game' mode.
Log
Looks similar to #1. Setting
D3D_FEATURE_LEVEL_12_0
crashes with a similar error. Log SettingD3D_FEATURE_LEVEL_10_0
crashes with a different error it seems like. Log