11 replies to this topic

[-Natural Selection-]

Logged in and switched to DX11. Just into a match and can see through objects near and far. Enemy standing there plain as day, only they are behind the wall 100m from me. Would be an advantage but you cant see the stuff you are running into. Think it might be good times for some teams to have a guy with this ability?


*the game did crash to desktop during the match.

[wolf74]

Can you upload a Screen shot of this please. Also What Video Card are you using. It almost Sound like the old ATI Anti-Aliasing bug. If you tried to force the Card from the Drivers it would do a See Thought ghosting Effect.

[-Natural Selection-]

Eww. This is funny! Looks like maps made of glass. I started recording, but this seems to also cause a crash. Its NVIDIA btw, but not stressing it. Nothing on my end changed and Ill play if it works and something else if it don't.

[Grendel408]

PCs utilizing SLI are having issues... try disabling that and testing it again (assuming you're running SLI setup)

[Wildstreak]

I cannot run DX11 but I can tell you under DX9 with graphics set to Low, there are still places where you can see through terrain. Recently had one on Caustic at the Training Grounds, could see the Cataphract target but when I shot it, hits did not register until I changed my location, hitting invisible terrain.

Point, if you can see through objects, might be graphics settings, don't know what yours are.

Edited by Merchant, 04 March 2014 - 07:38 PM.

[Grendel408]

I run my settings on High, no vsync... no motion blur. GPU is a ATI Radeon HD6850 overclocked, CPU is i7 3770K, 8GB Gskill Memory, Mobo Asus Z77-A, Corsair TX-750w PSU, all running on a OCZ 2gb SSD. Video resolution is set at 1920x1080, avg 32-46 FPS depending on how much is going on at any given moment in-game.

I do notice sometimes that some terrain begin to form to its supposed design as I approach during the first 2-3 minutes of the game... but have yet to see through terrain as you've posted... could be a graphics setting. Might want to check to ensure your GPU software settings don't conflict with MWO in-game settings, or allow the GPU software to allow the program (MWO) to determine settings, which at that point you just adjust your MWO settings.

Edit Note: I've yet to patch today so I can only tell you what I've experience thus far.

Edited by Grendel408, 05 March 2014 - 12:01 AM.

[ImperialKnight]

running SLI or XFire?

[wolf74]

Go in to your Catalyst Control Center, and Set your anti-alaising to Use application settings. If you try to Override the Game setting at the Driver level you get the Glass Look. OLD bug with ATI cards.



****Edit***
Catalyst Control Center
-Gaming
--3d Appication Settings
---Anti-Aliasing Mode : "Use application settings"
---Anti-Aliasing Samples : "Use application setting"


the above is the Logic Tree you will see in the CCC.

Edited by wolf74, 04 March 2014 - 10:03 PM.

[Grendel408]

As I stated in longhand, wolf74 just bluntly tells you LOL! love it And if it's a Nvidia card, there's a similar approach to that as well, Dozier.

All in all tonight though, DX11 was running pretty stable it didn't reset my graphics settings like they stated, but my FPS dipped about 10-12 below it's average as I stated previously.

[xengk]

Do you mean something like this?
Every object in the game that is not part of the map are transparent.

I encountered this in January 2014, reported to support and they recommend me to redownload the objects.pak, skyboxes_ig.pak, and textures.pak from their patching server.

But I was away for holiday and only came back after the 4th Jan patch was release.
Updating to that patch fixed my problem.

Maybe you can try the similar approach by contacting support.

[Shamous13]

I had some nasty problems last night running DX11, CTD, missing parts on mechs, missing terrain, when loading in to mech lab the componets on a mech would load in one section at a time. running the repair tool and removing the systemoverride.cfg solved the problems.

[-Natural Selection-]

Yes, I ended up having to delete mu user.cfg (some people may not have this), systemoverride.cfg , and run repair.