136 replies to this topic

[Bootsock]

Issues were:

• I had a strange issue, where despite client restarts and reboots, the options setting was 'full screen', but in game image appeared windowed in the top left of the screen. Alt-tabbing out of MWO, minimising it, then alt-tabbing back to MWO made it return to full screen. This issue went away when I'd worked out how to work-around the resolution issue too (apologies, I missed saving this as a screen-shot).
  
• There's a problem with resolution switching which seems to be related to new installations. I found the options to swap resolutions are missing (as shown here) and don't reappear in DX11 using a new install of the public test client (worked around eventually by going DX9 > restart client > change res > DX11 > restart client). On another machine which has run every public test to date all the expected options were there present in DX9 and DX11 and worked correctly.
  
• This error on launching second match (one off issue).
  
• Foot-step noises were missing.

Plus points to note were:

• Relatively few noticeable graphics glitches.
  
• Lighting effects seem to be much more impressive, pleasant or noticeable (more vibrant?) in this version.
  
• Only a small performance drop.
  
• Stable other than the crash with error on the second match - this only happened once.
  
• Well done, looks pretty close to ready!

Spoiler

------------------


System Information
------------------
Time of this report: 11/7/2013, 20:41:56
Machine name: XPC
Operating System: Windows 8.1 64-bit (6.3, Build 9600) (9600.winblue_gdr.130913-2141)
Language: English (Regional Setting: English)
System Manufacturer: Shuttle Inc.
System Model: SZ77
BIOS: BIOS Date: 05/14/13 11:32:35 Ver: 04.06.05
Processor: Intel® Core™ i7-3770S CPU @ 3.10GHz (8 CPUs), ~3.1GHz
Memory: 16384MB RAM
Available OS Memory: 16348MB RAM
Page File: 2273MB used, 16507MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.03.9600.16384 64bit Unicode
---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 760
Manufacturer: NVIDIA
Chip type: GeForce GTX 760
DAC type: Integrated RAMDAC
Device Type: Full Device
Device Key: Enum\PCI\VEN_10DE&DEV_1187&SUBSYS_27663842&REV_A1
Dedicated Memory: 3996 MB
Current Mode: 1920 x 1080 (32 bit) (59Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: PL2473HD
Monitor Id: IVM6107
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: HDMI

Edited by Bootsock, 07 November 2013 - 12:54 PM.

[drizz786]

GrimlockONE, on 07 November 2013 - 10:57 AM, said:

Well...if I cant choose resolution..and I am stuck in full window, I will go ahead and call this fail. How can you not have those options enabled for Windows 8 and 8.1?

amd x6 1100t @4.2
asus saber 990fx board r2
16 gig vengance 1866 @1864
kfa2 670 ex oc sli 2 way
2560x1440 hazro monitor
win 8.1 nv 331.65 driver

Apart from afore mentioned fot steps and map bug, test was ok so for me nice step up with no fps drop.
Easy fix for res is , reset to dx9, choose res, reset to dx11 restart and it holds res.

[Harmatia]

System Specs: i7 930 (2.8ghz), 12GB DDR3, Radeon 6950 2GB, Windows 7 64bit SP1.

I did two passes on each map in training grounds, once in-cockpit with a Shadowhawk and once 3rd person with a Locust. In addition I did 5 assault games.

• No footstep sounds.
  
• Minimal Screen tearing on Terra Therma in the caldera and throughout whole Alpine Peaks.
  
• Caustic Valley Performance drop.
  
• No mech foot effects, like water splashes or dust kick-up that are present in DX9.
  
• Canyon Network was slow (up to 15 seconds) to load game assets once game started.

Other than that the performance and stability seemed pretty good.

[Goose]

Screen would go black momentarily when I received my first missile strike; SRM or LRM, I guess.

That one thing that sparks in the 'mech bay was reduced down to one path …

Edited by Goose, 07 November 2013 - 02:44 PM.

[WaddisznoHUN]

Hi!

Spec.:
CoreI7 965 Extreme Edition Watercooled
Win7 64bit 1920x1080p
12 Gb Ram
Nvidia GTX 590 (two cores) Watercooled

In dx9 /my graphics card core0(Physx) not utilizing, the core1 takes about 98% utilized, graph settings very high all option vsync on/ after the start 60 fps / in the middle of big battle 40-50 fps

In dx11 /my graphics card core0(Physx) not utilizing, the core1 takes about 45-55% utilized, graph settings same as above/
after the start 30 fps / in the middle of big battle 10-20 fps, especially low(8-15) when smoke, or steam particle showing.
when i turn off the shadow the fps stabilizing on 60 frame/sec.

In the test 2 hour i have 2 crashing with black screen and have 10-12 playable run.

I use playclaw and i see the MWO using Dx11/32 bit mode not utilizing 64 bit...

Cheers!!!

Sincerelly

Waddiszno

[JD R]

With MSAA and TXAA the fps is nearly halve around 30-35fps compared to PostAA.


With MSAA Heatview shows sometimes black Mechs.
http://i44.tinypic.com/2uek4dd.jpg


On TXAA the mini Map shows more than the normal area.
http://i43.tinypic.com/24qnv3r.jpg

Got a few crashes from switching from PostAA without the message of need to restart the client.

Spoiler

Intel i7 3770
Nvidia 660ti newest Driver
16Gb Ram
1680x1050
All settings very high
Motion Blur High

[SgtMagor]

no resolution option
no foot step sounds
jump jet animation choppy
my mech movement in 3rd and first person is choppy (stopNgo)
frame rate drop to low 20's almost unplayable
laser beams look cut up into to small strips sometimes

I7-720qm
HD5800m

[Trucker]

System Spec
i7 3770k @ 4.7ghz
16g 2333mhz ram
GTX 780 @ 980
Windows 7
1920x1080 resolution


Feedback

TXAA worked fine, Post AA didn't do anything. Not enough time to test other AA settings

No footstep sounds (known)
No foot print details on the ground

Overall FPS has dropped by 50% from ~140fps to ~70fps

Minor Issues.

Mechlab component highlight on mech with Applejack skin does not highlight whole section



Range of target while Adv. Zoom active shows 0m.

[Veranova]

Intel i7-3770k Stock
GTX 680 2gb Factory OC
16gb Ram
256gb SSD Installations drive
I keep my system very clean and maintained for performance reasons.


Mostly incredibly stable, unusually smooth gameplay for MWO. A few little stutters occasionally, but could have been related to caching as I didn't play any maps more than once.

I had one issue where I was tabbed out during load, and then when the window came up I couldn't get back in to the game. After a bit of tabbing, the game then appeared as a tiny window in the middle of my screen. However as soon as the countdown timer reset to 20 seconds the game went fullscreen, and was fine except appearing a little blurry. Blurriness was fixed by a resolution cycle to a different resolution.
I haven't checked whether this is reproducible, as I wasn't in the test server for long enough.

My Mechs didn't have footstep sounds. But that's not related to DX11 probably.

Overall there's nothing worse than we're already used to, and nothing critical which I came across.

Edited by Veranova, 07 November 2013 - 12:43 PM.

[Neanot]

Win 7 64x
8Gb Ram
AMD Phenom™ II X4 965
ATI Radeon HD 7790

Everything ran fine, no stability issues save the no footsteps.
My FPS seemed to be soft-capped at 30fps. It would not go above that, no matter what settings I was using, and only dropped below under extreme load (middle of firefight with lots of explosion and in thermal vision). V-sync on or off both gave 30fps in game.
DX9 FPS normally around 50 with all setting on highest.

[DarthPayne]

Intel Core i7-3770S 3.1GHz, AMD Radeon HD 7790, Catalyst Driver v13.9, Windows 7 Pro 64bit.
Generally a slight reduction of FPS at the same detail settings, maybe minus 5-10 FPS in average. I'm not at full detail settings and get in the range of 45-65 FPS at 2048x1152 fullscreen. Full details get me down to 12-24 FPS.
Stability was in-game good. Twice, I got a short standstill of about 1 second each pretty much at the beginning after the unit lineup (maybe 2-4 seconds after start). Twice, I got a black screen exiting the client with no CPU usage. Had to kill the process in Task Manager.
I saw no significant visual differences to the productive version. Changing detail settings in-game didn't have large changes in FPS but restarting the client would make a big difference but I think that's the same with DX9.
Well, that's about what I can say about my experience. Doesn't make a difference visually but if it helps the devs in further development, that's great. Happy hacking.

[BladeXXL]

SnowdogJJJ, on 07 November 2013 - 11:23 AM, said:

• GTX 560
  
• Dual monitor - 1920 x1080 game screen (not the game window), a black bar runs over to the 2nd monitor (Alt tab fixes)
  
• Steps to Reproduce
  
  • always
• Fix - ALt Tab out and back

• GTX 560 Dual monitor - 1920 x1080 game screen
  
• Twitch stops moving on 2nd screen . all video stops on 2nd screen (Alt tab fixes)
  
• Steps to Reproduce
  
  • always
• Fix - Alt Tab out and back

...same to me!
Runing dual monitor Setup, the 2nd Monitor is broken while dropping ingame in full screen mode.

The reason is Aero! Seems to be a CryEngine issue:
http://www.colonyofg...hp/t-23710.html

Workaround:
Check "Disable Desktop Composition" in properties (tab compatibility) of the MWO link.
Now everything is fine!


-----------------------

1 more issue:
The Mechs sometimes disappears after Alt-tabbing


Switching 3PV and back a couple of times helped.

Edited by BladeXXL, 07 November 2013 - 01:31 PM.

[Edmiester]

• Your System Specifications
  Spoiler

  - CPU: Intel 4770K - GPU: GTX 770 - SoundCard: Sound Blaster Titanium Fatal1ty Professional - RAM: DDR3-1866 G.Skill Sniper CL9 - SSD: Intel 520 180GB - OS: Windows 7 SP1 64-bit
  
  
• Description of the Bug
  Spoiler

  - Any sound, when it flashes the black screen right after it finds a game and just before it hits the map loading screen, is muted: e.g. When someone's talking on TeamSpeak3, if they are speaking through the black screen just before the map loading screen, you don't hear them speak during that period. I was in full screen mode. Last update of driver from Creative: July - 2013
  
  
• Steps to Reproduce
  Spoiler

  Have someone speak during searching non-stop in TeamSpeak3 (or maybe any kind of sound) until it loads the map loading screen (and maybe some after) or even until it launches with the pilot names.

[Lupin]

Downloaded new test version of software for the first time.
First match on Canyon Network game crashed and got this error before I chance any options (Windowed 1280x720):

Uploaded with ImageShack.com

After reloading program I did not get error again after 5 matches (Tourmaline Desert,Terra Therma, Frozen City) and playing using medium (FPS 40+), high (FPS 40+) and very high (FPS dropped to 24 and under) settings at 1680x1050. Windowed at 1280x720.

Windows 7 64bit
AMD Phenom ™ II x4 850
8mg memory
Nvidia Geforce GTX 560.

[C12AZyED]

Specs:

i7 2600k
8 gig RAM
670 gtx

Large framerate dips when mass LRMs are present on screen. Particle effects from close up laser beams and flamer also cause significant framerate drop. These issues are also present in DX9 as well as DX11.

[Dirk Le Daring]

Unable to play.

"A network error occurred" is being displayed every time I try to log in.

Can still get into the live (non test) version of the game though.


Edit:
I think I had the times wrong, by an hour. Is there daylight saving there now ?

Edit:
Yep, I'm going with daylight saving.

Edit:
Overall there were no issues that crossed my path with this test.

Looks like you're on the right track PGI. Keep up the good work.

Edited by Dirk Le Daring, 07 November 2013 - 06:09 PM.

[Skelshy]

Matthew Craig, on 07 November 2013 - 10:28 AM, said:

Anyone experiencing this, if you have time to try updating your drivers to latest that may help. If not then we still have some work to do most likely, if you can post your dxdiag info so we can try and repro with your same setup.

I got this error too. dxdiag: http://sdrv.ms/HBoIBE. latest nvidia drivers. just getting into a match. tried twice.

Edited by Skelshy, 07 November 2013 - 04:14 PM.

[Matthew Craig]

Windows 8.1 appears to have other issues primarily around selecting resolution, bear in mind even the DX9 path doesn't officially support Windows 8.1 yet

[Mellowseven]

System Specs: (if a button for spoiler was available i would use it, but since i don't actually see one here....)
AMD FX-8300 Eight-Core Processor 3.3 GHz
16 GB RAM
64-bit Windows 8 (i have not installed 8.1 yet)
AMD Radeon HD 7700 graphics card

Bug #1
When I first logged in the option to choose a direct x version was greyed out and DX9 was selected. I exited the client and logged back in the direct x 11 was selected and I was able to choose.

Bug #2
Unable to choose resolution

Bug #3
FPS was at 60 pretty solid in the training grounds until firing missiles. It dropped to the high 20s, low 30s with missiles. It also sometimes stuttered pretty hard for no reason i could see. In a match it stayed closer to 30-40 all the time. I noticed less stuttering but maybe that is because it never got high enough to stutter from.

Edited by Mellowseven, 07 November 2013 - 04:39 PM.

[Galil Nain]

Mister Blastman, on 07 November 2013 - 10:44 AM, said:

I've found a VERY strange bug in the public DX 11 test today. When the game starts a drop--i.e. goes to the loading screen, my screen goes completely black. Alt-tabbing, ctrl-alt deleting, none of that will get me video back. The game will even start and the screen will stay black. The only way to fix it is to completely power-cycle my monitor. That means I have to turn it off, then turn it back on again to get video.

I have no idea what is causing this but it is an interesting and annoying bug.

Specs:
3770k
670 GTX
16 gigs RAM
Windows 7 64-bit

I don't have this problem in the regular game but of course, it isn't DX 11 either. It happens every game.

Have you tried pressing the Auto-Adjust button on your monitor? I've seen other programs do the same thing (albeit rarely) and this solves it in nearly all cases.

I would guess that the video being sent to your monitor is off-centre, so it simply displays nothing. Power-cycling kicks off an auto-adjust, which fixes it, but an auto-adjust should fix it in less button-presses, not to mention less time. Still doesn't explain why the app, in this case MWO, is sending video to the monitor offset from centred?!?