I'm not trying to be patronising at all here, it's just the way I come across some times. I just want to make sure we're all on the same page here about how XDF's and defining files work; it might just be the way you worded it.
When you load your bin into whatever editor, be it TunerPro or WinOLS, you need to load in a suitable XDF or .kp to allow the software to understand what data is stored within that file.
Now, the file that you've put into the software is the original bin from your car; which is fantastic. You cannot load in any other bin from any other car, because it does not match. You need to stick with your bin, and your own XDF, which will need padded out due to not one existing. Personally, I'd forget TunerPro and stick with WinOLS because it helps with defining maps not in your current mappack. With the "Connect Windows" button, you can find patterns between binaries to help you further define your file.
So, say your file is a 1.8t ME7.5 file. Load in a fully defined 1.8t ME7.5 file alongside it to allow for the connect windows option to work properly. Now line the windows up (you'll need an offset, which is why using connect windows is good, because it allows you to see patterns between the windows). Do it until your file lines up with the defined file. You can now use WinOLS to transfer the map details across to your file.
At this stage, your mappack has a new map. Your file has NOT been changed. The software just understands what is now stored in that location.
If you're comparing files, you must use similar ones, for obvious reasons.
The Stage 1 threads are good to give an understanding, but don't use the files within them if they're not suitable for your car. The map names are usually consistent though. Furthermore, use the Wiki, and have an A4 notepad beside you at all times for note taking; you'll need it a lot.
The way you worded your original sentence (Found a stg 1 nefmoto xml map created last year in the community project thread above. Imported it into the one I am creating for my current build." makes it look like you've imported a 2.7 xml into your 1.8t file. Correct me if I'm wrong, but that's the way it reads. If that is what you've done, it WILL NOT WORK. You need to suit XML's to their suitable files. That, and the is peculiar to a specific bin (hence my offset things. Although there is 10+ versions of 1.8t files, the data stored within are all at different locations. You can't use one XML for one file on another. They must match.
Probably too wordy, I just won't want you changing data where the XML points to the wrong address, that's all.
