As you know Pete, some routes really push things as far as detail goes. For example, few will be able to run parts of Thames Mersey and Dorset Coast with sliders on full. BD v2 seems to fall close to that category. however, some of the problems are more than likely caused by the high but realistic level of AI traffic, all with it's own sound files and all competing for your computers memory.
When i first ran a BD2 activity, Derby-Whatstandwell_Local Pass, I got constant lock-ups. Similar problems occured with the 70000 Elford Nottingham. I got through by running with sliders half way, which defeats the object of having such a nice route. Since then I have changed the soundcfg file as recomended, upped the RAM to 1gb and deleted a couple of programmes that ran in the background.
Last night i ran the Derby-Whatstandwell activity on full sliders all the way with no problems at all.
But. Frustratingly, i cannot yet run the 3dtrains modified Tehachapi route to the level I want. It just goes to show how frustrating and interesting MSTS can be. Don't you just love it?
Michael
That's Co - Driver - Mike. The one in the other seat.
Well Mike I'm the Opposite I can run Tehachapi on full settings but to be honest just give up on BD heard that much about bugs & dodgy Consist & .eg.files etc etc
I've got an old pentium celron 1.70ghz (what ever that is).
With the sliders turned down the frame rates are low average 22fps the only place it's gone down to 0 for a second was at Trent Valley then it jumped back up to 22 fps again,I haven't had any lockouts or contact uncle bill messages, by the computer only has built in sound and graphics.
I haven't inslalled a graphic card or sound card as there seems to be so many graphics around it gets confusing as to which one to buy, some people say get a nv vidia others g force and others some thing else.
I think it's yet again another excellent add on with also hardly any polluting diesels, but I can remember the smogs in London in 50's and early 60's caused by the smoke.
LOL! There's me ranting in the other B-D2 thread and I've found the same argument going on here. DOH! Well I ain't repeating it, but what I typed there, stands here as well.
I've also had problems with some activities causing MSTS crashes as mentioned above. I haven't had chance to see if 45521's the culprit, but after having a problem just past Burton when driving the Brit, I think it's prime suspect!
Other than this, I'm really impressed with what I've seen so far & pleased that there are now some upper quadrant signals. Sometimes the framerates are very low, but that's down to my hardware being a bit ancient.
Many thanks to all involved in developing this CD, my favorite route just got better!
Mike Hendle's comments seem to have passed unnoticed. How is it that he can get results with an "inferior" PC set-up whilst others with much more complex and expensive set-ups keep having problems?
Tony
Hi Tony, The specs that Mike has were about right when the MSTS was brought out, so then were top of the range, My PC is not the most up todate, yet with the BIN patch it seems like it is.I have just spent 2 hours exploring the BD add on and I am still finding new sidings and things to do. Mix it with Skipton to Carlisle-1920 stock and its a dream.
I'm now not sure that 45521 is the cause of my MSTS crashes, I've edited the suspect consist file to use another loco, but still seem to get a crash when passing Wetmore when driving 70000. I've also had a similar crash on the up in the Beeston area when driving a stopping passenger from Nottingham.
Thanks for the tip about MSTS bin1.6, I've managed to find it eventually by a Google search, downloaded & installed it. I've noticed so far that it seems to make front uncoupling much easier.