Picture-In-Picture broke my PA?

Discussion in 'Planetary Annihilation General Discussion' started by boylobster, February 21, 2014.

  1. tatsujb

    tatsujb Post Master General

    Messages:
    12,902
    Likes Received:
    5,385
    considering you can at any time delete PA and hit "VerifyFiles" on the uber Launcher and it still works that does not make sense to me.
  2. boylobster

    boylobster Active Member

    Messages:
    167
    Likes Received:
    185
    Apologies for the crap (read: nonexistant) troubleshooting before. As others have pointed out, it definitely seems to be a mod issue, but I wanted more specifics, and after a bunch of testing, have come to some general conclusions.

    - F5 seems to fix the issue in all cases

    - When running troublesome mods, the black screen is consistently encountered *when first loaded a new match*. If you refresh with F5, quit PA, and rejoin the game, there are good odds you won't encounter the issue.

    - "Better System View", surprisingly, can cause the black screen all by itself. Seems consistent.

    - Some combination of "Floating Framework" and "Blueprint Info Framework" also cause bad behavior, but seemingly at random. With these enabled, sometimes it would load the system properly, others, not. The inconsistency had almost had me believing that there was a difference between using the Uber launcher and the PA Mod Manager launcher, but now I don't believe so - that was just a by-product of inconsistent results. I think. o_O

    I hope that info can be of use to someone smarter than I... I'm getting a little tired of loading that same system over and over again, but maybe I'll try to run through the rest of my installed mods, however unlikely to be related, just to be thorough.

    Oh, and most testing was done with a tiny, single-moon system for quick loading. That didn't seem to be a differentiating factor, however.

    Thanks to everybody with the quick F5 solution, btw! *face meets palm*
  3. boylobster

    boylobster Active Member

    Messages:
    167
    Likes Received:
    185
    Update:

    Poor testing on my part. "Floating Framework" and Blueprint Info Framework" MAY be a problem, but I think the real culprit was "Commander Health Display".

    So, "Better System View" can cause it, and "Comm Health Display", in conjunction with "Floating Framework" and "Settings Manager" can cause it. I have no technical expertise here, but is it suspicious that both of these mods add an additional window to the screen? Just a thought.
  4. cola_colin

    cola_colin Moderator Alumni

    Messages:
    12,074
    Likes Received:
    16,221
    Last edited: February 22, 2014
    cptconundrum and Raevn like this.
  5. stormingkiwi

    stormingkiwi Post Master General

    Messages:
    3,266
    Likes Received:
    1,355
    Note that it seems that clashes (e.g. the "v" key) cause crashes.
  6. Tripax

    Tripax Member

    Messages:
    67
    Likes Received:
    62
    that would be a hotbuild2 keybind overlap, we'll look into it today
    for now just don't use v for hotbuild2, or reassign the pip keys under keyboard to an unused key
  7. stormingkiwi

    stormingkiwi Post Master General

    Messages:
    3,266
    Likes Received:
    1,355
    No it's not a hotbuild2 overlap.

    It's because PIP can't do whatever the shift+v function is defined as if the PIP isn't visible. So the game crashes.

    Same thing happens if you press shift+v without the clash.

Share This Page