Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
https://www.youtube.com/watch?v=xsXFUVYPIx4
Don't play words, I quoted high end, for a game like Halo Reach my PC is high end and should be able to run the game perfectly smooth I shouldn't need a ****ing nasa computer to run it and 16GB of ram is way enough nowadays.
I understood what you were getting at--and yeah, given your specs, you should be okay. That said, I get random frame drops even on an i7-7700k paired with an RTX 2080 (I also have 16 GB of RAM). It seems to be a general concern with the port as a whole when not using VSync.
That said, if you know the game runs better with VSync on, yet your preference to have it off is causing you issues, that's more of a you problem, right there.
I do not, after all, load up my old King's Quest titles on DOS Box and expect them to run at 4k/60 just because my PC could effectively run twenty copies of the game in tandem. You generally have to meet the program where it's at initially; brute forcing solutions only works up to a point.
If I was to answer this stupid message of yours the way I would want to, it would get me banned from the community. "Oh LoOk I hAvE a BeTtEr Pc ThAn YoUrS LoLoLoL GeT ReKt".
not true, since the game simply doesn't use that much RAM or VRAM (I think his card has 4GB).
people should actually look at a RAM graph before they say things like this
More of a "Me" problem ? Are you serious ? Anybody playing competitively knows that turning Vsync on is a no no, the problem is coming from garbage optimization of the game.
I mean, if your aspirations are to play competitively, then a sharper rig would probably be the first thing I'd be looking at (and I don't mean that as an insult--it's just that if you're going to get into the high-end stuff, you should be rolling a high-end rig, assuming that "every frame counts").
As far as "garbage optimization" goes--you are, in the case of Reach, talking about a game that's eleven years old. It hails from a time when 144hz monitors were not a widely available thing, and framerates above 60 were incredibly uncommon.
The idea that it should suddenly be fully unlocked and able to handle 300+ FPS--when all we were ever sold was a port, rather than a ground-up remake--is indicative of a failure to understand the realities of software development and hardware environments.
The game works very smoothly with VSync enabled, and however developed the competitive Halo scene might be, it's also not the current route to big bucks and "Ninja" level fame/success, so why you're leaning so hard on it performing in a category it never aspired to occupy, I don't know.
Yeah but people are stupid, they just buy expensive computers without knowing anything about how they work and then want to pretend they do just because of their specs, arena games like CS, Halo, Quake etc do not use a lot of ram indeed, my graphic card is probably the least efficient part of my PC but it should still run reach perfectly fine on lowest settings possible
Well when I read that people having the last graphic cards and processors still have some FPS issues, I am sure you can understand that I don't want to throw money out of the window and you could maybe agree that the problem is not really on my end...
indeed. I don't even know what game he thinks he's playing, because I notice on the highest settings at 1920x1080, it's only using 2GB of VRAM and just over 2GB of motherboard RAM (for the .exe, I mean)
https://ibb.co/9Vn6fN8
also, this is combat evolved. I think reach is pretty stuttery on nvidia, it's perfect on my rx 570. but I tried it on 750ti and it was stuttery (not performance related, since GPU usage wasn't high, although I suppose it's only 2GB card, but it should be fine using all 2GB as a large cache a lot of games do)
I can definitely agree that the stability of the framerate with VSync off is a software problem. When I said it was a "you" problem, what I meant was that a stabilizing solution exists--you're just refusing to use it.
That's certainly your right. I guess that for me, the "competitive" argument doesn't make a lot of sense, solely because Reach is not--to the best of my knowledge (please correct me if I'm wrong)--on any of the major tournament circuits right now.
I'm also old, and used to getting curb-stomped by younger folk with faster reflexes and more time to "git gud" at the game, so take my opinion here with a shaker or two of salt.
The thing is that Vsync is not a solution because when the said solution impacts your gameplay a lot, an causes a problem from fixing another problem, it is not a solution at all.
When I said competitively I meant try harding and not just playing for fun if you prefer, I am playing for score most of the time and these stutters make it really hard for me to play at my max performance, also but that is just my opinion, in the next months or year there very well may be tournaments and e-sport for Halo on PC.