Make sure to only report one bug per issue-report
Explain the feature you want
Explain the feature you want:
I would like VRCNext to implement a native Text-to-Speech (TTS) function for in-game notifications, similar to how it is built in VRCX. The function should use the operating system's built-in voice engines (e.g., Microsoft Windows TTS).
What it should do:
The program should actively monitor VRChat events and generate clear, audible speech for specific user interactions, allowing me to stay informed without looking at a screen.
Which notifications should be read aloud:
The TTS system should support the following event triggers:
When a friend joins the current world
When a friend leaves the current world
When a friend comes online
When a friend goes offline
When I receive a new friend request
When I receive a game invite
When a friend unfriends me
Required settings & controls (based on VRCX structure):
To make this feature fully usable, I would need the following configuration options, exactly as they are implemented in VRCX:
Event Filtering – A list of all notification types where each has its own filter setting (Off / Favorites / Friends / Everyone), similar to VRCX's notification filters.
Activation Mode – Choose when TTS is active with options like: Never, Inside VR, Game Running, Outside VRChat, or Always.
Voice Selection – Select different installed system voices from a dropdown menu (e.g., Microsoft Hedda-German).
Test Button – A "Play Test TTS" button to preview the selected voice before applying it.
Nickname Override – An option to set custom nicknames for users, so complicated usernames (e.g., xX_Shadow_99_Xx) are pronounced correctly (e.g., simply as "Shadow").
Suggested UI layout (based on VRCX):
To help visualize how this could look, here is the exact settings structure used in VRCX:
Settings → Notifications Tab
Desktop Notifications section:
Show Desktop Notifications: Dropdown with options (Never / Desktop Only / In VR / Outside VR / In VRChat / Outside VRChat / Always)
Show Notifications While AFK: Checkbox
Text-To-Speech section:
Notification TTS: Dropdown with options (Never / In VR / In VRChat / Outside VRChat / Always)
TTS Voice: Dropdown menu to select installed system voices
Use Memo Nicknames for TTS: Checkbox to use custom nicknames for pronunciation
Play Test TTS: Button to preview the selected voice
Notification Filters section:
A list of all notification types where each has its own filter setting:
OnPlayerJoining → Off / Favorites / Friends
OnPlayerJoined → Off / Favorites / Friends / Everyone
OnPlayerLeft → Off / Favorites / Friends / Everyone
Online → Off / Favorites / Friends
Offline → Off / Favorites / Friends
Invite → Off / Favorites / Friends
Friend Request → Off / On
Unfriend → Off / On
(and all other notification types with similar filter options)
Additional technical considerations:
To ensure a smooth user experience, please consider the following:
Queuing – If multiple notifications arrive at once, the TTS should queue them sequentially instead of overlapping or cutting off
Background Operation – TTS should remain active even when VRCNext is minimized or running in the system tray
Independent Volume – The TTS volume should have a separate slider, independent of the main application sound
Note: I have attached screenshots as visual reference to show what the VRCX settings structure looks like. These are only for illustration purposes to help understand the layout I am descr
Why should we add this feature?
Why should we add this feature?:
This feature would help many users, not just me. Here is why:
- Accessibility for people who need it
Some users have visual impairments and cannot read in-game notifications. TTS would make VRCNext usable for them.
Some users have reading disabilities like dyslexia (like myself) and struggle to read text quickly. TTS removes this barrier.
Some users have cognitive disabilities or attention issues and benefit from audio cues instead of reading.
- Good for the project
Adding this feature would show that VRCNext cares about accessibility and inclusivity.
It would attract more users who need or prefer TTS, helping the project grow.
- Easy to implement
TTS is already built into Windows. The feature does not require complex work – just connecting the existing notifications to the system's TTS engine.
Conclusion:
This is not just a personal request. It is a useful accessibility feature that would benefit many users – people with disabilities, and anyone who prefers audio feedback. It would make VRCNext more inclusive and user-friendly for everyone.
Make sure to only report one bug per issue-report
Explain the feature you want
Explain the feature you want:
I would like VRCNext to implement a native Text-to-Speech (TTS) function for in-game notifications, similar to how it is built in VRCX. The function should use the operating system's built-in voice engines (e.g., Microsoft Windows TTS).
What it should do:
The program should actively monitor VRChat events and generate clear, audible speech for specific user interactions, allowing me to stay informed without looking at a screen.
Which notifications should be read aloud:
The TTS system should support the following event triggers:
When a friend joins the current world
When a friend leaves the current world
When a friend comes online
When a friend goes offline
When I receive a new friend request
When I receive a game invite
When a friend unfriends me
Required settings & controls (based on VRCX structure):
To make this feature fully usable, I would need the following configuration options, exactly as they are implemented in VRCX:
Event Filtering – A list of all notification types where each has its own filter setting (Off / Favorites / Friends / Everyone), similar to VRCX's notification filters.
Activation Mode – Choose when TTS is active with options like: Never, Inside VR, Game Running, Outside VRChat, or Always.
Voice Selection – Select different installed system voices from a dropdown menu (e.g., Microsoft Hedda-German).
Test Button – A "Play Test TTS" button to preview the selected voice before applying it.
Nickname Override – An option to set custom nicknames for users, so complicated usernames (e.g., xX_Shadow_99_Xx) are pronounced correctly (e.g., simply as "Shadow").
Suggested UI layout (based on VRCX):
To help visualize how this could look, here is the exact settings structure used in VRCX:
Settings → Notifications Tab
Desktop Notifications section:
Show Desktop Notifications: Dropdown with options (Never / Desktop Only / In VR / Outside VR / In VRChat / Outside VRChat / Always)
Show Notifications While AFK: Checkbox
Text-To-Speech section:
Notification TTS: Dropdown with options (Never / In VR / In VRChat / Outside VRChat / Always)
TTS Voice: Dropdown menu to select installed system voices
Use Memo Nicknames for TTS: Checkbox to use custom nicknames for pronunciation
Play Test TTS: Button to preview the selected voice
Notification Filters section:
A list of all notification types where each has its own filter setting:
OnPlayerJoining → Off / Favorites / Friends
OnPlayerJoined → Off / Favorites / Friends / Everyone
OnPlayerLeft → Off / Favorites / Friends / Everyone
Online → Off / Favorites / Friends
Offline → Off / Favorites / Friends
Invite → Off / Favorites / Friends
Friend Request → Off / On
Unfriend → Off / On
(and all other notification types with similar filter options)
Additional technical considerations:
To ensure a smooth user experience, please consider the following:
Queuing – If multiple notifications arrive at once, the TTS should queue them sequentially instead of overlapping or cutting off
Background Operation – TTS should remain active even when VRCNext is minimized or running in the system tray
Independent Volume – The TTS volume should have a separate slider, independent of the main application sound
Note: I have attached screenshots as visual reference to show what the VRCX settings structure looks like. These are only for illustration purposes to help understand the layout I am descr
Why should we add this feature?
Why should we add this feature?:
This feature would help many users, not just me. Here is why:
Some users have visual impairments and cannot read in-game notifications. TTS would make VRCNext usable for them.
Some users have reading disabilities like dyslexia (like myself) and struggle to read text quickly. TTS removes this barrier.
Some users have cognitive disabilities or attention issues and benefit from audio cues instead of reading.
Adding this feature would show that VRCNext cares about accessibility and inclusivity.
It would attract more users who need or prefer TTS, helping the project grow.
TTS is already built into Windows. The feature does not require complex work – just connecting the existing notifications to the system's TTS engine.
Conclusion:
This is not just a personal request. It is a useful accessibility feature that would benefit many users – people with disabilities, and anyone who prefers audio feedback. It would make VRCNext more inclusive and user-friendly for everyone.