This topic contains 11 replies, has 0 voices, and was last updated by  The AI 9 years, 11 months ago.

  • Author
    Posts
  • #6067

    naka
    Participant

    MIRV dont follow cenrtal trajectory.
    After apex mirv splits normaly – one half up and one half down,
    but later bomblets start shifting forward from the cental path.
    At ground they missed completely the hit point.

    i ve noticed this effect after making corections.
    Normaly if you missed the first mirv shoot – the next shoot adjustment is done relative to the central hit spot of the mirv, but then you miss again. 😆

    #46908

    PeanutsRevenge
    Participant

    its the same with Death heads aswell, they push forward when splitting.

    i think it should be like that, makes it a little harder to use them.

    #46909

    parasti
    Participant

    Those are excellent screen-shots. I disagree with Peanuts — this must be fixed. All shots should land at the same exact spot regardless of the weapon type.

    #46910

    Bobirov
    Participant

    I found that putting in a WeaponVelocity with a relative velocity change of 0.83 or so just before the split in the weapon will cause MIRVs to roughly behave like they used to. Not a permanent solution, but can be used to work around this issue for now.

    #46911

    The AI
    Participant

    If anything, shouldn’t they go back from the projectile? Or couldn’t you just tweak it on the Xml end? Depends on how you make your mirvs, sure, but if instead of using the Mirv tag itself, just make it manual, I will look at some negative number fun later in the day.

    #46912

    Bobirov
    Participant

    @The AI wrote:

    If anything, shouldn’t they go back from the projectile? Or couldn’t you just tweak it on the Xml end? Depends on how you make your mirvs, sure, but if instead of using the Mirv tag itself, just make it manual, I will look at some negative number fun later in the day.

    Funny thing is, I was doing it manually in Apoc instead of using WeaponMirv and it does the same thing either way unless you put the velocity change and slow it down a bit.

    #46913

    The AI
    Participant

    I found out something odd, when you change the Vspread, it uses the out most shot as a guide. Set it to zero and it is still farther forward. The thing that is more strange, set it to two, with ten projectiles, and compare that to a normal shot… really odd. I also found out that an uneven spread to projectile results in a unbalanced amount of projectiles, one or more are doubled while the others are not.

    #46914

    KTM Rider
    Participant

    Man I’m glad that someone else pointed this out. I thought that I was either going insane, or losing anything left of my edge.

    I guess I’m sorta torn if this should be fixed. On one hand, I (and most everyone else, I’m sure) am used to v40 MIRVs. It allows you to damage area on both sides of the impact point without adjusting your aim. The v41 MIRV forces you to readjust in order to do damage on both sides of the impact point…..

    On the other hand, it wouldn’t be too hard to adapt to the new system.

    Yep, superb documentary shots, naka.

    #46915

    HWB
    Participant

    I don’t understand why this is a problem. I noticed it and I have to adjust my shots for the new spread. (now you have to undershoot them instead of overshooting) But kudos on the pics that really shows the spread of the mirvs.

    #46916

    Bobirov
    Participant

    @hwb wrote:

    I don’t understand why this is a problem.

    It is a problem because it is unintended behaviour. The MIRV spread should be centered around the original shot, that is how it is supposed to work. They are not supposed to overshoot the original shot location like they are currently.

    #46917

    The AI
    Participant

    The problem also increases with larger and larger spreads, the projectiles seem to gain an entire second period of thrust starting their arc at the apex of the original. I am going to have to do more testing. But I will most likely have some pictures to post.

    #46918

    cbx550f
    Participant

    I’d just like to say this:

    AI, this thread is a model for bug reports/complaints whatever. The description and the screenies are awesome.
    Nice work.

    I have a few things on my plate right now, but if Some Guy doesn’t get to it, I’ll keep it in mind for when I’m done the things I’m working on.

    #46919

    The AI
    Participant

    I hope these pictures help. They are inverse to help contrast, but I realise that they are not the best.

    the extreme one is of course extreme, but it is a good example.

Viewing 13 posts - 1 through 13 (of 13 total)

You must be logged in to reply to this topic.