RFC Europe Files

Just tried to start RFCe with the new patch but it crashes in the very beginning at loading the mod. :/

BAD NEWS! Updating the mod to 3.19 is far from trivial. Firaxis changes the .dll interface and it will take some time to update the mod. Changes in Python will also need to be done. I honestly thought that they were done with updating the .dll. I will ask in the main RFC forum page to see how Rhye has done it.

Basically it will be impossible to run simultaneously two versions of the mod. I guess at this point we have to make a decision on whether we should make everyone who is using the mod switch to 3.19. I guess we should do that.
 
BAD NEWS! Updating the mod to 3.19 is far from trivial. Firaxis changes the .dll interface and it will take some time to update the mod. Changes in Python will also need to be done. I honestly thought that they were done with updating the .dll. I will ask in the main RFC forum page to see how Rhye has done it.

Basically it will be impossible to run simultaneously two versions of the mod. I guess at this point we have to make a decision on whether we should make everyone who is using the mod switch to 3.19. I guess we should do that.

I've restored RFC to 3.17 and the mod works fine. I suggest leaving it until Rhye issues a 3.19 patch for RFC.
 
I've restored RFC to 3.17 and the mod works fine. I suggest leaving it until Rhye issues a 3.19 patch for RFC.

The patch is already out there, however, the changes from our mod to Rhye's are already too many for that to help.

There has to be a relatively easy way to do this, however, I cannot figure it out and the hard way is well - too hard.
 
It might not be too hard to do with SVN as described here. Hmmm... quite a conundrum. On the one hand, we're going to have to move to 3.19 at some point, on the other -- if we move before most people update then people won't be able to play our mod. I'm pretty sure nobody wants us to have two versions available concurrently.

Really, the merging will be about as difficult if we do it now versus later. I would propose we hold off on merging in the 3.19 changes until Rhye releases a version of RFC that works with 3.19. That will probably be the point at which which most of our play-testers can reasonably be expected to upgrade.
 
It might not be too hard to do with SVN as described here. Hmmm... quite a conundrum. On the one hand, we're going to have to move to 3.19 at some point, on the other -- if we move before most people update then people won't be able to play our mod. I'm pretty sure nobody wants us to have two versions available concurrently.

Really, the merging will be about as difficult if we do it now versus later. I would propose we hold off on merging in the 3.19 changes until Rhye releases a version of RFC that works with 3.19. That will probably be the point at which which most of our play-testers can reasonably be expected to upgrade.

3.19 comes with a working version of RFC. The complexity our code will pretty much make SVN useless. We have created too many changes. There is pretty much no resemblance between the RFC code and our anymore. For once, we only use dynamic memory allocation.

I have started the merge, right now everything loads until we hit initializing fonts. Then it all crashes. I will keep on working.
 
This last week I had over 30 free hours which I dedicated to this mod. Unfortunately over 15 of those had to be spend under the tedious task of converting the code to BtS 3.19. It was almost as bad as going back and redoing all the changes I had originally made to the .dll file (and that means a lot). I just hope Firaxis doesn't make me go through his one again.

The code migration might not be clean yet. Please report any and all bugs with a savegame (if possible).

Our mod is steadily approaching a "beta" version. We will have reached a beta when all the features that we want in have been implemented and all that remains is to put our efforts into testing - bug fixing - balancing.

I did not manage to put in all the features that I wanted, however, the list is pretty comprehensive. More work will be done in every area, however, the mod has grown to something more than what I was initially hoping for. Most civilizations are completely playable and people (including myself) are having lots of fun. Almost a year ago (Aug 15 2008) I released the first version of RFC Europe. I called a test version, since that's what it was, a test to see if I can understand some of the very fundamentals of the code. There was only one playable civilization (the Byzantines) and st Lucifer's first version of the RFCE map. Interesting trivia is that the first test version was only 38MB compared to the current 85MB (zipped). In view of that, I don't think it is fair to keep calling our current level of development "test version".

Today (exactly 301 days later), for the pride of the entire development community, I present:

RFC Europe version ALPHA 1

(available from the first post of this thread)
 
Great job! Though I'm not ready to update yet until Rhye gets his version fixed.:cry:
 
Well done, 3Miro. Much sooner than I expected as well. I've now upgraded to 3.19. Wiped all previous files and loaded RFC Europe Alpha1. (nice name too!):goodjob:
Played a test game as Burgundy until getting the first UHV in 1200AD. Very smooth so far though there was a period early in the game where the wait between turns slowed right down for awhile but speeded up again. Also Spain start is out of sequence on the start menu. Otherwise no bugs so far. Fingers crossed.:D
 
Great job 3Miro! :goodjob:
 
Great job! Though I'm not ready to update yet until Rhye gets his version fixed.:cry:

The 3.19 patch automatically updated Rhye's mod. His is an official one and Firaxis does not give out a patch unless RFC works with it. You can just update your game now you can play either RFC or RFCE.
 
I believe BTS 3.19 only includes RFC 1.181. I might be wrong.

I think that's right. The 3.19 patch only enables RFC 1.81. Rhye says he'ill update it for 3.19 in his 1.185 patch.
 
There is a patch that fixes the barbs problem, it is a big drawback for the gameplay so I had to release a patch immediately (the change is too small for a complete new version). Get it from the first post of the tread.
 
There is a patch that fixes the barbs problem, it is a big drawback for the gameplay so I had to release a patch immediately (the change is too small for a complete new version). Get it from the first post of the tread.

Sorry to be a noob. I tried putting the patch into Assets but it stands alone. Is there a file in Assets that it's supposed to replace? I can't find anything that even looks like "GameCore dll.". Is it in Python or XML or what ?:confused:
 
Sorry to be a noob. I tried putting the patch into Assets but it stands alone. Is there a file in Assets that it's supposed to replace? I can't find anything that even looks like "GameCore dll.". Is it in Python or XML or what ?:confused:

Sorry you have to unzip the file and it will create a CvGameCoreDLL.dll file. That is the one that replaces the existing file in Assets.
 
Sorry you have to unzip the file and it will create a CvGameCoreDLL.dll file. That is the one that replaces the existing file in Assets.

I did. I unzipped the file to the Assets folder. Does that mean I replaced a CvGameCoreDLL.dll file that was already there?
 
I did. I unzipped the file to the Assets folder. Does that mean I replaced a CvGameCoreDLL.dll file that was already there?

It should have done that. Check the barbs, use the WB and make some barb units next to your borders and see if they will attack.
 
Back
Top Bottom