(I've filed a similar report to this under the "Bug Report" forum and it was designated as "Not a Bug" there. If additional information is needed you can check my topic here: http://forum.square-enix.com/ffxiv/t...osses-Hunts%29)
When approaching a densely populated world event such as a FATE, Hunt, seasonal event, or world boss such as Odin or Behemoth players will begin only rendering entities relatively close to them. (Effect is more severe on low end PCs and on PS3, but is present on higher end PCs as well.) This makes it extremely difficult to target party members, or enemies in such events. Occasionally it becomes completely impossible to do so. The game will only render entities that are close enough to the player, seemingly randomly, and makes no distinction between party, non-party, pet, NPC, or enemy (Regardless of whether or not the enemy is engaged). Effect persists when settings are set to minimal and effects are off.
At the range Tanks and Melee must stand they are unreachable by Healers, and will therefore die. Healers must stand at range to do their job safely, but doing so makes them unable to target their parties tank. Being unable to target their party members the Healers, too, end up dead without protection. In addition Ranged DPS are unable to target the enemy or enemies. This leaves a good deal of players locked out of participation to the game content. This ranges from very disappointing, but not progression hindering (seasonal events and most FATES), to incredibly hindering (Quest required FATES, Hunts).
I know it's not the job of the reporter to come up with a fix for the issue, but I feel as though I should quickly add that simply making the game engine render entities in the order (Party > Engaged Enemy > Party Pets > Enemy > NPC > Other Players) would sufficiently alleviate the problem.
I am not reposting this to a new forum to make a nuisance of myself. I've searched the forums for other instances of this issue and found many who have been having to deal with the same problem. That goes double for those discussing it in game. And as of yet I have seen no response from any dev team or community representatives showing that they are even aware of the issue, much less that they are working on a fix. I don't like to think that this is simply being ignored. I would simply like to be reassured that the Dev Team is in fact aware that this is, and has been, an issue, and to know that it's one that is being worked on.