A new crash
 

The Nagot gick fel box, it says:

lic: bad lnr

It happens during the AI turn phase.

Re: A new crash
 

Look, for us to help you we need a lot more information.

You now basically said:

It doesn't work anymore.

What machine are you using, what age, mods, how long was the game running, any other relevant information you can think about?

Re: A new crash
 

When a problem has been seen many times the error message is often enough to ID it. Since the message isn't in English I have no idea of how informative or not it might be.

Win7, just over a year old.

Mods: Better independents, Endgame diversity.

Running: It's reproducible--load the turn and it will crash every time.

Re: A new crash
 

It is an error message. Even when in english it is hard.

Also, how long has your game been running (two turns, ten turns, 303 years). Is it MP/SP, which versions of the mods are you using? Did you buy the game or pirate it? (Copy protection issues will not be supported ;) ). What version of the game are you running? Etc. (Look, when I ask for more information, I really appreciate if you give it to me. You didn't even answer half the questions I asked).

Did you already search the forum for this error message? Google?

Run the game using the debug flags. What lnr is the error message talking about? (And is this the only information the error message gives or is there also a number behind the lnr).

Re: A new crash
 

Year 12.

SP, Better Independents is 2.1, Endgame diversity doesn't show a version #.

Legit.

Version 3.26.

I thought I answered them all.

Google returns this thread only.

There's no number. Here's the last lines of the debug log:

Udum'ukinna (str1093) attacking Rim Mountains (str312) (good 218)
Etimmu (str586) attacking Rim Mountains (str312) (good 20)
Ishu'kallu tag (good 1)
Kush'nah tag (good 95)
ai_recruitcom
ai_recruitcom
createslist lnr 420
ai_recruitcom
createslist lnr 289
Något gick fel!
lic: bad lnr
flushopengl
mem ok
DeinitPrint
freeing old texobjs

Re: A new crash
 

I found this thread. Maybe try deleting your license key and entering the key again?

Re: A new crash
 

Thanks for all the information.

Etimmu, that means LA Ermor.

Year 12. Let me guess, you also play at a huge map? I think the game ran out of commanders you can recruit. There is a max for this. Try playing the turn again, and try to get as much of your own commanders killed as possible (and don't recruit any new ones). If you can now play a few more turns before the problem arises you have the cause of the problem.

You should upgrade to 3.27 as it fixes a few bugs:

* Utterdark did far too many attacks, fixed.
* Recruitment queues are automatically reset once a fort is under siege.
* 2 x Crash during turn generation fixed.
* Fixed bug where AI would cast vengeance of the dead on empty provinces.

Re: A new crash
 

Yeah--I was trying an experiment. I was attempting to win as a peaceful Ermor--not attacking (at least openly--globals and anonymous attack spells are allowed) any other player, period, even if attacked.

I didn't realize I wasn't current. I'll patch.

Re: A new crash
 

Patched, still the same crash.

Re: A new crash
 

did you try the reduction of commanders thing? at 12 years with LA ermor, there is a computer resource running out :D.