I'm running on two different windows 7 machines, and finding distance issues on the latest version, never had this problem in the previous versions. When I set up a mineral exploration mission I can drag the flags to wherever I want but when I start the mission their locations shrink and fall inside the settlements zones. They still indicate the original distances ie. 30km for instance, and take just as much time as one would expect, but the flags show on the map within the settlements little circle, and don't check the location they should, they come up with materials at the settlement site.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After some testing I noticed that when I first setup a mission the default waypoint is about 8 degrees north of the base, but as soon as I click on the flag to move it it changes to 0.2 degrees north of the base, and even placing it outside the range circle for the rover it doesn't get past maybe 2 degrees in latitude or longitude. Obviously a math error of some sort happening here. Hoping it can get fixed soon since it makes it basically impossible to make my own missions :(
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank for reporting this bug, yurameki. I was able to confirm it on my linux development laptop. I modified the distance calculation algorithm for 3.02 and I'm guessing this may be related to that somehow. I will investigate this further.
I was able to fix this bug in 3.03 development. The problem affected the mineral exploration, ice/regolith prospecting, and field research panels in the mission creation wizard. These panels were calling the covertRectToSpherical method with the wrong parameters and were not translating pixels on the display to kilometers correctly.
We're expecting the 3.03 release in about two months. If you would like to try an early version of 3.03 that includes this bug fix, I could send you a link.
Scott
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ummm…it's not fixed in that snapshot…I can provide screenshots if you like…biggest change I can get within the rovers range is about 2.3 degrees as opposed to the 8 degrees it starts with…unless the starting math is/was incorrect. Pretty confusing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's strange. Are you sure you're running the program from that snapshot? I just tested it on my Windows 7 system and it appears to create a mineral exploration and a ice prospecting mission with nav points in the correct locations. Perhaps it requires starting a new simulation.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I believe I am having a similar problem. At first it appeared that the AI was making mineral explorations of the same sites over and over again. Then, when I tried to manually set waypoints, the distance from base was considerably shorter than intended. Though the AI's explorations seemed an appropriate distance. This has persisted even after trying the recent snapshot.
I am not running Windows 7, BTW. I am running Windows XP 64-bit.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for confirming the bug, acerm. That's strange though. I just downloaded the 3.03 b1 snapshot from the link above, unzipped it, started it up and created a new simulation. I created a new mineral exploration mission and a new ice prospecting mission and the nav points were correct (both on the mission tool map and the Mars navigator map).
I will create a new beta snap shot and post it on the project web site. I'll post the link when I get it done. I'll remove the previous file when I do this since there's limited space on the web site.
Thanks for the assistance with this bug, yurameki and acerm.
Scott
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This was all solved in that 303 build you redid, but with the new 304 that seems to call itself 302 it seems to be back, so I'm guessing the 304 in the download is not 304...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm running on two different windows 7 machines, and finding distance issues on the latest version, never had this problem in the previous versions. When I set up a mineral exploration mission I can drag the flags to wherever I want but when I start the mission their locations shrink and fall inside the settlements zones. They still indicate the original distances ie. 30km for instance, and take just as much time as one would expect, but the flags show on the map within the settlements little circle, and don't check the location they should, they come up with materials at the settlement site.
After some testing I noticed that when I first setup a mission the default waypoint is about 8 degrees north of the base, but as soon as I click on the flag to move it it changes to 0.2 degrees north of the base, and even placing it outside the range circle for the rover it doesn't get past maybe 2 degrees in latitude or longitude. Obviously a math error of some sort happening here. Hoping it can get fixed soon since it makes it basically impossible to make my own missions :(
Thank for reporting this bug, yurameki. I was able to confirm it on my linux development laptop. I modified the distance calculation algorithm for 3.02 and I'm guessing this may be related to that somehow. I will investigate this further.
I created a bug report for this (#44): https://sourceforge.net/apps/mantisbt/mars-sim/view.php?id=44
Scott
Hope I don't have to wait for the next version for a fix! Unless the next version is coming soon!!
I was able to fix this bug in 3.03 development. The problem affected the mineral exploration, ice/regolith prospecting, and field research panels in the mission creation wizard. These panels were calling the covertRectToSpherical method with the wrong parameters and were not translating pixels on the display to kilometers correctly.
We're expecting the 3.03 release in about two months. If you would like to try an early version of 3.03 that includes this bug fix, I could send you a link.
Scott
I would love to try the early version, that'd be fantastic, thank you.
I uploaded the most recent 3.03 snapshot onto the project website. It's basically version 3.02.1 with bugs #44 & 45 fixed.
http://mars-sim.sf.net/download/beta/MarsProject_3.03b1.zip
Please let me know if you have any troubles with the beta. I may upload further betas in the future and replace this file.
Thanks for the bug report!
Ummm…it's not fixed in that snapshot…I can provide screenshots if you like…biggest change I can get within the rovers range is about 2.3 degrees as opposed to the 8 degrees it starts with…unless the starting math is/was incorrect. Pretty confusing.
definitely shrinks them down to the inside the base points again…
That's strange. Are you sure you're running the program from that snapshot? I just tested it on my Windows 7 system and it appears to create a mineral exploration and a ice prospecting mission with nav points in the correct locations. Perhaps it requires starting a new simulation.
I believe I am having a similar problem. At first it appeared that the AI was making mineral explorations of the same sites over and over again. Then, when I tried to manually set waypoints, the distance from base was considerably shorter than intended. Though the AI's explorations seemed an appropriate distance. This has persisted even after trying the recent snapshot.
I am not running Windows 7, BTW. I am running Windows XP 64-bit.
Thanks for confirming the bug, acerm. That's strange though. I just downloaded the 3.03 b1 snapshot from the link above, unzipped it, started it up and created a new simulation. I created a new mineral exploration mission and a new ice prospecting mission and the nav points were correct (both on the mission tool map and the Mars navigator map).
I will create a new beta snap shot and post it on the project web site. I'll post the link when I get it done. I'll remove the previous file when I do this since there's limited space on the web site.
Thanks for the assistance with this bug, yurameki and acerm.
Scott
I uploaded a new 3.03 beta with the most recent code onto the project website:
http://mars-sim.sf.net/download/beta/MarsProject_3.03b2.zip
I removed the previous beta.
Please let me know if you're still seeing the distance problem in this beta.
Thanks for your help.
Scott
This was all solved in that 303 build you redid, but with the new 304 that seems to call itself 302 it seems to be back, so I'm guessing the 304 in the download is not 304...
I think you're correct. Something is wrong with the 3.04 release download you're using. Somehow it's using version 3.02 code.
I'm not aware of any distance problems that have cropped up again after they were fixed in version 3.03. Thanks for the help with that.
Scott
Is there a solution to get the 304 build?