node lines, desync?

Gankez

New member
Oct 4, 2020
5
5
3
any info on rather or not those two items are fixed in mo2? do ya get smacked in the back while blocking someone whos standing in front of you still ?
 

Teknique

Well-known member
Jun 15, 2020
1,721
1,329
113
any info on rather or not those two items are fixed in mo2? do ya get smacked in the back while blocking someone whos standing in front of you still ?
You still get random blocks which is annoying, but the dmg is pretty low and it’s not too bad.


There are no more node lines there are “level streams” instead. Which are very similar but instead of lagging out you out for 5+ seconds it’ll bring even the best of computers to 0 frames but for a very short duration less than a second.
 
  • Like
Reactions: Rolufe

Lasciel

Member
Oct 3, 2020
74
63
18
i c..so more of the same then ;\ .. tyvm..<3

The games combat retains the general feeling of the first game with being far more smooth and nowhere near as nonsensical. You don't really get desync, but there is some small disparity depending on the connections of the two players. Nothing like Mortal 1.

There is a lot of optimizing to do, but it feels far better already than the first game. I would say the extent of the de-sync and connection issues are really just small things you notice and adjust to immediately. Due to the nature of the combat system ping remains heavily important.
 

Sebastian Persson

Lead Programmer
Staff member
May 27, 2020
85
216
33
39
Sweden
You still get random blocks which is annoying, but the dmg is pretty low and it’s not too bad.


There are no more node lines there are “level streams” instead. Which are very similar but instead of lagging out you out for 5+ seconds it’ll bring even the best of computers to 0 frames but for a very short duration less than a second.
We are building a custom system to sort that out FYI
 

bbihah

Well-known member
Jul 10, 2020
1,115
952
113
Nice that you are working on something for it Seb. Because last time you guys reaaally just gave up on it, but the engines (UE & ATLAS) you guys were working on were extremely limited and personally I can't think of a way how you could make the old node system work by doing things on just your end.


The old system could possibly have worked better if the ATLAS node system would let you put overlapping servers that handle the same information at the same time as the others. But ATLAS didn't really have the capabilities for this from what i've been able to see from it, so already there the easiest and most reliable way to fix the main problem with the old node system goes out the window.



The way I'd try to solve the old system would be using this overlapping by using "node crossing servers" for the node crossings. They would snap up the information of the character that is moving into the start of the overlapping area, hold on to it and preemptively transfer over that information to the corresponding server so that when the next server is taking over from the previous one you'd end up with a much shorter "node lag". These server/s would have these intermediate nodes as their one and only job so they could possibly manage a lot of these intermediate areas to decrease the total amount of increase in hardware requirement/stress.

Unsure if this would play out as good as I'd hope it would. But it also requires a different kind of flexibility with the servers and I know for a fact ATLAS sucked BALLS and i'm running on the assumption you guys were not allowed to touch the inner workings of it at all. Basically you guys sent them what you wanted them to change and then just hope they did something that worked for you. The overlapping system would effectively increase the amount of server nodes required for the same game world so thats the main problem with that idea on top of it being a tiny bit of extra stress on the normal play nodes as well. And this is just basically jury rigging the system instead of actually finding a better solution all together.