Forums » General
Vendetta Online mentioned in a Linus Tech Tips video!
Figured I should also share here...
https://youtu.be/T-qyNFjZaQs?t=792
Super super SUPER cool to see VO get mentioned out in the wild, thanks to Spidey for catching this! Unfortunately, Linus gets timed out by his connection, which is only simulating a dialup connection (as opposed to actually using true dialup, which we DO have people using!). Incarnate had some ideas why it turned out this way, which he shared over on the discord.
Reminder, if you haven't joined yet, you can keep up with the community at http://discord.gg/vendetta
https://youtu.be/T-qyNFjZaQs?t=792
Super super SUPER cool to see VO get mentioned out in the wild, thanks to Spidey for catching this! Unfortunately, Linus gets timed out by his connection, which is only simulating a dialup connection (as opposed to actually using true dialup, which we DO have people using!). Incarnate had some ideas why it turned out this way, which he shared over on the discord.
Reminder, if you haven't joined yet, you can keep up with the community at http://discord.gg/vendetta
HAHAHA WE EXIST!
Incarnate had some ideas why it turned out this way, which he shared over on the discord.
While I still may (or may not) be accurate in my guess about LTT's simulated "pretend modem" connection doing some problematic protocol encapsulation stuff.. we've done further examination with our own in-house simulators today and found there's also a problem on our side.
We were able to repeatedly play the game successfully, without disconnection (on a 48kbit/s, 200ms connection), but the problem we found really makes the login process pretty excruciating.
That investigation is still evolving, but I'll post more after we've done further testing and are completely certain about what's happening.
While I still may (or may not) be accurate in my guess about LTT's simulated "pretend modem" connection doing some problematic protocol encapsulation stuff.. we've done further examination with our own in-house simulators today and found there's also a problem on our side.
We were able to repeatedly play the game successfully, without disconnection (on a 48kbit/s, 200ms connection), but the problem we found really makes the login process pretty excruciating.
That investigation is still evolving, but I'll post more after we've done further testing and are completely certain about what's happening.
https://www.vendetta-online.com/x/msgboard/2/39117?page=2
The last post in this thread is no longer accurate, and it is taking quite a long time again. I have noticed this for at least a few weeks. I'm not sure if it is related, but you should be informed.
The last post in this thread is no longer accurate, and it is taking quite a long time again. I have noticed this for at least a few weeks. I'm not sure if it is related, but you should be informed.
The last post in this thread is no longer accurate, and it is taking quite a long time again.
We just pushed a patch a few minutes ago, please let us know if this helped?
We just pushed a patch a few minutes ago, please let us know if this helped?
Definitely, it is fast again. Thank you.
Fixing a bug on fake dial up that affects literally no one while stuff like this continually affects paying customers on a daily basis, proving VR is just an after thought and all that is cared about is marketing:
https://drive.google.com/file/d/1om4I264ILjcUTn67VrnjGQfKbVGLzA2Y/view?usp=drive_link
https://drive.google.com/file/d/1Oq2-4-89nQwR4hqImz-80Cl0Vnstt71h/view?usp=drive_link
Not the first time these bugs have been reported.
https://drive.google.com/file/d/1om4I264ILjcUTn67VrnjGQfKbVGLzA2Y/view?usp=drive_link
https://drive.google.com/file/d/1Oq2-4-89nQwR4hqImz-80Cl0Vnstt71h/view?usp=drive_link
Not the first time these bugs have been reported.
doing a forum search for your name brought up explicitly two posts, this one and where you created a community on the quest community thing. No bug reports. I might've missed it, but I didn't see any bug reports mentioning VR within the past six months either?
I'm not even sure what exactly is being shown in the video. But, if something remains a bug over a period of time, *resubmit*. There's only two developers trying to hold up this game, please don't be so overly hostile right off the bat? It might've just slipped through. Especially because this "bug" in question, as both Incarnate mentioned and another user then pushed for, is affecting real people.
edit: Its also COMPLETELY tone-deaf considering the devs just released a patch before this last one specifically for fixing bugs with launching on VR (the patch Incarnate mentioned here hasn't been added *yet* when I typed this)
See this year's changelog here, where i've been copying it out of the launcher: https://vo-wiki.com/wiki/ChangeLog/1.8/2025
I'm not even sure what exactly is being shown in the video. But, if something remains a bug over a period of time, *resubmit*. There's only two developers trying to hold up this game, please don't be so overly hostile right off the bat? It might've just slipped through. Especially because this "bug" in question, as both Incarnate mentioned and another user then pushed for, is affecting real people.
edit: Its also COMPLETELY tone-deaf considering the devs just released a patch before this last one specifically for fixing bugs with launching on VR (the patch Incarnate mentioned here hasn't been added *yet* when I typed this)
See this year's changelog here, where i've been copying it out of the launcher: https://vo-wiki.com/wiki/ChangeLog/1.8/2025
Fixing a bug on fake dial up that affects literally no one
You mean, aside from Infinitis, who posted above, a subscriber who has been playing since 2008?
And who linked to an earlier Bugs thread where several different veteran players described their common connection issues?
Also, these "modem" type fixes impact practically anyone playing on limited bandwidth, high-latency mobile connections in places like Asia, which is thousands of users.
We have people playing in the jungles of the Philippines. We also have users on latent satellite connections, users on ships at sea, users in rural Siberia who have sporadic packet loss. All these types of players are impacted by these kinds of problems.
while stuff like this continually affects paying customers on a daily basis, proving VR is just an after thought and all that is cared about is marketing:
Oh, so you mean how we've been pushing Quest updates for the last several releases (as recently as last week), to try and fix these weird concurrency problems THAT WERE INDUCED BY META MAKING UNDOCUMENTED CHANGES TO THEIR OS?
*** Vendetta 1.8.751
- Fixed a Quest crash in cases where the game and the Launcher are started at the same time.
*** Vendetta 1.8.750
- Fixed crash on Quest in cases where the app gets backgrounded on startup. Clicking on the launch icon will bring the app to the foreground.
- Fixed crash on Quest in cases where the app starts up with a saved state instead of the Updater starting up.
Not the first time these bugs have been reported.
That's news to me. We've been doing our best to fix this stuff based on remote telemetry and automated crash reports. We have not been seeing anything on Bugs about this, or tickets from you, or emails, or any other kind of "reports"?
In fact, the only thing I've seen "you" report, forum-banned user, is that the IAP isn't working on Quest, something that was immediately added to our TODO, but we haven't been able to investigate yet.
Yes, something that impacts all users of high-latency and limited bandwidth is more important than things impacting a small subset of players on a small minority platform. That shouldn't require explaining.
You were kicked off the forums for being an unreasonable, self-righteous arse who refused to follow any rules. Your particular technical problem may not be helped by continuing to behave badly.
You mean, aside from Infinitis, who posted above, a subscriber who has been playing since 2008?
And who linked to an earlier Bugs thread where several different veteran players described their common connection issues?
Also, these "modem" type fixes impact practically anyone playing on limited bandwidth, high-latency mobile connections in places like Asia, which is thousands of users.
We have people playing in the jungles of the Philippines. We also have users on latent satellite connections, users on ships at sea, users in rural Siberia who have sporadic packet loss. All these types of players are impacted by these kinds of problems.
while stuff like this continually affects paying customers on a daily basis, proving VR is just an after thought and all that is cared about is marketing:
Oh, so you mean how we've been pushing Quest updates for the last several releases (as recently as last week), to try and fix these weird concurrency problems THAT WERE INDUCED BY META MAKING UNDOCUMENTED CHANGES TO THEIR OS?
*** Vendetta 1.8.751
- Fixed a Quest crash in cases where the game and the Launcher are started at the same time.
*** Vendetta 1.8.750
- Fixed crash on Quest in cases where the app gets backgrounded on startup. Clicking on the launch icon will bring the app to the foreground.
- Fixed crash on Quest in cases where the app starts up with a saved state instead of the Updater starting up.
Not the first time these bugs have been reported.
That's news to me. We've been doing our best to fix this stuff based on remote telemetry and automated crash reports. We have not been seeing anything on Bugs about this, or tickets from you, or emails, or any other kind of "reports"?
In fact, the only thing I've seen "you" report, forum-banned user, is that the IAP isn't working on Quest, something that was immediately added to our TODO, but we haven't been able to investigate yet.
Yes, something that impacts all users of high-latency and limited bandwidth is more important than things impacting a small subset of players on a small minority platform. That shouldn't require explaining.
You were kicked off the forums for being an unreasonable, self-righteous arse who refused to follow any rules. Your particular technical problem may not be helped by continuing to behave badly.
To provide some additional context, I live in the capital of a well-developed country. So no rainforest situation in my particular case, lol. I have a dedicated 2.5 Gbps internet connection. There is literally a fibre optic cable connected to my router, yet I was still experiencing the problem. So, I wouldn't describe it as a "fake dial-up" issue, and I can imagine how it would affect people living in the more extreme conditions that Incarnate mentioned.
I also have to say that bugs are fixed quickly if they can be reproduced and identified. The developers persist in trying, even when a bug is difficult to locate. I recall the extensive search for the unreliable "follow" command that was only randomly affecting a few users. They didn't give up and eventually found and resolved the problem. Naturally, there must be priorities. Even large development teams are driven by priorities, and this is even more crucial in small teams.
I worked in development and as an executive in my career, and I cannot personally imagine running such a large project with such a small team. There was a great post from Incarnate outlining what it takes to do so, allowing us to at least remotely imagine the challenge.
So, all I can usually say is, thank you.
I also have to say that bugs are fixed quickly if they can be reproduced and identified. The developers persist in trying, even when a bug is difficult to locate. I recall the extensive search for the unreliable "follow" command that was only randomly affecting a few users. They didn't give up and eventually found and resolved the problem. Naturally, there must be priorities. Even large development teams are driven by priorities, and this is even more crucial in small teams.
I worked in development and as an executive in my career, and I cannot personally imagine running such a large project with such a small team. There was a great post from Incarnate outlining what it takes to do so, allowing us to at least remotely imagine the challenge.
So, all I can usually say is, thank you.
And this is why no one bothers to provide any bug reports for you: For being a grown ass man you sure know how to cry like a little bitch quicker than you actually contribute to your own game. Six paragraphs of text and this bug still happens. I'm not sure what patch you think you provided but it didn't fix this. The only self-righteous asshole here is you. Still can't make any purchases on quest. Still can't even leave your boundary without the game crashing on quest. Background still fails to save settings. Keyboard fails to work properly. My guild has been leaving you emails for weeks but you banned our leader from the forums and spam their emails. Sucks to suck, we have a dozen better vr games to play, cheaper and with more love put into them than you ever have for VO. Meanwhile, our guild has single-handedly brought you over $1000 this year in subs and purchases. We're out here literally begging you for a reason to give you money and you're too stupid to look in front of your face and see the shit coming out of your mouth while you run your players off the forums. Had you not banned Az then you would not be here seeing year old reports as news. You have a worst attitude than anyone I have ever seen in my entire life. You get exactly what you deserve given to you in return Incarnate.
Go ahead and ban yet another person capable of writing thorough and detailed bug reports for you, we literally don't care lmao
Real people have better shit to do than invest in the forums for a game that does not care about them.
Go ahead and ban yet another person capable of writing thorough and detailed bug reports for you, we literally don't care lmao
Real people have better shit to do than invest in the forums for a game that does not care about them.
(This is pretty off-topic for this thread, but I'll respond once more and then move on..)
My guild has been leaving you emails for weeks but you banned our leader from the forums and spam their emails.
No, the only email we received from you was about the IAP issue, I already responded above that we immediately added it to our near-term priority list. We have not received any other reports.
Six paragraphs of text and this bug still happens. I'm not sure what patch you think you provided but it didn't fix this
Yes. We have absolutely failed to patch the Quest issue, despite a variety of attempts..
That's because we're trying to fix a problem that we cannot reproduce internally, on our own devices, and have no idea what the hell is wrong (and notably it does not appear to have been caused by any changes to our code or game, but rather a Meta lifecycle change from an OS update, that we have not identified).
It's basically "blind debugging": where you try to figure out a problem purely on remote telemetry, make patches, and then "see" if the problem continues to occur "in the wild" through further remote telemetry and crash reports. It is a pretty slow and frustrating process for the developer, and unsatisfying for the user as well, since there's no guarantee of an immediate "fix".
There's some added complexity from our also trying to keep the Quest version working for Quest 1 players.
But none of that implies that we don't care about VR players or VR problems, or are ignoring the issue. Basically the opposite?
The fact that you're more interested in being angry about it, instead of reporting anything, further exacerbates the problem.
(Notably, the IAP issue appears similar in that we have not made any changes on our side, and suddenly it stopped working. Meta tends to assume "every game" uses Unity and Meta's Unity-specific plugins).
Go ahead and ban yet another person capable of writing thorough and detailed bug reports for you, we literally don't care lmao
I definitely agree (based on what you wrote above and your past "contributions" as Az Neter). You've been repeatedly inappropriate and abusive towards us, and largely unhelpful in terms of bug reports. You are a bad fit for our community, and we would prefer if you never played our game again.
Our community requires adherence to a pretty simple and easy-to-meet standard set by the Rules of Conduct, to which you explicitly agreed, as it is cited in section six of the game's license agreement. We gave you leeway in past transgressions and tried to get you to alter your behaviour, but that appears to be infeasible.
We're out here literally begging you for a reason to give you money and you're too stupid to look in front of your face and see the shit coming out of your mouth while you run your players off the forums.
We do our best in terms of development, but if I'm understanding you correctly, then I agree on this point: We are not interested in money from people who cannot meet the basic standards of the Rules of Conduct. We would prefer you go play something else.
Perhaps you could do far better at building and maintaining a custom cross-platform MMORPG with a tiny dev team, I encourage you to go give it a try.
My guild has been leaving you emails for weeks but you banned our leader from the forums and spam their emails.
No, the only email we received from you was about the IAP issue, I already responded above that we immediately added it to our near-term priority list. We have not received any other reports.
Six paragraphs of text and this bug still happens. I'm not sure what patch you think you provided but it didn't fix this
Yes. We have absolutely failed to patch the Quest issue, despite a variety of attempts..
That's because we're trying to fix a problem that we cannot reproduce internally, on our own devices, and have no idea what the hell is wrong (and notably it does not appear to have been caused by any changes to our code or game, but rather a Meta lifecycle change from an OS update, that we have not identified).
It's basically "blind debugging": where you try to figure out a problem purely on remote telemetry, make patches, and then "see" if the problem continues to occur "in the wild" through further remote telemetry and crash reports. It is a pretty slow and frustrating process for the developer, and unsatisfying for the user as well, since there's no guarantee of an immediate "fix".
There's some added complexity from our also trying to keep the Quest version working for Quest 1 players.
But none of that implies that we don't care about VR players or VR problems, or are ignoring the issue. Basically the opposite?
The fact that you're more interested in being angry about it, instead of reporting anything, further exacerbates the problem.
(Notably, the IAP issue appears similar in that we have not made any changes on our side, and suddenly it stopped working. Meta tends to assume "every game" uses Unity and Meta's Unity-specific plugins).
Go ahead and ban yet another person capable of writing thorough and detailed bug reports for you, we literally don't care lmao
I definitely agree (based on what you wrote above and your past "contributions" as Az Neter). You've been repeatedly inappropriate and abusive towards us, and largely unhelpful in terms of bug reports. You are a bad fit for our community, and we would prefer if you never played our game again.
Our community requires adherence to a pretty simple and easy-to-meet standard set by the Rules of Conduct, to which you explicitly agreed, as it is cited in section six of the game's license agreement. We gave you leeway in past transgressions and tried to get you to alter your behaviour, but that appears to be infeasible.
We're out here literally begging you for a reason to give you money and you're too stupid to look in front of your face and see the shit coming out of your mouth while you run your players off the forums.
We do our best in terms of development, but if I'm understanding you correctly, then I agree on this point: We are not interested in money from people who cannot meet the basic standards of the Rules of Conduct. We would prefer you go play something else.
Perhaps you could do far better at building and maintaining a custom cross-platform MMORPG with a tiny dev team, I encourage you to go give it a try.