HoI2 Patch Project

[Gen. Skobelev]

I've gotten a nice mail from paradox today....

Most excellent news. And the possibility of free distribution indeed makes it to be indeed "just" bugfixing.

Are there any HSR modders left to enjoy the new EU3 engine then?

Don't know what will come of it but HSR site there has been some activity regarding 2.09 release for Armageddon.

 

[unmerged(96109)]

Good news, White Daimon!

I agree with you, we should go for a) a patch, b) people already having coding-experience c) the group of names you mentioned is enough d) add more people if needed, not otherwise.

I hope I can contribute somewhat in testing and giving feedback.

 

[rich-love]

Excellent news! I'm looking forward to getting started.

 

[theokrat]

So, shall we get a forum then? I propose a subforum for each bug where we can exchange ideas what part of code would have to be changed in which manner...

 

[coreymas]

Theokrat,

I suspect that there will be a sub-forum where users who have been registered with paradox as developers can go and communicate etc.

I also suspect that Paradox will offer some kind of a Bug tracking tool (like Mantis) where bugs will be registered and assigned to individuals to work on.

The bug tracking tool will take care of code sharing.....

Corey

 

[Gormadoc]

This looks very promissing indeed. Can hardly wait to see what you can come up with.

As already mentioned, you should feel free to add any part or all from the CDCP mod as you see fit, to this patch project.

If needs be i can probably be of assistance to make the files compatible with what you like to have done.

Some small bugs you might want to look into. If already mentioned plz disregard.

The F10 message options window. Where one can change which and how messages gets displayed.

There are 5-6 entries in that list that says "When we succeeded to send a spy" cant remember which spy missions are missing. I checked the config files, they are correct, so it is a code problem, it sends the wrong strings.

The "set_domestic" & "domestic" event commands calls the same message string. So they both say domestic vil be moved X number of steps. Instead "set_domestic" should state that it gets set to X. Tried to search the exe file for a set_domestic string, but was unable to find anything, so i gues the string does not exist. Also there is no config message for the set_domestic, so it would mostlikely require that you add such a string to the exe if possible.

small things i admit but nevertheless....

 

[coreymas]

I am willing to look at the smaller bugs first (like the string message one) as it will help me get my feet wet and is something that is readily apparent once it is fixed.

After that I was going to start to look at more significant bugs (like the Par Bug introduced in 1.2 Arma).

Has everyone agreed that we are going to concentrate on the latest version of Arma as a first priority?

Corey

 

[Hagar]

Agreed, as far as I'm concerned. I even wonder whether the other versions would warrant the effort really. The large majority of CORE players was already using ARM for the last release, which was a major consideration to make the upcoming one a dedicated ARM version. I'm not deadset against it, but...

Oh, and a personal favorite of mine that I really would like to see fixed is the need to have dummy files (for tech imagery, tech team imagery, as well as some game files IIRC) when using moddir.

 

[IndoEsia45]

What about things like Concurrent Versions System or CVS for this patch poject ?

 

[coreymas]

Oh, and a personal favorite of mine that I really would like to see fixed is the need to have dummy files (for tech imagery, tech team imagery, as well as some game files IIRC) when using moddir.

This actually might be as simple as introducing an If statement (or try/catch block) that says if there are no files here don't crash kind of thing

Corey

 

[rich-love]

Agreed about the most recent version question. I'm waiting to see what Paradox offers us (if anything) regarding version control, defect tracking, and the like. I'm especially curious to see how they organized their code.

Question: do we still agree to focus on those defects that are identified in the "Cumulative bug list" thread? If so, Gormandoc, do you maintain a list of those defects that CDCP fixes?

 

[coreymas]

Question: do we still agree to focus on those defects that are identified in the "Cumulative bug list" thread? If so, Gormandoc, do you maintain a list of those defects that CDCP fixes?

This brings up an interesting dilema.

Do we do code fixes where configuration fixes fix the code bug?

Example

if we put a certain value in a config file (like we do to correct the Para bug issue in 1.2 Arma) to fix an error in a mathematical calculation in code do we fix the mathematical calculation to function as it is supposed to be or leave it alone...

Corey

 

[De_Genius]

I agree that we stick to the cumulative list of bugs in Arm 1.2 as our main priority numero uno. Some of these seems easy to fix, some are not.
I hope to get our own forum and some kind of versioning. CVS or SVN is always an option, but if Paradox provides something else for us to use, I say let's use that.

P.S. I am sooo excited to get my hands on the code. It is way better than any Christmas eve in years.

Question: do we still agree to focus on those defects that are identified in the "Cumulative bug list" thread? If so, Gormandoc, do you maintain a list of those defects that CDCP fixes?

This brings up an interesting dilema.

Do we do code fixes where configuration fixes fix the code bug?

Example

if we put a certain value in a config file (like we do to correct the Para bug issue in 1.2 Arma) to fix an error in a mathematical calculation in code do we fix the mathematical calculation to function as it is supposed to be or leave it alone...

Corey

In that particular case I would definately prefer to fix the actual programming code instead of "fixing" it by use of parameter. By fixing it in a config file we risk that the bug will just show up again in another part of the code, which could have been avoided completely by correcting the code.
At least in this case it seems fairly obvious what is wrong and thereby how to fix it. In more severe cases we can discuss the outcome.

 

[theokrat]

We should fix the bug by code. If only to allow modders to actually use the paratrooper eff. to a higher degree.

I agree to suing the cbl, but with actually reconsider every point. 32 and 33 for instance are not bugs.

Germadoc:
I figure we can use all things that are not workarounds. So if you can provide a package of all typo fixes and stuff, that would be useful i guess.

 

[The Great Duck]

Speaking of the bug list,can anyone give a link?

 

[unmerged(37697)]

Speaking of the bug list,can anyone give a link?

Found two:

(Sorry... LOL) :rofl:

 

[Kouei]

Speaking of the bug list,can anyone give a link?

Here ya go: cumulative bug list

 

[Kouei]

Has everyone agreed that we are going to concentrate on the latest version of Arma as a first priority?

I agree. I have no idea of how many players prefer older versions of HoI2 or how many own the different versions, but I'm definetely more interested in Arma 1.2 than any other version.

 

[Kouei]

Do we do code fixes where configuration fixes fix the code bug?

Example

if we put a certain value in a config file (like we do to correct the Para bug issue in 1.2 Arma) to fix an error in a mathematical calculation in code do we fix the mathematical calculation to function as it is supposed to be or leave it alone...

I would prefer correcting the code. It will be more work and maybe we won't have time to fix as many bugs, but at least the ones that we take care of will be fixed properly.

 

[unmerged(76495)]

Hmmm...... Paradox has not responded in 2 swedish working days whether I can forward the contract. I don´t think they will have anything against it, but you known I really don´t want to do anything yo jepordise the project. But on the other hand, I would like you to read it and keep the project going. Suggestions?

I agree with Coreymas that easy fixable bugs should be at the top of the list. I personally find it much easier to get an understanding of how a large piece of software is constructed if I have a very specific initial task to solve rather than simply wandering aimlesly through the code.

Regarding older version: I think it only takes slightly more effort to do both rather than simply ARM, because a lot of the bugs in ARM 1.2 existed in DD or HoI2. And its pretty safe to say that the code portions that contain the bugs likely haven´t seen much change since HoI. So it would be kinda easy to adopt a solution developed for ARM to be used with DD or HoI.