Thread: Digital FX 2.0 Transparent Released

I just upgraded to 2.0 transparent. I've been running the old one for MONTHS. New one kicks *** but i noticed that i had to use the roadrunner.exe that is included in this thread. Once i use that my volume settings are all messed up. When i go into RR the volume changes to 100% and I cant adjust the volume up or down unless i first hit MUTE then UNMUTE. and when i change the volume its at weird percentages...I am use to 1-10% going up in increments of 1% then 10-100 in 5% increaments.

I've noticed the new Roadrunner.exe in this thread is about 2.4mb but the most current roadrunner.exe issued from the creator is much much smaller. Whats the difference?

Never had any issues before I upgraded. THe new skin works great just sound issues.

Originally Posted by meisner

OK, I just finished modifying the 8+ MB file to add the leading '0'. I used Wordpad and just let it sit for ~30 minutes while I did something else. It managed to finish!

Here's wiredwrx's file with the additional '0' on the 2nd coordinate. This is one big file (over 8MB when unzipped).

Enjoy!

Damn...it was just pointed out to me that there are still some errors in the file I posted. I searched and replaced all occurances of ","-with ","-0

This works fine for the entries that had only 2 digits for the longitude. I didn't notice that some entries already had 3 digits. Mike is updating the database again.

Sorry for the bad version guys. But it is a step closer.

I also modified the 8 meg file with all the correct digits and did a thirty minute drive through a couple of small towns to confirm that it all works. I did notice that sometimes it doesn't change when it's supposed to. For example, I drove through one small town called Midland and it didn't change from the previous town. Then when I drove back through Midland in the other direction, it did change to Midland. I don't know what that's all about.

Wiredwrx and Meisner, I also discovered that we needed to leave the coordinates with three digits alone. I'm assuming that the file posted above and mine are now identical, so I won't bother to post mine.

Anyway, I have verified that the large size of the file will not keep it from working, at least on faster computers. It does appear that the new file is more accurate than the one we've all been using, so Wiredwrx should be commended for his hard work in putting the new one together. Wiredwrx, I believe other skins may be using this functionality as well, so you may want to make the updated available elsewhere. Perhaps you should post a new thread with a link to the download.

Correct me if I am wrong here, but I believe the way this works is the dat file has coordinates that designate the center of a circle. The dat file dictates the details of the city this circle encompasses. So there will be some errors here and there since cities are not round.

Also, you may have seen a problem due to the update interval (localdatacaptureinterval=1). If this is set higher (or you made it thru Midland in < 1 minute), you may have missed that update.

Originally Posted by meisner

Correct me if I am wrong here, but I believe the way this works is the dat file has coordinates that designate the center of a circle. The dat file dictates the details of the city this circle encompasses. So there will be some errors here and there since cities are not round.

That's my understanding as well.

Originally Posted by meisner

Also, you may have seen a problem due to the update interval (localdatacaptureinterval=1). If this is set higher (or you made it thru Midland in < 1 minute), you may have missed that update.

That makes sense.

Originally Posted by JohnWPB

Wow, this Database seems a difficult and uncooperative one to get right

Florida still does not work, as well as Tennessee, Michigan, Ohio, Indiana & possibly some other states.

Looking at the zips.dat, the the above mentioned states, the line looks like the following:


The highlighted area above is the problem. Looks like the search and replace did not work correctly with these states, and turned out putting double coma's.

The error is in the original file posted by Wiredwrx; it was not a search and replace error. I don't think double commas appear anywhere else, so a search and replace should take care of it.