Tom Langwaldt

I wonder if our issues have the same origin, my Server logs the following: ``` June 17 17:12:03.212 info [OSVR Server]: Using default config file - pass a filename on...

> If anyone else encounters this, I worked around this limitation by keeping track of the previous velocity, and on body_entered signal, using the difference between the previous _physics_process' velocity...

Being used to Quad trees for planet rendering, I am really impressed by [how far commercial voxel engines](https://www.youtube.com/watch?v=nr5JqYYye3w) have come.

Generating a quad and handling basic events should be part of the engine, I'd agree it's okay to add it. As long as we keep @torkleyy's concerns in mind for...

@vcapra1 Edit: better answer below @Gurgel100 I doubt it is still relevant, just tested it. Compiles and prints sim data just fine.

Can confirm that it has to be a problem with the latest drivers not some weird configuration. Did a fresh install of my system. Code 105 still showing on Windows.

@mars979 When I run ViveDisplayExtractor.exe with your DLL from Google Drive I still get ``` Got error code 105 [DisplayExtractor] Error: could not start the server device provider in the...

@mars979 Really appreciate the effort, I will as soon as I have got my development environment set up. Had used the pre compiled binaries of yours before

Just tried it, PR #32 fixed DisplayExtractor error 105 on Windows right away. Works like a charm now. Thank you so much for the quick support!

@epage I wasn't aware of the experimental system, just wanted to contribute back a quick fix I had. If the new system replaces this one, I'll close the PR.