Jump to content

SVT Raptor jumped 35ft into the air & destroyed

Zane

By Zane
in Future GM News & Rumors

Recommended Posts

tyhuck Senior Enthusiast

tyhuck

Posted
Posted

I think what he is trying to say is that a trophy truck is build for this kind of stunts.

And to do so you have to throw expensive parts at the car.

 

so long

j-ten-ner

 

 

Exactly. I guess some people dont understand the concept of exageration. Besides, I built my truck on the cheap, so to me, they might as well cost millions. :D

  • Replies 50
  • Created
  • Last Reply
tanked_darren Senior Enthusiast

tanked_darren

Posted
Posted
I know several capable prerunner build that cost less than a Raptor.... :dunno:

 

When people have money its easier to just spend more. If you make enough, to some people its just easier to pay versus time spent. You won't see guys with families and huge mortgages they can barely pay buying and destroying vehicles like this.

 

Plus there is the coolness factor...

 

It's like saying I know how to build a stock mustang to beat a SVT cobra, it might be cheaper, but still not a SVT cobra

 

Sent from my Nokia 5190 using Tapatalk 2

 

 

sonjaab Senior Enthusiast

sonjaab

Posted
Posted

Those fools destroyed that truck!

 

The F*rd boys are in deep denial over that vid.!

I guess the Rupture ain't so TUFF after all.

Just another $pendy "look at me" driveway queen !!!!!!!!!!!!!!

Z71_Silvy2 Enthusiast

Z71_Silvy2

Posted
Posted

One of the guys had a thread on raptorforumz about it, something linked me to it once. Frame doesn't have enough support over rear bumpstop. Ford blamed it on people putting on aftermarket springs without the bumpstop contact attached to the bracket. After that they realized it was virtually all trucks that were on high speed runs, they then claimed that it was supposed to do that for safety reasons, so it wouldn't break the axle. There is a tooling hole right above the bump stop, sounds like a design accident to me...

 

 

The funny part is, right after the Ford floppy frame fiasco (you can call it the 'quad F'...lol), Ford completely changed their marketing for the Raptor....because people were doing exactly what the ads showed Ford doing.

 

Sometimes, you just can't fix cheap.

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

  • Latest Articles

  • Posts

    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • davester
      Replacement Radiator

      By davester · Posted

      And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • davester
      Turning radius

      By davester · Posted

      Just don't turn the steering wheel as much?
    • Snowcamo
      Replacement Radiator

      By Snowcamo · Posted

      Rockauto bud. I pass local stores for parts.   Findya something online. 

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...