Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
Anonymous's avatar
Anonymous
11 years ago

Hooking onto closed directx app for oculus SDK rendering

Hi,
I'm developing a program for the rift using Game Maker Studios. There is a community extension that enables oculus support but it has hit a roadblock when adding DK2 support, so I'm asking here in case someone can help. I'm not the developer of the extension, so I may not be the best person to post this, but I'm a bit impatient and I figured I would try to help with the development if I can.

We have gotten client based DK2 rendering working-ish, but a lot of problems would be solved with direct oculus SDK rendering instead, so that's what we are trying to achieve. For this we need to make the application texture(s) from the game maker program accessible to the rift SDK. Basically, the problem is that game maker pretty closed, so we don't have direct access to low-level code, so there is no way to do this. We can't get pointers to the surfaces game maker is using, etc.

So we're thinking the best/only way to get the image is to use a directx hook to fetch the window's content. But neither I or the extension's author know very much about c++ and especially not directx, so we don't know how to do this efficiently yet. Anyone have any tips?

Here is the official thread that gives a better overview of the situation, read especially from this post and downward: http://gmc.yoyogames.com/index.php?showtopic=591632&p=4625210
No Replies