12 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHMy paint detailing page
Leading reported evidence
Use each step: clay, polish ect ect
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed
woudl have been good to list exactly the product you used for each step: clay, polish ect ect...
Leading evidence: 'Use each step: clay, polish ect ect' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'bit of personal preference too' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Use each step: clay, polish ect ect' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that suspect a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suspected cause · Original poster
Fly - I reckon once it's down to choosing between waxes and sealers it's all sweet as in the hard works been done, and probably a bit of personal preference too.
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
bit of personal preference too
No successful repair reported for this finding.
0
Identified cause
1
Suspected cause
0
Reported fixes
Read evidence and context
Discussions that suspect a cause
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suspected cause · Original poster
Fly - I reckon once it's down to choosing between waxes and sealers it's all sweet as in the hard works been done, and probably a bit of personal preference too.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
12 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261027T165639Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I did some paint detailing/correction on my last black 996 which showed some pretty bad swirl marks.
I put together a web page to show some of the defects & improvements along with a few notes for anyone that might be considering trying something similar. I was very pleased with the results (wish I'd figured this out years ago). I'll never be concerned about owning a dark paint colour again.
http://www.oz951.com/public/detailing.htm
nice page.
woudl have been good to list exactly the product you used for each step: clay, polish ect ect... as newbies like me might be tempted but the shopping list is the most annoying part I think,
Real nice job on the write-up. My only comment is I'd do a wax or sealant (depending on the final look/result I'm after) not both. For example, on my 996 I do wax because I want more of a liquid type shine. Since it's not a daily driver, I'm ok with the shorter lasting application of wax. On a DD, I do sealant since I want more protection and it's longer lasting. From a looks perspective, sealant tends to be synthetic looking (plastic looking)....wax produces a more natural look.
I'll add some more detail over the weekend. I think a lot comes down to the combination of products that you can get your hands on at a reasonable price in your part of the world.
Fly - I reckon once it's down to choosing between waxes and sealers it's all sweet as in the hard works been done, and probably a bit of personal preference too.
Good stuff. Did you do any clay bar-ing before the polishing? I do that, and am really happy with the results.
Pretty much, once a year (sometimes twice a year) I: wash, clay bar, wash, dry, polish, seal/wax. Then several times a year, I just: wash, dry, seal.
