Midland Mainline - Skyhook Feedback

Do you have all the dlcs that layer into the route for both pc and xbox?

 

They need to get it together for sure (regardless of safety systems) as it’s constantly crashing on PlayStation!!!

 

I had AWS on and was going slow anyway on the approach to Nottingham as I was quite early. I was in initial braking doing around 40 way before the 50 limit (I think it's 50) and suddenly saw the yellow lozenge appear with no noise.

 

Having noticed an update come in overnight (on Steam), I picked up this route for the first time since the initial (broken) patch. The first service I tried was 6M93, using the SEHS 66.

I didn't notice at first that I had double-headed 66s. This train is definitely too light to warrant such power; even loaded, it would be within the capabilities of a single 66. The headlights of the rear one were switched on and bleeding through into my cab, washing out my view through the windscreen. The tail light was present on the rear wagon, though it was of the old oil-lamp type which is anachronistic for a train hauled by a 66.

On the bidirectional slow line to Syston, two AWS magnets were active, even though they were a mile and a half out of position for the signals they would apply to in this direction. I didn't get any TPWS activations, though I'm not sure if the 66 as modelled even has functioning TPWS. I will be paying attention to this when I move to passenger services.

Just after Syston, there was a short spurious section of 20mph limit. This should apply only to the diverging route (or rather the converging route in the opposite direction), not to the straight one.

At Loughborough and East Midlands Parkway, I had spurious signal checks almost to a stand, clearing only when I reached the mid-platform waypoint. There was no adverse traffic and no diverging route to set. I believe this is a matter of changing a flag on the waypoint so that routes are cleared through it - and this should be the default for go-via waypoints.

 

Just had the mml update,

BUT the dsd still cant be acknowledged with B button on series x.

 

Frustrating isn’t it !
I bit the bullet and bought a cheap wireless keyboard and operate the safety systems using that. Works very well, but I do have a desk to keep the keyboard on, maybe not be so much use if you don’t have room for it.

Keyboard also allows you to remove hud and other onscreen help individually, whereas Xbox controller either removes hud entirely or you have to have full on screen help.

 

u can use a keyboard on the x box u know trust me get rid of that controller the game is way more fun with keyboard and mouse

 

Pretty much the best thing keyboards offer to my mind. I couldn't live with that dreadful AP bar in the corner and removing the speedo without getting rid of the next stop HUD.

 

I

Yes, I find it much more immersive whilst still having some help for next stop distance, as I don’t know the routes very well yet.
I still use the controller for most of the train controls though.

 

Same here.

 

I´ve attached a keyboard to PS5 to deal with PZB and other safety systems. Also CTRL+F2 would enable/disable motion blur. But I can´t seem to find the short cut to get rid of that "dreadful AP bar". CTRL+F6 doesn´t do the trick?!

 

Xbox is CTRL + 6. Not F6

 

Thank you. I downloaded this morning.

 

Will try that, thanks!

Cool would be also a shortcut that blows those stupid yellow "NEW" banners away ...

 

Lol let me know if you find a way
P.S Not sure if it makes a difference but I use the number keys across the top of the keyboard and not the keypad on the right. Good luck!

 

Just did a Derby to Leicester service with HST and another emergency break application at Mountsorrel, though this was fixed?

 

I played MML for the first time since early May this morning hoping things would be better, sadly it looks the same.

Just crashed out about 2 miles from Leicester on the ‘Not Quite Awake’ scenario on PS5.‍♂️

 

I figure it out. I'm missing NTO on Xbox X. I guess some 66 services do the railtours which requires the coaches

 

Not had any major issues so far (PC). Loving the 158, and always good to have more use for the HST. Hope to see the route potentially expanded in the future!

 

Drove another 66-hauled night freight service in the opposite direction. Had a CTD, preceded by a long pause, approaching Leicester. As requested above, added a comment to the automatic bug report.

More AWS problems were noted on the slow lines. The Morpeth warning for the 50mph section through Loughborough gave the same Clear indication as the AWS for the signal immediately following. AWS magnets on the bidirectional line after Syston also still seem to be active in both directions, rather than just one.

Numerals on speed limit signs are still the wrong size. This is especially noticeable on the Morpeth warning boards. The one for the 20mph limit at the end of the quadruple-track section is particularly bad.

Also noticed that the banner repeaters are very dim at night. These modern types are self-luminous like any other signal, and should be bright enough to read clearly at a distance in any reasonable lighting conditions, including pitch darkness. At the moment they seem to be illuminated more by my headlamp than from within.

 

Noticed that Class 158's external PIS won't scroll texts after the update, thus often displaying half of its destination. Please have a look at this Skyhook.



Also would be great to see if AI drivers of HST and Class 158 could turn their wipers on during rainy/snowy days as it's been a standard feature for recent DTG stock. Thanks.

 

I made a summary of how AWS magnets are supposed to work. This is illustrative of behaviour only, and may differ from how the real ones are physically built, but should be close enough for simulation purposes:



Many AWS magnets, including the portable ones issued to P-Way teams, have only a single magnet fixed in the "upright" position. These give a warning to any train that passes over them in either direction. The upright magnet "arms" the receiver on the train, and it then triggers after a short timeout during which it is looking for a "reset" pulse.

A single-magnet AWS installation can also be placed into a "suppressed" state by inverting or nulling the magnet. This might be done for a magnet that must always sound (eg. for a Morpeth warning) for trains passing over it in one direction, but has no relevance to trains passing in the other direction, and a directional toggle would be included in the route setting apparatus for a bidirectional line. This avoids the nuisance of a spurious warning for drivers, and the installation of a St. Andrews Cross board to confirm that it is spurious.

Double-magnet AWS installations can give either a warning or a Clear indication, the latter by first arming the receiver with an upright magnet, then resetting it with an inverted one. Only that sequence will ring the Clear bell. If both magnets are upright, or the train passes from the inverted magnet to the upright one, a warning will be given as the receiver is armed but not then reset. This type can be suppressed for use on a bidirectional line like the single-magnet type, but both magnets must be inverted (or nulled) so that the receiver is never armed.

It is impossible for a double-magnet installation to give a Clear indication to trains travelling in both directions simultaneously. It must be set up for the correct direction. A triple-magnet installation could do this, but the circumstances where you would need to do so are probably rare at best.

 

I am glad to know that my fellow players are still beta testing this and reporting back all the bugs and issues that they find. Once it’s all fixed I will buy it. Thanks

 

I think I may also hold off for now.
Was really hoping the fixes would sort a majority of the safety system issues. I want to buy the route but I think I'll wait and get NTP instead in anticipation for JT route

Hopefully SHG and DTG can get this figured out though as I do want the route and its had some very good feedback. I think it has a lot of potential also!

 

I did part two, saw it stutter just before Derby, so I quickly saved it, it crashed a second or two later. Went back to the saved game and completed it no issues.

 

The whole route on PS5 just ‘feels’ unstable. Not like other DLC. It’s stuttering quite often and you feel it’s about to crash at any moment. I presume those stutters are simply a potential crash that either does or doesn’t happen. Worryingly it’s different services and even different points of the same service where it crashes. Software this unstable should never have been released.

What happens to these ‘reports’ that are automatically sent to Sony? Do Dovetail/Skyhook get these. The setting defaults to video so you should be sending a video of the crash. We are a small sample size but you have to assume it’s happening to a lot of PS5 players (thereby generating lots of crash reports). I’ve been sending mine since release day and they are still happening 2 months later.

 

I'm on PS5 but haven't touched MML since the 1st patch was released. It was concerning to hear on the live stream yesterday that the 1st patch was released correctly but going by this thread there were still a few issues and further issues caused. The 2nd patch also hasn't helped going by comments posted so MML will still be bypassed by me until things turn around.

 

Emboldened by the fixed collectable poster at Leicester, I did a quick runaround to see if one of the blue benches became paintable. No such luck. Collectables remain broken, as only 99 are present. One bench still missing. However, during the runaround, I noticed a few signage typos. So here they are.
This "EMR Lougne" is at Derby. (Edit: come to think of it, why does it even say "EMR," when, as evident from the trains' liveries, the route was operated by EMT in 2018?) Note also the inconsistent capitalisation of "Emergency Exit." Inconsistency in signage is present is so many places, I didn't even bother screenshotting them all.

This "Emergeny exit" sign at Leicester, Platform 2b, is the first sign the player sees upon beginning the first scenario, "Easy Trip." I vaguely remember it being reported already, but just in case. Note also how this exact sign looks IRL (a special green board, lowercase "e" in "exit").

This sign's board is too small for its text (at Loughborough).

"Gentlemen" is already plural, there is no need to pluralise it further. If it was intended as a possessive, then there should've been an apostrophe — and it would've been wrong anyway, as that exact sign IRL says "Gentlemen." Also, the pictogram on the "Gentlemen" and "Ladies" signs isn't an "i" in a circle, it's a figure of a man or a woman. You know, as one might expect to find on a sign pointing towards a toilet.

And finally, I have no idea what the typeface used on those particular sings IRL is called. Doesn't look like Rail Alphabet. Looks more like Transport. What it definitely isn't though, is Unreal Engine 4's default font. Using it on those signs is tolerable, I suppose, as it's reasonably close to the real thing. Putting a text block on trackside signage, however, instead of making a proper texture, isn't as unnoticeable. Not only does it look wrong, it results in signs like the one below. At speed, they are pretty much unreadable. Actual MML signs pictured for comparison.

 

we dont all sit at a desk so not being able to acknlowedge dsd with the controller needs to be sorted

 

I love this route and I want skyhook to add new things to it like class 222 and Sheffield but these bugs and issues are not helping at all. Just wondering I haven’t read the update articles but has the dsd circle shortcut on PlayStation been fixed yet?

 

Nope, still can’t acknowledge. DSD and AWS switches are still in he wrong place inside the HST as well. Pretty sure it was mentioned as fixed…

I’ll be running a crashed service later without safety systems to see if they are a root cause…

 

It is yes. I know i could put in a keyboard, but i have no where to use it properly.

 

That is the problem with the keyboard, I’m lucky I have taken over the spare bedroom in our house and have a desk and chair. Really, you just need the fix so the controller works as it should.

 

Yeah that’s what I thought about them fixing this patch

 

Just attempted to drive a service. The first drive post-patch. Towards the end, as I was approaching Leicester, I had a crash. This was my 5th crash on the route. Playing every other route combined for 900+ hours resulted, as I recall, in just 3 crashes, while this route managed to produce 5 in just 15 services played (or rather, 14; this would've been the 15th).
So, let's do a bit of a rough estimate. This route: about 10 hours of driving, 5 crashes. Every other route combined: being generous, 600 hours of driving (let's say the other 300 hours were spent AFKing, doing collectables etc.). 3 crashes. So, on average, this route produced a crash every 2 hours. And every other one produced, on average, a crash every 2 hundred hours.

And I'm not even playing on PS4/5. I'm playing on Steam. Guess the patch didn't do much with regards to frequent crashes, huh?

Edit: another service, another crash. This is actually a bit infuriating now.

 

When Spawning into Timetable mode on foot, the scheduled freight services are still not appearing.
Now I was under the impression that the latest patch which had just been released was the hotfix for patch one plus a few extra fixes that they managed to squeeze in. Now it seems that from what I can gather this latest patch is being called patch two. So could we have some clarification. Is this indeed the full fat patch two or merely a stopgap repair for the first patch.
Skyhook Jane did say that the problem of the non appearing Freight services would be addressed in the next patch some time ago, so I guess my question is when are we likely to see this problem addressed?
Are we going to get a proper patch two or was this it?
It would be great if DTG or SHG could clarify where we are in relation to upcoming fixes and what is actually being worked on and what has been overlooked in the confusion of broken patches etc.

 

Hi. Not sure you saw my earlier post but it was mentioned by Matt on the live stream yesterday that the 1st patch was the correct patch, apparently there was some miscommunication at the time. The 2nd recent patch is a separate patch. Worth checking out the live stream explains everything. For anyone interested in Matt's explanation it's 39 minutes into the stream.

 

Hang on. Are you saying that what just got released wasn't the hotfix to the broken release of Patch 1, but an entirely new, separate, and previously unannounced Patch 2? That's hilarious on so many levels.
Does Matt say if the hotfix is still coming? (No, I'm not watching a bloody livestream to see what's what, I mean, come on )

 

I think once Jane is back some of the issues can be addressed again I have had some stuttering but it hasn't crashed or anything it's still frustrating though

 

Yes I saw the live stream and rather than explain things, the statement actually muddies the waters even more than it clarifies as it is at odds with what we have been getting told for some time by Jane. Jane said quite explicitly that there was a second patch coming out in due course and that the hotfix patch had been passed to DTG for release. I can only assume from that that someone from DTG or SHG is mistaken or being untruthful. So which is it?

 

Just shut the engine down of the second 66 and haul it. no reason to waste diesel

 

• Fixed an issue where the TPWS trips with penalty brake on entry to Nottingham (approach C-Line below 48 mph, the TPWS should not trip)
• Fixed DRA and AWS isolate switches being reversed in operation

These are the HST patch notes for patch 1 released early June. Now I know some stuff was missed out and was supposedly put into this emergency patch we had yesterday to sort it all out however the 2 things above are still not fixed. I had the TPSW brake application yesterday at around 15mph, and item 2 is clearly not fixed just by entering a HST cab. So that would suggest there's still some missing files??

Looks a total mess to me.

 

Yes it still isn't right needs some more work hopefully that comes in the next few months

 

Yes. Matt explained that DTG have released everything they have from Skyhook and are up.to date. Obviously from various comments things still aren't right with MML so Skyhook need to keep working on the route.

 

After listening to last evening’s stream, I’m honestly so confused!
We were made to believe that the first patch was faulty and supposed to be fixed with the second patch we got this week. But the reality is that the first patch was not faulty, in fact it was exactly what Skyhook Games submitted. Which makes the completely incorrect patch notes and remaining huge bugs (that were supposed to be priority 1) very puzzling. In addition to that, the second patch that arrived this week, which was supposed to fix the issues caused by the first patch, again had incorrect patch notes, missing features and huge remaining bugs.

My question is: What went wrong there? We’ve had two patches now, which were supposed to take care of the most important issues, yet we still have (almost) all the game-breaking problems and it’s unclear what the patches actually changed for the better. On two platforms (PS4 and PS5), the DLC is essentially unplayable for the majority of players due to constant crashing. And on all platforms, various major problems with the safety systems are preventing the smooth completion of services.

Jane has been very active in here, logging all the issues and communicating with the community on many occasions. But something is obviously going wrong with the communication internally because the status updates on the patches we’ve been getting, as well as the contents of the patches themselves, have turned out to be completely incorrect. Hopefully Skyhook and DTG can look at this fiasco together and figure out how to ship the correct patches with the correct fixes to customers next time around!

 

A few weeks ago, we've been warned - and the claims were substantial. That was quickly covered up. It reminds me of Piers Morgan being fired by ITV for honestly stating his opinion on Meghan's Oprah interview. In the end, we now know how right he was.

Imho the sole purpose of this "communication" was to get more people into buying the unfinished DLC.

“It's easier to fool people than it is to convince them that they have been fooled.” – Mark Twain.

 

Totally agree the communication between DTG and Skyhook needs looking at. Unfortunately for some of this mega thread the information given has been incorrect regarding the 1st patch. Obviously DTG watch this thread, I wonder why they didn't step in with the explanation given on yesterday's live stream a few weeks ago? rather than everyone hoping for the missing files to appear that hadn't gone missing, the 1st patch was as intended. Also it was mentioned on this thread there were going to be further improvements added to MML with the 'hotfix' but there was nothing in the patch notes. For me like everyone one else I just want the route stable to play.

 

As I don't have time to check tonight could I just ask anyone on the xbox whether the TPWS issues are still there. Sorry if this has been said above but I have not got enough time to read through all of it. Any help will be much appreciated!