Victory Works WD "Austerity" 2-8-0

[michaelhendle]

Hi
I have just run the scenario on the Riveria in the 5o's route where you take the railway gun from Plymouth to the south coast, I was thinking at that stage of the war wouldn't they run the train during the blackout, not during the day, as the Germans used to have hit and run raids along the Channel,
My Mum and Dad told me that they were at Brixham, and were sitting in the harbour watching planes flying up and down the channel. when two broke away and flew towards the harbour. they were waving at it thinking it was friendly when the aircraft opened fire turns out they were German Aircraft

[Drogba11CFC]

A couple of things:

There doesn't seem to be a worn version of the BR Midland Region variety.

The number generator tells me I haven't purchased it.

[emrhd01]

A couple of things:

There doesn't seem to be a worn version of the BR Midland Region variety.

The number generator tells me I haven't purchased it.

This happened when I was testing the Austerity, which I reported and Pete corrected it whilst it was still in BETA. As the number generator always starts on the Saint (which you may not have in your collection) position when it opens, hence the purchase message will display. Did you select the Austerity at the bottom of the list and still get the purchase error message?

I have not had a "release" copy of the Austerity to check this out, but if this purchase message has returned again then Pete will soon sort it out.

[Drogba11CFC]

A couple of things:

There doesn't seem to be a worn version of the BR Midland Region variety.

The number generator tells me I haven't purchased it.

This happened when I was testing the Austerity, which I reported and Pete corrected it whilst it was still in BETA. As the number generator always starts on the Saint (which you may not have in your collection) position when it opens, hence the purchase message will display. Did you select the Austerity at the bottom of the list and still get the purchase error message?

I have not had a "release" copy of the Austerity to check this out, but if this purchase message has returned again then Pete will soon sort it out.

Yes. And I have the Saint.

[emrhd01]

I've noticed A small issue where the connection rod of the reverser disappears. This seems to be the case on all liveries.

20191102001405_1.jpg

Apart from that, it's a brilliant addition to any TS collection!

20191101235146_1.jpg

I have checked this with my BETA released (Test) version of the Austerity and this does not happen, the Reverser rodding displays fine at all angles.

Have you tried re-installing the Austerity pack, just in case the installer has had a 'Blip'.

[jstange]

Haven't had much time during the weekend to drive this, only now. Had an issue with an AI collision in the rescue scenario on Woodhead, but was not paying attention when it happened (was looking into the loco manual), so perhaps it was my mistake or something. Will try again tomorrow. One thing that I really appreciate though: fully animated reverser with real impact on the valve gear!! Great job!

[emrhd01]

A couple of things:

There doesn't seem to be a worn version of the BR Midland Region variety.

The number generator tells me I haven't purchased it.

This happened when I was testing the Austerity, which I reported and Pete corrected it whilst it was still in BETA. As the number generator always starts on the Saint (which you may not have in your collection) position when it opens, hence the purchase message will display. Did you select the Austerity at the bottom of the list and still get the purchase error message?

I have not had a "release" copy of the Austerity to check this out, but if this purchase message has returned again then Pete will soon sort it out.

Yes. And I have the Saint.

OK thanks for that, I have notified Pete, who will look into it for you.

[karma99]

I've noticed A small issue where the connection rod of the reverser disappears. This seems to be the case on all liveries.

20191102001405_1.jpg

This is a TS rendering oddity. The problem is that TS stops rendering things that are not "in view" and if an object has a centre point that's not actually in the centre then it can sometimes get overly aggressive and not draw objects that it needs to. In this case the reverser rod is rotated at one end so that is where the "centre" needs to be, and from certain acute angles TS decides that it's no longer in view. I tried a few different variations of this to try and resolve it but at the end of the day a long object with a rotation at one end is not a friend of TS it seems

Apart from that, it's a brilliant addition to any TS collection!

20191101235146_1.jpg

Thank you, really appreciate it

There doesn't seem to be a worn version of the BR Midland Region variety.

This was a late, last minute addition with the changed lamp brackets that wasn't originally planned. I'll see if we can add a worn version.

The number generator tells me I haven't purchased it.

Odd! It's probably best to get the Number Generator to re-fetch the numbering file. If you go to the location that the Number Generator is installed in and delete the folder AusterityWD inside the Data folder and then run the Generator again it should re-fetch it from the loco install.

[jstange]

So seems I was right - the Woodhead rescue mission has an issue of some sort, very weird indeed. Some 5-10 minutes into the scenario I completely lose the loco: increasing the regulator does nothing, I even can't hear any whistle sound. The loco runs further for a mile or two without power and then an AI collision pops up.

[emrhd01]

Strange that I BETA tested the scenario twice and had no problems, I'll have another look and see what happens.

[emrhd01]

@ jstange

OK, today I have completely re-run the Newton Rescue scenario that you said you had issues with and I have fully completed it with no problems. The Loco ran fine throughout, with non of the irregularities that you reported and I had no 'AI' collision pop up appear.

Perhaps you could try a re-install of the Austerity pack, just in case there had been a installation problem.

[jstange]

Thanks a lot, no idea why this is happening. Will try to reinstall both the WD pack and the route.

By the way are you sure you were using the published version of the pack when testing this?

Thanks again!

[92212]

..............are you sure you were using the published version of the pack when testing this?

Thanks again!

The published version is the test version renamed, as no additional fixes were required. Hope you manage to run the scenario successfully.

Regards
Matt

[jstange]

So I finally completed the Newton rescue scenario after reinstalling the route and the pack. However, I believe the issue was on my end, I probably passed a signal at danger and I missed it twice! So my apologies for being such a trouble.

However I still have one question and one bug that I found:
1/ isn't the reverser a bit too fast? And even the animation - are you sure it required only a few turns of the reverser wheel to get from mid to full? I think with the BMG's 8F there's a longer path of the wheel to get there... Of course it may be that your implementation is the right one (or perhaps WDs had it different than 8Fs), but I still think the reverser is a bit too fast and could be slightly slower.
2/ There is the same issue as the SSS sounds for the Panniers had when first released: the engine sound is cutting out at around 38 mph.

If you recall, Matt, I was sending you the fix for the Pannier sounds at the time, but even when you corrected it, there was still a small gap, or lower engine volume at one specific speed. I still have my own updated GWR Pannier's chuff proxybin file that I use because of that. If I may recommend please make the sound transitions a bit more overlapping, certainly gives it a more realistic feel!

[jstange]

I think the problem is here; there's no real gap per se, but I believe the overlap should be more aggressive, the sound is probably too low somewhere around 17.2-17.4 m/s. I'll test it tomorrow.

Code: Select all

<kLoud-cRVector2 d:id="559875">
							<X d:type="sFloat32">16.75</X>
							<Y d:type="sFloat32">1</Y>
						</kLoud-cRVector2>
						<kLoud-cRVector2 d:id="559878">
							<X d:type="sFloat32">17.5</X>
							<Y d:type="sFloat32">0</Y>
						</kLoud-cRVector2>
					</CurvePoint>
				</kLoud-cCurve>
				<kLoud-cCurve d:id="559881">
					<Name d:type="cDeltaString">ChuffsLoop5Volume</Name>
					<CurvePoint>
						<kLoud-cRVector2 d:id="559884">
							<X d:type="sFloat32">17</X>
							<Y d:type="sFloat32">0</Y>
						</kLoud-cRVector2>
						<kLoud-cRVector2 d:id="559887">
							<X d:type="sFloat32">18</X>
							<Y d:type="sFloat32">1</Y>
						</kLoud-cRVector2>