Can we please be more angry about the object culling in FFXIV?

Like, with Eureka, it's a serious problem within Eureka. With the way the game handles things, if there's a full instance of people in Eureka, you're lucky if you can even SEE the Notorious Monsters. It's a big enough problem to be able to damage the monster when you can't see it, but I've had instances where I can see the monster, but not the AoE indicators for some attacks.

Monster should take 100% priority on what is shown on screen at all times. Followed by your party members, then NPCs, then other players.

This is the only thing about Eureka I can say I completely loathe. I enjoy Eureka but the way the game chooses to phase out players and enemies spoils it so much sometimes.

Under no circumstances should party members be phased out. We lose xp if we res ourselves after level 6...I had a real "oh sh**" moment earlier when all but me in my party had died, I was on very low hp...and I couldn't target anyone to res them because the game decided players not in my group took priority. And they died because I couldn't heal them for the same reason. We all nearly lost xp through no fault of our own.

It's honestly a real d**k move to punish players for dying when this utterly retarded phasing system is in place.

Party members and boss mobs should NEVER phase out. You should always be able to heal and res your team mates. You should always be able to see hostile abilities a boss is casting.

Ideally the only thing that should get phased out is other players not in the same party.

There is already multiple threads on this matter. We all want this issue to be fixed or at least diverted for the better, but getting angrier about something that has been present in the game since forever and not fixed yet won't change anything, no matter how much we may want it to.

Quote:

---

Originally Posted by Joe777

but getting angrier about something that has been present in the game since forever and not fixed yet won't change anything, no matter how much we may want it to.

---

It's different now. Eureka is the first feature in the game to take xp away from you if you die. If you die because the game phased out the wrong targets...well you're just getting punished because of a bad ai dice roll and that's honestly s**t.

Quote:

---

Originally Posted by Penthea

It's different now. Eureka is the first feature in the game to take xp away from you if you die. If you die because the game phased out the wrong targets...well you're just getting punished because of a bad ai dice roll and that's honestly s**t.

---

I'm not saying it isn't a serious issue, nor has it never been a serious issue, I'm just saying getting more worked up over it isn't gonna impact if and when SE fixes or band-aid fixes it is all. All the feedback we have given so far should be enough to make them see the problem, provided they didn't already know about it (which I doubt), so all we can do is wait, which does indeed suck but it is all we can do now...

Quote:

---

Originally Posted by Joe777

There is already multiple threads on this matter. We all want this issue to be fixed or at least diverted for the better, but getting angrier about something that has been present in the game since forever and not fixed yet won't change anything, no matter how much we may want it to.

---

This only makes it worse since the longer something isn't fixed, the madder you should get.

Start demanding the drop of 32bit windows then. It has the same memory limitations as a PS3 but yet is still supported.

This is also the same reason why objects in your house/yard disappear.

I think that the problem was never the PS3 and the real problem comes from the game having spaghetti code. Sometimes I think that SE should just shut the game down, refound the lost days to ppl and fix things, because frankly it seems that nearly ANYTHING is bogged down by this

Quote:

---

Originally Posted by Zetsumei_Tsunarashi

Start demanding the drop of 32bit windows then. It has the same memory limitations as a PS3 but yet is still supported.

This is also the same reason why objects in your house/yard disappear.

---

Didn't they say 5.0 would be 64 bit only? Doesn't help with the situation now, but I believe they have already stated their intentions.

Agreed it's ridiculous. We are not playing on toasters anymore.

Quote:

---

Originally Posted by Zetsumei_Tsunarashi

Start demanding the drop of 32bit windows then. It has the same memory limitations as a PS3 but yet is still supported.

---

No it doesn't. Win32 has a limit for a given process of 2GB. The PS3 only had 0.5GB of memory in the entire system.

I mean, dropping Win32 is a good idea, but this isn't why. This problem is server end. Put too many people together and the server has to tell everyone what everyone else is doing, which creates an exponential growth load curve.

But to the OP's point - Yes, this is nonsense. I can't do my job as a healer in Eureka half the time on a NM because my party vanishes and the game thinks they're out of range when they're really right next to me. When the NM itself disappears? Absurd. Meanwhile, the combat log is sending me updates on what 100 people not in my party are doing. Do I REALLY need that?

There has to be some prioritization going on here. Enemies and party members should be first. If a load issue happens, occulsion should happen on non-alliance PCs. I don't need to see them to play the game, and I certainly don't need combat log data on them.

Quote:

---

Originally Posted by Tridus

This problem is server end. Put too many people together and the server has to tell everyone what everyone else is doing, which creates an exponential growth load curve.

---

So, the immediate work around is to lower the maximum number of people in an instance to say 96. A few reports I have seen around here about the instances that were closer a full Front Lines (72) seem to have no issues with NM monster display and targeting. Once the backend is fixed, then an increase back to the original 144 should be possible.

Quote:

---

Originally Posted by Granyala

Agreed it's ridiculous. We are not playing on toasters anymore.

---

Did someone say toasters?

https://www.youtube.com/watch?v=SHptn_3RyYE

Quote:

---

Originally Posted by ChameleonMS

So, the immediate work around is to lower the maximum number of people in an instance to say 96. A few reports I have seen around here about the instances that were closer a full Front Lines (72) seem to have no issues with NM monster display and targeting. Once the backend is fixed, then an increase back to the original 144 should be possible.

---

Yep. A friend of mine was in a Eureka the other day where the whole instance decided to split into two groups. They spawned their own NMs and such. That worked fine, as two groups of 72 is much less load than one group of 144.

They know they can't handle displaying models like with the Odin fate. They know they can't do interesting mechanics with a ton of people in one spot because of the lag and display issues. They know that a ton of people in one zone fighting causes server issues like with the Lochs.

They also know the playerbase just zergs everything. They know that they all stood in one spot in Diadem 1.0. They know that they make a massive train and spam FATEs as soon as they pop from back in 2.0 Northern Thanalan. They know the train will go anywhere there's a boss FATE like Odin or an S rank hunt.

So they designed Eureka with all that in mind, and we have those same issues. They know better and did it anyway. We've dealt with these issues for years and still have them. So don't hold your breath on them getting fixed.

It would be nice if mob pop in would be at least doubled and maybe add some low poly deforming/fade in for mobs far off so they don't just pop out of nowhere.

I can agree with this. I missed at least two NMs during my total time in Eureka because they wouldn't load in, and got hit by a ton of invisible AOEs for similar reasons.

There have been so many times where I've been killed by a random AOE because it wasn't telegraphed or some one pulled some random other monster that did an AOE that was invisible due to the amount of people. I've even had my effects turned down but still everything SUCKS.

For an MMORPG this game can't handle the MMO side of its genre. MMOs are meant to have lots of players in one place. XIV simply can't. It's always stuff like that which really get in my way enjoying more this game.
Can't zone in my player in my house and log in back in instead of out.
Can't see or target party members despite being next to me.
Can't target monsters.
Can't see all my furniture in my own house because there is a silly 40 interactive item limit for houses.
Game launcher still has no "Repair" function and a real "Backup" option to copy the contents in the My Documents folder where the important stuff is like Character UI,HUD,Macros.

Quote:

---

Originally Posted by Joe777

There is already multiple threads on this matter. We all want this issue to be fixed or at least diverted for the better, but getting angrier about something that has been present in the game since forever and not fixed yet won't change anything, no matter how much we may want it to.

---

Nonsense, of course it will. Increased anger leads to increased visibility for SE, which translates to a heightened priority. If you are in fact right - if getting angrier about an issue does not in fact affect SE's priorities and result in a faster fix - then FFXIV is in deep trouble. This is about the most basic sort of feedback cycle on the planet.

Quote:

---

Originally Posted by Vhailor

Nonsense, of course it will. Increased anger leads to increased visibility for SE, which translates to a heightened priority. If you are in fact right - if getting angrier about an issue does not in fact affect SE's priorities and result in a faster fix - then FFXIV is in deep trouble. This is about the most basic sort of feedback cycle on the planet.

---

Well you can't accurately show such emotion changes in text anyway without resorting to outright flaming, spamming, etc. imo but I'd say it really is enough just to keep giving feedback, regardless of how it is expressed. Emotions can be judged properly so feedback is deemed positive or negative despite anger levels and SE will see how upset we are about the issue and know how we feel through the feedback. Basically all I'm saying is trying to get angrier about it isn't gonna do anything different beyond whatever said anger does to yourself. I mean if you wanna get angrier about it then have fun with that, but I'd be willing to bet if the entire forum got that angry they would just begin mindlessly flaming SE and then the thread would probably not live long because that would be what getting angrier about this at this point would lead to. For example:

Angry about the issue: Damn it I can't see my peeps or my targets fix it SE!

Angrier about the issue: SE FIX YOUR FUCKING SHIT YOU INCOMPETENT FOOLS!!

At least that's my opinion of how it'd go lol and I believe what we have been saying so far is good enough to give proper feedback.

I keep saying it SE needs to evaluate if they need to shut the game down for some days/weeks to fix w/e is causing this memory problems.
This problems have been going for long and I would like to ask to ppl that interwiewed the dev team if they were allowed to actually asks this questions or not because frankly too much content has this kind of problem and getting around it with bandaids won't work forever

It has to do with how the netcode works and how the client and server sync. That stuff is hard to change and will likely break stuff if you change it. It would help a lot of problems if it was addressed all over the game, but it'd be painful. It's not a matter of days. That's likely something they'd want to do around 5.0 because it'd be a major change and would require extensive testing.