Printable View
Quote:
Originally Posted by RoyN
Had same problem after hibernation.
Also when I closed down FD window from MediaCar PC rebooted.
Couldn't try it this morning as kept getting signal to low message (Heavy cloud cover this morning)
BTW anyway to get rid of that voice prompt, I know how to do it in MapMonkey but there doesn't seem to be so many options in FD?
That's it for now (Oh except occasionally I get a flash of white on the screen (no it is not a speed camera))
The flash of white will be it updating the Cameras on screen, the only way to update the maps is by reloading the maps again ... I believe cdr has done this for speed.
Either that or too much of some thing good lol.Quote:
Originally Posted by UK_MP3Car
Terran
Ergh - thats sick
yeah the screen flash is to update the icons on screen.. I'm working on getting rid of this.. just need to suss out how D3 uses its dat format.. once I manage this.. the screen flash will be a thing of the past :-) Also expect a update in a day or two.. managed to fix a couple of bugs.. I just want to sort a couple of other things I've noticed before the update.
Then things next are
1. Sort out the D3 dat file reading/writing
2. Include online tracking in the next version
its getting there.. with the next update FreeDrive should be very usable.
cheers and thanks for all your support
Steve
CdRsKuLL
I really hope that you'll be able to diable that feature.Quote:
Originally Posted by CdRsKuLL
Yes, I am paranoid ;)
I used 0.6 in the car today and mostly it behaved like it should.
I had a few issues though...
8 / 10 times it was impossible to route to a different address than the one you first entered.
When that happened it simply igored the new route and tried to rout you to the initial
position you had when you first launched FD.
If you loose contact with the GPS (stand-by for example) and then go into
settings >> gps >> and re-activate it again...
The speed/distance isn't updated even though things like heading, lat. / long. are.
Is the warning distance in a fixed format, miles ?
Is it working ? ;) I only got one warning per camera.
Suggestion (long term project perhaps):
Take advantage of heading / direction of the speedcameras.
I know it isn't a five minute job, but you could probably keep your method
of adding cameras/parsing the database and then "just" compare the heading
before issuing the warning.
Heck, it's useful allready !Quote:
its getting there.. with the next update FreeDrive should be very usable.
yep.. will be a simple click in the settings :-)Quote:
Originally Posted by Maximus
Will look into this.. thought I had solved this prob.. just testing some different code now :-)Quote:
I used 0.6 in the car today and mostly it behaved like it should.
I had a few issues though...
8 / 10 times it was impossible to route to a different address than the one you first entered.
When that happened it simply igored the new route and tried to rout you to the initial
position you had when you first launched FD.!
Yep.. sorted this one already :-)Quote:
If you loose contact with the GPS (stand-by for example) and then go into
settings >> gps >> and re-activate it again...
The speed/distance isn't updated even though things like heading, lat. / long. are.!
Will check my code again.. if It was a speed camera and it held a speed for this camera, then it does only warn once.. unless you start going over its limit then it will start bleeping at you, otherwise it will just flash.Quote:
Is the warning distance in a fixed format, miles ?
Is it working ? ;) I only got one warning per camera.!
I understand what your saying here.. say the camera is just past a long bend, then it might cause a problem as you wouldnt be heading directly for it.Quote:
Suggestion (long term project perhaps):
Take advantage of heading / direction of the speedcameras.
I know it isn't a five minute job, but you could probably keep your method
of adding cameras/parsing the database and then "just" compare the heading
before issuing the warning.!
its getting there :-)Quote:
Heck, it's useful allready !
I know its quite buggie at the mo.. but I havent come across a bug I couldnt sort out :-) its just a case of try and try again :-) I am getting better at coding now so this should help with the bugs..
cheers
CdR
m8, how do I donate?
I think you exaggerate the bugs, so they're there, but the program is usful as is and we all know the bugs will be sorted sooner or later so that's fine by me.Quote:
Originally Posted by CdRsKuLL
Never mind the warnings, I just assumed that you haven't had the time to implement the "if the twat is speeding then, and only then, beep" feature :D
About the heading... I gave it some thought earlier and probably the easiest way would be to compare it in a 180 (or something) degree pattern.
Lets say you're heading NW (north west) then you'd get a warning from all cameras facing NE-E-SE-S-SW.
I agree with RoyN ;)
/M
I will be improving the alerts over the next couple of days. I am still trying to understand how D3's dat files are made.. will get there one day.
ok.. small upto, thought Please download this zip file and stick it over 0.60, it will fix the NMEA Parser which would cause FreeDrive to crash in certain conditions.. and yep it will also sort out a routing problem I found on the address bit.. mainly sometimes it didnt list the streets and it would take you to the wrong one.. I can hopefull say I think i've sorted it :-)
grab it
http://www.x-digital.addr.com/FD/FreeDrive.zip
update coming soon.. more sounds for the cams :-)
CdR
o yeah the donate button is on the top right of my site for those that were asking.. and no you dont have to donate to use freedrive.. its FREE