[StratComm]

Originally posted by darkchrono4


I checked out the Orion on a completely clean install of FS2 (no FS2_Open or anything else) and all three radar dishes turned 360 degrees.  I'm not sure what it would be doing with $fov, the only place in the code that ever reads a variable for that is if its a turret.

No, no, you're missing my point.  The Orion model (and probably all the others with rotating bits) actually have $fov=360 in the subobject properties.  I know the game doesn't use it, but it is there nonetheless.  It's probably got more to do with how coded their converter than it being useful, but if you impose a check that looks for the fov tag to determine new rotational behavior, you may end up affecting old things that should be left alone.

[Darkhill]

I understand you know.  Could always add another entry to the properties part.

[WMCoolmon]

Just add a new TBL field, $RotationLimit or something.

[StratComm]

I'd agree, do it in tables.  That's where the rest of the animation code is handled.

[Darkhill]

I'll have to look into it.

[WMCoolmon]

Code: [Select]

void parse_ship(bool is_chunk)
{
...
     if(optional_string("$RotationLimit"))
     {
          stuff_float(&submodelp->rotation_limit);
     }
...
}

something like that, the submodel stuff is at the bottom of parse_ship