409 réponses à ce sujet

[masleslie]

Trying to get back on topic,.. Although i may not agree with all your numbers the principle is sound.

I moved up to Gold a few months back after a year of playing Silver. A lot of weapons I used to play just don't cut it on the higher difficulty because they don't do enough damage. So buffing a bunch of them seems reasonable. It would also help some of the inexperienced players turning up in Gold lobbies with their Avenger II.

Problem is - it will never happen. All the devs who could do it are working on other things by now. So I guess we'll all just have to enjoy what we have till EA pulls the plug.

[Cyonan]

Element 0 wrote...

Oh. So the enemies just get stupid at 20 FPS, better at 30 and on 60 they are twice as good? And if you decide to take advantage of your 120 Hz monitor and unlock the FPS, they become even better? Okay. :innocent:

I didn't say that things weren't tied to framrate. I said BioWare wasn't responsible for it.

Commander Riker to the BSN. We need more facepalms.

[capn233]

Element 0 wrote...

And you should read the posts of Capn233 before posting. 

This should be everyone's goal.

[Cirvante]

Cyonan wrote...

Element 0 wrote...

Oh. So the enemies just get stupid at 20 FPS, better at 30 and on 60 they are twice as good? And if you decide to take advantage of your 120 Hz monitor and unlock the FPS, they become even better? Okay. :innocent:

I didn't say that things weren't tied to framrate. I said BioWare wasn't responsible for it.

Commander Riker to the BSN. We need more facepalms.

Riker to Cyonvi. Facepalm incoming in 3 ... 2 ... 1 ...

[Cyonan]

Element 0 wrote...
So you're saying Unreal Engine is? Cos I've played a lot of UE games and 30 FPS or 120 FPS or even more didn't have any difference.

Apparently I'm saying that everything in this game is perfect, so the engine couldn't possibly have such errors in them.

I'll post you BioWare's code that runs a unit's AI if you'd like, and you can point out to everybody the part that alters the programming based on the framerate.

The vast majority of people would neither know nor suspect anything about framerate altering things in this game had people like Corlist not told them about it. It's not really something that's painfully obvious.

[DHKany]

Well aren't you a special snowflake

[RoundedPlanet88]

DHKany wrote...

Well aren't you a special snowflake

That's cold man.
You really shouldn`t turn up the heat like that.

[Cyonan]

Element 0 wrote...

RLY NAO?. Cos I've seen RedJohn's videos WAY before the FPS thing and knew something was clearly wrong. When 2 hunters miss a stationary target point blank - we have a problem. When a Phantom Palm blasters every molecule around the character, but the character, we have a problem. 

Did you watch Red John play those other UE3 games, too?

[capn233]

I guess you might say E0's AI expectations...
*sunglasses*
...are a bit Unreal-istic.

YEEEEEEEEEEEEEEEEEEEAAAAAAAAAAAAAAAAAAAAAAAH!

[d_nought]

capn233 wrote...

I guess you might say E0's AI expectations...
*sunglasses*
...are a bit Unreal-istic.

YEEEEEEEEEEEEEEEEEEEAAAAAAAAAAAAAAAAAAAAAAAH!

Excellent

[BridgeBurner]

FailQuotes pls, it's bioware's variables which count here.

Simply adding an extra 0 to the enemyinterplocspeed variable causes the enemies to become inordinately dumb.

Removing the 0 from the default 20 (reducing it to 2) gives your AI "aimbot".

AFAIR, "enemyinterplocspeed" = 20 means the enemy AI gets an update on player locations every 20 frames. Meaning, at 30fps, the enemy updates your location every 0.66 seconds. At 120 fps, it's every 0.166 seconds... hence why the AI is dumber at lower frame rates, it's nothing to do with code really, it's a static variable which makes the code do what it's supposed to, with huge variance depending on frame rate.

Other Unreal Engine games probably do not use similar variables, though there will always be a dip in AI performance at lower frame rates simply due to lack of processing power.

And don't kid yourself FailQuotes, there's no way you play anywhere near 120fps, not after that performance vs fasterthanftl, no self respecting person with 120fps fails that badly.

Modifié par Annomander, 30 août 2013 - 08:11 .

[RoundedPlanet88]

Element 0 wrote...

capn233 wrote...

I guess you might say E0's AI expectations...
*sunglasses*
...are a bit Unreal-istic.

YEEEEEEEEEEEEEEEEEEEAAAAAAAAAAAAAAAAAAAAAAAH!

 

So it's my fault now in expecting some consistency in a game? Especially when crap hardware people can host and make Platinum look like a walk in a park? Or when I unlock my FPS - even BSN '"Soloists on Thunderdome" start to drop like flies? 

LOL, are you of all people asking for consistency?

Like, being consistent in argument positions?


Entitled 0 please.

[capn233]

Element 0 wrote...

So it's my fault now in expecting some consistency in a game? Especially when crap hardware people can host and make Platinum look like a walk in a park? Or when I unlock my FPS - even BSN '"Soloists on Thunderdome" start to drop like flies?

That's all very interesting, but the point Cyonan was making was that this is inherent to Unreal Engine 3 and unless Bioware was rewriting the engine, it basically has to behave like that.

[capn233]

All the variable does is make it wait a certain amount of frames to update player's location for the purpose of the AI.

It does not matter what you set interpenemylocspeed to, the AI will always scale with framerate. All the variable does is make them update more or less frequently at a given framerate.

Modifié par capn233, 30 août 2013 - 08:27 .

[BridgeBurner]

Element 0 wrote...

Annomander wrote...

FailQuotes pls, it's bioware's variables which count here.

Simply adding an extra 0 to the enemyinterplocspeed variable causes the enemies to become inordinately dumb.

Removing the 0 from the default 20 (reducing it to 2) gives your AI "aimbot".

AFAIR, "enemyinterplocspeed" = 20 means the enemy AI gets an update on player locations every 20 frames. Meaning, at 30fps, the enemy updates your location every 0.66 seconds. At 120 fps, it's every 0.166 seconds... hence why the AI is dumber at lower frame rates, it's nothing to do with code really, it's a static variable which makes the code do what it's supposed to, with huge variance depending on frame rate.

Other Unreal Engine games probably do not use similar variables, though there will always be a dip in AI performance at lower frame rates simply due to lack of processing power.

And don't kid yourself FailQuotes, there's no way you play anywhere near 120fps, not after that performance vs fasterthanftl, no self respecting person with 120fps fails that badly.

 

Pfff. I know about that interpret my loc speed thingy. Caratinoid told me about it months and months ago. 

Also, keyboard knight, show us your Platinum duos. Wanna do one now? 

I don't duo with scrubs who can't even complete a game, or get a 20 headshots medal using a GI talon... Remember, that really OP character that you still failed with?

And don't call other people a Keyboard knight either, it makes you look desperate, particularly if you have no IRL photos, or you refuse to tell people your name... I guess that would make you the "keyboard knight", huh?

[BridgeBurner]

Element 0 wrote...

Annomander wrote...

Element 0 wrote...

Annomander wrote...

FailQuotes pls, it's bioware's variables which count here.

Simply adding an extra 0 to the enemyinterplocspeed variable causes the enemies to become inordinately dumb.

Removing the 0 from the default 20 (reducing it to 2) gives your AI "aimbot".

AFAIR, "enemyinterplocspeed" = 20 means the enemy AI gets an update on player locations every 20 frames. Meaning, at 30fps, the enemy updates your location every 0.66 seconds. At 120 fps, it's every 0.166 seconds... hence why the AI is dumber at lower frame rates, it's nothing to do with code really, it's a static variable which makes the code do what it's supposed to, with huge variance depending on frame rate.

Other Unreal Engine games probably do not use similar variables, though there will always be a dip in AI performance at lower frame rates simply due to lack of processing power.

And don't kid yourself FailQuotes, there's no way you play anywhere near 120fps, not after that performance vs fasterthanftl, no self respecting person with 120fps fails that badly.

 

Pfff. I know about that interpret my loc speed thingy. Caratinoid told me about it months and months ago. 

Also, keyboard knight, show us your Platinum duos. Wanna do one now? 

I don't duo with scrubs who can't even complete a game, or get a 20 headshots medal using a GI talon... Remember, that really OP character that you still failed with?

And don't call other people a Keyboard knight either, it makes you look desperate, particularly if you have no IRL photos, or you refuse to tell people your name... I guess that would make you the "keyboard knight", huh?

 

I'm sorry you idiot, but I did get 20 headshots. Both times. So. Eff off. 

Guess you're just camera shy. And no, on the screenshots I saw, there was no 20 headshots medal. Not difficult, is it?

I may be an idiot, but what does that make you? People prove you wrong, time and time again, yet you still keep blindly repeating the same BS, without any logic or facts to back up anything you're saying...?

[Radford]

At this point this thread is kinda painful to watch, kind of like a guilty pleasure. If you didn't blow your top so easily you might have gotten your points across more easily, AQ.

Not saying people aren't pressing the right buttons...

Modifié par Radford, 30 août 2013 - 08:39 .