Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
There is also a "Write Cache" folder that creates under "Railworks" folder upon a crash. Just delete it and try again.
I believe the consist editor reads the file placed in there in the following session of edition, so it is why I delete it. An expert could tell us more detail about that particular file and folder.
TS2016 crashes create also a binary log in Railworks named something like this: railworks_540501_crash_2016_1_12T0_58_46C0.mdmp
I think this would serve to DTG to know what is going on in your game crashes. But be aware that the only missing in that log is the size number you use for your shoes.
It is one of those nasty game modules that never were rescued by DTG. I remember that the MSTS consist editor was much more stable.
However I use it much. Before upgading my computer I had very few crashes from the custom editor. I have had a few more since then, a couple months ago. It may be my new computer or just a corruption in my template file.
What I do is being "patient" with the custom editor. Do things slowly.
If you are getting crashes when trying to make a "new" consist, you may be better off by editing an existing consist and then replacing what you need to and saving with a different name. I can see that you are from UK, so probably you are making short consists. In my case I have made freight US consists normally between 50 and 100 wagons.
You may want to explore this method to build your own QD consists by using the blueprint editor:
http://trainsimlive.blogspot.co.uk/2015/04/creating-consists-via-blueprints-for.html
You may also build consists using RW_Tools.
I have never tried any of those methods, ......so far.
What I never experience is "freezing" (only dump crash). Maybe slowliness. One of my recipes is to be patient. The editor is slow mainly if you have many dlc.
These consists may also be used in the scenario builder. The only you need to do is assuring that the all rolling stock is set for the builder (selecting the provider/DLC with the little cube).
That's not quite true. More often than not the consist builder fails because of some asset file(s) and or folder(s) that is out of place, often related to a modification (3rd party reskins, other non default customisations of DLCs etc..). When the consist builder runs, working its way one by one through your game assets; if it finds something it doesn't recognise such as extra files or different file/folder locations than expected, it can often crash (stall) at that point. Using the Logmate app, you can more often than not find where in the loading (building process) that the consist editor crashes; and from this see the asset that is most probably causing the crash.
The "Logmate.exe" app is located with a player's main railworks folder. Simply run it, before pressing play as normal to start the game. The whole game loading and navigating in the game will slow signficantly, but this is only because of the intense scrutinization (listing of the programme's processses) going on in the background. Then run your consist builder for the train you wish to build, and wait for it to crash (stop responding) as you're currently experiencing. Then exit the game, and examine the Logmate readout. Reading the main programme process listing page, isn't too tricky. You will see that when you run the consist builder it carefully works its way through your game DLC assets; the point at which it abruptly stops, and the item listed above, which it was trying and failed to load and process is fairly likely to be the cause of your problem.
If you feel you have identified the likely culprit try removing the associated DLC from your game. Simply cut and paste it somewhere, a safe to place to put back adjusted once the problem has been identified. You many have more than one problem asset. If so it's a case of repeating the above process until you get to the bottom of the mystery. But in my experience it is often no more than a single troublesome asset causing the consist builder to throw a wobbly. For example I've had it fail because of an incorrectly installed MarketPlace add-on livery, and also a 3rd party loco reskin (a common reason to cause the consist builder to fail). Hope that helps you solve your problem. Sometimes it's not that easy, but the above method has never failed me yet. And I've had quite a lot of problems with the consist builder, it seems mainly because of the large amount of non default content in my game. Good luck!
A)
Which quoted part I wrote is not true?
-MSTS had a better consist editor
-DTG rescue for the custom editor non existing
-or that the forums are full of people writing they do not have a clue why the custom consist don´t work for them, including many of them recognized experts (and they use the blueprint method to do their own consists for QD)
B)
I agree that corrupt or out of place or a missing part of any rolling stock may crash the custom editor. The editor loads each of the items you have in your Assets. If only one is not right it will mostly crash.
But I think also that trying to go too fast in an old (and slow) program module with graphics of 15 years ago, will irremediably make it crash. This part will not kill my consist session.
I have recovered from the Custom Editor crashing in many instances:
1) Just deleting Write Cache without doing anything else.
2) Replacing ConsistTemplates.bin without doing anything else
3) Additionally to ConsistTemplates by deleting in some situations also some of the the caches in the Content folder (where all information of the custom consist is stored).
These caches have also user interface information. But you can just leave ConsistTemplates.XML and the game will generate all the deleted caches.
4) All replacements mentioned above come from my backups. I keep at least 3 at all times.
C) During issues I have also checked logmate, the dmp file in Railworks main folder (which is the same info the logmate reads in plain text) and the log file inside the Write Cache (with Wordpad though it is a binary). But It will not tell me why the custom editor is crashing your game. What I am sure is that what I did after the last success consist creation is the cause of the problem, so keep backing up those Content folder files.
Finally, whatever I do, it is always a mystery why that custom editor goes so wrong for others and pretty fair for me.
Two weeks ago I had a terrible sessions of crashes with the custom editor. It is gone. I am back on business. I was right making a consist while writing this message
Really no need for the mocking gesture; the end desirable outcome is simply to help the OP; and/or others having the same issue. I gave some suggestions to help, you've now given further ideas, which may be of help to others which is great. :)
A) "I am afraid nobody knows for what I have read in other forums"
I have just explained the main cause of problems for those having trouble with the Consist Builder. As indeed I have quite a few times in recent months. And I believe it has sorted the problem for all I tried to help. Matt Peddlesden on a number of different Railworks/TS forums is also another that has given a very clear explanation of why there are these problems and top advice (more detailed than myself; but I was trying to be relatively concise for fear of accusation of yet another Growler 'novel' lol). You've also just now added further possibilites yourself as to why there is a problem, and a method of going about resolving it.
B) You may have less problems than some because of the quite exclusive (limited content) you choose to run in your game. That's not a crticism, just a fact that you tend to heavily prefer US content and steam era locos at that. I probably have quite a few problems because I have a very diverse selection (virtually all official DLC) and a rather big selection of 3rd party content; my Railworks folder weighs in at just over 300GB; so I guess plenty of 'room' for upset with assets. If you keep it relatively simple with a much smaller number of DLC, mainly Steam supplied DLC only; then I strongly suspect as a player you're far less likely to encounter problems. And certainly in my experience those that frequently use 3rd party reskins are at prime risk of having difficulties with the QD Consist Builder. But fortunately good old Logmate (it's a very handy app for those that haven't used it) has always identified the problem for me.
As for reading & interpreting the generated .dmp files when the game crashes, perhaps you could kindly explain (maybe through a short guide) how to do so. That would be a huge help, because I haven't come across anyone before that can do this. Even DTG don't appear to be able to use these files, or at least that is what has been implied to players struggling with all sorts of crash problems. All the best.