Page 1 of 1
Problems compilling with scriptor
Posted: 18 Mar 2007, 14:37
by lgustavomp
Heya... wasup?
I created some stuff for TA some years ago. And never had troubles with scripter (or at least i dont remember ^^).
Ok.. here's the problem. always when i try to compile something i got an error msg on the final line. F*ck i'm not a coder but i don't rementer of that kind of thing happening a time ago.
As you can see... i used the ROCKO cob decripted by the scriptor and don't touched anything. Just decripted (ajusted some kind of bugs thar "0"s has turned on "$") and tried to compile.
btw sorry for my tarzanish english
grrr.. i hosted an img on imgshack.. but as i'm a 'new member' i can't post hyperlinks and blablabla.
Posted: 18 Mar 2007, 14:43
by lgustavomp
Nice.. will i need to do flood here to be able to show a img of my problem?
there's another way?
Posted: 18 Mar 2007, 14:47
by rattle
Are you german?
You need some more posts to be able to overcome the flood protection.
Posted: 18 Mar 2007, 14:52
by KDR_11k
Just copy and paste the relevant text.
Posted: 18 Mar 2007, 14:53
by lgustavomp
I'm brazilian.
Thx for the touch.
Posted: 18 Mar 2007, 15:00
by lgustavomp
Code: Select all
if( severity <= 99 )
{
corpsetype = 3;
explode ground type FALL | SMOKE | FIRE | EXPLODE_ON_HIT | BITMAP1;
explode lbarrel type FALL | SMOKE | FIRE | EXPLODE_ON_HIT | BITMAP2;
explode lfirept2 type FALL | SMOKE | FIRE | EXPLODE_ON_HIT | BITMAP3;
explode lfoot type FALL | SMOKE | FIRE | EXPLODE_ON_HIT | BITMAP4;
explode lleg type FALL | SMOKE | FIRE | EXPLODE_ON_HIT | BITMAP5;
explode lmisspod type FALL | SMOKE | FIRE | EXPLODE_ON_HIT | BITMAP1;
explode lthigh type FALL | SMOKE | FIRE | EXPLODE_ON_HIT | BITMAP2;
explode pelvis type FALL | SMOKE | FIRE | EXPLODE_ON_HIT | BITMAP3;
explode rfoot type FALL | SMOKE | FIRE | EXPLODE_ON_HIT | BITMAP4;
explode rleg type FALL | SMOKE | FIRE | EXPLODE_ON_HIT | BITMAP5;
explode rshield type FALL | SMOKE | FIRE | EXPLODE_ON_HIT | BITMAP1;
explode rthigh type FALL | SMOKE | FIRE | EXPLODE_ON_HIT | BITMAP2;
explode torso type SHATTER | BITMAP3;
return (0);
}
}
The line (551) means the last "}"
Compiling Bos...
Compiling sfxtype.h
Compiling exptype.h
Compiling SmokeUnit.h
Compiling SFXtype.h
Compiling EXPtype.h
Making Cob...
Error (551): Could not create cob [ C:\Documents and Settings\grr\Desktop\scripts\ARMROCK.bos ]
One or more errors occured while compiling the script.
Posted: 18 Mar 2007, 15:07
by KDR_11k
Something prevents it from writing the COB. Is the original COB you decompiled still there?
Posted: 18 Mar 2007, 15:19
by lgustavomp
here on the same directory? Didn't understand exacltly what do you meant
i decompiled on another place to have no need to overwrite anything when i need to compile again
http://img402.imageshack.us/img402/5816/imagemdt9.png
Posted: 18 Mar 2007, 15:29
by lgustavomp
I got it... i think
damn.. i just forgot to assign an output file name and dir
thx mates
Posted: 18 Mar 2007, 16:39
by lgustavomp
Here's something wrong...
Look the img below. On left side is a decripted BOS from the TOTALA1.HPI... Look that numeric values... all of them. Is that right? I don't think so... on the right side you can see the original BOS (not decripted)
http://img338.imageshack.us/img338/8945/imagemsr1.png
Does it happen with everyone?
Posted: 18 Mar 2007, 16:46
by Guessmyname
Yeah. Scriptor's decompiler strips out any comments (the grey bits with "//" before them) and renames static-vars (ie bCanAim) to generic stuff like Static_Var_3. It also removes any empty lines. As for
and
they do the same (while bCanAim is false - ie, the unit could not be able to aim - do stuff)
Posted: 18 Mar 2007, 17:18
by rattle
lgustavomp wrote:Here's something wrong...
Look the img below. On left side is a decripted BOS from the TOTALA1.HPI... Look that numeric values... all of them. Is that right? I don't think so... on the right side you can see the original BOS (not decripted)
http://img338.imageshack.us/img338/8945/imagemsr1.png
Does it happen with everyone?
The decompiled COB on the left probably doesn't belong to the BOS the right. Compile and decompile the BOS to see for yourself.
KDR_11k wrote:Something prevents it from writing the COB.
Yeah, try it on a different drive/partition. Check if you have enough rights in that directory etc.