If you play it frame by frame (using the < > keys while paused) at 0:09 upshift 2nd to 3rd almost redlining at 80mph; up until this point the engine damage indicator has been clear. At 0:10 downshifting 3rd to 2nd at between 86 and 87mph. Tach redline graphics increases, and finally catches up to actual rpm. At the precise moment (Easily visible if you set the playback quality to 1080p ) when the rpm on the gauge goes full/solid red, is the same frame we see the first indication of engine damage displayed on the car damage graphics (between the 4 tires, left of the speedometer). The very top left corner of the engine has a few pixels of red for this frame and about 3-4 frames following, then is full red the same frame he reaches 82mph. So it does in fact look like it was from overrevving. Hopefully somebody has tested this by now in a race *with the same vehicular damage settings*
Yeah this happened to me in a ford lm test car because i wasnt paying enough attention i was shifting at the limit and this happened. I am happy to see it wasnt just a bug but a mechanic
I've gotten one to 185 in real life...but then it totally quit. Then the spun bearing reared its head. I could have kept going at least 100 mph, but how much more damage would that have caused?
Just because it says failed engine doesn't mean the engine is actually failing. Could be a sensor failing that it requires to operate the engine at the limit it is at. Could have messed up air fuel mixtures.
Not always. Engines that have blown up can sometimes keep running as long as you never let off the throttle. The minute you let it slow is when it dies. It all depends on how exactly the engine has failed. For example, there are plenty of videos on YT of engines with gaping holes in the block running just fine. And they will until they lose enough oil through that hole to lock up. That's a blown up engine that's still running.
that's actually a really sick, but unlucky mechanic especially in the last lap ouchiesssss imagine if we got like some sort of noise to go along with it lol
I've never had this happen to me so far in GT7 since I never remember seeing or experiencing this before in the game myself although on my current car that I'm using, the oil is getting bad on it already even though I haven't changed it yet.
Can confirm, a catastrophic failure would infact cause the engine to stop immediately such as a sudden loss of oil pressure. A blown headgasket for instance, the engine would continue working until it completely overheats more similar to what is seen here.
Headgasket failure can happen too without engine overheating if fails between cylinders. Causes loss of power, detonation and reduced compression which in turn will reduce power considerably. Will get worse and worse until it destroys pistons and then will develop bad crankcase blowby too. Similar if piston rings fail. Engine will be very smokey and will lose power. Your right in that in the real world, will only notice a minor decrease in power over a very long time but that'll usually be a roadcar. Don't keep on top of maintenance on an engine that's being worked at 100% all the time on track, it'll be alot more noticeable and happen quicker.
I had this happen in a race at Spa. It didn’t come back even after a pit stop. Just dead. It seems like it’s a very rare occurrence but it does happen. No oil issue here either.
@0:01 the impact cause damage to the engine temporarily. Thus the engine flashing light. After awhile the engine will restore itself and have the power back. Could the ride height too low cause the car to bottom out? Maybe?
@@korbynnull7666I am talking about the engine failure indicator on the left of the screen. I was able to make it flash when I hit the car really hard on the ground.
i tried to simulate engine failure, after 1500 miles crashes on purpose, redlining etc. still works fine. Thats something i miss in GT7, redlining should result in engine failure.
