|
 |
|
07-01-2005, 03:51 PM
|
#1
|
|
Variable Bitrate
Join Date: Dec 2004
Posts: 295
|
iGuidance 2.1 3D Crash
Title says it all, as soon as I put iG 2.1 into 3D mode is crashes unmercifully. This only happens on my EPIA, not on my VAIO laptop. Has anyone experienced this? I'm going to guess its a DirectX issue.
|
|
|
|
|
|
Advertisement
|
Sponsored links
|
|
09-10-2005, 01:13 PM
|
#2
|
|
Variable Bitrate
Join Date: Dec 2004
Posts: 295
|
No one else has seen this problem?
|
|
|
|
|
09-11-2005, 12:08 AM
|
#3
|
|
Variable Bitrate
Join Date: May 2005
Location: Crappy Bangor, Maine
Posts: 328
|
nope
|
|
|
|
|
09-11-2005, 12:20 AM
|
#4
|
|
My Village Called
Join Date: Jul 2004
Location: Berkeley, CA
Posts: 10,517
|
Nope.
BTW: iG does not use DirectX.
|
|
|
|
|
09-11-2005, 12:26 AM
|
#5
|
|
Variable Bitrate
Join Date: Dec 2004
Posts: 295
|
I discovered tonight that the same thing happens with iGuidance 2.0. I would think if it was any kind of EPIA driver issue, someone else would have the same problem.
What the hell...
|
|
|
|
|
09-11-2005, 12:34 AM
|
#6
|
|
My Village Called
Join Date: Jul 2004
Location: Berkeley, CA
Posts: 10,517
|
Reinstall windows.
|
|
|
|
|
09-11-2005, 07:57 AM
|
#7
|
|
Maximum Bitrate
Join Date: Apr 2004
Posts: 497
|
I'm running a VIA and IG 2.0 but it never crashes on me in 3d mode or any other mode. I do have the newest drivers from via though
|
|
|
|
|
09-11-2005, 08:07 AM
|
#8
|
|
Variable Bitrate
Join Date: Apr 2004
Location: Tampa, Florida
Posts: 284
|
Quote: Originally Posted by 0l33l
Reinstall windows.
Dito
|
|
|
|
|
Sponsored links
|
|
Advertisement
|
|
|
09-11-2005, 01:05 PM
|
#9
|
|
Variable Bitrate
Join Date: Dec 2004
Posts: 295
|
Doesn't seem like a very good solution to me.
Sadly, it would probably do the trick.
|
|
|
|
|
09-20-2005, 08:58 PM
|
#10
|
|
Variable Bitrate
Join Date: Dec 2004
Posts: 295
|
Reinstall windows...works fine...put PC in car, connect to GPS, starts crashing again. Change GPS, same. Test RAM, fine. Change com ports, no change. Remove GPS entirely, no change. Remove/reinstall has no effect. Crashes if its in 3D mode instantly, every time. Otherwise crashes randomly when routing.
What the hell??????
|
|
|
|
|
09-20-2005, 09:03 PM
|
#11
|
|
Maximum Bitrate
Join Date: Apr 2004
Posts: 497
|
Did you install all the device drivers?
|
|
|
|
|
09-20-2005, 09:07 PM
|
#12
|
|
FLAC
Join Date: Jun 2005
Location: Anoka County, MN
Posts: 1,021
|
Your using a full install of windows right? Not one of those crippled optomized versions?
|
|
|
|
|
09-20-2005, 09:25 PM
|
#13
|
|
Variable Bitrate
Join Date: Dec 2004
Posts: 295
|
No, nLite sucks. Full windows. I'm not trying to be a dick, but please realize that it WORKS FINE up until a certain point...more information on that here:
I can re-create the situation, and now FIX it 100% of the time? The fix? Delete the LastHead, LastLat, or LastLon registry keys. If these are deleted, iGuidance launches and/or switches into 3D mode with no problem. Obviously this is with the com port set to the wrong port (port the GPS is not on). Now, as soon as I change the com port to the correct port (basically LastHead, LastLat, and LastLon get written) CRASH. Instant crash. Like I said, I can re-create this situation 100% of the time.
Before you say its the GPS, I've tried a different one, and it gives perfect NMEA data that works just fine in 2D mode (until the random routing crashes). The problem is not the GPS, serial, or the NMEA strings.
And yes, I installed the god damn device drivers.
I am ready to flip out.
|
|
|
|
|
09-20-2005, 09:48 PM
|
#14
|
|
FLAC
Join Date: Jun 2005
Location: Anoka County, MN
Posts: 1,021
|
Don't mean to be an ***, but if its crashing when writing to the registry, does it have access too? I mean you are running it as administrator, right? (I don't see why you wouldn't but its hard for me to think of other reasons why it behaves like it is)
|
|
|
|
|
09-20-2005, 09:53 PM
|
#15
|
|
Variable Bitrate
Join Date: Dec 2004
Posts: 295
|
Yeah, its not like a user permissions problem. Keep in mind I'm not suggesting that it crashes when actually writing the registry key, I'm just saying thats when it happens. Much more likely is that some code for calculating position is vomiting. Perhaps a routine that is only called when drawing the cursor on the screen when in 3D mode.
By the way, creating the registry key ShowWarning and setting it to 0 is a much better way to get rid of the iGuidance nag screen.
|
|
|
|
|
Sponsored links
|
|
Advertisement
|
|
| Thread Tools |
|
|
| Display Modes |
 Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 01:48 PM.
| |
