unable to resume valid save in X2120
#1
Posted 25 March 2014 - 01:58 PM
I have been out of the loop for a few weeks and decided to see how far OR has progressed over that time. The gains have been outstanding. However, I decided to resume a valid save that I had generated using X2120. Unfortunately, I am unable to resume anything that I had saved. The following is the error statement that pops up:
System.ArgumentOutOfRangeException: fieldOfView takes a value between 0 and Pi (180 degrees) in radians.
Parameter name: fieldOfView
I should point out that I was able to resume valid saves using X2071 (an indication of how long I've been away from OR).
Thanks for any help on this. I can file a bug report if needed.
Gary
System.ArgumentOutOfRangeException: fieldOfView takes a value between 0 and Pi (180 degrees) in radians.
Parameter name: fieldOfView
I should point out that I was able to resume valid saves using X2071 (an indication of how long I've been away from OR).
Thanks for any help on this. I can file a bug report if needed.
Gary
#2
Posted 25 March 2014 - 02:33 PM
Hi Gary,
I am puzzled by this.
When you upgrade to the next version, all saves should be marked as invalid, so how did you manage to resume one?
Gary54, on 25 March 2014 - 01:58 PM, said:
I should point out that I was able to resume valid saves using X2071 (an indication of how long I've been away from OR).
I am puzzled by this.
When you upgrade to the next version, all saves should be marked as invalid, so how did you manage to resume one?
#3
Posted 25 March 2014 - 02:55 PM
Hi Chris,
I generally keep the most recent versions that I have used available by simply renaming the "open rails" file name (z 2071, for example). Then I install the most recent version of OR (X2120). After failing to resume the saved games in X2120, I deactivated X2120 by renaming its OR file and reactivated X2071. Of course, I deleted the now invalid x2120 saves, started an activity in X2071, saved it, and was then able resume running it without problem. I know, it sounds a bit confusing but it works.
Gary
I generally keep the most recent versions that I have used available by simply renaming the "open rails" file name (z 2071, for example). Then I install the most recent version of OR (X2120). After failing to resume the saved games in X2120, I deactivated X2120 by renaming its OR file and reactivated X2071. Of course, I deleted the now invalid x2120 saves, started an activity in X2071, saved it, and was then able resume running it without problem. I know, it sounds a bit confusing but it works.
Gary
#4
Posted 25 March 2014 - 03:17 PM
I just noticed that Reply #4 under the topic "ORX 2120 Crash" mentions a "System.ArgumentOutOfRangeException: fieldOfView" error that sounds much like the error that I have documented.
Gary
Gary
#5
Posted 25 March 2014 - 09:07 PM
That's what I did with mine to go back to previous download -- X2118 and it's working for me too.
John
John
#6
Posted 26 March 2014 - 12:44 AM
The bug is there, I have just tested it. If you start the game with rel.2120, fiddle a bit with FOV (mouse wheel) and changing cameras, save, and restart with same version, you get the bug. And someone has already posted a bug report in Launchpad.
#7
Posted 26 March 2014 - 01:00 AM
I'd guess the problem is something to do with the order of events when resuming, so the FieldOfView field is not initialised when the first ScreenChange() occurs. I probably won't have time until Friday to fix it, so if anyone else wants a go they're welcome. :search:
#8
Posted 26 March 2014 - 11:54 AM
That's what happens when you save as a float and try to read it as an int... ;)
Here's the patch:
Cameras.cs.patch.zip (349bytes)
Number of downloads: 327
As I am not enabled to commit, I kindly ask someone enabled to do it.
James, I hope that as a reward you remove (or at least move to the top right of the screen and strongly reduce in size) the pop-up showing the FOV value...
Here's the patch:
Cameras.cs.patch.zip (349bytes)
Number of downloads: 327
As I am not enabled to commit, I kindly ask someone enabled to do it.
James, I hope that as a reward you remove (or at least move to the top right of the screen and strongly reduce in size) the pop-up showing the FOV value...
#9
Posted 27 March 2014 - 03:15 AM
#10
Posted 27 March 2014 - 10:04 AM
Should be fixed in X2123. I've also tampered with the notice window, so feedback on that's good too. :unknw: