Jump to content
SaltyNewt

'{' encountered instead of '='

Recommended Posts

So I have a script in my description.ext file for some custom voices

Quote

class CfgRadio
{
    sounds[]={};
    class kam1
    {
        name="kam1";
        sound[]={"dubbing\kam1.ogg", db - 100, 1.0 };
        title="Kamino to Broadway, shots fired!";
    };
    class kam2
    {
        name="kam2";
        sound[]={"dubbing\kam2.ogg", db - 100, 1.0 };
        title="Requesting support, Broadway do you copy? Over.";
    };
    class br1
    {
        name="br1";
        sound[]={"dubbing\br1.ogg", db - 100, 1.0 };
        title="Kamino, Broadway, we read you, wait one.";
    };
};

but when I open the mission in the Eden Editor it gives me this error message: "C:\Users\User\Documents\Arma 3\missions\mission_name\description.ext, line 1: '.': '{' encountered instead of '='." 

I've looked through it about 10 times and still don't know what it's talking about, any ideas?

Share this post


Link to post
Share on other sites
11 hours ago, SaltyNewt said:

description.ext, line 1

 

Would you like to check the first line and post your description.ext here ?

Share this post


Link to post
Share on other sites

 

alright so here's my predicament, I managed to get them working, but I put three more lines in, as shown below, but for some reason when the sqf I put them in is activated by a trigger, it just says the name of the sound file, but I've looked through it about 100 times and can't find anything wrong with it.

 

5zr4PTR.jpg 

 

Share this post


Link to post
Share on other sites

add also a \ in front of the directory of the file like:

 

sound[] = { "\sound\filename1.ogg", db - 100, 1.0 };

 

Share this post


Link to post
Share on other sites

Didn't work, I even tried backing out of the editor and reloading the mission

Share this post


Link to post
Share on other sites

at least you are not getting any error , right ?

Just i don't kmow to tell you anything about the cfg radio

 

you got so else this topic to follow :

 

Share this post


Link to post
Share on other sites
On 2/24/2019 at 3:20 PM, SaltyNewt said:

alright so here's my predicament, I managed to get them working

Shouldn't be working, missing quotes in lines 35, 41, 47

 

which sounds don't work? Does it say anything about them in the RPT log?

  • Like 2

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×