ron
Recruit
Posts: 17 
|
Post by ron on Feb 21, 2018 5:10:39 GMT
Is there a problem with ship ops in 2018 as compared to 2017? I have had trouble with the ship movements and, after sifting through over 35 days of carriers at Norfolk, found that every carrier and support ship follows the schedule on the shipfinder for the year 2017. So do San Diego ships. However, if I use the shipfinder for 2018 and set FSX time to 2018 I don't see the carriers as they should show up. For example, in 2017 CVN-77, Bush, departs Norfolk on 10 February (Day4) on or about 183443 and returns to Norfolk on 4 March (Day26) on or about 203828 as expected. In 2018 the same carrier arrives on 17 February (Day12) on or about 203828 and departs on 2 March (Day25) at 183443.
Has anyone else observed this?
I don't see how the database is incorrect. There is a swapover at the end of 2017 when cvn77 arrives back in Norfolk on 13 January (Day 26), but when using the ship finder for 2018 it shows the ship leaving Norfolk on 5 January (Day4). I suppose that each year the cycles start over so that cannot be a factor in my effort to understand what is going on here.
I do believe that the documentation is outstanding and I apologize if I am just not understanding how to use the tables. My simple solution is to use the 2017 tables and fly in that year.
|
|
|
|
Post by Ripcord on Feb 21, 2018 20:15:39 GMT
Ron,
I've also noticed something was wrong with the 2018 scheduling, but I haven't yet figured out what.
The 'rule' is that the first Monday of the year is day 0 of the first cycle. So for 2018 it should be Jan 1, but evidently not the case. More research is required by me. Please stand by, sir.
|
|
ron
Recruit
Posts: 17
|
Post by ron on Feb 22, 2018 2:25:28 GMT
Ripcord, I hope you do not mind that I am doing some analyzing and commenting on my observations. This is a great program and I watched the fleet sail out of Mayport today, right on schedule (in 2017).I have mapped the Norfolk carriers again and noticed that the correct pattern repeats for every Day0 in 2018 as it does in 2017, just that it is offset by 15 or 16 days. I wondered, earlier, if the traffic schedule resets to the new year so that the first Monday is, in fact, Day0. If it does not, then there may be the root of the offset. According to the DateFinder the last cycle in 2017 begins on December 18. If it runs through all 35 days it will end around the 21st day of January in 2018. My pattern shows that, on or about Day21 the sequence continues as it should if it was Day0 again. This was not a problem for simmers in 2017. I suspect that it is a fairly simple fix (assuming this is the problem).
Ron
|
|
|
|
Post by Ripcord on Feb 23, 2018 12:01:56 GMT
Ron, we might be dealing with an end of year transition -- meaning that a traffic interval that begins in 2017 will (my theory) continue into 2018 until that 35 day interval is completed. But does that mean that the traffic intervals that begin later in the year, in March or April or whenever, will still operate according to the 'correct pattern' as we understand it?
EDIT: No, I agree with you Ron, it does appear that the traffic just continues into 2018 and beyond using the same intervals, no reset at all. So Day 0 is really Jan 22, 2018 -- the next day following the end of the previous interval.
Of course, it is easy enough to fix this in excel, but this has real implications. This means, or might mean, that just because we created & compiled these traffic files in 2017, that automatically becomes the starting year for all the traffic. Why else would 2017 follow the day 0 rule and not subsequent years? So this means that if I now go back and modify ANY of the traffic files in 2018, then I need to go back and recompile ALL of them in 2018. Otherwise we'll have some operating on one schedule, and others on another. Not sure if that is clear enough to understand.
Then I would have to go back and change all the saved flights/scenarios, which is easy, but still.
None of this is difficult, but I just need to fully understand it.
|
|
ron
Recruit
Posts: 17
|
Post by ron on Feb 23, 2018 22:37:55 GMT
Ripcord I don't think this is all that bad. I assigned new dates for Day 0 and stuff works. The year 2017 is correct. AND 2019 is correct as well, so those two years are good. In fact, 2021 will be ok as well. The years in between, 2018, 2020 etc are not following the traffic files as set in the scenery/world/scenery folder.
My new schedule for 2018 for Day0 is 1/22, 2/26, 4/2, 5/7, 6/11, 7/16, 8/20, 9/24, 10/29, and 12/3. If you count 35 days from 12/3 it takes you to January 7, 2018, which is the correct date for Day 0. I did the same for 2020 starting with 1/27, 3/2, 4/6, etc.
And ALL of those dates are still Mondays!
I apologize but I do not see what you are concerned with about the Day0 rule and 2017. I found that in 2017 the first Day0 is 1/2, in 2018 it is 1/22, in 2019 it is 1/7, in 2020 it is 1/27, and in 2021 it will be 1/11. If you count all the days you come back to a Monday for the first Day0 every time.
I don't see you having to change the traffic files. The pattern of those files is fixed and you know how it works now. The need is to document it.
There is no need to change the Database or the Timetables. If I want to know when CVN-73 arrives in Norfolk I see the timetable says it is Day11 at 231102. I use my corrected datefinder and see that in 2018 one of those times occurs on June 22 (My Day0 is 6/11).
The date finder can be easily changed, just as I did mine. The big problem, to me, and I am not much of an EXCEL man, is the Ship finder because there you tell the actual dates.
So, for now. I don't use the ship finder. There is plenty of other documentation needed to find a ship.
By the way, I landed my Grumman tracker on Abraham Lincoln last night (after my eighth attempt) and used the elevator to go below. Cool.
|
|
|
|
Post by Ripcord on Feb 25, 2018 21:21:50 GMT
Ron
I am concerned with the cause. I will need to make changes and update traffic files from time to time, as I am sure you can imagine. So I just need to know the traffic files I compile in 2018 will yield the same predictable results that they did in 2017. But, might be just my imagination working overtime, so more testing.
Excel is the easy part!
Thanks Ron
|
|
|
|
Post by Ripcord on Feb 26, 2018 11:30:44 GMT
Ron, I have been testing some new traffic files, which I changed just slightly (minor adjustments to parking positions) just a couple weeks ago, and they function as the others do that were compiled previously. So that crazy theory seems to have been refuted, and it should just be a matter of editing/fixing the excel file.
From here, do a bit more testing on the 2018 departures, using the corrected timetables I am working on. Then I'll go ahead and take a quick look at 2019 and subsequent years, just to be sure, but I won't spend a lot of time on that -- after all, I'll be needing to do a whole new traffic update on the fleet, to reflect changes in homeports that are always happening.
Thanks again
|
|
ron
Recruit
Posts: 17
|
Post by ron on Feb 26, 2018 17:36:42 GMT
Great! I know you want to move on with a lot of other add-ons and improvements so hopefully this will not take long.
|
|
|
|
Post by Ripcord on Mar 11, 2018 16:17:24 GMT
Yes OK, so Ron I confirm your results. 2018 was wrong, as was 2020. Got them sorted now, and I'll post that new excel file here. Just to recap, there is no 'reset' at the start of each year. The first cycle of a year begins on the day following the end of the previous cycle from the end of the previous year. Clearly I made this a lot harder than it ever needed to be. But we're good now. |
|
ron
Recruit
Posts: 17
|
Post by ron on Mar 12, 2018 1:45:40 GMT
Got it! I will run some searches using this latest timetable info and I know it will work. Thanks for following through on this fix. Ron
|
|
|
|
Post by udidwht on Apr 4, 2018 6:05:53 GMT
Does this file replace the one in Haze Gray Studios>Documentation folder?
|
|
