1000 FPS on loading screen safe for CPU/GPU?

[Knight]

As the title states; a few games hit crazy high fps on loading screens and intros for me even with the vsync on and I can't force nvidia control panel vsync because that causes fps drops in certain areas. I was just wondering if it's safe for me or not, heard stuff like this ends up causing coil whine on GPUs.

[Frank ツ]

Its oke, i have it sometimes in games to with a black loading screen 4000 fps, nothing wrong.

[Knight]

TCC Frank님이 먼저 게시:

Its oke, i have it sometimes in games to with a black loading screen 4000 fps, nothing wrong.

Okay, thank you for the response, this had me worried badly with Max Payne 3. I tried forcing vsync with nvidia control panel, that caused me fps drops and capping the fps also crashed the game sometimes

[kitt]

TCC Frank님이 먼저 게시:

Its oke, i have it sometimes in games to with a black loading screen 4000 fps, nothing wrong.

just not true, just look at the latest example New World and why Amazon hardcoded a FPS Limit into the Main Menu

It should be ok, doesn't mean it is in any case

[Cathulhu]

No matter what a game or software does, it should never be able to outright kill hardware. Unless they run on such a low level that they have direct access to the hardware, which games clearly don't. That's why APIs like DirectX, OpenGL and Vulkan exist. So they don't have to directly address the hundreds if not thousands of different hardware designs. They just use the API and optimize for that.

A game may be more or less taxing on hardware, but if something dies, it is clearly either the fault of the hardware, its firmware, or the driver for it. Not the software itself.
Just in case with New World and the EVGA videocards where EVGA admitted they were sloppy with the soldering of the MOSFETs. Which in turn lead to those cards dying prematurely.

While there are certainly problems with New World, it still shouldn't kill videocards. Poor cooling and bad design does.

[Knight]

kitt님이 먼저 게시:

TCC Frank님이 먼저 게시:

Its oke, i have it sometimes in games to with a black loading screen 4000 fps, nothing wrong.

just not true, just look at the latest example New World and why Amazon hardcoded a FPS Limit into the Main Menu

It should be ok, doesn't mean it is in any case

Many games have an fps limit, I'm mainly talking singleplayer here. Witcher 3's loading screen goes down to like 32fps and rises back up in gameplay as capped by vsync but for me here, some game's don't work that way.

[Brian9824]

Cathulhu님이 먼저 게시:

No matter what a game or software does, it should never be able to outright kill hardware. Unless they run on such a low level that they have direct access to the hardware, which games clearly don't. That's why APIs like DirectX, OpenGL and Vulkan exist. So they don't have to directly address the hundreds if not thousands of different hardware designs. They just use the API and optimize for that.

A game may be more or less taxing on hardware, but if something dies, it is clearly either the fault of the hardware, its firmware, or the driver for it. Not the software itself.
Just in case with New World and the EVGA videocards where EVGA admitted they were sloppy with the soldering of the MOSFETs. Which in turn lead to those cards dying prematurely.

While there are certainly problems with New World, it still shouldn't kill videocards. Poor cooling and bad design does.

Yep this, lots of people THOUGHT it was the game, turned out it was a poor solder job on a handful of cards.

[Satoru]

Again people need to stop thinking FPS is going to kill their system

You computer can render millions of FPS without issue for a decade

The fact your system has more dust bunnies than a Totoro movie and has airflow like an asthmatic smoker is the problem

[Knight]

Satoru님이 먼저 게시:

Again people need to stop thinking FPS is going to kill their system

You computer can render millions of FPS without issue for a decade

The fact your system has more dust bunnies than a Totoro movie and has airflow like an asthmatic smoker is the problem

Really appreciate the response and the kind words.

[Muppet among Puppets]

Set max fps to monitor refresh rate in the grafic driver settings itself. Everything else is useless to calculate

[kitt]

Satoru님이 먼저 게시:

Again people need to stop thinking FPS is going to kill their system

You computer can render millions of FPS without issue for a decade

The fact your system has more dust bunnies than a Totoro movie and has airflow like an asthmatic smoker is the problem

your posts about hardware are always so false and indicate you have no basic knowledge about anything, you just drop some buzzwords and make claims which don't even make any sense at all (showing you lack of basic knowledge)


High FPS can cause heat problems which in return can cause problems especially with bad Air Flow, bad cooling solution, power draw and so on..

but surely you knew that but just ingore it make claims like you do.. #blocked because I get more stupid just reading your Hardware related nonsense




https://www.youtube.com/watch?v=kxoXbfzP5BU

https://www.youtube.com/watch?v=3a4fOIXEvZo

I can already see the usual (oh its youtube blablabla), don't even bother.

[crunchyfrog]

Ask yourself this - why would ANY manufacturer create a device that could eat itself alive or other devices? Ever heard of liability?

If such a thing happened (by design), then they would be sued to hell and back wouldn't they? Besides that, it would be stupid business practice.

So no, framrate doesn't kill things, nor does certain games killing an Xbox/PS4/console or computer of your choice. These sort of myths are endemic.

This is very much like buying a bog standard car new from a garage and asking "wow the rev range is a bit high? Will it explode?"

The point being if the rev range is high, then that engine revs that high BY DESIGN. It's meant to operate there.

[crunchyfrog]

kitt님이 먼저 게시:

Satoru님이 먼저 게시:

Again people need to stop thinking FPS is going to kill their system

You computer can render millions of FPS without issue for a decade

The fact your system has more dust bunnies than a Totoro movie and has airflow like an asthmatic smoker is the problem

your posts about hardware are always so false and indicate you have no basic knowledge about anything, you just drop some buzzwords and make claims which don't even make any sense at all (showing you lack of basic knowledge)


https://www.youtube.com/watch?v=kxoXbfzP5BU

https://www.youtube.com/watch?v=3a4fOIXEvZo

I can already see the usual (oh its youtube blablabla), don't even bother.

They are not good evidence.

Correlation doesn't equal causation.

What likely happens in their cases are that they already have flaws on their system and delving heavily into a new game would push it over the edge. That CANNOT mean it causes it.

I used to have World of Warcraft ONLY shut my laptop down some years ago, despite playing thousands of games. Just that one game. So did it cause it? Nope. It was because the graphics card was on it's way out, and because WOW was using most of the PCs resrouces it was just enough to push it over the edge.

This is very much the same as those posts like "x game broke my Xbox" or "x game ruined my PS2 DVD drive". That doesn't happen, and evidence has to be FAR More specific than those daft Youtubers who don't know how logic works.

[Muppet among Puppets]

It is a good advice to set the max fps to monitor max.

Every other image just gets calculated to show a higher number in an fps counter. It is a waste of processing power, and energy. Transforming energy in computing power creates heat. That is a fact.

In other words, you create nothing, but heat. Above your monitor max frames, your computer is a heater.

[crunchyfrog]

Muppet among Puppets님이 먼저 게시:

It is a good advice to set the max fps to monitor max.

Every other image just gets calculated to show a higher number in an fps counter. It is a waste of processing power, and energy. Transforming energy in computing power creates heat. That is a fact.

In other words, you create nothing, but heat. Above your monitor max frames, your computer is a heater.

This, so very much (should have pointed this out in my post).

I'm sure everyone has seen shutter rolling effects or screen tearing before. That's caused by framerate of the monitor not dividing up exactly with the graphics provision.

It's not markedly dissimilar to getting a turntable and using a strobe disc with the light plugged into the same power source as the turntable. Watch the lines on the strobe disc until they don't appear to move, then you know you have the right speed.

So, yeah, if you have say a 120Hz monitor, having 120Hz, 240HZ or even 60Hz is a good bet. Even if the efefcts are minimal from incorrect choices, as you rightly say, it wastes resources.

[Muppet among Puppets]

And nothing will be different.
Like when i undervolted an oven cpu. It ran fine. Just way colder.

I have no idea why that "rational fps limit" isnt default...... well apart of for marketing.