Jump to content

ChronoReverse

Members
  • Posts

    321
  • Joined

  • Last visited

Posts posted by ChronoReverse

  1. I don't see how Alto arriving doesn't make sense. The Varja jumped ignoring the fold distortions and arrived. Alto jumped maybe an hour after the Varja jumped using the prototype booster that ignores fold distortion.

    Anyway, while we got plenty of awesome, this episode felt a little bit packed and rushed. But who knows, maybe they have a lot for the second half of Macross F. It's not a terrible flaw though and it was nice how even though the Frontier Fleet was winning at the end, it didn't feel much like a victory.

  2. Interesting how the PPB punch is still there (isn't there no PPB for the 25's?). I wish there'd be more literature about the reason for the 171 as it's starting to look less and less like a cost-reduced version of the 17

  3. I HATE inertial damping, precisely BECAUSE it's the easy way out. It's an epidemic excuse that isn't even remotely plausable and removes consideration for the design to do anything other than look good.

    And inertia damping automatically means you aren't being overly technical. It's the standard Trek solution to a problem: throw technobabble at it.

    Unfortunately they're already in Macross from the very beginning. The moment you have "gravity generators" you automatically have a form of inertial dampeners.

  4. I'm just glad it really wasn't the SDF-1. It would have a monumental gimmick to have had the SDF-1 out nowhere without telling us in episode 1. The SDF-1 Macross is too big, too iconic and too important to not mention if it just lifted off, much less crashed/disappeared.

  5. It's fridge logic. If the original design wasn't meant to transform, retrofitting the thing to be able to transform is a huge undertaking. It seems even more far-fetched than usual to think that they went "Hmm, we really need to connect these two points because the fold engines disappeared on us. I know! We'll try transforming the ship!". Surely it would've been easier to lay out long cables (considering they could rebuild a city so quickly) unless it was intentionally rebuilt to transform.

  6. Like I said, fighters of today do have eye tracking cameras, they just aren't used to the extent Macross has had them used yet. However they are designed for this purpose and they are probably working on a system that isn't as simple as it may look.

    The issue isn't tracking the movements of the eye. That's simple enough and really is just an engineering issue. The problem is the selection process.

    For it to be fine-grained it would be putting more burden on the pilot instead of reducing it. But if you add advanced heuristics then the control of the pilot is less. The latter is not a bad thing but it's the opposite of what's shown in Macross.

  7. I've never liked the idea of the eye tracking thing even back in Zero and I still don't like it now as presented.

    Unless the interface has access to your brain signals, there's no good way to indicate what you're looking at should be targeted. It can't be anything my gaze sweeps over since if I go from A to C, where the view is [A B C], I'll include B. Do I have to be careful to steer my eyes around that? How do you do that for a cloud of 50? Suppose I press a control to indicate what I'm looking at is to be targeted. Does that mean I'll have to do 50 clicks in a second on a single control? That's a lot of split second decisions. While flying and making a lot of other split second decisions.

    What I could see as being useful is a combination of the eye tracking and a button on the controls. It'll be similar to drawing a box to select with a mouse except it takes your gaze instead. Instead of the far-fetched individual targeting of each missile in a swarm, clusters of missiles are treated as a single object in terms of selection and thus targeted. It would of course require refined computer algorithms to be practical but it would provide greater granularity without putting too much burden on the pilot's concentration.

  8. WHITES?????? I hope you mean Yellows otherwise you know something that the rest of us don't!!! :rolleyes::lol::wacko:

    Well, they may be considered yellow but they look more white to me =P

    Gunpod = Rounds kill yellow Vajra, bounce off of Red Vajra

    Missiles = Blow Vajra up if they hit

    Clan Clan's Shoulder Cannon = Cracks the armor on a Red Vajra

    Mikhails Sniper Rifle = Blows chunks off of the Red Vajra

    Knife = Penetrates Red Vajra armor

    I dunno.

    The missile blasts in the first episode only made the Red shudder. Even when the bajillion missiles were unloaded into it, it didn't even get scratched. I'd say that missiles are only effect against the smaller ones unless they're reaction type.

    As for the knife, it penetrates the gaps between the Red's armor but cutting the normal armor would probably take too long most of the time in melee combat.

  9. With today’s technology, it’s easy to have a city-wide network of surveillance cameras using facial recognition software. Such a system would automatically pick up an individual that wasn’t registered in the population database and report them to the law enforcement authorities. We are already moving that way in real life, with UK for example having 40 million surveillance cameras! Just surprised that after Macross 7, such a system wasn’t adopted as standard on colony fleets to guard against infiltration by hostile forces.

    Except not =/. There was a recent news article about a study which showed all the cameras in UK had pretty negligible effect on crime. And current facial recognition technology isn't quite as good as you're making it out to be. There's a reason why people are still paid to look for faces.

    This doesn't discount the possibility of all this in a Macross future setting though and it does seem like a pretty interesting oversight.

×
×
  • Create New...