How to make a game without requiring copy-pasta'd terrain.

[gifthorse]

Nope. If we take it on theory, then yes, maybe, but in this case, big fat nope.

We can clearly see where the "loads" are, because the maps are "boxy". That's an old engineer's trick, and that should have been most of what they needed. The copy and pasting on top of that smells of rush jobs, and laziness.

And they didn't even work that hard to hide the "box" trick.

What is the box trick? Look At the maps. big open area, long corridor, big area, long corridor, aka choke point, for a seamless load. Characters moving through that corridor = loading in background.

It's easy to spot, because the moment you look on the map, people will look for "short cuts" of course they are quick to realize, there exist none, because each section is closed off followed by a "tube" that connected to the next region. That is where the technical trick is.

Copy and pasting is a whole separate issue it seems, and one likely attributed to money.

I agree that it could have been disguised better, but the point I was making is that making a series of individual discrete objects and then fitting them together is more difficult than just making one giant discrete object. One object would require more data than several repeated ones, hence why SE chose the latter. Their attempts at disguising it failed though.

The goal is to make several smaller objects and then fit them together or superimpose them in such a way that it gives the impression of one, greater unique object. SE failed at fitting their smaller individual objects together, they didn't fail at making them.

After all, they can't just make infinite amounts of discrete objects with today's technology. I mean they can if they want to, but their engine can't load them all in. SE faces technological constraints on the amount of data they can load in. Using another engine may have helped, but they would have to then compromise on graphical quality.

I think those zone margins within the greater zones are more network-based, and probably don't alleviate as much stress on people's video cards and ram as you think. The mini zones within the zones are still using the same textures, and whatnot. The tunnels which conveniently separate the areas are most likely there so people can load in the arrangement of the objects while travelling rather than to help load in entirely new objects.

[kukurumei]

I agree that it could have been disguised better, but the point I was making is that making a series of individual discrete objects and then fitting them together is more difficult than just making one giant discrete object. One object would require more data than several repeated ones, hence why SE chose the latter. Their attempts at disguising it failed though.

The goal is to make several smaller objects and then fit them together or superimpose them in such a way that it gives the impression of one, greater unique object. SE failed at fitting their smaller individual objects together, they didn't fail at making them.

After all, they can't just make infinite amounts of discrete objects with today's technology. I mean they can if they want to, but their engine can't load them all in. SE faces technological constraints on the amount of data they can load in. Using another engine may have helped, but they would have to then compromise on graphical quality.

For example. A shack, if it was procedural, it would have been scaled, reshaped and maybe even colored differently or the arrangement of the camp would have been mixed and matched. None of that was even there.

I think those zone margins within the greater zones are more network-based, and probably don't alleviate as much stress on people's video cards and ram as you think. The mini zones within the zones are still using the same textures, and whatnot. The tunnels which conveniently separate the areas are most likely there so people can load in the arrangement of the objects while travelling rather than to help load in entirely new objects.

That's a a little far fetched to me. Since we know that Lod is indeed used in the engine, and the objects in general aren't very procedural in FF14. There isn't that much procedural work done, rather repetition, which begs the question, of what they are they trying to optimize here.

You would have a point if there is aggressive use of procedural work, which would lead to the conclusion they needed to squeeze that memory requirement, but given how the game is programmed, it's more of a question why didn't they use more of it to squeeze that memory requirement.

Copy and pasting objects as a technical solution is a last result ideal. The fact the game wasn't even squeezing it, and having regular old trees and tents and shacks put around over and over leads to different conclusions.

For example, if it was procedural, we would have had changed shaped, scaled, and maybe even different colors. That shows there were simply being dumped on to a scene, rather then manipulated like most procedural work.

Even then that's rather minimal compare to the graphics requirements. Server load balancing hand outs is like...a drop in the water to put a 3 minute corridor. There is no reason to be doing that unless the client is flushing the memory of behind, to load, in front.

We can always easily blame it on the engine, but then we can blame the engine for everything as ultimately, it's always a limitation of engines. The sad fact here is, there's too much and too overly done.

Something isn't adding up here. There are too many holes in the story where any decent graphics designer would immediately have made his living.