Closed ShoesForClues closed 5 years ago
Hey, thanks for opening this. It would be interesting to figure out if it's related to the executable itself or if it's something related to rendering (there hasn't been much testing on Intel GPUs). Some questions that might help narrow things down:
lovr --version
print anything out when you run that from cmd.exe? If it does, then at least the executable is working properly and it's getting into the C main function.running "lovr --version" did not output anything, neither did printing from main.lua in the function lovr.load() I'm assuming this does have to do with openVR because it was said it wasn't supported for intel graphics or something.
Hmm, so someone else has run into this same issue on a GTX 660. --version should print stuff way before any of the headset code starts to initialize, so I'm wondering if it's something wrong with the way the executable is packaged (Visual C++ Redistributables?) or something. Going to keep investigating...
Managed to track this down to an issue with the shader compilation. The fix is included in v0.12.0. Please reopen if the issue persists.
Tried to run it on my computer, didn't even open, no window or anything. Tried compatibility mode for windows 7 & 8, as well as running in administrator. I also tested both 32 and 64 bit releases. I'd assume it should work without the need of a VR headset connected as the FAQ claims it would run in a simulated VR window.
Here's my specs: Processor: i5 3230-M 2.6GHz RAM: 8GB GPU: Intel HD Graphics 4000 OS: Windows 10 Home x64