Echo Vr Shutting Down
Eleanora Parrot
Hi everyone ! Got my units (T-Echo + T-Beam Supreme), and flashed them to the latest alpha available. They both communicate great in my tests, but found an issue / strange behaviour of the T-Echo.
You can shutdown the unit through the Android App (2.2.8) and it works, but a blue led remains ON inside the T-Echo box. You can see it looking through the top left holes. I tried shutting down the unit by pressing the switch on the bottom, it did work, but still, the blue led remains ON.
Hi, I have bee digging into Lilygo forum messages, and there is no way to disable the LED according to their answer. So, only option is disconnecting the battery, or adding a switch. Really a big issue in my opinion.
For some more context, the L76K reference doc shows the 1PPS pin activating a transistor, the LED itself is powered by VCC, which will be off when the device is powered down.
L76K Reference591532 19.1 KB
So the current draw was not as bad as I expected, with the device powered off, current draw at the battery was 97A, I snipped the LED with a micro scissor and it dropped to 81A, meaning the LED was pulling 16A. Note this is with the in-progress firmware 2.3.16 which may dramatically reduce power usage on the T-Echo. That is still a 20% increase in power usage when the device is off, so it makes a big difference. I also did the same test with 2.3.15, the numbers were the same
Echo VR was one of the most successful online VR games of its time. Between 2017 and 2023, the developer studio Ready at Dawn, which was acquired by Meta, built up a considerable fan base. The futuristic sports game for PC VR and Meta Quest 2 allowed players to glide in zero gravity, introducing a form of locomotion perfectly suited to Virtual Reality. The two game modes, Echo Arena and Echo Combat, even established themselves in the e-sports world.
Then, in early 2023, came the bad news for many fans: Ready at Dawn announced that it would be shutting down the Echo VR multiplayer servers on August 1, 2023. However, thanks to the dedication of a passionate community, multiplayer duels in Echo VR have been revived. Marcel Hentschel, one of the German community hosts, provides an insight into a cult VR game that was thought to be dead.
Meta's CTO Andrew Bosworth cited declining user numbers and the need to reallocate resources as reasons for the decision to discontinue Echo VR. However, Meta's decision was met with criticism, including from John Carmack, former CTO of Oculus and an advisor to Meta until 2022.
Carmack argued in favor of retention, arguing that the loss of something fans loved would not be offset by the creation of something new and valuable. The retention of Echo VR that Carmack called for is now being taken on by the fans themselves.
"Two months after the game's servers were shut down in August 2023, a completely self-developed relay appeared on GitHub that allows us to host our own servers," says Hentschel. The person responsible for this is a developer called "Xenomega", who says he was never part of the EchoVR community. "He was probably just keen on the project and nobody knew anything about it until the surprise release," says Hentschel. The relay acts as a matchmaker and connects players with Echo VR's integrated servers.
In response to this new development, several small communities have formed around the game. The largest of these is the Echo VR Lounge, where many members volunteer to host servers at their own expense. The Echo VR Lounge offers servers all over the world and currently has over 7,000 members.
Despite the initial setback, the revival of Echo VR is a perfect example of the power of community support and passion for a beloved game. Thanks to the efforts of Xenomega and hosts like Marcel Hentschel, Echo VR continues to thrive, providing an immersive experience for dedicated gamers around the world.
Wow what a price cut. This thing must be a total flop. Makes sense as I have been waiting for updates and promised apps at launch that are nowhere to be seen. Really wish I would have returned the device and saved $400 just waiting for a price cut like this
I want to express my dissatisfaction with Meta's recent decision to cut the Meta Quest Pro's price by 25% just days outside of the return window for early adopters/day one customers. I believe this decision is unfair to us, and I am not alone in this belief.
As a day one customer and early adopter, I feel let down by the decision to reduce the price of the Meta Quest Pro so soon after its release. I made an investment in the product based on the belief that I was purchasing a premium product at a fair price, but now just a few days outside the holiday return window, the same product is available at a significantly reduced price. This sends a message that early adopters are not valued, and that our investment in the product was not appreciated.
I believe that Meta needs to stand by their early adopters and show that they value the trust and investment that we have made in the product. Failure to do so will likely result in a loss of future business from early adopters, as well as negative word-of-mouth recommendations.
If it was just Ready At Dawn, I could understand that they might not be able to afford keeping servers going. But they are owned by Meta. Then again, Meta did just fire a huge number of people, so this could just be another cost cutting measure.
Echo Combat is a high-quality PCVR multiplayer experience - there are very few such games, and nothing to replace it.
"Echo Combat was built specifically for the Rift using PC spec and PC engine specific features as our guidelines for building maps and systems. Moving this game mode over to Quest / Quest 2 would not be possible without major changes to the game itself. Therefore, we want to reiterate that we will not be bringing Echo Combat to Meta Quest. Combat is still available for play on Quest via Link and Air Link (beta) for our users who wish to use that option."
Source: medium.com/echo-games-blog/echo-combat-lone-echo-ii-developer-log-july-15-2022-17b3c15b12a8
There's simply no way Meta can make a better and more high-quality VR experience if the new content is based on the power of a cheap phone gpu. Echo VR/Combat was a core product for Oculus, it does feel like the killing of a sacred animal...
Despite some spirited protests against it, Meta and its child-studio Ready at Dawn are set to shut down the popular multiplayer game Echo VR, with plans to turn off severs come August 1st. While the sporty Echo Arena portion of the game has always been free on both Quest and Rift, the squad-based shooter half of Echo VR, Echo Combat, will be free on PC from now until server shutdown.
And last but not least, Ready at Dawn confirmed that Echo Combat, the lesser-played FPS variant of the game (which never made the leap to Quest) will also be shutting down as of August 1st, and is already no longer available for purchase.
Yeah, these people are so naive. These companies do this to force their developers onto other projects and herd their user base onto other games. Not as big a fail as one company that killed VR for AR that went nowhere!
I have a unique problem in which a ups on power failure shuts windows down, but it seems to shut it down too fast. Faster than an app is able to save a database to a solid state drive. I was wondering if anyone knew the code that the ups uses to initiate the shutdown procedure and if it is changeable? I was able to narrow the problem to ups since a windows shutdown by all other means resulted in the database being saved. Only on ups power failure did shutdown rather expediently end all threads.
Does it use the ExitWindowsEx function I assume?
If so what are the values of the flags associated with this function?
Thank you
APC cannot provide proprietary code to customers, unfortunately.
Maybe if one of our other customers has dug into this issue in depth, they can provide some insight to the issue.
What version of our software are you using out of curiosity?
The BR series of Back-UPS UPS' are simple signaling which mean the UPS will only report events like low battery on battery, and UPS turnoff, and a limited amount of data on battery health and technical data, much of which Windows Native will not pick up.
You can try the BR1500 with PCBE agent in "Simple Signalling with any APC UPS" mode, but it's not an "officially supported" solution and you may find communication to be spotty.
PowerChute Personal version 2.0 is in use. Didn't mean to step on any code legalities, just wanted to ascertain what exactly how the system(Back UPS RS 1500) manages and executes a shutdown due to power failure. The main configuration settings don't yield many options into the behavior of the event.
Are there any ways to control or coax the PowerChute program to allow threads to perhaps even certain threads to continue until they have run their course?
Perhaps is there a way to run my own shutdown exe or script file triggered by a power loss event? If I could set the configuration settings to use up power until only 5 minutes were left and run my script immediately on a power loss event then I'm sure the database would get saved.
Any registry keys that might be useful to modify? Or is the registry more or less off limits? Any config files open to being edited? or services that would be useful to look at?
Thanks
-Ryan Wilson
Applied Vision Corporation
Message was edited by: ryanshowseason2
What UPS are you using?
Scripting is only supported using our PCNS and PCBE software. You could try and get the PowerChute Business Edition agent working with your UPS, depending on the UPS model you have.
Quick question: Does PCPE set off the alarms in windows - control panel - power options?
EDIT:
I've been looking around and realized that the system should be recognizing my ups as a battery. It does appear in the device manager as such. similarly as described here:
Link:[Answersboard -en.apc.com/cgi-bin/nam_en.cfg/php/enduser/std_adp.php?p_faqid=2497&p_created=1025713924&p...]
But not as described I do not have the alarms tab and power meter tab. Instead I have the ups tab. Which doesn't seem to function correctly. I can go into selection and try to connect to my ups on com1 but it does not seem able to connect presumably because I am connecting by USB and not a COM port. With the options in the ups tab I believe I could reach a satisfactory solution, or if the alarms and power meter tab were existent like they are supposed to be I believe I could similarly reach a solution but they don't seem to work correctly...yet.
EDIT2:
Ok I got the connection to seemingly work between windows power options and the ups, but the actions I specified in the ups tab of power options do not seem to be executing. I have windows set to shutdown the system after 2 minutes on battery and the ups set to shut down the system after 3 minutes on ups. Windows doesn't seem to get any notifications however and the UPS shuts down the system instead. Perhaps the ups isn't sending windows anything...
Message was edited by: ryanshowseason2