If you're having so much trouble finding the proper co-ords in T-Search; I know why...
If you type "showfps 1" into the console; you'll get a floating point approximation; meaning that the EXACT value is rounded to 1 decimal place. If you try searching for the EXACT floating point value XXX.X; you won't get any hits; because it's actually XXX.XXXXXX etc.
So how did I find it? Well, I originally thought; I'll search for a RANGE between the values "showfps 1" displays. Lets say "showfps 1" claims your x position is 19.6; It would make sense to search for any floating point values between 19.5 -> 19.7
I found that, T-search has a subtle bug- in that it doesn't correctly display floating point value ranges. When I eventually found the 19.6XXXX value; it still didn't show up when a did a floating point range search 19.5 -> 19.7 .
So, perhaps the best way to do it- is locate the z coord first; (eg, direction towards the sky). It'll take patience, but pick a map with a huge slope (like the start of NVA base on US team). Firstly, search for Unknown; then use a combination of search next'ing for "Value has increased" when you've increase your altitude - and correspondingly, "Value has decreased" for decreased altitude etc. Repeat this process over and over until you've got just over a hundred hits... lol... You can either lock them individually- switch back to the game- and see if you're direction is "locked" in a certain direction (eg. when you jump- something weird happens), or change the values; and see if you end up somewhere different (eg teleport)... (I'd advise simply locking them if you're not sure, though).
When you've got just 1 co-ordinate in DMA, you're set. Other 2 (for x and y in this case) are 4 bytes in either the + or - direction; can't remember exactly.
Try to find static pointers to these addresses using the T-Search debugger, so you don't have to fiddle around with DMA every time.