Don't limit radar command's range to fit into world map
Limited since Chainsaw 2 so that the radar map fits into a world map without clipping, i.e. its diameter neither exceeds WORLD_X / 2 nor WORLD_Y. Maybe range exceeding that triggered bugs then. It doesn't now, and it makes no sense. The limit never applied to automatic bmap update from ship radar.
This commit is contained in:
parent
a65ee5e9b2
commit
e49cb13480
1 changed files with 0 additions and 8 deletions
|
@ -74,10 +74,6 @@ radar(int type)
|
||||||
if (!snxtsct(&ns, cp))
|
if (!snxtsct(&ns, cp))
|
||||||
return RET_SYN;
|
return RET_SYN;
|
||||||
tech = tfact(player->cnum, 8.0);
|
tech = tfact(player->cnum, 8.0);
|
||||||
if (tech > WORLD_Y / 4.0)
|
|
||||||
tech = WORLD_Y / 4.0;
|
|
||||||
if (tech > WORLD_X / 8.0)
|
|
||||||
tech = WORLD_X / 8.0;
|
|
||||||
while (nxtsct(&ns, &item.sect)) {
|
while (nxtsct(&ns, &item.sect)) {
|
||||||
if (item.sect.sct_type != SCT_RADAR)
|
if (item.sect.sct_type != SCT_RADAR)
|
||||||
continue;
|
continue;
|
||||||
|
@ -117,10 +113,6 @@ radar(int type)
|
||||||
}
|
}
|
||||||
|
|
||||||
pr("%s at ", obj_nameof(&item.gen));
|
pr("%s at ", obj_nameof(&item.gen));
|
||||||
if (tech > WORLD_Y / 2.0)
|
|
||||||
tech = WORLD_Y / 2.0;
|
|
||||||
if (tech > WORLD_X / 4.0)
|
|
||||||
tech = WORLD_X / 4.0;
|
|
||||||
radmap(item.gen.x, item.gen.y, item.gen.effic, (int)tech, tf);
|
radmap(item.gen.x, item.gen.y, item.gen.effic, (int)tech, tf);
|
||||||
}
|
}
|
||||||
break;
|
break;
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue