Dash9 updated!

[Machinist]

I use Brazil server, but I guess it doesn't matter.

So far I noticed they changed the name of .geo file, but kept the same name of engine.bin (and this may explains the problems with re-paints). What they changed is the (internal) name of engine and also the localisation name (that one which appears on engine list, to pick it up and place on track), it shouldn't been causing problems, unless RWTools (for those using the tool) is using the internal name (or localisation name) and messing the things. As I said, IMHO if default scenarios are working (unless they were re-written and updated), the problem is at the user's end when setting its own (or 3rd party) scenario. I'm creating a new scenario with Scenario Editor (didn't use RWTools so far) and it's running flawlessly.

[Merlin75]

Thanks Kali I'll give that a go. If it don't work it's not a big problem as I have a Dash 9 folder thats not updated and will just replace the updated version with the one thats not.

[artimrj]

I use Brazil server, but I guess it doesn't matter.

So far I noticed they changed the name of .geo file, but kept the same name of engine.bin (and this may explains the problems with re-paints). What they changed is the (internal) name of engine and also the localisation name (that one which appears on engine list, to pick it up and place on track), it shouldn't been causing problems, unless RWTools (for those using the tool) is using the internal name (or localisation name) and messing the things. As I said, IMHO if default scenarios are working (unless they were re-written and updated), the problem is at the user's end when setting its own (or 3rd party) scenario. I'm creating a new scenario with Scenario Editor (didn't use RWTools so far) and it's running flawlessly.

Nothing shows up for me. Not even the RSC\dash9package to turn assets on with. They are physically there on my hard drive though. Reason I asked which server is possibly the DC server got a bad upload. Anyway, I will be on it tonight to see what can be done. May have to reverify cache again or maybe delete the d9 package and verify to get it back. So far I have only seen 3 people post that everything is alright with their installations. At least 40 people have broken D9's. Those are just the ones that post.

[Kali]

Thanks Kali I'll give that a go. If it don't work it's not a big problem as I have a Dash 9 folder thats not updated and will just replace the updated version with the one thats not.

Well if Doc had a look & they've changed the geo file name, you'll have to change that in the repaints too - although *that* should be fine with the old one unless there's some new geo feature other than copy protection.

[roinuj]

I'm also having the same problems so you can add me to the list.

All RSC support suggested so far was to delete the Dash9 asset folder and verify the game so a new download is done and then clear the cache before starting. It didn't work and the verification didn't add the Super Dash folder that the initial download updated?

Problem I have is the fact you go to any existing scenario (default or user created) to edit and there is no Dash9 option in the asset list as well as in the asset provider fly-out under RSC. When I tried creating a new scenario, it shows the Dash9 in the asset provider fly-out but it doesn't/won't list any Dash9s and then when you re-try the asset provider fly-out, there is no Dash9 option under RSC.

This is pretty messed up.

[PamBrooker]

So are the Dash 9s working now? Was it a delayed update? Last night at 8 pm they were not working for me, but I am getting new carpetting today and had to tear the computor down so I won't know until tonight.

Um, no.. sadly.. I did a complete reinstall of railwaorks last night and even then it didnt download the two blueprint files, and the engines didnt work. Experimenting further, i have a small touchscreen computer i use as a backup so i installed steam and railworks on it too with no other addons. Its totally vanilla, and the dash 9s do not work on it either.

[dfcfu342]

Is the Dash9 working in a say normal (built-in) scenario? That is (or should be) usually the first attempt when (re)installing assets. If yes, than the problem is in your scenario, and there are tons of things that may be causing the SBHH: missing .geo files, unchecked blueprint flyout, vehicles overriding each other, vehicles over junctions, juctions against etc...

I've been using the built in scneraios and it still doesn't work. Even other scenarios that don't include the Dash 9 don't work now since the update.

[PamBrooker]

I'm actually rather torn over this. I dont know how many verifications i did on this computer yesterday, and the reinstall on this computer and the fresh install on the little computer upstairs, has me wondering.. Maybe its not RSCs problem. Maybe its steams problem. Everything seems to be related to whats downloaded and whats not. For some, the engines work beautifully, for others they dont work at all. Further research across other forums on the web supplied evidence that most if not all non working installations have the missing blueprint.spk and blueprint.spk.md5 files, and no matter whats tried, those will not be downloaded.. Now, I dont know a lot about trains i admit, but i spent 35 years doing system administration and network administration and kinda know my way around that you could say.. If there was a way to have gotten those files to test i would have.. But i digress.. RSC clearly put out a working product. It works for quite a few people as point of fact, but for a great many of us, well.. It dont work at all.. I tend to think this is a steam oriented problem and Not RSC at all..
However, RSC is far from innocent. I posted a very polite, well worded ( non whining ) comment about the situation on their facebook page last night. Within an hour it had been censored and the comment thread of four or five people that responded was gone. Maybe its because i'm american, but i cant stand being told what i can and cant say. Worse, I cant stand grand standing and money grabbing such as RSC has painted the picture of what they are doing..
Shame on both of them..
Pam

[Samwolf]

Nothing shows up for me. Not even the RSC\dash9package to turn assets on with. They are physically there on my hard drive though. Reason I asked which server is possibly the DC server got a bad upload. Anyway, I will be on it tonight to see what can be done. May have to reverify cache again or maybe delete the d9 package and verify to get it back. So far I have only seen 3 people post that everything is alright with their installations. At least 40 people have broken D9's. Those are just the ones that post.

My default Dash 9's seem to be fine (not including any repaints). Tried the stock sceanrios and they run.

P.S. Just another indication that nothing good comes out of DC.

[PamBrooker]

I retract my statement against RSC regarding censorship.. Though its not exactly easy to find, my posting on their facbook page is still there.. For accusing them of censorship, I apologize..
Pam

[PapaXpress]

The problem is that they have all these channels to talk to their users, and yet they say nothing.

[PamBrooker]

I hear ya Papa.. And i agree.. They're spending too much energy on new products and expanding they're distribution base and marketing, and not enough time and energy on supporting the products they do have.. For most companies, that scenario is a death sentence.. I hope it doesnt turn into that for RSC.

[Machinist]

my mistake they didn't change the "name" of default .geo, the .geo was only updated (same name).
I also checked (confirmed with RWTools) that before the update there were on BSB 3 freeroam for Dash9 (starting with [Dash9]), and now only 2 with slightly different names (no long [Dash9] on name). Does it means they changed the .geo? and previous scenarios are broken now? What is the reason of scenario's change for?

Now when I go to "Drive by Train" I get listed engines names starting with for example Dash9 BNSF (old scenario), Dash9-CW44 BNSF (old standart I have) ... and also GE C44-9W BNSF (new RSC freeroam)... However in Scenario Editor you can see only Dash9-CW44 BNSF (even with Dash9Pack01 checked). This is why somewhere in scenario files the name is fixed, even if the engine files is updated, until you save scenario again with Scenario Editor. A mess!

What I have now (functioning):
\railworks\Assets\RSC\Dash9Pack01\RailVehicles\Diesel\Dash9\Default\Engine
After update:
Dash9.bin
Dash9-44CW.GeoPcDx
Name: Dash9-44CW BNSF
Localisation name: Dash9-44CW BNSF
Before update:
Dash9.bin
Dash9-44CW.GeoPcDx
Name: Dash9-44CW BNSF
Localisation name: Dash9-44CW BNSF

Delete the whole Dash9Pack01 and verify cache maybe is a good idea (from RSC), but if you still have old scenarios your engines list will show the older names also. What I can suggest is using the names starting with Dash9-44CW (althoug RSC stated the new correct name starts with GE C44-9W).

I'm afraid of re-verify cache and mess my current working installation.

God have mercy on us! Save yourself if you can.
Doc.

[PamBrooker]

got another kicker for ya Doc..
anyone who had purchased the bnsf-dash 9 pack from steam will find that not only will they not work, but if you delete them off your system, steam will not redownload them like they do with everything else youve payed for ( and a few pieces of trash games you didnt ask for either )..
Now, this has been my direct experience ( i loved my bnsf dash 9s. and it just keeps making me madder and madder ), but others may se other results.. I live in the pacific northwest so i dont know what server it is i download from. perhaps its a problem with the server..

Oh and,, GE C-44-9W doesnt show up in my selection list either.. :(..

[SMMDigital]

...maybe it's Steam because some installations work and others don't...

I'm not letting RSC off that easy. They have a looooooooooooong track record of breaking stuff when they do updates. It could also be the difference in computer configurations, same as happened to me with the NSAND. Higher end systems run it, lower ends don't. It wouldn' t have killed RSC though to have released this to a few different people with different computer specs to see if something like this would happen.

It's a good thing they aren't censoring Farcebook, because I was neither kind nor tactful about the situation.