The International Simutrans Forum

PakSets and Customization => Pak128.Britain => Topic started by: The Hood on December 01, 2012, 01:04:57 PM

Title: Upcoming release (1.13)
Post by: The Hood on December 01, 2012, 01:04:57 PM
I'm proposing to make the next release just before Christmas, as it's been a few months since the last release. So far the additions would be mainly the new ships I have been drawing, plus a number of bugfixes from previous releases. At the minute this would be less substantial change than previous new releases (but I'm guessing people would appreciate an update?). If there are any other contributions out there that aren't quite ready yet, or if anyone wants to complete something in time for that release, please do...
Title: Re: Upcoming release (1.13)
Post by: jamespetts on December 01, 2012, 01:26:32 PM
Have you looked at the new graphics for the 4/6 wheel carriages from the 1870s/1880s that I have uploaded to the Experimental Github repository? The 6-wheelers you might have seen before: not sure about the 4-wheelers, which are more recent (they are shorter than the ones already in the game).

Also, do you have:


Actually, if you have a look at the Github commit history (https://github.com/jamespetts/simutrans-pak128.britain/commits/master?page=1), you will see the things that have been added to the Experimental version recently that you can add to the Standard version for the next update, as well as the consequential changes that I have made to accommodate the additions.

I hope that this helps!
Title: Re: Upcoming release (1.13)
Post by: The Hood on December 01, 2012, 02:06:55 PM
Got all of those except the choose sign I think.
Title: Re: Upcoming release (1.13)
Post by: jamespetts on December 01, 2012, 02:17:34 PM
Even the re-sized 1870s four wheelers? That wasn't announced on the forum, and were recent.
Title: Re: Upcoming release (1.13)
Post by: Fabio on December 01, 2012, 02:30:18 PM
I suggest you guys add also James's phenomenal arched basement as default city basement.
Title: Re: Upcoming release (1.13)
Post by: jamespetts on December 01, 2012, 02:43:59 PM
Do you mean the artificial slopes side graphic? And thank you!
Title: Re: Upcoming release (1.13)
Post by: Fabio on December 01, 2012, 02:59:29 PM
Exactly!

Since probably you didn't read the thread in Pak128 board, I want to thank you here as well for the inspiration you gave me with them (new slope wall in Pak 128)
Title: Re: Upcoming release (1.13)
Post by: The Hood on December 01, 2012, 03:29:06 PM
Quote from: jamespetts on December 01, 2012, 02:17:34 PM
Even the re-sized 1870s four wheelers? That wasn't announced on the forum, and were recent.

Oh, I must have missed that. Will merge it in. Any chance you could announce new graphics/objects in the forum in future?
Title: Re: Upcoming release (1.13)
Post by: greenling on December 01, 2012, 05:55:36 PM
The hood
that it very nice that you work on a new pakset relase for pak128.britain.
Title: Re: Upcoming release (1.13)
Post by: wlindley on December 04, 2012, 05:00:23 PM
The roadway crossing for Narrow Gauge is available from 1855, but shouldn't that be earlier, at least 1850 when the first passenger carriages appear?

Also, there is a rail crossing for N.G. defined since 1836, but I cannot seem to be able to build one.
Title: Re: Upcoming release (1.13)
Post by: AP on December 07, 2012, 08:12:08 PM
Is the rail  one-way sign making an appearance?
Title: Re: Upcoming release (1.13)
Post by: The Hood on December 07, 2012, 08:16:51 PM
It's already in SVN so yes, it will be in 1.13
Title: Re: Upcoming release (1.13)
Post by: The Hood on December 08, 2012, 02:00:59 PM
Quote from: wlindley on December 04, 2012, 05:00:23 PM
The roadway crossing for Narrow Gauge is available from 1855, but shouldn't that be earlier, at least 1850 when the first passenger carriages appear?

Also, there is a rail crossing for N.G. defined since 1836, but I cannot seem to be able to build one.


OK, I've added a new unprotected crossing from early on. I also tracked down the bug with the rail-rail crossing and fixed it.