Home   Help Search Login Register  

Author Topic: "Config: End of Line encountered after......"  (Read 2357 times)

0 Members and 1 Guest are viewing this topic.

Crippler

  • Guest
"Config: End of Line encountered after......"
« on: 26 Apr 2003, 23:24:10 »
Hey all :)
I've been retexturing the Tornado 1.12 into an RAF Gr4 skin and have been changing the config.cpp. I've retextured a Maverick into a Brimstone (poorly) but when I changed the config.cpp to use the new brimstone I get an error message from flashpoint:-

"Config: End of line encountered after \ITA_TRD_MFG\brimstone_proxy.p3d"

 :'(

This is the bit from the CfgAmmo part of the cpp that I have changed:-

class RAF_Brimstone : Hellfire
   {
      hit=1900;indirectHit=800;indirectHitRange=2.5;
   model= "\ITA_TRD_MFG\brimstone.p3d";
   minRange=200;minRangeProbab=0.30;
   midRange=600;midRangeProbab=0.80;
   maxRange=2000;maxRangeProbab=0.50;
   thrust=700;
   laserLock=false;
         proxyShape= "\ITA_TRD_MFG\brimstone_proxy.p3d;
   irLock=1;
   initSpeed=0;
   initTime=0.2;
   };

can anyone tell me what I'm doing wrong? ???

Cheers

Crippler

DeadMeatXM2

  • Guest
Re:"Config: End of Line encountered after......"
« Reply #1 on: 26 Apr 2003, 23:42:17 »
"Config: End of line encountered after \ITA_TRD_MFG\brimstone_proxy.p3d"

         proxyShape= "\ITA_TRD_MFG\brimstone_proxy.p3d";

You were missing a " at the end of the proxy definiton ;)

Crippler

  • Guest
Re:"Config: End of Line encountered after......"
« Reply #2 on: 27 Apr 2003, 13:40:38 »
Thanks Deadmeat :) Flashpoint loads up now, but when I try to fly the new Brimstone variant of the tornado, it just goes straight back to windows, with no error message or anything  :'( Does anyone know what could be causing this? The other tornados work fine, its just the brimstone one that isnt :(

Cheers
Crippler

Crippler

  • Guest
Re:"Config: End of Line encountered after......"
« Reply #3 on: 27 Apr 2003, 14:00:19 »
Sorry- its sorted now :D I think the brimstone_proxy.p3d file was corrupted or something, but i've changed it and it works now :)

Thanks
Crippler