<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.speedsolving.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Clincher</id>
	<title>Speedsolving.com Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.speedsolving.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Clincher"/>
	<link rel="alternate" type="text/html" href="https://www.speedsolving.com/wiki/index.php/Special:Contributions/Clincher"/>
	<updated>2026-10-30T20:44:31Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.8</generator>
	<entry>
		<id>https://www.speedsolving.com/wiki/index.php?title=Advanced_techniques_for_Roux&amp;diff=16870</id>
		<title>Advanced techniques for Roux</title>
		<link rel="alternate" type="text/html" href="https://www.speedsolving.com/wiki/index.php?title=Advanced_techniques_for_Roux&amp;diff=16870"/>
		<updated>2012-01-03T18:04:26Z</updated>

		<summary type="html">&lt;p&gt;Clincher: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Blockbuilding =&lt;br /&gt;
There are a couple of techniques which come to mind for improving you blockbuilding and influencing later steps and such.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Influencing the second block&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Influencing the second block during the first block may not sound very specific or important, but it&#039;s crucial to get your times as low as possible. Here are a few cases, experiment with them, then make some of your own:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Making the second block not too inefficient&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The second block in Roux is usually where we all get frustrated with high movecount, and feel there&#039;s not much to do about it- some cases for the second block are really annoying. You can try to apply [[Multi-slotting]] to reduce cases. There also are many cases where it may look like it&#039;ll take many moves, but it won&#039;t. Here are some cases which may not be immediately apparent in solving.&lt;br /&gt;
&lt;br /&gt;
= Corners =&lt;br /&gt;
KCLL is what comes to mind here. It is basically influencing edge orientation while solving the U corners. Notice it&#039;s not necessarily &#039;&#039;&#039;solving&#039;&#039;&#039; EO, but influencing it. Sometimes solving EO may be more trouble than just influencing, say, a 4 flip then simply doing M&#039;UM&#039;. This is why it helps to know multiple algs for each case.&lt;br /&gt;
&lt;br /&gt;
You can change EO by just inserting a slice move before an alg. A very obvious case is if you got a Sune case with UF and UR flipped. If you insert the M&#039; before it, to make r U R&#039; U R U2 r&#039;, you flip the edges, with literally no extra moves. This comes in handy as some EO cases take many moves to execute, like 2 flips or the 6-flip.&lt;br /&gt;
&lt;br /&gt;
[[OLLCP]] can be applied here too. And if DF and DB are oriented you can solve Eo easily during CMLL.&lt;br /&gt;
&lt;br /&gt;
= LSE =&lt;br /&gt;
&#039;&#039;&#039;Non-matching centres: allowing free centre orienation from the beginning of LSE&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
You were always told to orient your centres first before doing EO. But sometimes, it&#039;s useful NOT to, or to make centres free. You see, an edge that is not an L/R edge is oriented if it has the same orientation as the centres. Whilst the L/R edges will be oriented if you have your U/D colour on top/bottom. So this leads to some fun...&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Non-matching centres: misorienting centres to ease EO&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Here it&#039;s different. You orient your centres beforehand but then use the property to your advantage to ease EO. Just look at these tasty moos:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:visualcube.png]] Orientation for this is just M, how delightful!&lt;br /&gt;
&lt;br /&gt;
Orientation for this is just M&#039;/M.&lt;br /&gt;
&lt;br /&gt;
{{stub}}&lt;/div&gt;</summary>
		<author><name>Clincher</name></author>
	</entry>
</feed>