32bit Graphics Extra Zoom Patch

[Vitus]

You have to use patched version in order to use the two new extra zoom levels. Clean trunk builds (such as nightlies) don't support it.

[zottelloco]

You have to use patched version in order to use the two new extra zoom levels. Clean trunk builds (such as nightlies) don't support it.

Do you mean this?:
http://www.tt-forums.net/viewtopic.php? ... &start=582

if I shall use a patched version, why is there an additional newgrf?

[GeekToo]

The patch provides the two extra zoom levels, the newgrf makes sure 32bpp graphics are shown correctly independent of the baseset opengfx or default graphics. The newgrf can also be used in combination with trunk.

[zottelloco]

Hi,
i have patched a ottd r20025 with a ExtraZoom-r19024.diff (actually, to patch with it ottdr19024) and it works well.
Now i have found this site:
http://dev.openttdcoop.org/projects/32b ... es/ez.diff

and I can see there are some recent ez-patches than r19024...
If I have now the pure ottd r20026 source code without ez, what I neet to select on this page?

[GeekToo]

Just download the ez.diff from:
http://dev.openttdcoop.org/projects/32b ... es/ez.diff

and patch with patch -p1 < ez.diff

[zottelloco]

Just download the ez.diff from:
http://dev.openttdcoop.org/projects/32b ... es/ez.diff

and patch with patch -p1 < ez.diff

Thank you for your help, but this tip does not apply for Windows or?
The problem is, in the .diff there are the following folder- structure: <sourcefolder>/a/src and <sourcefolder>/b/src.
My local folder-structure for the source code is only <sourcefolder>/src. So my merge tool complains about it. In previous .diffs, there was no such problems.

[Ammler]

That is why you need to use p1 instead p0

[zottelloco]

That is why you need to use p1 instead p0

Sorry but I dont know what is meant with p1 and p0, is this a linux thing?

[GeekToo]

Hi,
i have patched a ottd r20025 with a ExtraZoom-r19024.diff (actually, to patch with it ottdr19024) and it works well.

Reading this, I assumed you knew how to apply a patch. Yes, patch is originally a Unix utitility, also available in most (all?) Linux-distros, to apply a patch-file/diff to sources.

On windows you can also apply patches, using cygwin or mingw, or by some other program like Tortoise (though the latter has some issues with patches that are not p0, I believe)

p0 assumes to apply the patch to the paths as present in the patch file, p1 means the first part of the path (the a/ and b/ part in your case) will get stripped, before applying the patch

[zottelloco]

Reading this, I assumed you knew how to apply a patch. Yes, patch is originally a Unix utitility, also available in most (all?) Linux-distros, to apply a patch-file/diff to sources.

On windows you can also apply patches, using cygwin or mingw, or by some other program like Tortoise (though the latter has some issues with patches that are not p0, I believe)

p0 assumes to apply the patch to the paths as present in the patch file, p1 means the first part of the path (the a/ and b/ part in your case) will get stripped, before applying the patch

Yes I use Tortoise on Windows to patch and I wondered what should be this p0 and p1.
Perhaps, it helps to switch to mingw.

[ArmEagle]

Reading this, I assumed you knew how to apply a patch. Yes, patch is originally a Unix utitility, also available in most (all?) Linux-distros, to apply a patch-file/diff to sources.

On windows you can also apply patches, using cygwin or mingw, or by some other program like Tortoise (though the latter has some issues with patches that are not p0, I believe)

p0 assumes to apply the patch to the paths as present in the patch file, p1 means the first part of the path (the a/ and b/ part in your case) will get stripped, before applying the patch

Yes I use Tortoise on Windows to patch and I wondered what should be this p0 and p1.
Perhaps, it helps to switch to mingw.

Well, if it really is just those a/ b/ parts in the paths that bothers Tortoise, then I'd just run an editor over the patch file and search-replace(remove) those parts. Mingw is quite the large 'program' to install just to be able to run patch -p1.

[GeekToo]

or use a patch program that can handle this diff format: maybe: http://gnuwin32.sourceforge.net/packages/patch.htm will do the trick for you (you may have to convert LF->CR/LF in the patch file before, but any decent editor can do that).

[zottelloco]

or use a patch program that can handle this diff format: maybe: http://gnuwin32.sourceforge.net/packages/patch.htm will do the trick for you (you may have to convert LF->CR/LF in the patch file before, but any decent editor can do that).

Ok i will try this. But it is not necessary to change the format, because the diffs on this page all seem to be in CR/LF(Windows) format (at least I can not see UNIX line breaks, or something similar...)

[Storm Reaver]

delete

[schlummOr]

Is it normal that the coverage are has the same color as the area where the station is build?
This is a screenshot of a 2x7 station:

[ChillCore]

May I please request someone to upload a win32 binary against the latest version.

I would very much like to have a version that I can configure to not look in the shared directory to test properly.
Unfortunately my self compiled binaries on Linux look in my shared directory and I have no clue how to prevent them from doing that.
Putting a config file next to the .exe does not prevent it from doing that while downloaded windows binaries under wine behave like I want.

I would prefer not removing my 32bpp graphics I have allready in my shared directory.
As an alternative, if someone knows how I can achieve what I want, without messing with the source to much, it would be appreciated just as much if not more.

The version Storm Reaver has uploaded has two problems.
1. The zip has a password.
2. After entering the PW it refuses to unzip properly.

Thank you in advance.

[GeekToo]

http://wiki.openttd.org/Readme.txt section 4.2 may give you a hint about the search order.

[Storm Reaver]

delete

[ChillCore]

I have update my post.

Thank you Storm Reaver the .zip works for me.
Now I can test properly while knowing what graphics I am using while doing so.

Please also note that you MUST provide COPYING with your binary to stay in compliance with the liscence. (read COPYING)
You may also include the readme.txt, known bugs.txt and changelog.txt but COPYING is the most important if you want to distribute binaries legally.
These files can be found 1 level up from the bin directory.
The "make bundle" command will make a new directory "bundle" with all nessecary files included.

http://wiki.openttd.org/Readme.txt section 4.2 may give you a hint about the search order.

Section 4.2 will not tell me why this happens without putting graphic set and sound set near .exe:

Windows binary:
- No config near .exe:
-> Normal startup using shared directory in .wine/profiles/personal_directory/Mijn_Documenten/openttd
-> Shared directory for newgrf and data is used

- With config file near .exe:
-> complain about no graphics or soundset -> refuse to startup
-> After putting basesets -> startup but shared directory is not used.

Linux binary:
-> It does not matter if I put my config near the exe or not -> graphics and soundset are found and game starts up either way.
With config file near .exe -> graphics from ./openttd are still used.
note:
- usr/shared is not used as I have uninstalled the OpenTTD version from the linux software repository.
- For (auto)saving and loading game the gui opens in the directory where the config file is found as specified by section 4.2.



Anyway enough off topic for now,
Please find attached a few screenies, tested with my linux build.
1. Position drawn on smallmap is off
2. Trees position is not drawn correctly. When zooming in and out they also shift position. This also cause glitches sometimes when moving the main gui left or right.
3. Multiple:
- There is a space between tiles when zooming in. (See also industrie in second picture.)
- Glitches outside the map.
- Land information cursor is not drawn on the map.
- Gui is unreadable. Why not use the original colours for the guis?

[maquinista]

There is a black tile that should fix these dots over the background. I will upload it.