Who has iGuidance 2.1?

voidunknown · 05-09-2005, 12:34 PM

Thinking of going from iGuidance 2.0 to 2.1. Would this be a good idea, or should i save my money? Are there really ANY differences you notice in iGuidance 2.1? One thing I really don't like is the screen is so damn jerky in 3D mode. Other programs like TomTom have a nice smooth 3D mode. Any 3D improvments in 2.1? Thanks for the input!

Fizzle · 05-09-2005, 01:06 PM

While I didn't have 2.0 to compare to, I can say the screen is jerky in 3D Mode in 2.1. I don't know if it's improved however.

0l33l · 05-09-2005, 01:07 PM

v2.1 won't work with a few apps because it uses different window names. When I get it, that will be fixed.

Marvin Hlavac · 05-09-2005, 04:44 PM

If you compare the current iGuidance 2.1 or the previous versions to application like TomTom, then yes, you can say iGuidance is "jerky". TomTom is so "smooth" because it refreshes the screen 4 times per second as opposed to most other current software which does the same only once per one second. (The GPS itself gives new position still only once per second, even in TomTom, so this is just a software thing.)

Upgrade or not upgrade from 2.0 to 2.1? That's a hard question. If you live in Canada, then it may be a must to upgrade, because 2.1 is the first version that has a street level coverage of the whole country (even little towns). But other that that you should perhaps be aware that the famous THEME.INI file which let people customize GUI will not work in 2.1. There may be a new theme.ini released for 2.1, though.

Here is a very brief "What's New in 2.1": http://www.gpspassion.com/fr/articles.asp?id=137&page=6

voidunknown · 05-09-2005, 04:51 PM

Quote: Originally Posted by Marvin Hlavac

If you compare the current iGuidance 2.1 or the previous versions to application like TomTom, then yes, you can say iGuidance is "jerky". TomTom is so "smooth" because it refreshes the screen 4 times per second as opposed to most other current software which does the same only once per one second. (The GPS itself gives new position still only once per second, even in TomTom, so this is just a software thing.)

Upgrade or not upgrade from 2.0 to 2.1? That's a hard question. If you live in Canada, then it may be a must to upgrade, because 2.1 is the first version that has a street level coverage of the whole country (even little towns). But other that that you should perhaps be aware that the famous THEME.INI file which let people customize GUI will not work in 2.1. There may be a new theme.ini released for 2.1, though.

Here is a very brief "What's New in 2.1": http://www.gpspassion.com/fr/articles.asp?id=137&page=6

I have never used the Theme.ini file. What's can you do with it?

MatchStick · 05-09-2005, 04:54 PM

Quote: Originally Posted by Marvin Hlavac

If you compare the current iGuidance 2.1 or the previous versions to application like TomTom, then yes, you can say iGuidance is "jerky". TomTom is so "smooth" because it refreshes the screen 4 times per second as opposed to most other current software which does the same only once per one second. (The GPS itself gives new position still only once per second, even in TomTom, so this is just a software thing.)

Can we hack it to refresh more often?

voidunknown · 05-09-2005, 04:57 PM

Quote: Originally Posted by MatchStick

Can we hack it to refresh more often?

Excellent Idea!

maxxell · 05-09-2005, 05:00 PM

Theme.ini allowed v2.0 users to change what they wanted in iGuidance. Street name sizes, colors of just about anything. A LOT of freedom. Between theme.ini and reshacker, there is very little about the GUI you couldn't change. Now v2.1 doesn't allow theme.ini, so that's out the door.
Nice work, inav.

lastberserker · 05-09-2005, 05:11 PM

Quote: Originally Posted by maxxell

Theme.ini allowed v2.0 users to change what they wanted in iGuidance. Street name sizes, colors of just about anything. A LOT of freedom. Between theme.ini and reshacker, there is very little about the GUI you couldn't change. Now v2.1 doesn't allow theme.ini, so that's out the door.
Nice work, inav.

That's it, I'm waiting for 2.2 then!

Marvin Hlavac · 05-09-2005, 05:24 PM

;-) Last time I heard they were working on version 2.1.1

Marvin Hlavac · 05-09-2005, 07:28 PM

Quote: Originally Posted by maxxell

...Now v2.1 doesn't allow theme.ini

Well, to be technically correct, I wouldn't say the new 2.1 doesn't "allow" it. I'm sure the 2.1 is ready for doing the same (or more) if a proper *.ini is introduced. It is just that the old theme.ini is not working in the new 2.1, and that users like us haven't figured out on our own yet how to modify it to work in the 2.1.

Hopefully the developer of the software will make a new *.ini file available so we can have some more fun again ;-)

lastberserker · 05-09-2005, 07:45 PM

Quote: Originally Posted by Marvin Hlavac

;-) Last time I heard they were working on version 2.1.1

Yeah, sure

How many minor (i.e. free) updated did they issue before asking folks to shell out some greens for 2.0 -> 2.1 upgrade?

Wiredwrx · 05-16-2005, 07:13 PM

Quote: Originally Posted by Marvin Hlavac

Well, to be technically correct, I wouldn't say the new 2.1 doesn't "allow" it. I'm sure the 2.1 is ready for doing the same (or more) if a proper *.ini is introduced. It is just that the old theme.ini is not working in the new 2.1, and that users like us haven't figured out on our own yet how to modify it to work in the 2.1.

Hopefully the developer of the software will make a new *.ini file available so we can have some more fun again ;-)

Actually, some one contacted INAVCORP regarding theme.ini and version 2.1,and they specifically said that it is not supported. You can find the post in the "IG Font is killing me......" thread

Michael

Marvin Hlavac · 05-16-2005, 08:23 PM

Okay, it does seem to work (finally). I've been playing with it for a few moments now... Rename the file to ctheme.ini ;-) It does seem to work in 2.1 ;-)

maxxell · 05-17-2005, 12:00 AM

How on earth did you figure that out, Marvin?