EPB Collision Box Fix
17th March 2024Updated June 21st 2024 to include a batch file to possibly fix a issue where the patch would not work.
A simple fix to allow the 2/4EPB units to pass each other without colliding. Requires the DTG NSE Class 415 AND/OR BR Blue Diesel/Electric Pack. This also applies to reskins available from Backdated TrainSim and Richard Fletcher, but are optional.
Hello. I have a feeling that the patch hasn´t applied to the Blue / Grey class 416 2EPB as this still gives a collision when used in consists where EPB´s pass each other. Just thought you might like to take a look.
Many thanks,
Simon
Hey Simon, the patch is working fine on my end with the Blue/Grey EPB. Try deleting the blueprint.pak file again and see if that does the trick. If not I’ll have to look deeper.
Hi Mattg. Unfortunately deleting the blueprint.pak hasn´t solved the issue. It does seem that it´s mainly the 416´s (all of them) that are still causing the collision when units pass. For example a 10 coach rake with a 416 tagged on the end crashes with any EPB heading in the opposite direction on a section of line between London Bridge and London Cannon Street. The units pass 415 to 415 but as soon as a 416 is involved it´s collision, error message telling me of the services having the issue and game over.
It´s a strange one. I am working around it but it´s not ideal. I figured you should know
Good luck,
Simon
Hello again Simon, I’ve tried to rectify this by having a batch file to attempt to circumvent the issue. Try giving it a redownload.
Windows Security is stating there is ‘Trojan:Script/Wacatac.H!ml’ included so am unable to download and install this.
Try giving it a redownload, I changed the file to be a standard Zip file. Seems like 7Zip is causing headaches as of late.
The “ml” bit of the alleged trojan report means “machine learning” – in other words, Defender isn’t quite sure what the file is (quite possibly as Windows doesn’t natively recognise 7zip files), so it’s erring on the side of caution and in this case reporting a false positive. I’ve had a fair few problems with 7z files recently (including ones I’ve created myself, so I’m 100% sure they’re free of viruses and other nasties), so it looks as if MS have changed something in Defender to make it stupidly suspicious of *anything* with an extension that it doesn’t recognise.
For future reference, you *can* download files that Defender flags as suspicious if you are satisfied about the origin – go to the Windows Security page and allow the file there. Google it if you’re not sure.
Interesting, I’ll keep that in mind. Thanks for the insight 🙂