|
Notes |
|
|
|
|
Please, try latest nightly version. And use Debug version for reproduce this bug. After crash attach *.elf file. |
|
|
|
|
|
I switched to nightly, downloaded a 7z file. I opened it but cannot figure out what to do with the contents. Please explain. |
|
|
|
|
|
Save all files with replacement to SAS folder and run SASPlanet.Debug.exe |
|
|
|
|
I extracted the files an copied all to the SAS folder. After that nothing worked anymore.
I then tried to uninstall the software but couldn't find it in the list of programs to uninstall. So then I deleted the SAS folder.
I will now try to reinstall.
Sorry I haven't used Windows since 2007. I bought a Windows computer especially for your SAS planet software but this Windows 10 is, well, impossible to use. |
|
|
|
|
When I copy the nightly files to the SASPlanet folder then (1) SASPlanet will not run anymore and (2) the debug.exe also does not run.
When I try to execute any of the exe files in only the nightly file folder then nothing happens.
In both cases I get a message "The file or directory is corrupted and unreadable"
So now SASPlanet still does not support my Garmin GPS18x USB.
Also the Google and Bing satellite images are not displayed properly (very very low resolution only). |
|
|
|
(0018082)
|
|
zed
|
|
15-10-2017 10:01
|
|
|
Create new empty folder and use 7zip to unpack archive to it. Then run SASPlanet.NonUnicode.Debug.exe, reproduce error, close SAS, find SASPlanet.NonUnicode.Debug.elf file with error log and attach it to this issue. |
|
|
|
|
Thanks the debug file actually runs without the problems I described.
However I did notice the following problems:
1. The GPS positions me about 60 m south of where I really am on the Google sat image.
2. The GPS speed shows unrealistically high values. |
|
|
|
|
In the regular SASPlanet app I just updated the google version number to 745. But I am right away again getting the floating point errors.
SEE ATTACHED PNG file |
|
|
|
(0018085)
|
|
zed
|
|
15-10-2017 11:37
|
|
|
What about time? It shows correct value? |
|
|
|
|
The debug version shows a local time anywhere between 03:08 and 03:45
The "stable" version shows similar local time.
For both the UTC time shown is 20:08 - 20:45
The local time here (Jakarta) is 18:45
(Sorry my computer clock was set to Singapore before, 1 hour later. I just fixed that) |
|
|
|
(0018087)
|
|
zed
|
|
15-10-2017 11:52
|
|
Try this exe: https://yadi.sk/d/FRYuORmy3NmG75 It should print more information about error.
Put SASPlanet.3276.exe to folder with nightly build and run. Log will be named as SASPlanet.3276.elf.
|
|
|
|
|
This showed same behaviour as the debug version.
UTC time varied between 20:49 and 21:24
Local time varied between 03:49 and 04:24
Actual local time is 19:23 |
|
|
|
(0018089)
|
|
zed
|
|
15-10-2017 12:34
|
|
|
I don't see error in attached log. Do you reproduce it? Can you take screenshot with error message? |
|
|
|
|
Correct, the debug version shows no floating point errors but the "stable" version does.
The debug version does show an incorrect local and UTC time, even though the GPS pinned my location correctly. |
|
|
|
(0018098)
|
|
zed
|
17-10-2017 19:27
(edited on: 17-10-2017 19:32) |
|
Your first log (SASPlanet.NonUnicode.Debug.elf) has error:
EConvertError: 14722840.71 Julian cannot be represented as a DateTime.
Try to reproduce this error with SASPlanet.3276.exe. I need to know, why this error happened. It maybe because of invalid time value or bug in SunCalc library.
And forget about the "stable" version. It's outdated. Use latest nightly build - it's more stable then last release. If nightly version works fine, without "floating point error", then here is nothing to do - bug was somehow fixed.
Incorrect time is an another issue and you should open a new one ticket.
|
|
|
|
|
|
Sorry for late reply. Yes I will report the time issue as a separate ticket. Thanks for your assistance. |
|
SASPlanet.NonUnicode.Debug.elf (185,856) 15-10-2017 11:09
floating point error.png (4,363,376) 15-10-2017 11:25