lag in the abyssals.
OP lost a ship and demands FC follow their reimbursement protocol, which for abyssals, is no reimbursement.
3 Likes
Abyssal should be contained singularities, compartimentized from external factors.
They should run in their own sub-structure with real-time priority.
LAG should be inexistent. Abyssal are not Jita where there is time.stretch delay compensation, and miriads of distant market bots, all concurring for a spot in the cue to make their adjustments.
Yet somehow the two are linked in someway.
a BUG in Jita apparently can affect all near 100 Jumps distance Systems.
The difficult part is taking the two occurances apart.
There was no lag. He was stuck on a huge space rock.
Which is impossible, no matter what you run your instance on there will always be other external factors, they are not going to spin up an entire physical machine just for 1 person to run abyssals on, and even then lag will still exist because the internet exists
CCP doesn’t even normally run a single entire solar system on a single physical node, so you aren’t getting abyssals to run on them because its not resource efficient
1 Like
Oh, this is speaking, they are virtualizing the Abyssal space within said a 0,9 space, wit alreadu close to 100 people., all running their own Abyssal content, if not a normal mission. Fact is,
there no real-time prioritization for Abyssal spaces, which we know to be particularly brutal on players if they fail to make their exit in time.
My Advice, was try to compartialize the Abyssal runs, so at the very least, because they are risking more, their instance get some kind of privilege in the bandwidth assignation, so it would perForm netter with less LAG.
This is the kind of constructive discussion I was hoping for.
Thank YOU for re-establish EQUILIBRIUM in the FORCE!!!
YES, there was. And it was so blatant that the ship freezed TWICE whilts trying to get to the canister, ans the HUGE ROCK was apparently protruding 2km beyond it’s line, si my ship could not come close enough to the canister and loot it. Ot was in fact a comboof unoptimization, freeze, and lag, which is freeze but 10 times more powerful. It happened in space when I was orbiting the hung rock the first time I came back… the ship stuck fro 5 seconds, anthought it only had one comand: approach the canister.
then it did it again in fronty of the canister, freezing for other 5 secs,
and then, once shoot into space by me for frustration, I also clicked immediately to reverse its course and direction, so the ship, although damaged, would have survive the excursion.
She didn’t alter her course, and my click was clearly in time to save the ship. at that speed…
but what prevented it from changing course? RAIN???
The ship slipped like on ICE? Because there is an alternative narration. it was LAG.
Ina T-1 DARK ABYSS with ZERO SHIPS LEFT on the field.
LAG as a byproduct of not giving Abyssal virtual spaces, a higher priority in the game structure.
We all know it’s a dangerous space. And it is more dangerous running them in O.1 sec with zero players around, than in a 0.9 sec where there are hundreds other players, all occupying the same bandwdith, althought their occupation is in NO WAY as DANGEROUS as ABYSSAL SPACE LETHALITY.
PS. You can run some Abyssal filaments ONLY in 0.9 space, for some reason, where LAG is naturally higher. There is more “protection” of course also"…
but if you try an abyssal filament in a 0.9 space and one in a 0.5 space with zero people, the difference is night and day. LAG suddenly disappear.
LAG IS OMNIPRESENT. Every frame is measured in ms. longer than usual ms, is COMMONLY CALLED LAG. In reality is just a background process. So you are not completely wrong saying there is no LAG in the abyssals… that huge space rock just helped better visualize other “processes” performing very poorly…
https://sgewebdev.com/strategies-for-reducing-latency-in-virtualized-applications/
Having a node just for abyssals is just a massive waste of resources, there aren’t enough being run at any one time to justify that waste of resources, so no there is no real time prioritisation as its treated the same as all other content, but if you’re not seeing a TiDi indicator you’re not on a node that is anywhere near its capacity so the node isn’t the issue
the node is the structure.
No the node is the portion of the server that runs 1 or more solar systems at any given time, every system in EVE is allocated to a node at boot time and barring any major issues will continue to run said system until the next downtime where that node might be allocated a new set of systems or just be given back the ones it ran before
This is why you might see sudden spikes in TiDi on a system that is otherwise empty, because the node is busy processing something that is happening on one of the other systems it has been allocated, but TiDi is pretty much an all or nothing, as in all the system on that overloaded node are affected or none of them are
Certain systems like Jita are allocated to their own node because the load is known, you can also request a reinforced node for a fleet fight you know is going to happen and CCP have a way to request those ahead of time and will keep an eye out for things like major battles around structures previously etc
So it is extremely rare for a single random system to ever be on its own node, it will however end up on a node where the other systems are essentially dead which means all the node resources can be used by a single system, but even then its not really going to be working hard as a single system with a couple of people in doesn’t exactly generate much load
Never minding whether you believe me on being stuck on the rock or not, at no point in your video did it show your client experiencing actual lag. Lag shows up as the client being slow/unresponsive. Your client was not unresponsive. You were trying to approach an object in a straight line, and there was a mass between you and the object that just stopped your ship dead. The same thing happens in large asteroid/ice fields and in some mission/anomaly pockets when trying to get to an object that has spawned really close to a massive obstacle in the way. Your ship does not automatically go around the corners of that mass, you need to manually pilot there.
The huge rock protruding ‘‘beyond its line’’ is an intentional design method used by Fenris to slow down your progress in the Abyss, and to make your looting harder. On some cans you can approach in a straight line and loot them, on others you cannot, because they have been stuffed behind rocks or other space debris.
That was just a “frame” in the entire video. And that is that you say is true.
What you don’t mention, or are not trained to see, are the parts where the ship slows down
with nothing but free space around. Especially the part at 6:03 mins where my ship is approaching the container on the rock, with nothing in between, and it freezes completely, for like 4 seconds the ship can’t barely move. It can’t open the canister. The “Abyss” is suffering sever lag in that moment. The Main Server wasn’t communicating the commands to my ship, or were delivered with a delay. These delays were ultimately the cause of my dead as the ship did receive one command and any one of the other ones immediately following that should have at least “steered” my ship back to safety after being ejected. She proceeded in a straight line.
How do you call that? “Transmission problems” _ The terms may vary, but ultimately, the source for all these “bugs” are related to the central server that is trying his best to give everybody the best possible experience. With Time-stretch delay optimizations and other cool features that allows a world as big as Eve to work in Sync for 99.99% of its activity with optimal uptime.
Authorities are aware of the manipulations in action. After the facts recorded yesterday, they do have already enough material for an initial investigation request, ready to be ported to the Icelandic Consumer right protection agency.
Osmon has usually an average of over 100+ ppl at any moment, + a bunch of public, and private owned structures, with bands of bots ranging from the usual 10 up to 30+ bots/gankers.
Where I make my other Abyss video for my Alpha Alt, it’s usually 3, 4 ppl max, and I never experienced any lag ever. Both Lost ships, where lost in Osmon.
Not really sure why you’re assuming that an abyssal system is necessarily hosted on the same nodes as the system you entered from. Which nodes are hosting which systems is generally unrelated to in-game adjacency.
TBH, it sounds like you probably have connectivity issues in general and would be better off diagnosing and resolving those.
1 Like
It is not, just sayin’
Well this is a sure way to get you application rejected for the partnership program.
3 Likes
I feel a new complaint thread for this already forming in the OPs mind…slowly realizing the impact…
Which one? This?
Can little ole me please be the other pilot?
1 Like
Nah…if you already are or planned to be a creator…
So after a legal battle, i guess you will not have a good standing with FC as is required… 
Man, 6:03 was the exact point in time I was talking about when I said that the container was behind a huge rock. That is not lag. Your client does not freeze even for a second. What took place was you approached the cache and shot at it. Once it was destroyed a cargo can spawned ON THE OTHER SIDE OF THE HUGE ROCK. Cargo cans from destroyed cache/wrecks do not necessarily spawn at the same spot where the cache was at. They can spawn a couple thousand m away. You were giving your ship approach in a straight line command – that command stops your ship dead in its tracks when there is a massive object between you and the can. Which there was. And you mistook it for a lag.
There was zero lag. I have tried to patiently explain it to you, but you completely reject even the possibility, because you have a tunnel vision about some injustice done to you by Fenris. In reality, that’s normal space rock in the abyss with your can spawning behind it. So you have to manually go around the rock to reach the can.
There is no cause for complaint, no reason to blame Fenris. No ‘‘authorities’’ are gonna give the time of day to this ‘‘issue’’ of yours. You’re kidding yourself if you think anybody is going to take this ‘‘investigation request’’ seriously. You misread the situation and didn’t have the awareness to realize you were stuck on a rock and not lagging.
Just look at your own video again. Or send it to someone who is expert at running Abyssals. They will confirm that at 6:03 you were stuck on a rock and nothing nefarious was going on there.
2 Likes