SBHH after SBHH after SBHH

[RSderek]

I am building with what everyone has.
Settle to Carlisle has all been built with the tools that are available to all. (except career mode scenarios and raindrops on glass)

There is an issue with the redraw of lofts being restricted in the editor to x amount per second which causes a lag, I have no evidence to show it has anything to do with a SBHH.
But if anyone does have repros please email support.

To the best of my knowledge this has been addressed and in beta for testing, to be released in due course.

regards

Derek

[markwhale]

In reply to the following statement:

Are you sending them the dump files when you have an SBHH? Otherwise, how are they going to know?

I am sure they have received many such dump file and are fully aware of the problem/s regarding this issue with SBHH. To be honest, going by comments by other forum members who have repeatedly contacted support for an answer have received very little in the way of support. If this issue was isolated then you could suggest that it may be an individual problem with your system setup, but too many people are getting the same issues which stem from the last upgrade! So begs the question, are these upgrades fully tested prior to release? All too often now, you are purchasing software which is riddled with bugs and errors which the developers resorts to sending out several fixes to try to put right., RW is no exception.

I am now at a point in which I have a love/hate relationship with RW. I love the game (when it runs) but hate it with a passion when hours of work has blown off into wind.

It is my hope that they will acknowledge the issues and get them fixed properly... soon....we can only hope!!!

Mark.

[smarty2]

I started over, placing only default RSC engines and cars, making the scenario exactly the same as the first scenario, not one single SBHH yet. Not only does reskinned engines seem to crash the scenario editor, but reskinned cars as well.

Bingo! I have mentioned before that imo we should have a Quality Tested system like they have on over at Amicitreni, I was shot down by irate third party creators as being unworkable, despite the Italians managing it, but I still maintain this would eliminate these silly errors. Got over my sbhh problems by doing two things, deleting my Kuju folder (which was full of re-skins) and letting steam re install it, and getting 8 gig of fast ram.

[hertsbob]

No need for sarcasm Bob. All I want is an straightforward answer to a straightforward question, am I wasting my time detailing a 50 mile route if the tools to create resultant scenarios are now borked. The issue of how RSC or their associates do it was an aside albeit in attempt to establish whether it is a universal problem or not.

Well I will say no more on the matter, unless someone is prepared to offer a sensible answer.

My apologies. I firmly believe that the lowest form of wit still contains many, as yet, un-plumbed depths and I am determined to find them all.

Straightforward answer to a straightforward question:
Yes. But not necessarily because the scenario tools are borked. Because they're not.

I'm thinking about 85% on the sensible-reply-ometer. Hope that's good enough to get through to the next round...

Cheers

Bob

[FoggyMorning]

I started over, placing only default RSC engines and cars, making the scenario exactly the same as the first scenario, not one single SBHH yet. Not only does reskinned engines seem to crash the scenario editor, but reskinned cars as well.

Bingo! I have mentioned before that imo we should have a Quality Tested system like they have on over at Amicitreni, I was shot down by irate third party creators as being unworkable, despite the Italians managing it, but I still maintain this would eliminate these silly errors. Got over my sbhh problems by doing two things, deleting my Kuju folder (which was full of re-skins) and letting steam re install it, and getting 8 gig of fast ram.

We have gone some distance in that direction with the UKTS free packs, which are all being tested on a variety of set ups before release

Ultimately though, I think there are too many variable to ever eliminate every possible glitch

[smarty2]

I started over, placing only default RSC engines and cars, making the scenario exactly the same as the first scenario, not one single SBHH yet. Not only does reskinned engines seem to crash the scenario editor, but reskinned cars as well.

Bingo! I have mentioned before that imo we should have a Quality Tested system like they have on over at Amicitreni, I was shot down by irate third party creators as being unworkable, despite the Italians managing it, but I still maintain this would eliminate these silly errors. Got over my sbhh problems by doing two things, deleting my Kuju folder (which was full of re-skins) and letting steam re install it, and getting 8 gig of fast ram.

We have gone some distance in that direction with the UKTS free packs, which are all being tested on a variety of set ups before release

Ultimately though, I think there are too many variable to ever eliminate every possible glitch

Unfortunately it was one of those packs that borked my installation, and it was more than a "glitch" causing sbhh's, line errors and so forth, and if i'm not mistaken so did quite a few others have the same errors with them? And having not re installed them it now works fine. I think the problem arose by the fact I had all the stuff in the packs anyway and there was a conflict probably with one or two of the reskins, will never know? But if I do re-start making scenarios the re-skins I do have are in the packs anyway so should still work, since the wcmln scenario pack runs fine without the packs for me.

[chrisreb]

Definately something up with other assets causing issues even if not used in the scenario. Could only load about 3 or so from each pack. Copied in a base Kuju folder and only installed what scenarios in pack needed and was able to load another 2 or 3 from each pack. Rest still load to HUD etc and black screen. Seems to prove the assets in Kuju folder (or any other folder referenced) can cause issues even if not used directly.