Isn't it funny how you can walk the whole Fallout: New Vegas map and there isn't one loading sequence like Fo3 or tes games?? So does this mean that everything that is accessible on the main map is continuously going on at all times?? Are the Cazadors at their nest still buzzing around Vault 22, while the Radscorpions scamper by the Golden Geckos by the Mojave Drive-In?? If they are responded by your distance from them, how long does the game register their bodies after you kill them?? Is this the reason why my gamesaves start from 3mb to 8mb?? Could this be the main issue of freezes and many other common glitches in FoNV?? Just too many things going on at the same time??

Let me rephrase this a little. I don't me an loading screen while your playing what I meant was this: [F03] When walking from Megaton to Tenpenny's Tower, you will occasionally be stopped and on the bottom of the screen you will get [Loading...]. The way I saw it was that the map was broken up by segments. When you reach the end of the segment the game will load the next one. I was stating how FoNV didn't do this and shouldn't it. Some have made me aware that pc didn't go this with TES or Fo3 and that's cool, but I'm on ps3 sorry for not saying that earlier.

Umm. Those other games weren't supposed to have loading screens either in the open world. If you got them that's usually an indication that your hardware was operating too slowly.

I'm sorry, in console games they sort of paused in the middle of the game while exploring and on the bottom screen it would read [LOADING...] I just assumed all platforms were like this..

My last xbox (which finally got it's first RROD after 2 years) had that problem with Oblivion.
Sometimes it just didn't load fast enough as I was running so sometime a little "loading" popped up in the middle and it freezed and then went back to normal after a couple of seconds.
But I never got that with FO3.

I know that freeze and loading is normal. That's what I was saying, shouldn't FoNV have that too. Have the map broken up by segments? Not just one huge massive cluster [*].

in fact, even if your hardware wasn't very good, you woulnf't actually get a loading screen, the game would just take a moment to load, loading screens only occurred when fast traveling or when traveling through loading doors, like into interior locations or some exteriors that are on different worldspaces from the rest of the world, like Freeside and the Strip. This isn't to say that the game didn't have to load new cells when you're exploring exterior areas, of course, just that the loading screen only comes up when making transitions through loading doors, which doesn't seem like a bad design as it would be rather distracting if the loading screen came up regularly while you're exploring the wasteland.

But in any case, since Fallout: New Vegas uses the same engine as Fallout 3 and Oblivion, I'd assume that cells are handled the same way. And I don't even seem to recall the game ever pausing and giving me a "loading" message in Fallout 3, now, there was sometimes stuttering and poor framerate, but that can happen even when you're not loading a new cell. So I'd guess that the version of the engine used in Fallout 3 and New Vegas might be more efficient at loading data for interior cells than the earlier version from Oblivion.