1
Mouse doesn't stay in the game, it will wander in and out, difficult to turn and fire when your click selects the desktop. Also, you can drag the game window around until you are able to pilot your mech, then holding click on the top bar just selects the window and you are now moving your upper torso, so the game window stays put where ever it is throughout that whole match, even if it is divided between your monitors... Also, when you are doing something else on another monitor when the queue pops a game, it instantly steals your pointer, but then doesn't keep it as you can drag right out of the window =P. Highly annoying.
Full Screen Mode:
After logging in and the game activates full screen, sometimes it gets stuck in an infinite loop of going between minimizing and attempting to grab the whole screen about twice a second. Blink, blink, blink, blink, blink, blink, blink, etc... alt+tab sometimes works, best to just ctrl+alt+delete, select task manager (higher system priority) then select the game on the task bar and it then usually loads up correctly. This uncommonly happens when the queue pops a game and it tries to load up which leads me to believe something in the program crashed. Sometimes this causes the whole game to simply crash to desktop the instant the queue pops a game. At any time after the game is full screen, attempting to minimize with alt+tab uncommonly works, usually have to force minimize with ctrl+alt+delete. Doing this too often will crash the game to desktop. When attempting to unminimize the game, I have about a 40% chance of getting the infinite loop. If I have a webpage open on the other monitor, every time the game goes full screen from a fresh game boot, unminimizing or queue pops a game, the other monitor seems to have a 33% chance of doing one of the following: (1) going completely black, (2) making only the window on the other monitor black, such as the web browser, or (3) not changing anything on the other monitor which is how it should be all the time...
The inconsistency of all these affects also points to crashing code. The fact that things DO sometimes work correctly says I have a good install of the game. Also, during anything MWO is being clunky about or crashing completely on, the rest of my computer and anything else I have running is working perfectly which means my computer and it's hardware is fine. The result is poor game coding. Considering the graphics engine and hitbox parameters don't coordinate and feels like I'm playing on the N64 in 2014 I'm not surprised. That was the #1 clue that corners where cut to get this game running. The game is a great idea, but very poor implementation from the UI, to the engine, to the code itself. If I were project lead, I would concentrate on stabilizing what you already have before implementing new things and making this task bigger and harder in the future. It's like being the process of tripping over your own shoe laces and at the same time grabbing to hold onto new breakable items that you don't want to break. Why would you do that?
For the sake of procedure, here's my specs:
64-bit Windows 7 Home Premium SP1 (installed on 120 GB SSD).
Core i5 (socket 1156 next gen) 3.4GHz, 3.4GHz.
8 GB DDR3 RAM (I don't do a lot at once, just not my style).
ASUS P8 variant motherboard.
NVIDIA GeForce GTX 750Ti Driver 9.18.13.4475, updated last week.
MWO installed on 7200 RPM SATA 6GB/s HD on the same partition as the rest of my games.
Low bandwidth internet, but smooth 3 Mbps down, 5 Mbps up.
Edited by destroika, 17 December 2014 - 12:58 PM.
Or maybe you do... Heh. Either way - thanks for coming back with the real fix.
