You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thought I'd write an update because a few people have reported bugs or asked when a new feature will be implemented.
I realised I limited myself here by using YAML to define user settings, particularly if those settings need to change within the game.
For instance, suppose some parts of the game require a nunchuk, while others require all extensions to be detached; my original plan was to allow two separate "modes" to be defined in the YAML, with one including the nunchuk, and the other excluding all attachments. OK so far... But what if you also want to change something else separately, such as disabling the stereoscopic 3D? Do you have four modes: 3D + nunchuk, 2D + nunchuk, 3D - nunchuk, 2D - nunchuk?
This got really messy, to the point where I was basically writing code to allow DorsalVR to interpret YAML as a scripting language. So I've decided to ditch YAML and switch to an actual scripting language instead. It's a fairly big task, though, and I don't have too much time to work on this, which is why it's taking a while.
As I implement this I'm trying to tackle other issues people have flagged up along the way. For instance:
By default, in the new setup, the Dolphin output screen should show the Dolphin UI until a game is launched, at which point the screen will show the game, fixing Allow game to be selected in Dolphin within headset #13. (I'll also make it possible to have a separate screen just for the UI.)
It will be possible to remove every virtual object (including the screen) so that no rendering has to be done, which should make the Non-HMD mode run a bit faster, improving Non-HMD mode #3.
There are some other features this will unlock that I'll document on release.
After this is done, I plan to work on a better method of communicating between DorsalVR and Dolphin, which will allow - among many other things - much more accurate Wii Remote IR emulation. But that's a little way off yet!
The text was updated successfully, but these errors were encountered:
Excited for that! Been using DorsalVR for a bit on my Valve Index, and it works surprisingly well! Sure, it's not perfect (and it seems to have some difficulties detecting certain movements on Wii Motion Plus games) but, I'd say I'm really happy for something like this to be worked on!
Thought I'd write an update because a few people have reported bugs or asked when a new feature will be implemented.
I realised I limited myself here by using YAML to define user settings, particularly if those settings need to change within the game.
For instance, suppose some parts of the game require a nunchuk, while others require all extensions to be detached; my original plan was to allow two separate "modes" to be defined in the YAML, with one including the nunchuk, and the other excluding all attachments. OK so far... But what if you also want to change something else separately, such as disabling the stereoscopic 3D? Do you have four modes: 3D + nunchuk, 2D + nunchuk, 3D - nunchuk, 2D - nunchuk?
This got really messy, to the point where I was basically writing code to allow DorsalVR to interpret YAML as a scripting language. So I've decided to ditch YAML and switch to an actual scripting language instead. It's a fairly big task, though, and I don't have too much time to work on this, which is why it's taking a while.
As I implement this I'm trying to tackle other issues people have flagged up along the way. For instance:
There are some other features this will unlock that I'll document on release.
After this is done, I plan to work on a better method of communicating between DorsalVR and Dolphin, which will allow - among many other things - much more accurate Wii Remote IR emulation. But that's a little way off yet!
The text was updated successfully, but these errors were encountered: