Easiest way to get some debug output
Posted: Sat Aug 23, 2014 5:06 pm
Hey everyone! First off, I’d like to thank all the developers of this awesome piece of software for the effort they did and do put in to it. I know it’s not easy to give up so much spare time. So, really, thank you!
I got my DK2 recently and was playing around with Vireio 2.03, with and without custom dll/fx files that I found in some Vireio Skyrim thread to improve DK2 compatibility. Everything worked beautifully and I have to say it’s quite the experience! Nice work!
So far so good, but as soon as I started other games it obviously wasn't so nice anymore. I know this is a work in progress, so I actually don’t mind that at all. I’d rather have one awesome proof-of-concept than a half ass experience in 50 different games.
Since I had some spare time and the interest, I took different bits of fx files and made one that’s just a zoomed out SBS with a simple distortion correction. Additionally I disabled all tracking. The idea is to make a mode that is as compatible as possible, so more games will work with it. It now looks a lot like the floating desktop programs that are around, minus the movement (the screen is fixed, which is fine for me at the moment). While it’s probably the dumbest possible implementation of it (the game still runs in 1080p), it works surprisingly well for my purposes.
So, now that I have the basics working, I’d like to get some more games to run in this mode.
So far I have seen 3 failure modes with the games I tried:
1. game crashes
2. game renders a single, normal view over the entire screen (this then also happens with the normal SBS view; seems like Vireio is not hooked, even when copying the dlls over)
3. game renders 2 views, but they are not 3D, i.e. there is no separation
What I would like to do is work my way up this list, so start with a game that has 2 views but no 3D and get it to work, since those seem to be the easiest targets.
What I did up until now is to play around with both the profiler and the in-game menu to get some separation, but to no avail. I also read all the documentation I could find, a lot of wiki entries and read through some threads here, but I did not get any further.
So, seemingly having reached a dead end on the GUI-path (unless I missed something obvious), what I would really like at this point is to have some debug output, which (finally) gets me to the reason why I'm posting: Where would the best/easiest/fastest place be to get some simple debug output? Are there log files that can be enabled or would it be best to pull the code and run in debug mode (or something similar)? In case of the latter: Are the build instructions on GitHub up to date? I’m asking because it mentions Oculus SDK 0.2.5c.
TLDR: What’s the easiest way to get some simple debug output of a non-working game in Vireio?
Thanks for listening and keep up the good work!
I got my DK2 recently and was playing around with Vireio 2.03, with and without custom dll/fx files that I found in some Vireio Skyrim thread to improve DK2 compatibility. Everything worked beautifully and I have to say it’s quite the experience! Nice work!
So far so good, but as soon as I started other games it obviously wasn't so nice anymore. I know this is a work in progress, so I actually don’t mind that at all. I’d rather have one awesome proof-of-concept than a half ass experience in 50 different games.
Since I had some spare time and the interest, I took different bits of fx files and made one that’s just a zoomed out SBS with a simple distortion correction. Additionally I disabled all tracking. The idea is to make a mode that is as compatible as possible, so more games will work with it. It now looks a lot like the floating desktop programs that are around, minus the movement (the screen is fixed, which is fine for me at the moment). While it’s probably the dumbest possible implementation of it (the game still runs in 1080p), it works surprisingly well for my purposes.
So, now that I have the basics working, I’d like to get some more games to run in this mode.
So far I have seen 3 failure modes with the games I tried:
1. game crashes
2. game renders a single, normal view over the entire screen (this then also happens with the normal SBS view; seems like Vireio is not hooked, even when copying the dlls over)
3. game renders 2 views, but they are not 3D, i.e. there is no separation
What I would like to do is work my way up this list, so start with a game that has 2 views but no 3D and get it to work, since those seem to be the easiest targets.
What I did up until now is to play around with both the profiler and the in-game menu to get some separation, but to no avail. I also read all the documentation I could find, a lot of wiki entries and read through some threads here, but I did not get any further.
So, seemingly having reached a dead end on the GUI-path (unless I missed something obvious), what I would really like at this point is to have some debug output, which (finally) gets me to the reason why I'm posting: Where would the best/easiest/fastest place be to get some simple debug output? Are there log files that can be enabled or would it be best to pull the code and run in debug mode (or something similar)? In case of the latter: Are the build instructions on GitHub up to date? I’m asking because it mentions Oculus SDK 0.2.5c.
TLDR: What’s the easiest way to get some simple debug output of a non-working game in Vireio?
Thanks for listening and keep up the good work!