Error message

[Legionnaire_Dan]

Hello!

 

I have tried tonite from a clean install, ( PC formated so it is very clean install ) to launch DCS BS from Modam latest version and also from the exe from my desktop, but I got that error message and don't know why. Can anyone tell me what's causing this please?

 

Thank you!

 

Here is a picture of the error mesage:

 

 

 

 

 

Thank you! :mad:

[EtherealN]

Excuse my ignorance, but what is "Modam"? Do you mean Modman and if so, which version and which mods are in?

 

Anyhow, the cause of the issue would appear to be a syntax fault in db_countries.lua, on line 48 if I understand that correctly. My db_countries.lua does, however, not have anything on line 48.

 

The relevant area in my file:

 

46:local function cnt_unit(clsid, name, color_schemes)
47:  local res = { CLSID = clsid, Name = name, ColorSchemes = color_schemes };
48:  
49:  return res;
50:end

 

Do NOT copy paste that into yours, I added the line counts to it and a direct copy-paste will destroy your file even more. Also, do not edit any lua files ever with regular notepad, it can destroy the syntax. If you have Notepad++ (it's free software) you could check what your db_countries.lua says on that line and it would be easier to troubleshoot the problem.

[Legionnaire_Dan]

Excuse my ignorance, but what is "Modam"? Do you mean Modman and if so, which version and which mods are in?

 

Anyhow, the cause of the issue would appear to be a syntax fault in db_countries.lua, on line 48 if I understand that correctly. My db_countries.lua does, however, not have anything on line 48.

 

The relevant area in my file:

 

46:local function cnt_unit(clsid, name, color_schemes)
47:  local res = { CLSID = clsid, Name = name, ColorSchemes = color_schemes };
48:  
49:  return res;
50:end

 

Do NOT copy paste that into yours, I added the line counts to it and a direct copy-paste will destroy your file even more. Also, do not edit any lua files ever with regular notepad, it can destroy the syntax. If you have Notepad++ (it's free software) you could check what your db_countries.lua says on that line and it would be easier to troubleshoot the problem.

 

Well sorry it's Modman I wanted to say.

Edited March 18, 2009 by Legionnaire_Dan

[Legionnaire_Dan]

Found what was the error problem by myself

 

Allo!

 

Well after posting in here the problem I was experiencing with that error message, the error is: / Scripts/Database/db_countries.lua:48: unexpected symbol near. I thought, well let's try to see what I might have done so... I decided to back track the event following that bug report.

 

I have Modman installed, version 7.1.1.0, that's the latest one if I am not mistaking. At first, I was pissed and upset, and wanted to uninstall the game right away but, instead I stood to my first idea, and proceed to try to found what cause that damm error message.

 

And I did find it. But......... before I tell you what cause the error, let me tell you first, how I did it. With barely no damm experience with PC's, nor sims games, I really deserved guy's and girls, and Oscar. Just kidding :smartass:

 

So I decided to uninstall all the mods that I did install with Modman, and relaunch the game, after rebooting, just to see, if it wasn't something install with Modman or even Modman itself. And surprise to me, the game launch perfectly. I was amazed and very happy, with my PC knowledge, well I was stunned.

 

Of course from now on I knew half the problem was solved and it was related to Modman. Without Modman the game was also launching if no mods were installed. So I knew it wasn't the game itself. It was related to Modman or a mod installed with Modman.

 

But it that case wich mod, was causing the error message then? By the way, just to let you know, all the mods that I have installed with Modman today, were all Modman compatible. If it wasn't saying Modman compatible, before I download it, I would not install the mod.

 

The ONLY way to know it, was to reinstall each mod, one by one, and then every single time, launch BS, to see witch mod would give me that error message. I did find it, and it's a mod compatible with Modman 7.1.1.0. But what bothers me more, is it an error purely related to Modman, related to my computer, or is it a conflict with the game itself, or perhaps it's a conflict with another mod? Alot of questions to myself, that I cannot answer anyway, maybe someone will come up with the answer in a near future, time will tell us, I guess. :)

 

Someone with better knowledge in that sort of business will have to find it, and let us all know. Anyway now I will show you a picture of my desktop, and look at the bottom of Modman in red you will see the cause of my BIGGGGGGGGG problem now solved. :thumbup:

 

Also I put that picture in here cause it might help the person who made that mod to pinpoint the problem, by seeing all the mods that I have activated, and is mod causing the error, so he could solve maybe the problem.

 

Am sure you are all very interested to see that picture isnt it? well here it is:

 

 

Well anyway here is that little bugger, I took it out, and now my game is top notch!

 

Than you all!

PS - Sorry for my bad english but my native tongue is french, hope you did all understood my post.

Edited March 18, 2009 by Legionnaire_Dan

[EtherealN]

Excellent to see you got it working. :)

 

And yeah, I guess it's possible that with so many mods working on Canadian skins in there it's possible they end up modifying the same place so many times that a syntax error might occur. I'm no mod expert myself though (I only have the airbase textures by DragonRR installed, which are awesome).

[Legionnaire_Dan]

Excellent to see you got it working. :)

 

And yeah, I guess it's possible that with so many mods working on Canadian skins in there it's possible they end up modifying the same place so many times that a syntax error might occur. I'm no mod expert myself though (I only have the airbase textures by DragonRR installed, which are awesome).

 

 

Well thank you, it might help someone in a near future, that's mainly why I came to post my findings causing that error message. :thumbup: