You can get it HERE RIGHT NOW!
It is a 7-zip self installer which needs to be run in your EAW 128E folder.

The info.txt reads:

***********************************************************************************************
This package installs two test eaw.exe versions set up for OAW128 in
"E-128E_Fix08_TM2" and "E EAW1.28e_10 _TM2" folders.
These exes are modified versions of Knegel's 1.28E fix08 and fix10
which use the TM2 tilemap system started by Will Gee.

Three replacement CDF files are installed.
They are the standard 1.28E ones with additional files added which the
TM2 system needs, so they are totally compatible with all previous versions
of 1.28E

The TM2 system needs to have a "EAWTM2" folder in the EAW folder.
This folder contains the default the "BumpVal.eaw" file which is read if there is no
"BumpVal.eaw" file in the root folder.
This file maps the terrain tiles to their corresponding "BP*.TER" files and is essential.
Only people who make new extended terrain tile sets will need to hane their own
"BumpVal.eaw" file in the root folder, so there is no need for anyone to worry
about this for the time being.
The "EAW32TM_maker" folder contains a utility which reads a "eaw.tm"
file and makes a "eaw32.tm" file which the TM2 system uses in place of "eaw.tm".

The "BatchFile" folder contains a batch file which creates three additional "BP*.TER" files
in terrain sets which have their own "BP*.TER" files.
The three default ones ate in the extended TERRAIN.CDF.

The "DirSetPicker_stuff" folder contains folders containing the "eaw32tm" file
for the scenarios downloaded to use with the DirSet Picker from my web page.
None are needed for scenarios which use the standard tilemap, such as "ETO_01",
"SWOTL" and "ModSqaudBoB".


Finally, for testing purposes

There in a "G-sillyTM2" folder in the "OAW128" folder.
If loaded it puts the high res and low res versions of the 65th tile (Tile64.TR) in the
EAW folder.
It puts a modified "eaw32.tm" file in the EAW folder in which all references to
tile #2 (water) have been replaced with #64 and a snowy city tile appears where
the sea should be.
In order to do this the exe needs to know that there are 65 tiles instead of the default 64.
This is achieved by the loading of a "NumTiles.eaw" file from this folder.
"NumTiles.eaw" is a simple one line text file- this one reads "65".

Jel
26th December 2011

***********************************************************************************************

The main thing is to test the appropriate eaw.exe with your current system, and then try the 65th tile possibility.



Jel

Please let me know if you are testing it

Jel

Hello Jel - what is the drill for the most up to date 128E setup?

Moggy DCM

Moggy!
Check my webpage for links to the basic install and Ralf's posts re V10.

Pobs & Co



This is a new version of V7 which has a vertical scrollbar in the tile selection panel which accommodates up to 256 tiles.
It now reads the "eaw32.tm" file.
The tile number and orientation is shown.
That is all I have done so far, but it is a good start.

Jel

Jell,

well done mate, the new editor looks fine

I don't have time tonight (family commitments), but I will try the new system out tomorrow...


cheers,



Pobs

If you do I'll send you the new editor- I have just finished it

If you guys want a tile set with a few extra tiles ready to test you can grab a set of the EAW Demo tiles from WOB. There are 71 tiles, I think, including some coast tiles and extra road tiles.

Here is the link: http://www.sandbagger.uk.com/WOBT/Demo/EAWoriginaltiles.zip

Hello Tony.

I know you have not set any descriptive file names in the exe or your editor so here's an idea. Just extend the ranges of the existing tile name which we are all familiar with, with a few new ones.

BNRoad to BNRoad20
BNRiver to BNRiver20
BNMount to BNMount10
BNForst to BNForst10
BNField to BNField20
BNCosst to BNCosst20
BNAlcty to BNAlcty20
BNCanal to BNCanal20 New Canal tiles
BNRivrfk to BNRivrfk5
BNRivrnd to BNRivrnd5
BNRivrbr to BNRivrbr5
BNRivrtr to BNRivrtr5
Bncostu to Bncostu10
BNCosttr to BNCosttr5
BNCostrv to BNCostrv5
BNCostct to BNCostct5
BNCostbr to BNCostbr5
BNCnroad to BNCnroad5 New Canal road crossing tiles
BNTrench to BNTrench15 New Trench tiles for WWI, but could be used for fortified emplacements in WW2

I think that should more than cover your 256 slots and a few extras.

Col the names are flexible in a file named "tilename.str" so the terrain makers can call them what they like.
They may need to watch the 8 character name limit if they want to pack them into a CDF.
I'm really dismayed that nobody seems to be testing the exes, because we need to know that they are working with existing 1.28E scenarios, multiplayer, career etc.

Anyhow I made a new eaw32.tm file with the my new tilemap utility which is using a list with 65 tiles






Jel

Sorry to say I can't spend any time on this until this weekend. I downloaded from the link and will try it out. BTW how do you get the new v7 editor...email? I am kinda slow with such things....maybe why I like terrain tiles....slow work.

Hi Tony.

I don't know about Shawn, but I've never liked this free structure idea.

We need a Default setup to work from, and it simply makes life much easier.

Just imagine if we used a free texture structure for Aircraft skins. It would be mayhem if we had no default names, something I fought long and hard for, and is now any excepted Default.

At the moment, you simply overwrite one terrain with another, but if you have different file names for different file sets, you could end up with lots of glitches.

This is evident from, sorry to say this, Moggy's Iraq, which has custom named tiles in the file set.

With keeping the existing file structure, and simply adding a few new types of tile, and extending the number range of tile types, we retain a semblance of a Default system.

As a 3DZ Builder, I'm still waiting for a complete default list of 3DZ models required for the new 255 Tmod Default World.

All I can do is build something and test it as a Hanger, as I have no idea what slot number it's supposed to be for, so I can't give the texture a Default Grnd**.pcx name as I have no clue where it's supposed to go!

See what I mean Tony?

This is an idea time to start ss we mean to go on.

Thank you very much for your work Toni.
I always say that your work in the near future an inseparable part of our beloved EAW

Thanks BBG!

Col
The way that I see it is that a terrain tile maker would not be starting from scratch but would be adding to an existing set.
So he might make nine extra tiles and name them:

BNCnl1.ter
BNCnlX.ter
BNCnlfk.ter
BNTrch1.ter
BNTrch2.ter
BNLake1.ter
BNLake2.ter
BNSwmp1.ter
BNSwmp2.ter

Then all he needs to do is make a new "tilename.str" file which reads

Field8.ter
Grass.ter
.
.
.
rivrtr.ter
costct.ter
costtr.ter
alcty6.ter
base.ter
field3.ter
field9.ter
river3.ter
Cnl1.ter
CnlX.ter
Cnlfk.ter
Trch1.ter
Trch2.ter
Lake1.ter
Lake2.ter
Swmp1.ter
Swmp2.ter
Til073.ter
Til074.ter
.
.
.

Til254.ter
Til255.ter

His new tile names have replaced Til064.ter to Til072.ter in the default "tilename.str" file.
In the list the first 64 names are the stock ones in the order of the old hardcoded list.
The "NumTiles.eaw" file in the root folder would have the entry "73" and the exe would not bother with "Til073.ter"...."Til255.ter"

Jel

I guess this is what I'm supposed to see?

The original tiles sent by ColG had four terrain tiles which are not in the standard set, so I made use of them.
I created an island south of Hawkinge made using all four of these new tiles (#64, #65, #66 and #67) , plus the standard corner tiles:



It works



Jel

OK, so far, so good.

How's about placing Tmods on them?

...and the next logical step was to test the target editor.
I shifted Hawkinge onto the new island, and took off from there.






There's an OAW "G folder" with this setup and everything it needs here in a 7-zip self installer:

http://www.users.on.net/pam_biddell/G-68TilesTM2.exe

Jel

Seems to work the old fashioned way.

Perhaps some trees now?

Thanks John!
This is a new starting point.
TMods will be fine, we just need to deal with the eaw_ttd.dat now

Jel

Oh, you know me Tony, I test everything in a root directoy, manually, just to make sure there is no copying errors.

So, if it works for me, there is no problem.

Couple of other idiot questions. Where do the eaw32.tm files for the FAW/SAW etc scenarios go? Should there also be filename.str files for those?

Moggy DCM

Moggy

All of the existing scenarios use the same tile names, so they use the "tilename.str" in the "Text_eng.cdf".

I have heaps of Dirset Picker files because I test things, but this screenie should help.
You can see where mine are.



They all have a main folder, and putting the "eaw32.tm" in it will be fine.

In most cases I had used the "eaw32.tm" maker in the folder where the scenario's "eaw.tm" file was located.
I inadvertently have two in Malta.

Jel

Thanks Jel. Seem to have that working now.

Because SAW has its own TEXT_ENG.cdf, had to remove a copy of tilename.str from the new default version of that cdf and pop it into the 128E SAW folder so that the TM2 setup would work with SAW.

I think I have a working 128E setup now, patched up to the latest including TM2. which is a start.

Moggy DCM

That's right Moggy. I should mention that any scenario which uses its own version of the "text_eng.CDF" will need the "tilename.str" in the root folder.
I had forgotten about those.
Also, it a special "terrain.cdf" has "BP*.ter" files in it then ideally the three that need to be created with the batch file need to be made.
The new version of the routine that handles them only runs if the "BP*.ter" files exist, so if the three new ones are missing there is no "Cannot find...." CTD, and you might never even spot the difference visually.

Jel

Okay, done that. Added the three BP tiles to the SAW128E root.

Moggy DCM

Hello, I have tested this on my main computer it is a dual-boot Windows XP Pro & Windows 7 Pro (32 bit)and with both get the winter tile in the water...




I must admit I just followed your directions and I don't really understand how to edit or add the new tiles.

I was was thinking of the fact that we have been able to add 4 tiles already to the terrain layout for a while now and I have worked up 2 summer and a fall and now working on a winter terrain that still only use the original 59 tiles...I was thinking that it wouldn't be great to have it possible for more than 59 tiles but because one doesn't understand how to add them they would just work in the old 59 tile layout.
Just a thought (to get an opinion)...How about adding and kinda like Col.G said come up with some basic names even if the tiles are only used once in the game they will be in there and you could use the editor to add more. I guess if there was a basic set of European tiles a guy like me could paint larger terrain sets without needing to edit the map along with painting 100's of tiles. I would love to try and edit (or add) many more tiles now that it seems possible but I have to get a grip on how to do it...I did use the editor v6 but didn't get a good understanding on how it worked back at the start of Euro-512 tiles but was so excited about moving the tile work forward just said I can add the other 4 tiles later...but still haven't done so.

I just made another test exe and it may give us the choices that some people prefer.
There are four particular graphics routines in the exe which are designed to process a file, but are programmed to CTD with a error message such as "Pic not found BNROAD3.TER!" if the file does not exist.
That was always going to be a problem if we had a long tile list in the manner that ColG suggested.
There would be names in the list which the exe could not find, especially if it were using a 59 or 64 tile system.

The terrain tile loading routines in the exe that I have just made have been modified to check that the tile exists before doing anything else.
If it does exist then the graphics routines involved in loading the tile are "called" and run, and do so without a "Pic not found..." CTD
If it does not exist the graphics routines are not called.
So this exe does not CTD through trying to load a terrain tile that does not exist.

Shaun

The more tiles the merrier!
There are people who make tiles, and others who make terrains using them.
Currently we have 64 to select from. Nobody says you have to use all 64 in a new terrain.
However, having a wider selection to choose from would allow terrain makers to produce some much more interesting terrains.
Just make some additional tiles and we will have a shot at using them


Everyone

Happy New Year!

Jel

Yup,

I second that, we can add new tiles to existing terrains fairly easily, Jell do you know if your 'tile replacer' will work with more than the original set of tiles ? it is very handy to swap a whole tile throughout the map in one go, especially if we want to edit an existing map....


cheers,


Pobs

It would be really easy for me to write a tile replacer for TM2. Probably the best place for it is in the TM utility allowing a global replacement.

Jel

There is a new download available for testing. It is the one referred to in my response to SagginB.
The link is in the "1.28E users" thread.

Jel,
tested with all scenarios.....all ok.
AO

Nice progress Tony!

I haven't had a chance to try it yet.

One thing exciting about the extension of available terrain / tiles I think is that geographical areas / climate can be more diverse.
So for instance one terrain might have complete deserts,
green valleys, alpine, snowy peaks / bare peaks, tropical, artic, farmland, rocky coasts / sandy coasts etc.

Also I should be able to make my water tiles match coasts in the various scenarios now.