8 replies to this topic

[cSand]

I had an idea, let's get some system specs from all you folks having "the" texture issue..

Post em up, we'll see if we can't find something we have in common perhaps?

I cleared mine up by setting my anti-aliasing in Catalyst control center to plain old "multisampling." Not sure that is the issue for sure though since some nVidia folks are seeing it too, (also those who aren't using AA)

-system specs
-game settings
-any other issues you're having
-video card settings too

If there's a thread like this, I couldn't see one, but if there is, I apologize

Edited by cSand, 14 January 2014 - 05:43 PM.

[Durant Carlyle]

Intel Core i7-4700 CPU
ASUS Z87 Gryphon mATX MB
Corsair Vengeance LP 4x4GB 1600 RAM
EVGA GTX 780 SuperClocked w/ ACX 3GB GPU (+52 core and +286 memory in Precision X)
Samsung 840 Pro 256GB SSD
Seagate Barracuda 3TB 7200 RPM HD
ASUS BW-12B1ST DVD Writer Blu-Ray Player
ASUS PB278Q 27" 2560x1440 Monitor
Razer BlackWidow Ultimate 2013 Keyboard
Razer Taipan Laser Gaming Mouse
Razer Kabuto Mouse Mat
Plantronics Headset
Win7 Pro 64-Bit

Nvidia 332.21 drivers

Game settings don't matter -- have textures in FC and FCN only about 50% of the time. AP has the problem too, but nowhere near as often. My usual settings are 2560x1440, full-screen, everything maxed. Have tried other settings, but problem persists. Also happens even if I don't everclock the GPU.

Nvidia driver settings: Have mine set to Application-Controlled and Performance when applicable. AA-Transparency set to Multisample.

At one point a few patches ago, the problem had nearly disappeared. Only about 1 in 10 matches on FC/FCN didn't have textures. Lately it has been about half of the matches.

[Werewolf486 ScorpS]

I appreciate what you are doing, but it's not us, it's them. If it happened on more then just FC/N then I would say yeah it could be us, but I garantee you it's not us. Yes our system specs could contribute to the frequency that it happens, but our computers are not to blame for this. I have MWO on 4 different systems in my house with a mix of cards new and old, both AMD HD4870's and HD7870's to nVidia GTX550 ti. All intel CPU's from a Wolfsdale E8500 dual core to a Haswell 4770k to my new 4930K in my Rampage Black.

[Dexter Herbivore]

64 bit OS is the common factor. That much has already been worked out.

[Sparks Murphey]

Werewolf486, on 14 January 2014 - 09:32 PM, said:

I appreciate what you are doing, but it's not us, it's them. If it happened on more then just FC/N then I would say yeah it could be us, but I garantee you it's not us. Yes our system specs could contribute to the frequency that it happens, but our computers are not to blame for this. I have MWO on 4 different systems in my house with a mix of cards new and old, both AMD HD4870's and HD7870's to nVidia GTX550 ti. All intel CPU's from a Wolfsdale E8500 dual core to a Haswell 4770k to my new 4930K in my Rampage Black.

I don't think that's the point of the thread. This isn't a us/versus them thing, it's a "let's get some common system specs to see if we can help PGI find a solution". If it works fine on some computers but not others, then in at least some factor those afflicted computers have in common is related to the problem, even if it is a software problem. Narrowing this down will help identify exactly which 0 needs to become a 1 (or whatever the problem is) to allow a fix.

[Werewolf486 ScorpS]

Sparks Murphey, on 15 January 2014 - 12:12 AM, said:

I don't think that's the point of the thread. This isn't a us/versus them thing, it's a "let's get some common system specs to see if we can help PGI find a solution". If it works fine on some computers but not others, then in at least some factor those afflicted computers have in common is related to the problem, even if it is a software problem. Narrowing this down will help identify exactly which 0 needs to become a 1 (or whatever the problem is) to allow a fix.

I can tell you that the system commonality has nothing to do with it. It has to do with the map, I've seen this before as an alpha tester with MWLL, it has to do with how the map has been built. Seems like the map has corrupted testures, or theres a conflict in how they are called in. I'm telling you this is an utter waste of effort on our parts, they simply need to spend the time to go through the map and find the issue and correct it, unless they lost some of the files on the map at which point this map is what it is and shall never work right. As for it working right on some systems an not others, I can't believe that anyone who plays this game hasn't experianced it and I can't believe that there's even one system that has never had this issue with this map.

[Tarl Cabot]

Believe!!

For myself, I had this issue once. Changed forced video card settings to application control, no more issue. For others it could be with unstable or too aggressive memory settings.

And PGI, if the issue is purely in their code, would need to be able to replicate it internally, constantly then track down the interdependency lines of code, across several files.

And it takes those who are being affected to report it to PGI. And posting about it like this thread may help those who are not reporting it but simply taking it into stride the encouragement to actually report it with the necessary information.

[Golrar]

I did not have this issue until the last major patch in December. I have tried everything up to and including reinstalling the game. It was about a 1:1 ratio at first with textures/no textures, but now I never see them. Sometimes when flipping from heat/ regular vision I will get a texture flash if I am close to a building.

Like most people say though, they are familiar enough with the map that it doesn't affect them. However, you kind of want the game to work right every time. I am also of the belief this is not on the client side or some combination of video card settings or such. Too many variables involved in the community that is experiencing this for there to be a common denominator on the user side.

[Wildstreak]

Processor Type: Core2Duo E2200
Processor Speed: 2.20 GHz
Operating System / Service Pack: Windows Vista™ Home Premium (6.0, Build 6002) Service Pack 2 (6002.vistasp2_gdr.130104-1437)
System RAM: 2 GB
Video Card Manufacturer: NVIDIA
Video Card Model: Geforce 8500 GT
Video Card RAM: 512 MB
Video Card Driver Version: 9.18.0013.1422 (English)

Game Settings: Low on everything

Issues:
- Terra Therma at start does not show textures, used to. All ground is dark grey with white lines.
- Used to have the FC textures problem. Thought a patch fixed it but I did try changing a few settings seen below. Now FC is fine, just when TT starts.
- River City, I used to get flickering at the beginning, have not played it much lately to be sure.

Ambient Occlusion: Off
Anisotropic Filtering: Application Controlled
Antialiasing - FXAA: Off
Antialiasing - Gamma Correction: On
Antialiasing - Mode: Application Controlled
Antialiasing - Setting: (greyed out) Application Controlled
Antialiasing - Transparency: Multisampling
CUDA - GPUs: All
Maximum pre-rendered frames: Use the 3D Application Setting
Multi-display/Mixed-GPU Acceleration: Single Display Performance Mode
Texture Filtering - Anisotrpoic Sample: On
Texture Filtering - Negative LOD Bias: Allow
Texture Filtering - Quality: Performance
Texture Filtering - Trilinear Optimization: On
Threaded Optimization: Auto
Triple Buffering: On
Vertical Sync: Use the 3D Application Setting