Topic on Talk:Final Fantasy XIII

Just a heads up that this edit was just meant to make it so that the guide was linked directly in the fix instead of as a reference, not a revert. The fix template doesn't like direct links in the main header, so I basically took a trimmed version of my old explanation and give the long one below. BONKERS completely replaced it previously, as it was a bit too general by itself. Hopefully it's technically accurate (guide version is still below).

The eventual goal is to move some version of it back to essential improvements (unless Square fixes it by then...... yes, you can stop laughing now) after I digest what BONKERS has told me and the related information and turn that into something coherent. Long story short and incomplete it's a Fermi+ fix and doesn't appear on the XXXX line, and may be strictly a Fermi+ issue (4XX on).

P.S. originally the page was NVIDIA, so I changed those occurrences to be all caps. It seems inconsistent everywhere, especially on the articles here, but I think the correct spelling is Nvidia?

The linking feature can be disabled by adding the link=false parameter to the template; I'm personally of the opinion that the link function should be removed entirely because of this sort of problem.

EDIT: Nvidia use all caps to emphasise the brand (many companies do this); writing it as Nvidia is fine (Wikipedia does this) since it's not an acronym or special casing (unlike GeForce). This wiki currently has no standard in this area.

Thanks. For some reason I could get it to work with the NVIDIA Inspector link but not the guide link - it would always turn all the text to "

{{1}}

" with the Guru3D forum guide link. I tried doing raw HTML and it worked that way (but later did a reorg of the page so I wouldn't have to), and it seems to be the Anchor template that it's wrapped in that's causing issues.

Also went the Wikipedia format for Nvidia, as that what incoming edits were using.

If a link has an equals sign in it (as with the Guru3D forums) you'll have to specify the number for the template parameter (like {{Fixbox/fix|1=Some description}}) otherwise the equals sign in the link will be interpreted as a parameter.

The fixbox linking feature has been removed so that aspect isn't an issue now.

EDIT2: OK, I understand the other problem here.

Interesting. Yes, it does work with the 1=, but still bugs out without it. I'd say that was intended if the other link didn't work either.

It seems like the arguments are being passed correctly from the fix template, but the anchor template itself doesn't like it without the 1=? Take

{{Anchor|Follow [http://forums.guru3d.com/showpost.php?p=4936011&postcount=2444 this guide] under}}

Which gives: {{{1}}}

Now take:

{{Anchor|1=Follow [http://forums.guru3d.com/showpost.php?p=4936011&postcount=2444 this guide] under}}

Which gives: Follow this guide under
---

Currently all the anchor template is:

<span id="{{{2|{{{1}}}}}}">{{{1}}}</span>

It's literally including the entirety of the fixbox header as a span id for the anchor since we aren't passing a second argument to T:Anchor through T:Fixbox (I find this incredibly wasteful now that I think about it...). However, if there's a quotation mark in the anchor header (with or without 1=) it just puts an empty span tag there instead that I assume is put there by the wiki parser (I assume the intention was anchor fixbox headers, but having to anchor and reference it using the fixbox header text that useful?).

Quoation example:

{{Anchor|Quotation "killed" the span id}}

Which gives (note no span id): Quotation "killed" the span id

Which kills the span id in the full sentence, which made this response turn out weird before edits (again, no span id): Follow this guide under the section "GeDoSaTo Setup" to create a driver profile for Final Fantasy XIII and enable the "AntiAliasing Fix" to fix block like artifacts on character hair

The equals sign and quotation mark behaviour are technical limitations of MediaWiki.

I've removed the anchor feature from this template since it is also a remnant of the unused fixbox linking capability.

Ah, I had to experiment a lot to get the text/links to be presentable at all. I was wondering why I couldn't fixbox with a text link. Sorry, had to try and work around that. The way MPM did it now, works very well I think. Better than what I could come up with I suppose.

Though I still think there should be a link to the video, I'm just nitpicking I guess. Especially since my post on Guru3D has the video linked twice!

Considering you are already linking the solution in your Guru3D post..
why not "porting" the instructions here?

And if it's too much for a fluent reading, well... it may be time for a dedicated GeDoSaTo article then

It is quite a wall of text. The guide itself has a lot of links and what not too.

Dunno.

IMO it's high time for an article on GeDoSaTo in general considering its wide and flexible support now.

Still waiting ^^