I guess I'll add a little textbox to mine which says "1615"Inferis said:For the record: there's no GUI whatsoever, so you'll have to wait until somebody decides to write one before you have a dialogbox.XieChengnuo said:
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Depends on your machine. If it can manage the export and import of the full map, and it can work with a 3 layer PSD file of size 18944x7296 (you do the math), you'll be able to edit the map in a whole.Mr. Capiatlist said:
Otherwise, you'll have to do it part by part, depending on your machine limit (larger parts, more demands performancewise).
You made a good point however: I have no way to create an empty map ATM: I'll include a /create option in mextract to create an empty map instead of extracting the existing map.
Will your tools ignore extra layers in the PSD? Will it look for particular layer names?Inferis said:
Also, what happens if the map exceeds the 16 meg limit? Just an error returned or partial drawing?
Other layers can be there. They will be ignored.WiSK said:
mimage will look for layer names. Since you can have multiple layers with the same name, I also have to say that it will take the first layer found (with the specified name). There's also currently a bug in the PSD code that causes the layers to be locked in Photoshop, but since you can duplicate them and continue editing on the duplicate (and throw away the original) that's not a very important problem.
There's no checking in valid input yet. If you fuck up, the (eu2map) file is likely to be left corrupt. I'll add stuff like that layer (probably a mcheck tool, I dunno).WiSK said:
The tools in their first version will be very rudimentairy and probably will contain a buttload of bugs.
o I have to admit I'm not very good at testing my own code. But I guess I'll have you people for that.
Last edited:
Perhaps we'll find a use for Hive after allInferis said:The tools in their first version will be very rudimentairy and probably will contain a buttload of bugs.
I think I've decided to go with four layers instead of your three, Inferis. I did some experimenting with 'guessing' the nearest province when a border crosses a river. This was okay, but leads to some inconsistant results for me. Especially the fact that in the original lightmaps many borders are divided lengthways such that each half is on opposing provinces. I couldn't recreate this effect consistantly.
So I'm planning the following 'layers': shading, provinces, borders, rivers. When you extract the provinces, you get no river provinces whatsoever, instead the rivers are covered over by their neighbouring provinces. This is much more consistant, since in the original lightmaps 'pure' river nodes (where province descriptor primary id is a river and there is no river id part in the descriptor) are always surrounded by a single neighbouring primary province.
I think this will allow the user much more control over how the borders and rivers will look in the game. On the downside, an extra source layer is another few hundred megabytes on disk.
So I'm planning the following 'layers': shading, provinces, borders, rivers. When you extract the provinces, you get no river provinces whatsoever, instead the rivers are covered over by their neighbouring provinces. This is much more consistant, since in the original lightmaps 'pure' river nodes (where province descriptor primary id is a river and there is no river id part in the descriptor) are always surrounded by a single neighbouring primary province.
I think this will allow the user much more control over how the borders and rivers will look in the game. On the downside, an extra source layer is another few hundred megabytes on disk.
WiSK said:
But that problem is that the current lightmaps do not have that overlap, only the parts that are under a border have the complex encoding (with adjacenties). While you could generate all 4 layers for those pixels, the parts of the rivers not covered by borders is something else. Although you could argue that you could use the "find-nearest-province" algorithm to fill those in for you.
I don't know... I'm not sure the added accuracy weighs up against the added complexity for editing.
That's what I meant with the following:Inferis said:
The important thing is that those 'uncovered' bits of river are easier to match with a province than the borders are to split. For me at leastWiSK said:
That's the thing, in my head I'm looking at a different model for the source maps I guess. If it turns out to be unusable, I will change it. I do see that your model is easier for the user, but I think the whole thing is probably going to be more complex than some people expected anyway.Inferis said:
My machine? If you mean computer it is the latest Gateway.... if you mean my Photoshop it is 7.0 public version. What are the other two layers for? Right now my map is one layer....Inferis said:
Have a look at Inferis' example psd demoMr. Capiatlist said:
Are you going to fix the download link on your site? My boss is at a client all day tomorrow, so maybe got some time to playInferis said:
Check mail...WiSK said:Are you going to fix the download link on your site? My boss is at a client all day tomorrow, so maybe got some time to play
To edit the full map, you'll need A LOT OF MEMORY (and harddisk space).Mr. Capiatlist said:
File size = 18944 x 7296 x 3 x 3 = (mapsize) x (bytes per pixel) x layers = 1.243.938.816 bytes or 1.15 gigabytes.
Opening this in photoshop will be one thing, but extracting, exporting and importing will take it's toll too (which will be even larger, probably).
Clear now?
Inferis do you have some numbers as to exactly how much memory we'll need? right now i have a gig of RAM and 130GB of space -- is that enough?
As a beta tester for Inferis, I'm proud to show you all my first rather successful edit to the map:
Having said that, though, I must also say that the editor still have a number of bugs - some of them being quite big, actually (if I hadn't cropped this image, you would see huge chunks of weird PTI placed in random positions all around the map for some reason).
So it will probably take a while before he have an editor usable for "real" editing ready. But he sure is on the right track!
Having said that, though, I must also say that the editor still have a number of bugs - some of them being quite big, actually (if I hadn't cropped this image, you would see huge chunks of weird PTI placed in random positions all around the map for some reason).
So it will probably take a while before he have an editor usable for "real" editing ready. But he sure is on the right track!
1 gigabyte of RAM should be plentyXieChengnuo said:
As the other alphatester, I was busy cutting a strait between Kyushu and Kansai. No screenshot I'm afraid, cos it didn't like the modified adjacenciesHive said:
EDIT: my bad, I used the wrong parameter: /G2 instead of /G ... screenshot coming up ...
Inferis said:
I dropped one of the Greenland provs, and instead merged them (as well as added the Greenland PTI, so that Greenland is now 1 huge province).
Well, it's a bit rough, but I made a bit of sea between Kansai and Kyushu (click for screenshot). It's not a proper strait because I still have to exchange the province id's for those of Kent and Calais. Be interesting to see if that works
WiSK said:Well, it's a bit rough, but I made a bit of sea between Kansai and Kyushu (click for screenshot). It's not a proper strait because I still have to exchange the province id's for those of Kent and Calais. Be interesting to see if that works
That reminds me of my own sketches of a new Japan:
Though I'm not sure about that Calais/Kent thing.... because if Johan then removes it in a future patch, Kansai and Kyushu will be cut off from each other...