Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / LuxCoreRender/LuxMark issues and pull requests
#20 - LuxMark v3.1hangs with render scene missing when chosing Native C++ on Linux
Issue -
State: open - Opened by terminatorul over 1 year ago
#19 - LuxMark v3.1 crash for OpenCL platform with 0 devices
Issue -
State: open - Opened by terminatorul over 1 year ago
#18 - cmake: link against LuxCore libopencolorio
Pull Request -
State: open - Opened by illwieckz over 1 year ago
#17 - cmake: fix building with recent Oidn
Pull Request -
State: open - Opened by illwieckz over 1 year ago
- 1 comment
#16 - luxmark: catch OpenCL errors like CL_DEVICE_NOT_FOUND when listing devices
Pull Request -
State: open - Opened by illwieckz over 1 year ago
#15 - luxmark: hide compilation dialog on errors like CL_OUT_OF_HOST_MEMORY
Pull Request -
State: open - Opened by illwieckz over 1 year ago
#14 - SIGABRT during Luxmark 3.1 execution
Issue -
State: open - Opened by haonanya over 1 year ago
#13 - Luxmark 3.1x cmd line doesn't print any logs on Windows
Issue -
State: closed - Opened by albintho almost 2 years ago
- 3 comments
#12 - Does LuxMark support CPU with ARM arch?
Issue -
State: open - Opened by didiHe over 2 years ago
- 2 comments
#11 - LuxMark v4.0alpha1 binaries?
Issue -
State: open - Opened by oscarbg over 3 years ago
#10 - Rendering issues with AMD GPUs due to unsafe default settings
Issue -
State: open - Opened by PMunkes over 3 years ago
#9 - division by zero with default compilation options produced artefacts
Issue -
State: closed - Opened by BenjaminCoquelle about 4 years ago
- 1 comment
Labels: bug, wontfix
#8 - Doesn't provide useful message when clError is thrown
Issue -
State: open - Opened by baryluk over 4 years ago
#7 - LuxMark 4.0 alpha on Linux amd64 crashing
Issue -
State: closed - Opened by baryluk over 4 years ago
- 5 comments
Labels: question
#6 - Set default thread count using Windows API for Benchmark Native CPP mode
Pull Request -
State: closed - Opened by umadevimcw over 4 years ago
- 1 comment
#5 - Luxmark 4.0 alpha Mac support (&binaries)?
Issue -
State: closed - Opened by oscarbg about 5 years ago
- 1 comment
Labels: question
#4 - Luxmark does not check for errors returned by driver when it fails to allocate memory. This causes the app to crash. Typically seen with limited GPU memory ( ~1 GB) in VM setup.
Issue -
State: open - Opened by dibasc over 5 years ago
#3 - LuxMark 3.1 not print result to stdout with --single-run option
Issue -
State: closed - Opened by lzp729 over 5 years ago
- 2 comments
Labels: question
#2 - Luxmark 2.0 how to download / compile
Issue -
State: closed - Opened by mrkapqa over 6 years ago
- 5 comments
Labels: question
#1 - LuxMark crashes
Issue -
State: closed - Opened by retsyo over 6 years ago
- 3 comments
Labels: question