2017-05-29, 21:02
New builds posted!
I've started discussing shader support with vel0cityX from here. We're thinking of redesigning the entire OSD for games to create an intuitive way to configure the shader pipeline. But in order to do that... you have to be able to open the OSD from within a game!
So new in this build is the ability to open the OSD from within a game by holding start/back/guide for 1 second. Also you can add a "holdtime" parameter to keys in joystick.xml.
Some questions:
For reference, here's what the game OSD (ripped straight from the video OSD) looks like now:
I've started discussing shader support with vel0cityX from here. We're thinking of redesigning the entire OSD for games to create an intuitive way to configure the shader pipeline. But in order to do that... you have to be able to open the OSD from within a game!
So new in this build is the ability to open the OSD from within a game by holding start/back/guide for 1 second. Also you can add a "holdtime" parameter to keys in joystick.xml.
Some questions:
- Is it annoying that the OSD button still has an effect in the game?
- Does holding any of these buttons conflict with any games?
- Should you be able to "overload" a button, one with a holdtime and one without? e.g.:
Code:
<FullscreenGame>
<joystick>
<start>Pause</start>
<start holdtime="1000">OSD</start>
</joystick>
</FullscreenGame>
For reference, here's what the game OSD (ripped straight from the video OSD) looks like now: