
- OpenGFX
- settings: different settings don't matter (tried different settings for every option)
- reproduce: it happens every time I tried.
Could give screenshots but that won't give you more information, would it?
Moderator: OpenTTD Developers
No they would not nor would savegames. I have edited my previous post while you was replying ...Could give screenshots but that won't give you more information, would it?
Code: Select all
changeset: 402:e8eeec5ebf1f
tag: tip
user: Ammler <ammler@openttdcoop.org>
date: Sat Mar 27 11:08:58 2010 +0100
summary: Doc: update credits and blame list
changeset: 401:d457fa3c333b
user: Ammler <ammler@openttdcoop.org>
date: Sat Mar 27 10:20:06 2010 +0100
summary: Feature [#869]: include gui icon for debug tools
changeset: 400:28d9710d143e
user: Ammler <ammler@openttdcoop.org>
date: Fri Mar 26 22:44:43 2010 +0100
summary: Feature [#869]: gui icon for debug tools
changeset: 399:3d21b3586027
tag: tip
user: planetmaker <ottd@planetmaker.de>
date: Thu Mar 25 17:13:02 2010 +0100
summary: Doc: Update readme a bit
changeset: 398:39bc95ffc8b0
user: planetmaker <ottd@planetmaker.de>
date: Thu Mar 25 16:55:49 2010 +0100
summary: Change: Make Debian and Fedora users happy (Rubidium)
changeset: 397:128315c6c280
user: planetmaker <ottd@planetmaker.de>
date: Thu Mar 25 16:39:00 2010 +0100
summary: Fix: [Makefile] Don't build when calling clean and mrproper but clean more thoroughly (Rubidium)
changeset: 396:f27f00e31817
user: planetmaker <ottd@planetmaker.de>
date: Wed Mar 24 18:25:39 2010 +0100
summary: Change: [Makefile] Update Makefile to r77
Code: Select all
-static const uint16 OPENTTD_SPRITE_COUNT = 172;
+static const uint16 OPENTTD_SPRITE_COUNT = 173;
...
-static const SpriteID SPR_FLAT_BLACKTILES = SPR_OPENTTD_BASE + 153;
+static const SpriteID SPR_FLAT_BLACKTILES = SPR_OPENTTD_BASE + 154;
I do not consider doing something I like doing to be work, but I appreciate that you apreciate what I do.tjook wrote: I can't wait to play a glitch-free version!
Thanks for all the hard work Chill!
You may want to try and install liblzo2-dev instead.2007Alain2007 wrote: Hi
I just gave it a go and having A LOT of probles with liblzo2 tryed to install it and says its a viuse and also it dose not work so i am hoping some one esle who knows a bit more what there doing can make a win 32 build
and can we conpile with out liblzo2 if so i give it a go again tonight
if not liblzo2 is evil![]()
Maybe the sprinkles part will be part of the next version maybe it will not.SpComb, in the cargodist with sprinkles, thread wrote: For daylength factors of 1, 2 and 3, the running costs behave correctly. However, with a daylength factor of 4 (DAY_TICKS = 296), the value of Vehicle::running_ticks will overflow, and thence running costs will be completely wrong.
Thank you for the build Scautura. Many people will appreciate it.Scautura wrote: My turn!
I haven't played this yet, but I was sick of the last binary having issues with NuTracks (Steam engines being electrified in NARS2) so I built my own. As there hasn't been a post with a binary for this version (or a version since V4 came along), I figured I'd give it back to save others from doing their own.
This is built using MSYS/MinGW, so there's no crash info when you crash. Otherwise, enjoy.![]()
Compiles and runs well so far. I'll take her for a spin tonight. Thanks for the effort.ChillCore wrote:By request the patch attached to this post has the sprinkles part of this patch:[...].
variable-daylength_town-cargo_misc.patch against cargodist is the patch I have added to my patchpak.
Cool, let me know how it goes.Freak_NL wrote: Compiles and runs well so far. I'll take her for a spin tonight. Thanks for the effort.
I assume that when disabled there is no influence.Freak_NL wrote: Do the "sprinkles" have any influence on the rest of the patchpack and OpenTTD if you don't configure them in the option tree? Variable daylength and passenger/cargo generation work really well together if you lengthen the days and lower the passenger production.
SpComb, in the cargodist with sprinkles, thread wrote: For daylength factors of 1, 2 and 3, the running costs behave correctly. However, with a daylength factor of 4 (DAY_TICKS = 296), the value of Vehicle::running_ticks will overflow, and thence running costs will be completely wrong.
I do not know what else may be broken(yet) with higher day lenght settings.ChillCore, a few posts back wrote: In my own build I have changed "byte running_ticks;" into "int16 running_ticks;" in vehicle_base.h for testing.
The running costs seem to behave correctly with higher daylenght settings but I do not know if I have broken something else while doing so. That is why the posted patch does not include this change(yet).
Code: Select all
DiagDirection dir = GetTunnelBridgeDirection(tile);
Code: Select all
DiagDirection dir;
dir = GetTunnelBridgeDirection(tile);
Users browsing this forum: No registered users and 24 guests