C337Skymaster, on 27 May 2021 - 08:07 PM, said:
Everything that happened prior to KLONDIKE would have already reduced the Pentagon Worlds into an approximate representation of the Successor States, and the Kerensky Cluster is canonically desolate. Not buying any of that, the entire Clan storyline as-written is simply self-fellating junk. Space Goody-Two-Shoes taking his toys with him out of the sandbox instead of pragmatically aligning with the least bad successor state to truncate the coming conflicts? And then having a son who goes full Godwin's Law? Pretty cringe.
Superior writing would have Amaris fleeing to the Pentagon Worlds at the end of the Civil War and Kerensky taking a contingent with him to hunt him down, with the Clans being descendants of the two factions after they had ground each other down to the point that the combat was now just ritualistic tradition and the original reason for it is a faded memory twisted into myths and legends.
Quote
Eh, I would not call that a good analogy. Although the R1 is faster, it's not significantly more flexible in utility than the Inspiron 9400. A better analogy would be having separate devices for playing music, placing a telephone call, and taking a photograph, each costing between $50 to $100, versus having a single $1000 device that can do all three and more. The speed and accuracy has little to do with it; if my camera is using the same sensor as the smartphone and the imaging software is just as good, then the camera will be just as good at taking photos as the smartphone. This has benefits, because if all I need is something that can take pictures then I can get it for a huge savings. Or I can get a better camera than the smartphone for the same cost as the smartphone. That's the logic where a BattleMech and its computer make sense.
That said, if you've already invested in a standardized ecosystem, there are economies of scale to be leveraged and a BattleMech is sophisticated enough that even a low-end one would have ridiculously capable computer hardware, so it's all in the software that the OmniMech magic happens and software is cheap long-term. So once you've got the Omni computer software developed, you'd just deploy that and only that and stick it in everything to amortize the development costs across as many units as possible. Even the IS would have realistically implemented something like this before, during, and after the Amaris Civil War and no amount of Comstar mucking about would have prevented it because it's basic economic sense.
Quote
You would write routines that take care of the calibration automatically. It would be part of your Omni spec. The KC-135 is simple because there is no system in place to automate the task you are describing, not because the task itself is simple. The operator is the control system, there, rather than a machine. Having such systems in place is what makes the OmniMech computer what it is. It takes longer to add such systems, but it's sort of a one-time thing.
A BattleMech, being intended for a much narrower application, is the one that will need a lot of time with the tech to even get it working because the code and the power feeds and the mounts are all probably not designed to work with your mod. And you have to dive in for every single mod. But not for things like walking with different equipment, that shouldn't require anything because the navigation systems should already be designed to compensate for various forces acting on the 'Mech or else it wouldn't work at all. We're talking about things like simply getting fire control to work with the new gun and its feed mechanism or re-cabling the power system and modifying the power management software because that new PPC addition needs more power in a place that wasn't originally intended to receive it.