Eh, no worries. I should have left it be, since you were already in there.

 

Nice ... someone added my tutorial from way back when ... now I've got to finish it! Damn you ...

Great work on the Wiki guys.

 

How about acronym in Wiki? Good ref for noob? eg: afr, tbe, ait, iac, etc...

 

Go for it, add it to the wiki with a link of the main page for a glossery,

 

I think I'd add but unsure how to link it to the main page. Can someone see them? I can see mine when I client "Recent Change".

 

Hey, I added a link to the main page and moved the glossary over to a new paged called glossary. It was created in your private user section.

To create a new page, you simply type in the URL for the page you want to create. If you want a glossary page, you simply replace the word Main Page with Glossary and then it will allow you to create that page.

Check out the main page again, there is now a link for the glossary. Nice work by the way, that should be helpful for new users. If you get some time, how about expanded some of the more complicated terms to include short definitions so that new users can learn more about what each term really means.

 

FYI, for help on how-to wiki (since the converters aren't always clean or easy) you can simply click help or click the little "powered by mediawiki" link on the bottom right and view their help section.

For reference, there's here's a few direct links:
http://www.mediawiki.org/wiki/Help:Editing_pages
http://www.mediawiki.org/wiki/Help:Starting_a_new_page
http://www.mediawiki.org/wiki/Help:Formatting


These show you how to create a new page and how-to just about anything for the n00bs

 

Awesome work guys, helpfull to the whole community .

 

Added this section:

http://evoecu.logic.net/wiki/Patching#Pre-Patched_ROMs

Let me know if you want me to move it around or feel free to do so yourself. Also, I'm not sure I properly linked the zip files. Someone please fix them if they will result in broken links.

 

Thanks for adding that.....the is the final step in building the wiki into the ultimate resource.
Do you happen to have matching EvoScan files by chance?

Or really just one EvoScan file with all of the loggable paramaters. If we included one evoscan file with all of the paramaters the end user could choose what to log. For example there is no harm including an entry for JDM map, and if the user doesn't have a JDM map he simply will not log that paramater

 

here is the download section

http://evoecu.logic.net/wiki/Downloads

 

I never wound up doing it because in 2.5 there are already the three 2 byte entries as well as MAP (full range) and JDM MAP. Might not hurt for the guys using older evoscan versions, but I didn't know if the defs file could break anything in their program... so if they updated to 2.5 they would have it anyway.

Not sure if 2.5 has the correct wgdc error though, I could add that.

Were the zip files linked properly? I linked them as an external link as ...did not seem to work. I don't want the links to break though if someone updates the file.

---
Also, if anyone updates those it might be a good idea to change the date created section in the readme to a revision history. Even though there will be a place for it on the upload itself people rarely seem to look there.

 

Also I think we should delete the text files in the zip (other than readme) It seems redundant as it tells you to copy everything over, but you have already done all of that.

 

What about adding an entry for the 1byte load value now used in tephra v 5.10
and also boost related entires for direct boost control.
What are some other things people might want to log?
Clutch switch position? Alt Map voltage?
I'm just thinking here.

We should be able to make one evoscan file that will work for all 885900105 roms


I have fixed the download links. Now all you need to do is upload a new file and the link will still work.

 

I guess the only problem with alt-map voltage/activation (aside from my current issue with getting it to work, see 5.0 thread) is that its pretty much a 1 time deal and you are out. I don't think theres a good standard MUT for it, and its kind of pointless to have it take 1 or 2 up forever.

Didn't know there was a clutch switch position value, that could be helpful. the 1 byte is also a good idea (with a note to modify it but a standard value).