Eleven: Table Tennis VR
(0.251.4) another patch for pico3 support
in related news, there is a typo in the pico 3 controller label that steam spits back at the app
i still haven't been able to test pico3 with steamvr..so again, if anyone can test, please let me know
i'm only pushing this out because there are users that wouldn't go to forums, but would just see the game not work and give up.
Pico3 and 4 compatibility patch (0.251.3)
So if anyone with a pico3 link that can connect to pcvr can confirm, I'd appreciate it :)
I've also added pico 4 steamvr compatibility (as far as Eleven is concerned)..so if they ever provide that functionality Eleven would work day 1 with it.
0.251.1
-adapter calibrator tool: https://www.youtube.com/watch?v=U_T9nqMx9Bs
-some pico 4 related updates
-fixed steamvr positioning bug (finally ^_^)
-updated/added a bunch of paddle adapters
-added some steamvr tracker puck haptics code (still needs some work)
-added togglable 11clubhouse linking tool (pending implementation on the website). this will allow users to link accounts without going through the name change path (which was very clever)
-added some logic to help prevent wrongly attributed win/loss during disconnects (pending some server update)
-cleaned up some user restriction/report processes server side...so soon the moderators will have nice tools so that they can act quicker on reports that should be acted on...right now the process is very annoying and slow
various fixes and encryption
live on oculus pc
steam pc
quest
there is a big change in how you communicate with the server here. Please try this and let me know if you have any issues.
1. fixed one bug that was leading to stuck balls: having to do with bad serves being hit.
2. i think i fixed the mismatch collider issue
3. some steam htc tracker fixes
4. updated some old paddle position issues..might have been causing lefty problems for the adapter.
5. encrypted user data in storage and server communications on transmission
6. another room positioning fix or quest/oculus
7. room positioning for cases where there isn't an oculus guardian defined (so steamvr, monitor, etc).
8. added a means by which I can push changes that aren't backwards compatible, client wise, without having to worry about Pico, or any other future platform with a delayed push, from holding back the change
9. tab button revolves 2d spectator 180 degrees about table.
10. fixed rank number display
11. limit to 3 ball resets per use per match. I am seeing many cases of this being used maliciously. I will very soon start to tighten the control on this.
12. added reset all settings button. It's in the logs debug menu. (sorry no better place to put it for now)
13. each user report/block will also no send logs from both people. This will help in report analysis.
14. some logs reduction. It looks like quests lose connections to wifi when they sleep for a while sometimes, and this was throwing an error.
15. some recentering logging reduction
16. updated exit room logging
249.1
live on oculus pc
steam pc
quest
just added some logging to track how long after serve is assigned a user serves during a ranked match...then at the end of the match it sends these numbers to the server. I want to get a better idea of serve timing metrics before enabling serve delay
Change Log up to 246.4 (12/31/2021)
Thank you all for your patience, your topspin, your love, and your undying hunger of ELO rating ❤️ ❤️
I can't wait to push so many updates next year that I've been raving for since Eleven was released on the quest..and updates that I wasn't raving for but should have 🙂
I'm pushing the latest patch along with the changes below to live now. (still no avatars, sorry)
Change Log up to 246.4 (12/31/2021)
Currently available on:
Steam store
Oculus pcvr
Quest: “Eleven Table Tennis Preview”
Quest
Pico: pending testing
Updates from previous patch notes:
-Midmatch blocking causing an end of match may be disabled at some point if it is deemed that is it being exploited
-When you report/block someone for a voice related offense, a prompt will pop up asking if you want to mute them. This should help as some people aren’t familiar with the UI and aren’t sure how to mute users.
-Fixed no-bounce serve hint not showing up in serve practice mode
-Added an update to the language menu in the tutorial view. Some users have had issues getting past this menu. In 30 seconds of not choosing a language, a panel pops up to the right showing all of the fields of a controller being updated in real time (and logged). By 60 seconds, this panel says “logs sent”. This way I can help troubleshoot issues with users’ controllers
-Added a process that lets the server know what your ping ball/ping compensation settings are. This is for both our own data collection to know what is being used, and also related to some community driven questions
-Changed the processing system on the server to in an attempt to fix server hiccups.
change log doc
https://docs.google.com/document/d/1GYIYo6QETKVgwOVCb074738lFKAw-fgxxu3A3a8pjkw/edit
240.0 - collider hotfix
0.239.1
-fixed MP ball machine not appearing
-some updates regarding loading colliders. I think this might have been the core reasons why mismatch environments
were causing game freezes (currently a work around enabled)
-update to pico trigger zone values, clamping .5 to .95
-added multiplayer AI functionality (just like mp ball machine). The multiplayer AI has its own free hit UI. I don't
think a remote player can play with a local AI, but a remote player can view this hit - which means now you can
use pc spectator to spectate on free hit with AI (just not matches for now)
-fixed ball color settings issue
-fixed issue that was causing opponent mic setting not to persist between sessions
-reset pcvr render mode to multi-pass. It looks like single pass was causing some people performance issues. This is
very strange considering that it's supposed to reduce performance load.
-fixed issue that some quest 2 users, when connected to pc, were not being recognized properly, and thus those users
weren't getting access to the adapters.
-fixed spectator monitor viewers able to hop into a friend's match to spectate, and fixed being able to pull one of those users into your room...however the latter needs a server side update.
-updated issues causing g2 and i think index users to occasionally have their camera flip backwards
-updated rift S right controller paddle reposition grip bug
-added audio debug option to mute lose sound (special request)
236.0
-updated room reset UI button functionality. Now it works regardless of the checkbox state to the left of it
-fixed room repositioning toggle. It wasn't hooked up to anything, which is why many people couldn't recenter
the room all of a sudden, and couldn't fix it
-some logging updates to catch some bugs
-another net message display fix
-fixed steam tracking debug page
-fixed invite over capability against monitor users
-disabled avatar2 scene object. (avatar2s aren't even enabled at the moment, but it was causing an issue for one user)
patch to the patch
(this is likely not to be the last update. This recent big push had a lot of deep and shallow changes so bugs are bound to be found and fixed asap..sorry in advance)
0.234.0
-added more logging and a temporary work around for the environment override bug
-fixed some user maintenence code
-updated custom room code length to 4-20 characters.
-rooms jointed through custom code support ranked play.
This may be temporary or permanent, but for now this
is the only way to allow for the various tournaments to
make ranked play mandatory and easily verifiable
-added whitelist/blacklist versioning so that I can force an update
for platforms while allowing a specific, still functional older version to work (pico)
This way i don't have to wait for the Pico qa process. Another situation that occured was
that I pushed an update that I wanted to force people to undo, but didn'table
have the means to do so without kicking people on an earlier version off.
-server update to allow for revert/reverse for matches for over a week
-server side updates for the quickmatch process. The default behavior for now will be
that the filters you set in the quickmatch screen will be hard limits. I've also
added more logging so that I can see what is going on.
-net message visibility fix