INFO Setting camera edge scroll to off (no mouselock) INFO Setting camera mouse pan speed to 1x INFO Setting option graphics.display_mode to 'fullscreen' INFO Setting option graphics.aa to 'off' INFO Setting option graphics.hdr to 'on' INFO Setting option graphics.shadows to 'medium' INFO Setting option graphics.headlights to 'medium' INFO Setting option graphics.vte to 'medium' INFO Setting option graphics to 'medium' ERROR :1: Uncaught TypeError: Object # has no method '_trigger' WARN LoadedLocalModCollection::loadLocalModCollection: Could not open /server_mods/mods.json file mods will not be mounted INFO LoadedLocalModCollection::loadLocalModCollection: Failed listDir call for "/server_mods/" no mods will be loaded from this path INFO Loading mod : cheat_allow_mod_data_updates INFO Loading mod : cheat_allow_create_unit INFO Loading mod : cheat_allow_change_vision INFO Loading mod : cheat_allow_change_control ERROR Error reading C:\Program Files (x86)\Steam\steamapps\common\Planetary Annihilation Titans\media\stock_mods\server\: 3 INFO Loading mod : community-mods-client INFO Loading mod : server_browser_show_cheat_servers ERROR Error reading C:\Program Files (x86)\Steam\steamapps\common\Planetary Annihilation Titans\media\stock_mods\client\: 3 Here are the last few lines of the crash log: I've tried uninstalling/reinstalling, verifying game cache, disabling firewall/antivirus, and restarting my computer to no avail. If I launch the program outside of steam (where it doesn't auto-connect to playfab) the game works fine until I try to sign in to my uber account. The game starts up normally, but when the CONNECTING TO PLAYFAB window opens on startup, the little planet loading icon spins for a bit and then freezes, followed by a crash. Because that was the only hiccup in an otherwise GLORIOUS match that really lived up to what this game's about.My PA: Titans has been working fine since I got it a few weeks ago, and the original was working fine for about a year since I got it, but suddenly it started crashing out of the blue. I don't know where "improved orbital mechanics" goes on the pipeline, but having planets be annihilated when they strike the sun would be handy. I ended up self-destructing and claiming a moral victory. So, too, were nukes, and after attempting to fire Luna to destroy both planets, Luna simply suffered the same fate. They were summarily trapped in a tight solar orbit, unable to escape. So when I sent invasion forces to clean up the remaining planetoids, my opponent send his Commander and all his orbital units to. It was a perpetually exploding white dot lodged into/orbiting along the surface of the sun, which could be clicked on in the planet menu and zoomed into - you could see the metal spots and everything. Hilarity aside, the subsequent issue was that Phobos still existed. Phobos, trying to maintain its attack vector, does something neither of us expected: It crashes directly into the sun. Quickly orchestrating teleporter evacs for all my massed ground forces, including my last Commander, I set Venus on a crash course with Mars. Unfortunately, he hadn't noticed that I had started Halleys on Venus. The fourth team/player takes advantage of the multi-front stalemate and snipes the remaining commanders for me, then chucks Phobos at my main base on Venus to try to finish me off. Earth becomes a tough naval/artillery stalemate against one player, as a large peninsula separates our adjacent naval bases and prevents easy steamrolling with our forces, and Venus turns into a ground slog against a second player as I pump units and artillery from a proxy teleporter base while he scrambles to counter my units and set up anchors to prevent aggressive tower creep. My ally and I take to Venus and Earth respectively, and after he lags out I'm left to handle both fronts on my own. Or, "How do you MISS with a moon?" Gather 'round, this is gonna be a silly one.Ģv2v2v2 on Inner Sol System.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |