|
|
Post by survivorsean on May 16, 2018 20:05:30 GMT -6
So tonight after a cool return to CA, I wanted to harness some of the ideas I was getting for Florida. I went back to Waycross and began to hump. I knew that a major issue of explosions when strings getting too long was resolved.
But even the other night in WC I did still have a nagging issue of something that said "too many cars over the switch - Hump Controller Disabled". I checked to make sure nothing got screwed up and continued to hump no harm no foul I figured at the time.
Waycross however gave me an issue I really thought would have been resolved by now, but has not. That is the issue of "car so and so is on the wrong track - hump controller disabled".
So I'm not sure what is going on because this was a known issue a year ago with Run8. In fact I recall Jason talking about giving access back to the hump switches (which you currently can't do anything about and remain locked) to get some of these cars back. I wasn't sure if perhaps it's my computer, or too much resource issues or something. After all I'm running single player and not even hosting. Yes Waycross has lots of cars in it, but I'm not purposely trying to fill every track. Frame rates are taking a bit of a hit, but has done so since the shadows were introduced. They especially take hits near yard larges, and around sunrise sunset which ironically is exactly where both my world save, as well as the current SRS session was at.
So I want to know before I go stirring up the pot and burning more bridges with Run8, is this a known issue that people are still experiencing? Scott told me tonight on chat he still has this happen at WC. So far BAR has not given me an issue since my return. WC is a bit bigger than BAR so I don't know if that is possibly part of the issue.
Unfortunately this puts a big damper in my attitude about starting up a server in the fall. I will however do what I can here on SRS as I've had lots of fun and will continue to do so regardless of these annoying nagging issues with Run8.
Let me know what you guys are experiencing?
Thanks
Sean
|
|
|
|
Post by Ski on May 16, 2018 20:56:06 GMT -6
I have not done anything with Waycross, but I can start a single player save and see what happens. Will let you know my results.
|
|
|
|
Post by survivorsean on May 16, 2018 21:29:47 GMT -6
Have you had issues with WC by any chance? BAR I haven't had any recent issues. The WC issue I had was too many cars over a switch or something.
I'm curious if others have reported these issues as well.
If you need the save file I'm using I have at least 1 hump left and only 1 trim in a fairly full yard.
Let me know.
Thanks
Sean
|
|
|
|
Post by mikerice on May 16, 2018 23:24:04 GMT -6
So I'm confused........is there an issue with WC or BAR? I haven't heard of anything to this point. Unfortunately due to time constraints I've never had a chance to hump at Waycross, even though I'd like to some day.
Mike
|
|
|
|
Post by gerry47 on May 17, 2018 5:09:44 GMT -6
I hump quite a lot at Waycross and have had the same issue as Sean. On the other hand I found if I slow down the humping speed to about 1.5mph, I can get an error free hump. Humping at 3mph definitely increases the chance of mis-hump or too many cars across a switch.
|
|
|
|
Post by survivorsean on May 17, 2018 5:29:51 GMT -6
Interesting. I can try it to 1.5 MPH and see what happens. What is the speed they recommend 2MPH? I've heard people humping at 3 no problem. The WC hump did not cause any issue as I was able to pickup and resume. All cars were humped correctly I just grabbed them and continue.
As for Waycross well that's a double issue because not only does it do this and others but you can't access the switches to retrieve missorts. The program will report the missort.
Anyways is 1.5 what people are humping at BAR these days? I don't mind doing it I'm just not sure what the optimal setting is supposed to be for where.
Thanks
Sean
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on May 17, 2018 6:18:45 GMT -6
I've been using 2.8 since they fixed the physics in the last patch. It works in single player at both BAR and WC. I was trying 3 but I think the hump controller gets too crowded with cars at that point, returning the "too many cars over a switch" issue. I only see errors when tracks overflow, most of the time. I'm not sure how Run8 handles client vs. server relations, so there might be something going on there.
|
|
|
|
Post by Ski on May 17, 2018 6:58:02 GMT -6
Sean, I usually hump at 2.5 MPH at BAR and WC and have not run into any issues. Last night in Waycross I was also able to hump 4 trains at 2.5 mph with out any issues as well. I also let some of the bowl tracks built up to capacity to see if that was causing the issue, but still did not experience the issue. Now if it's due to frame rates, I could not get my frame rates to drop below 60, but that is because I am running a GTX 1080Ti. I would say I had the entire bowl a little more than half full by the time I was done as when I started there were already cars in the bowl as well.
|
|
|
|
Post by gerry47 on May 17, 2018 8:35:24 GMT -6
Apparently 1.5mph is normal walking speed for the human pin puller at a hump.
|
|
|
|
Post by survivorsean on May 17, 2018 10:20:40 GMT -6
My graphics are much older so it could be a factor, as it is with others. But I'm going to try Gerry's 1.5 MPH and see if I get better results. BAR I have not had an issue in the 1 train I humped but it seemed to be blocked much better. The WC train I forget what it was I did but it was only 1 odd issue otherwise ran fine. Now Florida was very wide spread and typically would hump to 2/3 of the yard tracks maximum as I've divided it into 3 regional segments and 1 local segment.
The theory I'm going on it could be a combination of complexity, speed, and resources on my end. But again I'm not the only one having these issues. I could dial back the graphics but it's kind of like certain addictions. Once you have a taste of it, you don't want to go back to something just plain.
Again I like the 1.5 MPH approach and will try it. What frame rates do you normally get Gerry. I USED to be able to run locked on 20 but I tend to have had issues since the shadows came out. Before that only issues I had was BAR once in a while with frame hits. I may have to dial back due to necessity, but we will see. Thankfully any CA issues SHOULD be isolated if the operator is paying attention.
Thanks
Sean
|
|
|
|
Post by Clint on May 17, 2018 12:50:51 GMT -6
Just tossing in my experience. I have really only humped more than a time or two at Barstow, the others not so much. I used to run at 3 on single player, but found that 2.5 mph is more reliable on the server. I have still gotten the rare error, and I mean very rare, which I don't let bother me too much as I assume the real equipment can malfunction from time to time. I would be frustrated with consistent errors though like you have experienced in Waycross. I have even tried to turn off the pin puller and do it manually, just for the fun of it, but that doesn't seem to work very well for whatever reason.
|
|
|
|
Post by gerry47 on May 17, 2018 15:12:10 GMT -6
Hi Sean, I just went into Rice yard, Waycross, and I had 26 FPS plus there was thunder and lightening going on.
|
|
|
|
Post by Clint on May 17, 2018 23:54:36 GMT -6
Found out tonight that if one person is actively humping, and someone else tries to open the hump controller, even just to look at it, it will cause all kinds of weird things to happen. Once it switched the configuration I was using mid hump, and then I lost my temporary hump config that I had made to block the L-CAL0102 all together. And then when I went to pull the config from host, it crashed my client, not sure if that was related, but I'm thinking so since it has never happened before.
|
|
|
|
Post by survivorsean on May 18, 2018 7:08:48 GMT -6
No so far this is all single player and I'm below 20 FPS as it bounces. I think it's a combination of speed, resources, too much configuration to deal with, etc. I'll bring my sliders down to something more reasonable and likely do away with the shadows if necessary. Try and get myself locked back into 20 and go with 1.5 MPH and see what happens. BTW I have heard better computers than mine having the same issues even at 1.5 MPH. Barstow is not as much of an issue simply because the configuration is simpler. WC not so bad either though I only humped 1 train had 1 issue.
If they would address the issues people are having, and follow through with stuff they say they are going to (such as giving us access to the remote switches) then at least I can live with the odd failures etc.
But anyways it's not going to bother me on CA because I can see what is happening and quickly fix any issues happening.
Thanks
Sean
|
|
SMRY
New Member
Posts: 27 
|
Post by SMRY on May 18, 2018 7:41:19 GMT -6
I'm just bringing the following over from RTS/Wikia enjoy the reading material:
"Believe Sean, & just about everyone's aware by now, 1 side of Fla. crest operational, old news... Anyways Sean uses the left side in the first place. I myself have the same issue, both, at BAR & WC / NY at times as well... More to do with glitch within entire program... Sounds like the info/advise given to Daniel, perhaps others, a means to blow him/others off, skirt the issue... My hump speed is always 1.5mph no matter which location... which seems I recall can be (supposedly) safely used up to 2.5mph. Anyways, when wrong path taken by car(s), or, longer cars coming to screeching halt, I've grown accustomed to deleting the offender(s), by then rather sick of the issue, not wishing to pull back up the crest try another attempt.. Hell, even deleting the offender(s) can be a pain, as, we're not able to just click/delete, as, we must relinquish our present position prior, would be nice the ability to just click/delete the offender(s) whiles in control of another, least within range of Crest/Bowl areas, if no where else within Run8."
"I hear you about frame rates etc... though I have 4 vid-cards operating in Crossfire mode, along with a nice speedy CPU, perhaps out dated by couple yrs, about it... I have my frames locked within Run8... I also use an AMD program/suite that is setup to boost Run8 & help maintain FRs locked at 62... Hell I even use/activate Game-Booster prior to starting Run8, which pretty much shuts-down non-essential programs whiles Run8 in operation... The misroutes/length issues aren't that often, but annoying none-the-less... "
"I chose 1.5mph when V1 was hot, & still the same speed within V2 now... I would say for me the level of misroutes/length issue pretty much the same from V1 onward, which isn't often, or, often, as others have experienced.. The other reason 1.5 chosen as we called that "walking-pace" during my RR days & found in just about all of our rule books when referenced.. At that speed, able to both play the role of "pin-puller" from ground level rather nicely, or, from "drone-view".."
|
|
|
|
Post by survivorsean on May 18, 2018 19:06:21 GMT -6
The other thing that is coming up now is that a particular track might be the culprit on the left hand side at Waycross. I'm going to pay close attention to this one later this week and see if there is an issue I can isolate. But I will take the steps to bring down speed to 1.5 hoping it helps. The old thing that used to always give me issues was a bunch of cement hoppers for some reason  Lately it seems to be gondolas on this track. Again BAR has been fine, WCL not enough data just yet. Thanks Sean |
|
|
|
Post by Ski on May 18, 2018 19:29:50 GMT -6
Yesterday I humped two trains in WC without issue. Granted I was humping around 2.5 MPH on average.
-Ski
|
|
|
|
Post by chrisb on May 19, 2018 7:31:02 GMT -6
I run Barstow at 3mph and WC at 2.5 mph with no issues.
|
|
|
|
Post by survivorsean on May 19, 2018 10:59:37 GMT -6
Again I've never had an issue with BAR, and WC only 1 at 3 MPH. I'll back of to 1.5 as it's prototypical anyways and report how things are going. The main issue appears to be possibly a particular track on the left hand side of Waycross. In fact I recall most if not all my issues came from the left side so I'll have to take a look at the latter very carefully.
What I find a bit odd about this is I haven't seen public complaints about this issue, yet at least 2 people now can confirm similar issues. I'm going to to document everything moving forward and hopefully have some better results that people and the developers can use.
Thanks
Sean
|
|
Lately it seems to be gondolas on this track.