Well, I still can't get it to load, but I think I've made progress. I believe the memory error message was due to having a texts.txt file that was not empty - I copied it from the Slot? Also, I checked my map_t.tga and discovered that Photoshop had somehow altered it. So I created a new one from my saved BMP, using GIMP. I've read about this problem elsewhere in here, and it seems to be true - stay safe and use GIMP to create your tga's!
Now I am still getting a load.ini error, and I can't figure out what is wrong...
sure...I'll give it a try out :wink:
Thanks fabianfred! So let me see if I understand this correctly: All I need to do to get it to load is change my map_h and map_t to grayscale instead of RGB?
I'll have to look and see what the problem is with the alignment. I did notice some SRTM data problems - little bumpy areas here and there - but it's possible I could have somehow screwed up my alignment when I cropped the images to get the 32x dimensions. I tried to crop each in exactly the same way, but maybe I didn't.
Yeah, map_F was just a place holder, to see if that was what was keeping it from loading.
ideally, alignment should be done all together....
load the MWmap_c tga into Photshop at its correct size........then load map_t and map_h into PS... but upsize them to be the same scale as map_c...then move them on top of map_c as new layers
adjust them as layers...moving and changing their opacity as necessary...as each is aligned then lock them together....when all done......make only the layer C as visible then save it...then do the same with map H and map T...save them as new tga's greyscale no compression
after that reload the T and H tga's and resize down to a quarter of C
all should then align correctly....... but your sea bumps may not be misalignment...... but just need the edges of their skirts pulling down at the water/land interface...using the blur tool in FMB
Thanks. I attempted the layer method first, but ran into problems with the size of my images (map_c was pretty huge). Since then, though, I've transferred my work to a better computer with far more RAM.
But I think it's not an alignment problem. I will try the blur method you speak of. Plus, like I said, I know of some SRTM data anomolies on some of the northern islands, that I will have to address by hand.
Fabianfred, many thanks for looking at the map and finding the causes of non-loading. Re textures and actors.static, I used the load.ini from Big_yamato's West Java map but progressively deleted items in order to find the cause of non-loading including the textures lines. Didn't think textures were relevant at this stage since I hadn't applied any. I used a blank actors.static since I hadn't added any objects to the map (couldn't add anything since it wouldn't load in the first place).
As for the incorrect naming of ed_m01 and 02........ :oops: :oops: :oops: I can't understand how I missed that mistake given the number of times I checked stuff........ but obviously my checks weren't good enough. Missed the info on unticking compression along the line too- can't remember having read about that.
I'll correct the deficiencies, once the map loads first thing to do will be to check the coastlines for any anomalies resulting from changes due to development over the years, though I don't think there will be many (at least I hope not!).
so all your alterations to the map size/scale thinking size was the problem... perhaps you can go back to an earlier version now :wink:
Now I am just tearing my hair out... I changed my map_h and map_T to greyscale, and even re-sized my ed_m02, but I am still getting an immediate load.ini error (same as on first page of this post). I have searched and searched my load.ini and map folder, but I can't find any inconsistencies.
fabianfred, are you sure there wasn't anything else you had to do to my files to get them to load on your machine?
Both Canon and Ash use a mapF twice the size of map t/h.......
and ed_m01 is same size as F.....02 same size as t/h
Dleg when you changed t/h to greyscale and resaved did you compress?...should not (they are 9,096kb each for me)
don't forget you guys.....when map has loaded into FMB....press Shift/tab to see any error messages
that helped me see where the problems were