I haven't been curious enough to try that specific setup yet but I think I will now and let you know how it goes. I would be willing to bet that it will since the steam overlay works perfectly with the RetroArch renderer, I use the Vulkan one but OGL also worked fine from what I could tell. I just haven't had the time to try and check to see if that will work. RetroArch does have a DOSbox core and all video output and control inputs are not using DOSbox code and are instead part of RretroArch. It was first released in 2002, when DOS technology was becoming obsolete. I think DOSbox is trying too hard to perfectly and correctly simulate the exact output from those old machines and in so doing making it hard for the steam overlay to pop up because of it's own dependency in the games, or in this case emulators, frame output. DOSBox is a free and open-source emulator which runs software for MS-DOS compatible disk operating systemsprimarily video games. My theory also states that if you use another port of DOSbox that shares zero display code with the normal DOSbox it should work because it won't be doing any partial updates of the frame but whole frames. This also causes crashes because the framebuffer isn't being updated completely on every frame, among other things or at least this is my uneducated theory. When you open a game, you will notice that the overlay will open but it will only display at times when, on original hardware, it would have updated the WHOLE screen. In DOS box, you will notice that with openGL as your renderer, the SC will be fine when you are on the command prompt. 10 FPS for the game equals 10 FPS for the overlay and so on. For example, if you are playing a game that is 30FPS then the steam overlay will be 30 FPS. It all has to do with the precise way DOSbox updates the screen. I have actually had some revelations regarding the steam overlay and how it works.
0 Comments
Leave a Reply. |