-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build.cmd & Run.cmd referencing wrong version? #345
Comments
I managed to edit them manually with notepad and got it to download, unfortunately after 3x24 hour runs (accidents in the first two and last one failed to find output in ow sibernetics folder, not the first time I've had that issue however, I'll replicate from Linux another time) I've pretty much become exhausted by it atm 😅 But will check the source to see if it matches :) |
Thanks for the update. It's all not very well tested on Windows unfortunately, simply because most of us work on Linux/Mac, but if you do have suggestions for improvments we're happy to incorporate them. |
@pgleeson Does it run on Docker Engine in Linux? And for Windows, Would love a way to utilise my GPU to accelerate it without completely passing through my GPU to the VM. Would make testing a lot faster, no? Docker Desktop seems to only have guides for NVIDIA GPU's which I found strange considering they're seen as more difficult to work with on Linux. |
Also just realised the issue I faced is mirrored on #336 except it applies to 0.9.4 aswell |
shall i solve this issues |
If you can solve that one which seems to happen across multiple operating systems as seen in #336 then that'd be great @ElamathiiSelvan |
@pgleeson Also closing this as the problem seems to be better described in the other issue |
Thanks @Daasin |
Discussed in #344
Originally posted by Daasin May 3, 2024
and is there a way to get 0.9.4? Opening the files it seems to reference 0.9.4 but says 0.9.3 in windows terminal after building or running
Turns out build.cmd and run.cmd both referenced the older version
The text was updated successfully, but these errors were encountered: