New CabView then Resume not a bug but something that occurs
#1
Posted 05 October 2014 - 06:35 PM
It is easily remedied by switching to any outside view (headout, camera 2, etc.) and then switching back to camera 1 (CabView).
An activity is saved. Between the save and resume the cabview is changed. When the activity is resumed all three views are looking downward at the tracks. Going to any "outside of the cab" camera will reset the views to straight ahead when the cabview is re-entered.
Not a big deal - just something that occurs. Does is seem a good idea to fix this? Is it easy to fix without bringing on a lot of other headaches/troubles/coding problems? Anyone else notice this?
See Screenshots - Cab1 is cabview at time of save; Cabs2,3,4 are downward looking views after changing cabview and resuming. CAB5 shot is corrected view after reset (any outside camera)
(I had not brought it up before because my initial reaction was "well what do you expect when you change something and then try to restart" I don't know what would happen in MSTS - did it ignore, crash or what?)
#2
Posted 06 October 2014 - 12:18 AM
#3
Posted 06 October 2014 - 01:43 AM
#4
Posted 06 October 2014 - 01:23 PM
To make myself clear .... you have to save while in the cabview, exit OR, change player's cvf to another working cabview, resume and the cabview will be oriented downward. Switch to any outside camera and then back to cabview and the orientation is straight ahead. I wonder if it could be cabview specific?
The two examples above are:
1st screenshot: GE-U23B-EW-CR-AS.cvf (cabview folder name: Common.Cab//SHR.CABS//GE-STD-7-CAB [Charlie Sibaja]
2,3,4 screenshots: sd40_CR.cvf (cabview folder name: Common.Cab\\CABVIEW_EMD_STANDARD_DIGITAL [Brad Bailey] and #5 after switching to outside view and reentering cabview - oriented correctly
Attached File(s)
-
OpenRailsLog.txt (15.33K)
Number of downloads: 172
#5
Posted 31 October 2014 - 09:29 AM
On a broader note, I think some attention to the Save/Resume code is likely in order. It seems that some things that work in the initial startup (AI smoke of late, for example) may not work in a resume game.
As always, I appreciate the hard work of the OR development team. Despite any such "irritations" as I described above, OR is such a HUGE improvement over MSTS that OR's relatively few issues are far, far outweighed by its many fine features.
#6
Posted 31 October 2014 - 12:40 PM
#7
Posted 01 November 2014 - 05:49 AM
railguy, on 31 October 2014 - 09:29 AM, said:
Pressing Ctrl+8 resets the camera views and will allow you to adjust the cab viewpoint with the arrow keys again.
#8
Posted 01 November 2014 - 06:09 AM
#9
Posted 01 November 2014 - 01:14 PM
Sequence was:
- start explore mode
- save
- go to external view
- exit game
- restore
and the view was correct.
Then I made it a bit more complicated:
- start explore mode
- save
- go to external view
- go to cabview
- go to side cabview
- save
- go to external cabview
- exit game
- restore
and the view was correct.
Also switching between front and rear cab (I have added a rear cab, equal to the front cab, to the Dash9) does not cause the problem.
So I'm not able to reproduce the problem.
#10
Posted 02 November 2014 - 04:19 AM
Csantucci, on 01 November 2014 - 01:14 PM, said:
Sequence was:
- start explore mode
- save
- go to external view
- exit game
- restore
and the view was correct.
Then I made it a bit more complicated:
- start explore mode
- save
- go to external view
- go to cabview
- go to side cabview
- save
- go to external cabview
- exit game
- restore
and the view was correct.
Also switching between front and rear cab (I have added a rear cab, equal to the front cab, to the Dash9) does not cause the problem.
So I'm not able to reproduce the problem.
Hello,
What display aspect ratio are you using? I think people that are experiencing problems may be using widescreen aspect ratios.