I completly read the article without skipping any words…
Everyone knew the tages reading wasn’t the problem. I already had dumped duplicates sectors myself using the truman xperimental tools long time ago…
What i cant still understand, it’s why spath using that particular “twin sectors” insertions pattern will all theses cryptic ratio and only 50-100 dup sectors.
(I understand he had no choice to reduce the dup sector count numbers because of laser travel distance restrictions between normal sector and duplicate sector)
But why using this particular duplicate sector format disposal ?
(This might work for now, but if tages SA decide to update their drivers or sequence auth over a next game update, this could probably wont work anymore with only a 50 sectors subset!!)
This is the pattern “spath” using to write :
Sector A = Normal Sector Sector B = Duplicate Sector number of A And where Sector Bi is a duplicate of sector Ai but might containt different data. ----SECTOR A----- ----SECTOR B----- [A1A2A3A4...A50] - [B1B2B4B4...B50] There's an important travel lenght between A1-B1, and that's why spath need to keep distance as short as possible by removing some "optionals" duplicates sectors. === My question is why writing only a subset of duplicates sectors when we could write all of them to make it more robust? Why can't we use that pattern instead to write :
Where Sector Ai is a duplicate of sector Bi.
All Sectors are very nearby of it’s normal equivalent… So there’s no lenght problems…
We have 50% of chance of hitting the normal or duplicate one
over a direct seek…
Any idea ? Red/Orange book Issues ?