Removal of loading screens

[Valkyrie_Lenneth]

1.0 did have loading screens, they were long narrow pathways between zones where you would see players phase out and in.

[Evergrey]

1.0 did have loading screens, they were long narrow pathways between zones where you would see players phase out and in.

This.
I never really played 1.0 but I've listened to explenations about the old loading screens.
They disguised it as narrow pathways that blocked the line of sight of the old and new area and while you ran there the game was loading in the new zone while phasing out of the old one outside of the players field of vision.

[Bright-Flower]

This.
I never really played 1.0 but I've listened to explenations about the old loading screens.
They disguised it as narrow pathways that blocked the line of sight of the old and new area and while you ran there the game was loading in the new zone while phasing out of the old one outside of the players field of vision.

This reminds me of somethign WoW did in a lot of its city entrances. You walk in the gate, and there's a wall you have to run around before you get into the actual city to buy time for things to load.

In Metroid Prime new rooms would load when you shot a door to open it, and you could tell sometimes it was struggling when it'd take several seconds for one to open.

Little disguises like that for load times aren't all that uncommon.

[Larirawiel]

Blizzard don't have to take console into consideration, and it's not like wow is a graphical monster compared to 14, granted 14 has some terrible textures.

They could keep the loading screens on old consoles and remove them on PC or on modern consoles.

This.
They disguised it as narrow pathways that blocked the line of sight of the old and new area and while you ran there the game was loading in the new zone while phasing out of the old one outside of the players field of vision.

A GPU can also discard non-visible objects and skip rendering them as long as front-to-back-rendering is used. That's also the reason for such line-of-sight-optimizations. But this is difficult in MMOs because most of them are open world and there not many opportunities to do so.


Cheers

[Daeriion_Aeradiir]

They could keep the loading screens on old consoles and remove them on PC or on modern consoles.

This wouldn't work. Because of console <-> PC crossplay, any changes to the zones and worlds needs to be reflected on both ends since its a persistent world. To give loading screens to Consoles and not PC, they would effectively have to have 3 versions of Limsa and segregate the instance based on what platform you're on:

-'Full Limsa instance', only accessible by PC players
-'Limsa Lominsa Lower Decks', only accesible by console players.
-'Limsa Lominsa upper decks', only accessible by console players.

Which would not only be cumbersome, but also just plain hindering for the game as a whole since it would be effectively one step away from console exclusive servers. If they're going to stitch zones back together, they have to do it for all. But that's besides the point; PS4 is hardly a chokepoint for the game these days. There's still lots of players who play the game on very outdated or lower end hardware that even the PS4 is stronger than. I know plenty of friends who play on PS4 still that outside of hunts don't have issues ever playing the game.

Personally I'd like to see the cities stitched back together. Ul'dah would feel a lot nicer without the main road being cut by a loading screen. Kugane & Crystarium both show how incredibly big they can make the cities these days, a re-combined city shouldn't be an issue technical wise. though it's likely an extremely low priority thing for them since there'd be little playoff from it, dev wise. Especially since the recent loading screen change they did, you can load into zones at like <1s if you have a good SSD.