Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Sergius]

the shacks and trees are hardcoded to fall apart... they arent made out of peices of things that you can just hit off.

Sorry, but you're very wrong on this count. You probably shouldn't be arguing with anyone if you haven't even played one of the games in question. I still don't understand exactly what the argument is about, but still.

I've played Crysis, the engine does some sort of boolean subdivision and/or spawn new models from pieces of the old models, which is pretty nifty. But it's not as if each tree trunk is made of 100 tiny little cubes of wood.

Also why are people comparing Crysis with Fallout 3? I'm lucky if I can get 2 FPS in Crysis at minimum detail, low quality textures and all the shadows and effects turned out, yet I play Fallout 3 at maximum detail (I only turn off dynamic shadows which my 7800GT apparently sucks at... they're slow and look fugly) and I get easily 20-40 fps even in my dated PC configuration.

[Reasonableman]

Just for the record, I thought oblivion ran worse than fallout 3. Well, I still do.

But it doesnt matter that much, they both run like mol-ass-es.

This man speaks the truth.

[Puck]

This man speaks the truth.

This man is reasonable.

[Micro102]

I thought it's about if the gamebryo engine sucks.

I'd estimate 50% (did you know that 80% percent of all statistics are made up on the spot?) of gamers cannot or do not perceive one of the major problems of the engine. People tend to call it "microstuttering" but apparently that term actually describes a specific SLI synch problem, but there is no better word for the problem in the gamebryo engine yet.

Anyways. Pick an outside spot in FO3/Oblivion. A spot your PC is able to render properly at a decent framerate. Turn around 360°. If you dont notice how the vertical lines jump back and forth (IM NOT TALKING ABOUT TEARING HERE) youre one of the lucky people that doesnt notice it and can go play it happily ever after.

The rest of us, you know, the people that actually have put some points into perception, have to suffer from this horrible horrible thing.

If you use the ifpsclamp setting in the ini file, you can remedy that, but you have to provide a constant framerate to make it useful. The only way to RELIABLE cap the framerate in oblivion and fo3 is using vsync, tho, which means you have to spend a whole lot of mola so you can have a puter that constantly provides 60 frames.

now here comes the hook: go to rivet town, for instance. walk over the bridge, turn right, enter the market there. proceed in the direction of the burning barrel. Your fps WILL drop for no apparent reason.

I dont know whats going on there. Other than my cpu, maybe (2.4ghz core2duo) I have more than enough juice to run the game. I tried it on 800x600 with lowest settings, fps drops there.

Which fucks up the ifpsclamp setting.

Oblivion has even more of those mysterious molasses spots.

its because the fire creates random pixel sequences to make it look like a flame. the closer you get the larger the flame gets which makes it lag


ok i just realized we cant compare games like this. we have different computers and different requirments. but on the xbox 360 there is no change in content and fallout runs perfectly. is crysis on the xbox too?

[Puck]

That's what I thought first too, but im 100% sure its not the fires - there are hundreds of burning barrels or whatever firesources that dont do the trick, but rooms without any special light effects and are really dim and bland that do the same.

I just picked the spot i described above because its easy to find.

[KaelGotDwarves]

So I read part of this thread expecting to find some firsthand accounts on whether Fallout3 is a game worth getting.

What I discovered is that Fallout 3 = drama.

[Puck]

whether Fallout3 is a game worth getting.

A friend of mine got it, I installed it and finished it twice. I enjoyed myself, but I'm happy I didnt spend any money on it. If the money it would cost you doesnt matter that much to you, you can safely buy it.

If you have to count every penny twice, don't.

[Torak]

its because the fire creates random pixel sequences to make it look like a flame. the closer you get the larger the flame gets which makes it lag

You've really got no idea what you're talking about. Making 'random pixel sequences' does not bring a modern computer to it's knees. If that were the case every visual effect in a media player would cause computers to halt.

[Micro102]

all i know is that a computer having to contantly change pixels like that will run more slowly then if your looking at a wall

[Torak]

all i know is that a computer having to contantly change pixels like that will run more slowly then if your looking at a wall

All you know is baloney.

[Puck]

In my defense, I assumed this stream of "randomized pixels" would actually be a stream of lots of little lightsources, but I also quickly doubted that theory anyways, as I said, I quickly moved on to "its not the fire"

But in his defense...
When I played STALKER with my older vidcard it would run acceptable on high-ish settings, but looking at ANY campfire or burning barrel would bring it down real good.

But that doesnt seem to be the problem with fo3. its something else there.

[Reasonableman]

When I played STALKER with my older vidcard it would run acceptable on high-ish settings, but looking at ANY campfire or burning barrel would bring it down real good.

Methinks that's 'cause STALKER's flames flickered, requiring shadows to be recalculated with each 'flickering'. Just a guess. Still, I've lost track of just what we're arguing over and why.

[Micro102]

of FO3 could be using more advanced lighting...making some sort stream of bloom or shadow pixels, or something else you cant see

[Soulwynd]

That has to do with the number of sprites in the scene. Those lil faeries have been the reason why explosions and most fire animations screw your fps.

Of course, I haven't played f3 in a while, and I don't feel like going in game just to look at some flame. Secondary guesses (unless you post me a screenshot, then I can tell you for sure what's happening) are bad sprite encoding (I've seen games with that issue before and it tends to only affect certain systems), volumetric particles (not likely, I don't remember seeing anything like that), a regular number of sprites with the dumbassness of allowing them to be affected by dynamic lights without using billboarding which is ugly anyway, some shitty lod code making it generate more sprites/particles than it actually should (back to way too many sprites to begin with), and maybe, the sprites have complex shaders which would be just nuts. Actually, one of the games I'm alpha testing has about 8 shader transparent particles when you run around, cute looking, but poor slow vcards.

[Puck]

When you rescue poor daddy from tranquility lane or woteveritscalled and then follow him on foot to rivet town, you cross a small raider outpost. One guy there carries a rocket launcher.

That scene tends to get a whole shitload of cars blown up. I'm talking nasty fireworks here. Like a 50 metres chain of cars, busses and old train thingies rising up through the air in a ball of fire.
The framerate drops a LITTLE when all the effects are being loaded. It stutters for the fraction of a second.

But I can watch the pwetty lights and everything and pretty much 60 frames.

I really start to regret I mentioned that burning barrel in rivet city  Because you can get the framerate down there, at the market, even without looking at it.

oh, just for the record... I got me a 9800gt just for fo3, I guess the card provides enoug juice, now, does it?