161 replies to this topic

[Shomer Shalom]

[color=#959595]CPU: Intel® Core™ i5 2550 CPU[/color]
[color=#959595]GPU: nVidia GTX 560[/color]

[color=#959595]When issues appear, always at the start of the game.[/color]

[SenselessNoise]

AMD FX-4100
8GB GSkill DDR3 1333
MSI Radeon 7850

Everything is set to High, but AA and VSync is turned off.

This is a new rig, so I don't know if these issues are new or old. My old computer didn't have any of these issues. I had some bad rubber banding before that patch (it's pretty much completely fixed now), but I've just noticed more and more HUD bugs.

[SGT Puddles]

you are missing the one of the more annoying ones "the Spinny Mini-Map of Doom" ots one of the more distracting bugs

[jay35]

I've experienced all of the HUD bugs from no HUD up to and including the full HUD freakout where everything possible is displayed. You can always tell as soon as the match starts and you can move around a bit, whether there are any bugs affecting you that match.

I've also had at least two that I don't think are listed there:

• Random string of characters replacing mech name (same location as WWWWWWWW) that changes as you move your mech around.
  
• Drag_Grid text string appears in chat area when firing weapons. Alternated between 1 and 0 each time right-mouse button Group 2 is fired.

Spoiler

You can see the first bug here:

And the second one here:

And proof no one by that name exists in the match:

And I've had these bugs on two systems, my old one and the new one I built hoping to improve FPS (which it hasn't, and in fact since the rubberbanding hotfix, there's been a significant degradation in the framerate up to 40-50% on some maps, which never happened before. Just like the silent CTDs that started only since the rubberbanding hotfix. But I suppose that's for another thread.

The two systems are:
Core2Duo i5-750, 8GB DDR3, Radeon HD6950 2GB
IvyBridge i5-3570K 16GB, Radeon HD6950 2GB x 2 (Crossfire, but since I play windowed mode for MWO, that hasn't really helped a whole lot).
Both are Win7 x64. The old one was SP1, the new one was OEM (this thread actually reminded me to go drop SP1 on it, so I'm installing that now).

Edited by jay35, 29 April 2013 - 08:19 PM.

[LancerJ]

Quote

In addition, please include your CPU and GPU model specifications in your text reply, as well as any further details which you believe might assist us including but not limited to:

• When/Where the Issue first appears
  
• Whether or not the issue appears only after performing certain actions in the menus
  
• Whether or not the issue appears in sequences.
  
• Whether or not the player was performing any specific actions prior to appearance.
  
• Whether any other issues were occuring at the same time.

CPU: Intel Core i5 2500k
GPU: nVidia GeForce GTX 660

1. Issues first appear almost exclusively at the beginning of a match and are noticeable as soon as the HUD loads. Issues continue until end of match and never recover before that point.

2. No discernible pattern.

3. No discernible pattern.

4. No discernible pattern.

5. Issues involving the Minimap often have a moderate to severe effect on the Battlegrid as well. Issues involving faulty friend/foe markers are usually not concurrent with other HUD issues.

[Serious Table]

It's worth noting that I have 6 GB of RAM in my machine, which wasn't an option. Just throwing that out there.

CPU: Core i7-920
GPU: nVidia GeForce GTX 650Ti

Issues appear at the beginning of the match. I've never had a bug appear during the match that wasn't there at the very beginning. Otherwise, no pattern for 2-4, and anything that involves the Minimap directly affects the Battlegrid. IFF issues do NOT appear to affect the Minimap, however.

[Superstoff]

CPU: AMD Phenom II X4 955 (4x ~ 3,2GHz)
GPU: ATI Radeon 5870

1) at startup, never had issues in the middle of a match

2) negative

3) negative

4) negative

5) mostly single occurrences, but I noticed something through ingame chat: if I have a map bug, some players (sometimes 3-4 players per match/both teams) confirm the same problem. It seems that especially the minimap-related problems frequently occur in clusters.

Edited by Superstoff, 29 April 2013 - 09:38 PM.

[F lan Ker]

S!

The bugs appear at beginning of match mostly and stay that way all through the match. Happens usually to many players on both sides. Sometimes even get the HUD on/off thing where HUD decides to flick on and then off when trying to shoot a Mech. It seems the HUD stays on if not looking at other MEchs.

My GPU is AMD 7970HD 3Gb GHz Edition with Catalyst 13.4 WHQL drivers. Custom setting in graphics, disabled Post Processing and Motion Blur. Tried both VSync On and Off, no difference. Playing Fullscreen because other modes give degraded performance, not much but can be seen.

CPU is AMD FX8350 4.0GHz.

[Deathlike]

I wonder if it is a partly network-related problem...

The only reason why I say that when the radar/minimap goes out, the lance info is all messed up... and lists ?? as locations. Although.. it could simply be that the code is tied to the minimap interface, so it's a logical breakdown.

Edited by Deathlike, 29 April 2013 - 09:43 PM.

[The_Furthest_Man_From_Home]

One match (Alpine - Assault) when I had ZERO HUD, nothing...no map, no reticle, no weapons display, no compass, no scoreboard, NOTHING.

So I started playing around with it and I found out that if I powered down my mech and then powered back up again, the entire HUD would appear for a few seconds and then disappear again.

[Argent Usher]

CPU: Intel Intel® Core™ i7-3770K CPU @ 3.50GHz
GPU: NVIDIA GeForce GTX 670 (Driver Version 314.07)

All maps

[Groutknoll]

From /Logbackups/omicron Build* Files

Spoiler

CPU: Intel	   Intel® Core™ i7-3610QM CPU @ 2.30GHz
Windows 7 64 bit SP 1 (build 6.1.7601)
8088MB physical memory installed, 6281MB available, 4095MB virtual memory installed, 22 percent of memory in use
PageFile usage: 28MB, Working Set: 20MB, Peak PageFile usage: 29MB,
Current display mode is 1920x1080x32, (Unknown graphics card)
my graphics card is NVidia GT 650m, don't know why it is unknown in this logfile, latest drivers

The hud/map bugs are st the start of a match, right after mech power on. I seem to get a 50-60% increase of bugs when I have ie 10 and mwo running (seems to be 1 in 10 games with out ie running and 6-7 in 10 games with ie running).

While looking to see why I was getting a fps degrade I looked at the /Logbackups/omicron Build* Files and seen a number of errors. The logfiles are around the time I was getting hud/map bugs, I posted some of the errors from one logfile here.

Edited by Groutknoll, 29 April 2013 - 10:24 PM.

[Vxheous]

Desktop: i5 3570K @ 4.4Ghz, 8GB RAM, Nvidia GTX 570. 1920x1080, all settings ultra high, shadows low, v-sync on.
Laptop: i7 2630QM, 8GB RAM, Nvidia GTX 560M. 1920x1080, all settings low, v-sync on.

Additional bug noted: Arm's locked, even though it is not selected in options, left-shift does not change it. However, when this bug occurs, it appears my torso twists alot faster than it normally does when arm-lock is used.

[Pertz]

• When/Where the Issue first appears

Always from the beginning of the match

• Whether or not the issue appears only after performing certain actions in the menus

No pattern, occurs frequently when just repeatedly launching games.

• Whether or not the issue appears in sequences.

None noticable.

• Whether or not the player was performing any specific actions prior to appearance.

None noticable.

• Whether any other issues were occuring at the same time.

Sometimes the large map comes up invisible. By this I mean when I press b it blocks mech input and shows the cursor, but does not actually show the visual overlay.

Another bug I have is no chat.

Sometimes the no chat bug occurs only when I am spectating.

Phenom II 745
XFX Radeon 7850

Custom settings: Low everything except high textures.

[K o i l]

Same as everyone has described above, but there is also another bug where you die, but are unable to spectate as the match continues on. Not sure if it falls into the same arena, but thought I would throw it out there.

Bugs are always visible right at power up, after the animated sequence.

Never been able to rectify or get rid of it. When they happen, you got it the whole match.

Seem to get the no map at all / black square with arrow pointing up more than the others, but have experienced them all at some point or another.


GPU: AMD XFX R7870
CPU: I7 870

Edited by K o i l, 29 April 2013 - 11:24 PM.

[SirLankyIII]

cpu - I7 920
gpu - radeon hd 5750

ram is actually 6gb, not 8gb

edit: scratch that cpu is a 920 at 2.67 ghz, not a 260, which probably doesn't exist

Edited by SirLankyIII, 30 April 2013 - 04:09 AM.

[Kageru Ikazuchi]

CPU: Intel Core i5-3470, GPU: GTX 670 (GIGABYTE GV-N670OC-2GD)

Never had the kaleidoscope bug ... HUD bugs I can remember ...

• No HUD, minimap, scoreboard, etc. at all (most frustrating, because I can't even chat that I have a problem)
  
• No HUD (but have blue/red triangles on minimap)
  
• Conquest scoreboard red/blue swapped (cap points were right on the HUD, minimap and battlegrid)
  
• Minimap locked north
  
• No minimap, but blue/red triangles on black screen
  
• Rainbow minimap
  
• weird reticule around the crosshairs (looked like a concept, possibly?)
  
• WWWWWWWWWWWWWWWWWWWWWWW instead of mech name
  
• a constantly changing number (looks like some kind of coordinates) instead of mech name
  
• Minimap shrunk

The bugs last for the entire match and persist when spectating.

[Tahribator]

CPU: Intel i7 2670QM
GPU: Nvidia Geforce 555M


When/Where the Issue first appears: Randomly after mech start-up sequence. It's a dice roll every time.
Whether or not the issue appears only after performing certain actions in the menus: No menu action necessary.
Whether or not the issue appears in sequences: Seems totally random.
Whether or not the player was performing any specific actions prior to appearance: I sometimes alt-tab during loading screen. Not sure if it's related.
Whether any other issues were occuring at the same time: On my low-end system HUD bugs also affect FPS, considerably lowering them.

I also had other bugs;

• Coordinates replacing mech name(numbers changing when I move).
  
• Cap indicators disappearing in conquest.
  
• Cap scores being replaced by "undefined" in conquest.
  
• Coordinates replacing cap scores(?!?)
  
• FPS getting progressively worse during a HUD-bugged game and ultimately crashing to desktop.

Weird, but I never got a corruption in weapons box.

Edited by Tahribator, 30 April 2013 - 01:27 AM.

[Windrider]

Processor: AMD FX-6100 6 core
Graphics Card: AMD Radeon HD 6900

Additional HUD issues:

I have had situations where my mech controls get locked up when I try to access the Scoreboard or the Map. Usually once this happens the game either freezes or crashed out completely. Occasionally I am able to alt-tab out of the game and then come back in and the issue corrects itself, but that works less then 20% of the time.

Note, I play fullscreen mode, but I do have dual monitors.

[Homeless Bill]

The only way to reliably reproduce a HUD bug that I know of is 3x zoom. At least 50% of the time in 3x zoom, I have no IFF indicators. Everything else seems to be random: the minimap issues, the crashes, etc.

GTX 680
i7 3770k