Jump to content

Recommended Posts

Posted

I thought my Camaro was straight black but just always looked dusty till I bought the pint of paint and saw all the metallic in it. Then I looked closer at the car and it is VERY subtle, but it is metallic.

  • Like 1
Posted (edited)

spacer.pngI might as well chime in. I have a 2021 Sierra Denali 1500 with Onyx black and its w/o a doubt non-metallic.  If it was metallic, it would say it was metallic in the paint name.

 

Ebony Twilight Metallic is another black color that was offered in 2021.

 

 

Edited by elcamino
Posted

Looking at it a little more this morning, my mirror caps, bumpers, and all plastics on the front end don't have any metallic either... What a letdown

Posted
1 hour ago, 20Denali21 said:

Looking at it a little more this morning, my mirror caps, bumpers, and all plastics on the front end don't have any metallic either... What a letdown

So it's only on the hood? 

Posted
1 hour ago, mafd2 said:

So it's only on the hood? 

The hood and front end has it the worst. The metallic color on the bed is 1/2 of what it is on the front. The whole truck has it other than the plastics though.

Posted (edited)

I have a 2022 LTD LTZ that is black . No Metallic. 

I also have a 2022 LTD High Country that is Mosaic black. It has Metallic. From 10 ft away they look the same.

 

Screenshot_20220210-113252_Drive.jpg

 

 

 

Screenshot_20220226-155527_Drive.jpg

Edited by dieselfan1
Posted

Went in this morning to have the dealer look at it and the service and sales manager both agreed that it wasn't right. 

 

I have an appointment next Monday to bring it back and drop it off to see what the solution is going to be. They already said they'll replace the vehicle but have to get this ball rolling sooooo here we go... weee

Posted

Truck got damaged in shipping and was repainted the wrong color possibly? 

  • 20L8TSierra24 changed the title to Does Onyx Black now have red glitter?
Posted
45 minutes ago, jlong1984 said:

Truck got damaged in shipping and was repainted the wrong color possibly? 

The whole vehicle is this way. I don't think so because there wasn't any real long delays either. My dealer called me as soon as it hit the lot too.

Posted (edited)
37 minutes ago, jaxcam02 said:

my guess is that it is rail dust from transportation. Might want to get iron remover.

Definitely not rail dust. It's definitely in the base under the clear.

Edited by 20Denali21
Posted
On 5/16/2022 at 12:05 PM, 20Denali21 said:

 They already said they'll replace the vehicle but have to get this ball rolling sooooo here we go... weee

What are you waiting for?

I'm not accepting a new truck that has a shittty paint job.

You are never going to like it the way it is. Repaint? You ain't going to like that either. 

Just my two cents 

  • Like 1
Posted (edited)
1 hour ago, dieselfan1 said:

What are you waiting for?

I'm not accepting a new truck that has a shittty paint job.

You are never going to like it the way it is. Repaint? You ain't going to like that either. 

Just my two cents 

They have to refinish it so they can resell it is what i was told. It was a cloudy/rainy day when I picked it up so I had no clue it was like this until the next day at home.

 

They are ordering me the exact truck but I have to drive this one in the meantime until that vehicle shows up.

 

They said I'd be no out of pocket unless I wanted to add options. 

Edited by 20Denali21
  • Like 2
Posted
51 minutes ago, 20Denali21 said:

They have to refinish it so they can resell it is what i was told. It was a cloudy/rainy day when I picked it up so I had no clue it was like this until the next day at home.

 

They are ordering me the exact truck but I have to drive this one in the meantime until that vehicle shows up.

 

They said I'd be no out of pocket unless I wanted to add options. 

That's good. At first I thought you were having it fixed.

Glad you got a good dealer.

A lot would say pound sand we are fixing it.

 

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   4 Members, 0 Anonymous, 1,694 Guests (See full list)

  • Latest Articles

  • Posts

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...