Problem with "background script"

[BrunoBrotto]

Ok, I understand. I think I wil need to buy more RAM for my pc.... I have 1gb already, but I think it's not enought, Am I right? Thanks with the help!
(Again, sorry for my english... )

[Mediolanicus]

I think you'll need at least 2gig to play EB as smoothly as RTW, and even then...
But anyway EB is playable with less RAM. My pc has a mere 512MB RAM, but EB is perfectly playable (although it more that occasionally lags..)

P.S.: You're English is fine. Half the people on here don't speak English as their first language either - and I'm one of them.

[BrunoBrotto]

Ok, Thanks with the help. I will buy more RAM for my PC or maybe a new one in Christmas . Therefore, this a great mod, and I wish in future I can play it without problems!
Thanks about my english, I'm trying to learn in a english school in my city... but I think I have to study much more ahhahahah!

[Ymarsakar]

I had the same problem, and since I use esdf to move in first person shooters and RTS games like RTW, I literally had to have my keyboard scrolling.

So I went into the EBBS background script and removed all the client ruler code that was taking up something like 5 or something megs.

The keyboard scroll still wasn't as smooth as the original, but it was manageable.

If you wish to do the same, simply go to your EB folder/data/scripts/show_me

Open the EBBS script file with a text editor or word editor.

Look at the table of contents, copy the "client ruler line" and then search for it. You should get a line of code that has been commented out (with a ; in front) that says Client Ruler section or something close to it.

Now erase all of the code there, through highlighting via holding down shift and hitting mouse, untill you get to the next section. How easy this is for you depends upon whether you can make sense of some of the code and what it is for.

Now you won't be able to spawn client rulers when you build Level 4 MICs, but your scrolling will be fixed. And besides, I didn't need client rulers after I had gained lesser celtic generals.

Btw, once you slim down the EBBS code, the speed at which your computer processes EB turns increases by some 50%-100%. This is probably due to the fact that the Client Ruler code is checking EVERY city on the campaign map for client rulers and gov4 buildings, which wastes processing power. You could speed it up even more by removing the code for reforms, but I was satisfied with things as is.

You can still build level 4 governments with the background script removed, and it didn't crash my Romani campaign in the 70 odds years I have been playing it.

However, you will get the "interloper" trait if you put one of your generals/family members into a city with a level 4 government. This can be solved by going into the EB/Data folder and look at the export_descr_character_traits.txt file

Search for "Interloper" without quotes. You will find lists of code saying "Affect Interloper 1 100" or something similar to that.

The 100 is the percentage. Change it to 1. Or if you want a perfect solution, change "Interloper" with "ReverseInterloper". I've recently tested it out, and it's good.

Btw, I didn't have your problem with the battle map. That is probably a graphical/ram/cpu issue. Which you can reduce by looking up the EB performance FAQ somewhere here. Essentially, you should keep your unit size to small or normal and cut down on some of the graphics/textures/shadows.

And I also don't think the keyboard scrolling on the campaign map lag problem has to do with CPU either, since my mouse scrolls quite well. It is when you hit a key that things slow down, perhaps connected with script processes being interrupted or something.

[bovi]

That's actually one of the pieces of the script which is sort of safe to remove. Perhaps you would like to post your files in the unofficial submods forum, so others who get too low performance won't have to do them on their own?

[Ymarsakar]

Done, in the unofficial mods forum.

[Lgk]

Oh, it's here too...

Already posted in another thread that setting CAMPAIGN_MAP_CAMERA_SMOOTHING:FALSE option in preferences.txt file should help. What happens methinks is that processing the huge script confuses i/o routines so constantly pressed keys are sometimes perceived as "released" and hence map scrolls in very small steps, like it does when tapping arrow keys quickly w/o activating the script.