Elite Hunt Mobs, and rendering (LOOK SE!)

[Mcshiggs]

Your complaint is like... someone designs a bus for 50 passengers, but you decide to cram in 100+ passengers and proceed to complain that the bus runs badly.

Actually the servers were designed to hold a few thousand people at once, so for them to toss out open world content that becomes unplayable when there are too many people in the area, is more like SE designing a bus big enough for 100 people, but only putting enough seats on for 20. Of course they still sell tickets to all 100 though.

[Dhex]

There are two simple solutions:
1) Get a better computer that can actually handle the load during prime time when "everyone" goes nuts and zerg even B-ranks
2) Do your hunting at other times

Your complaint is like... someone designs a bus for 50 passengers, but you decide to cram in 100+ passengers and proceed to complain that the bus runs badly.

Calm down, take a deep breath, and if 1 and 2 is not "acceptable" to you, wait a week or two for the most impatient people to get their stuff and there will be much less people doing it at prime time.

Improving their computer won't do anything about the maximum number of PC & NPC models that the game allows to load. It's the engine limitation or rather it's the current engine's biggest issue.

I've got a high-end PC that runs everything on Max even in crowds and anything excess of 150+ models will start turning some models invisible - this includes the Hunt marks & monsters.

It should be fixed so that by default it will prioritize Monster models over excess PC models - they didn't give Hunt model priority in the engine like with the fixes they made on Odin and Behemoth.

[Alukah]

For SE is more important that egis and minions load before monsters.

The priority seems to go summons > random people > party members > random mobs around > the S rank you want to attack, but oh look, it disappeared again to load one new egi that just got summoned.

[Mcshiggs]

For SE is more important that egis and minions load before monsters.

The priority seems to go summons > random people > party members > random mobs around > the S rank you want to attack, but oh look, it disappeared again to load one new egi that just got summoned.

Part of it is their grid layout, they have said in the past that it loads by grids, so even if a party member is 10 feet away, if they crossed an invisible grid line, it will load everything in the grid you are in before it will start to load another.

[Damie]

This issue seems to be stumping SE and has since Odin. They seem to be skirting this issue and others regarding hunts. But honestly, I'm not even sure it is something that they can fix in the next 6 months.

It was so frustrating to see an A rank disappear, then not know if it had been engaged because of the huge crowd of people on top of it. By the time I got a handle on where it was, it died. So far, they have barely assured people they are focused on fixing this content. This isn't a F2P game....I just want a real assurance from SE here other than what they said with the band-aid patch last week about the allied seals. It is like someone is telling SE's PR, "hey, do not address these controversial issues publicly...as there is nothing we can do about them right now." As a paying customer, I at least want to know TOP MEN are working on this right now. TOP. MEN.

[Monty]

I still think, a year later, SE hasn't realized that this game is successful. It's as if they keep thinking, things will settle, and we won't need to fix it. But no, a year later, the game's still going strong and they seem to be in utter denial about it.

[Mcshiggs]

I still think, a year later, SE hasn't realized that this game is successful. It's as if they keep thinking, things will settle, and we won't need to fix it. But no, a year later, the game's still going strong and they seem to be in utter denial about it.

They know it is successful, but they seem to have the projected budget from when they didn't realize it would be this big, that way their guys at the top get to pocket more money.

[Zephyranthes]

There are two simple solutions:
1) Get a better computer that can actually handle the load during prime time when "everyone" goes nuts and zerg even B-ranks
2) Do your hunting at other times

Your complaint is like... someone designs a bus for 50 passengers, but you decide to cram in 100+ passengers and proceed to complain that the bus runs badly.

Calm down, take a deep breath, and if 1 and 2 is not "acceptable" to you, wait a week or two for the most impatient people to get their stuff and there will be much less people doing it at prime time.

1. Not a user hardware issue.
2. People are not available to play anytime 24/7.

Saying that the solution is for players to adjust rather than SE fixing a technical problem is poor way to show paying customers how they handle the business.

[HumsterMKX]

There are two simple solutions:
1) Get a better computer that can actually handle the load during prime time when "everyone" goes nuts and zerg even B-ranks
2) Do your hunting at other times

Your complaint is like... someone designs a bus for 50 passengers, but you decide to cram in 100+ passengers and proceed to complain that the bus runs badly.

Calm down, take a deep breath, and if 1 and 2 is not "acceptable" to you, wait a week or two for the most impatient people to get their stuff and there will be much less people doing it at prime time.

Hey! I got some extra white paint which will go well with your armour.

It throw in polishing chemicals too.

Edit: will throw in lalafell squire for free.

[Nekodar]

Part of it is their grid layout, they have said in the past that it loads by grids, so even if a party member is 10 feet away, if they crossed an invisible grid line, it will load everything in the grid you are in before it will start to load another.

For Odin and Behemoth they made changes so that they could be displayed despite the grid limitations.
For S-rank they only changed display priority.
Getting the same grid changes for S-rank probably requires more work than to simply change the priority value.