Home Trending Latest threads New posts Developer diaries

Magellan 1.0

Jump to latest Follow Reply
  • 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.
17blue17 said:
4) The file is always a regular csv-file type (as long as you save it as a csv-file type in excel). It just continues to permanently display in excel in columns once you have asked excel to do this. In other words you asked excel to display a ";" as a column. The file still has the ";" but excel displays it as a column. I have never found a way to undo this but on the other hand there is really no reason to want to undo this. This has no impact on the game.
Click to expand...
This is not true. Just now (to test this theory) I opened the vanilla .csv file in Excel. I changed from semicolons to columns, and saved the file as a new .csv file with a different name. I opened the .csv file in Notepad, and it showed up with spaces between and no semicolons.
 
deallus said:
This is not true. Just now (to test this theory) I opened the vanilla .csv file in Excel. I changed from semicolons to columns, and saved the file as a new .csv file with a different name. I opened the .csv file in Notepad, and it showed up with spaces between and no semicolons.
Click to expand...

When I try the same thing it works as I described - columns in excel and ; in note pad. Are you saving it in excel using "save as" then "save as type" with the choice CSV? it is not enough to name it .csv but you have to choose the file type of csv. I have been doing this almost every weekend for the last 2-3 years with no problems. If you try again and keep having this result maybe there is a bug in the version of excel you are using - I use excel 2000.
 
When I choose filetype, the standard choice from Excel is "Text (tabulated) - txt", and write the file name I want (for instance province.csv). I use Excel 2000.

I just tried to save it using the .sdv file type setting, that worked like a charm. I can live with having to split the columns every time I open it.
 
Here'swhat you need:
Go to www.OpenOffice.org download the pack and install it (you can choose which programs you want in this case you only need the Calc)
When installed open your file with OpenOffice Calc and then there comes a popup do this:
Clear the Comma( , ) button and click the semicolon( ; ) button and then where it says ( " ) dunno the name in english mark it all and press delete and press ( OK )
you can now edit and when you save it press ( Save ) and then a popup comes press ( Yes ) and then it's saved:D
 
OK, let's take an example.

The province.csv file is full of 2020 fillers, and the first province I want to edit is province #19, which is a coastal mountain province. When I have edited it and injected the province.csv file into the eu2map-file, shouldn't province #19 appear yellowish brown in mview, like it does when I use mview on the vanilla map?
 
@deallus: how have you created the eu2map file? Was it created "empty" or extracted from EU2? mview doesn't show colouring on the map if it doesn't have access to a colorscales.csv. This file is embedded in the eu2map file when you extract the map from EU2, but it's not there when you create a new file.

Currently, there is no way to manually insert the colorscales info into an eu2map file. If you really need it, I might code an extension to mextract or mimage (or whatever) to handle that...

@cooltoxic: I have a new version ready, I'll try to deploy it asap (I don't have the source handy here).
 
Inferis - I would like to learn.

Would you please explain what I was doing wrong when I exported a region of an existing map, then changed the name of a province that crossed a region boundry, and then brought the .psd back into the map file with the result that the map items to the right of the boundry slid down. I see other areas on the Mymap version that I am working with that have a similar effect - mainly in sea zones - so I can't be the only one who has this problem - is it a bug or am I doing something wrong?

Also you mentioned to Deallus how the province.csv connects with the colors on an existing map. I don't understand. If I take an existing map and want to draw a new province - say Hong Kong - I need to draw and color this in a .psd file - don't I? Or are you saying somehow what I enter in province.csv will somehow color it for me? Or are you saying that if colored correctly in a psd and if correctly entered in province.csv the province will display the color correctly in mview?
 
First off all you need to seperate the two "colors" the first you talk about we call "province ID color" and the second we call "terrain color", it's the color that is determined in the colorscales.csv and the color you see on mView when looking at the "normal" map and the province ID color is the color you paint with on the "ID's" layer in a PSD file and the color you see on mView when looking at the "IDs(lightmap)" map.
 
The first thing you mention is probably a bug. I haven't been able to look at the file you sent, so there's no fix yet.

About colouring provinces: the colours your draw in the PSD file are not actual colours used in the game: they are solely used for identification purposes. That's why you can't use whatever colour you want. As for visuals, you can only draw shading: how dark or light a pixel will be, but that's about it.
EU2 colours the province according to the terrain you've assigned to it: this is defined in provinces.csv, and the colour is taken from colorscales.csv. In effect, there is no colour information in the map files.

Is that a bit more clear?
 
Inferis said:
The first thing you mention is probably a bug. I haven't been able to look at the file you sent, so there's no fix yet.

About colouring provinces: the colours your draw in the PSD file are not actual colours used in the game: they are solely used for identification purposes. That's why you can't use whatever colour you want. As for visuals, you can only draw shading: how dark or light a pixel will be, but that's about it.
EU2 colours the province according to the terrain you've assigned to it: this is defined in provinces.csv, and the colour is taken from colorscales.csv. In effect, there is no colour information in the map files.

Is that a bit more clear?
Click to expand...

Thank you
 
cool-toxic said:
First off all you need to seperate the two "colors" the first you talk about we call "province ID color" and the second we call "terrain color", it's the color that is determined in the colorscales.csv and the color you see on mView when looking at the "normal" map and the province ID color is the color you paint with on the "ID's" layer in a PSD file and the color you see on mView when looking at the "IDs(lightmap)" map.
Click to expand...

Thank you
 
Inferis said:
The first thing you mention is probably a bug. I haven't been able to look at the file you sent, so there's no fix yet.
Click to expand...
I think that was random bug if modified province in border map
for example province with x-coordinate from 18912 ---> 32
that was in idgrid region A or C in the image below
idgrid.jpg

for some province magellan tool miss read that coordinat like that province was in two separate part. So if we type that id in mview will go to central map.
I just remember after mextract vanilla map, that bug appear in second sea province from upper map.
i've platest just add one province in border of empty map. that bug will appear in fifty-fifty.
 
Last edited:
Inferis said:
Would anyone mind that I release the next version as a .Net Framework 2.0 version instead of the old 1.1?

The only hassle this will cause (at most) is that you'll need to install the 2.0 framework.
Click to expand...

what ever is easier for you. Microsoft windows update has been pushing 2.0 anyway.
 
Inferis said:
Would anyone mind that I release the next version as a .Net Framework 2.0 version instead of the old 1.1?

The only hassle this will cause (at most) is that you'll need to install the 2.0 framework.
Click to expand...
As long as you make this fact known (and easily visible) on the web site, I have no complaints.. :)
 
You must log in or register to reply here.
Top Bottom
Back