|
el cid again -> RE: Japanese floatplanes in RHS (6/5/2008 11:42:46 PM)
|
quote:
ORIGINAL: Bogo Mil quote:
ORIGINAL: el cid again This is a problem in terms of historical scenarios: I try to have units upgrade "correctly" as they did. On the other hand - in EOS family - it makes some sense. Floatplanes often flew ASW missions - and also did significant search missions. IJN preferred floatplanes to carrier bombers for search - and also developed special long range carrier search planes. But the floatplanes were considered multi-role - sort of like sea control ships - seaplane carriers were to control lesser contested waters. They could bomb land targets - or even ships. I want a Pete that can do that - but WITP code does not treat seaplane fighters properly. Yes, we have a conflict here. We can choose do use the historical correct plane types (well, at least before the ahistoric mass upgrade from Pete to Rufe) - but then we don't have the historical correct mission types available. With my proposal, the player would get at least a one time decision which of the historically used mission typess he wants a squadron to fly, but it gives up the correctness of the plane types, of course. AE will solve this dilemma - great. Until then, we have to grasp one nettle, but can decide which one. I would give the decision to the player. If he thinks that using the historical plane types was more important - nothing hinders him to keep all FF as FF and all FP as FP. We are always limited by something. Apparently in AE we won't have true seaplane fighters at all. This is very wierd -but no doubt related to the fact Japanese thinking (and not implemented American thinking) is alien to whoever did this change. They don't understand that there really was a float fighter concept - and not being able to fly cap or escort or lrcap is to gut it completely. This means we have different unfortunate limits in AE - not that it has fixed the problems we now have. But in a broader sense, that is likely to be the case to some extent. Everything is compromise, and programmers don't like to turn us loose completely (with soft controls for as much as possible).
|
|
|
|