As I reported before, the texture white out happens to me too.
Before that I had the out of memory crashes under direct3d 9 settings. Those crashes went away by using the direct3d 11 and since season 8 the direct3d 9ex settings.
Here are my specs:
Operating System: Windows 7 Professional 32-bit (6.1, Build 7601) Service Pack 1
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: GA-790FXTA-UD5
BIOS: Award Modular BIOS v6.00PG
Processor: AMD Phenom(tm) II X4 965 Processor (4 CPUs), ~3.4GHz
Memory: 4096MB RAM
Available OS Memory: 3326MB RAM
Page File: 1242MB used, 2354MB available
DirectX Version: DirectX 11
DxDiag Version: 6.01.7601.17514 32bit Unicode
I actually noticed this too. I was able to play for several hours in Q's Wonderland with many instance changes and never had the problem pop up. The one time I did have it show up was when I already had the messed up graphics from running around doing doff missions. The Wonderland did have the messed up graphics after that. But I haven't had it trigger from inside the Wonderland itself. Very odd.
I guess I'll join you eating pies and killing snowmen lol.
Maybe it's a conspiracy. A Q conspiracy to make you stay in Winterland... FOREVEEEEEEEER!!
Or the Iconians are slowly pushing the galaxy out of phase, right into the Eternal Light, because the Eternal Darkness is already owned by Nintendo and the Big I prefer not to mess with the Big N.
Another spec for the list.
WinXP SP3 32 bit, dx9 of course
Phenom II X4 955 @321 GHz
nVidia Geforce GTX 760 w/ 2GB GDDR5 vram
No overclocking of any kind, no heat problems of any kind.
No graphic problems in Season 7, but missing textures, wrong colors, etc in Season 8, every single day, sometimes occurring right from the start (missing textures in the character select screen), sometimes taking as long as an hour or 2 to happen.
Entering DS9 is pretty much GUARANTEED to cause it. I can't remember the last time I got there and didn't see people with missing costume textures.
Curiously, they aren't missing all the textures, just some of them, and editing my own costume, I might have one or several textures missing. IE all the costume is there except the boot textures.
Now way back when in another Cryptic game, City of Heroes, they had other texture problems, so they added the /reloadgfx command which would force a reload of textures..
Maybe that was added after Cryptic left and Paragon took over - I forget exactly when it went in.
Please Cryptic, until you can figure out what's causing the corruption and misloading of textures and color, ADD THIS COMMAND to this game so we can at least see what we're doing without having to relog all the time in the hopes it might fix it.
That's not really an option in some long missions that you have to redo from the start if you leave, with no guarantee the texture bug isn't going to strike again part way through once you do restart it.
Things like Borg encounters where your graphics are fine until you answer the alert, but when you arrive it's pure white space with white ships, white beams etc and all your tray icons are invisible.
Or the "fun" of scanning for some element, and having to match the signals, only instead of matching red to blue, you have to match black to black on a black background.
A reload textures command isn't a fix, but a workaround to let people keep on playing in cases where logging out isn't an option (not that relogging is guaranteed to fix the problem since it can occur on game startup.) and it could be bound to a key for an instant (nearly) reload of the graphics every time they screw up (more often for some than others.)
Exiting the game and restarting ISN'T FUN, and since the problem can reoccur almost instantly, it really makes the game suck when the graphics go all 1980s low res or worse.
Consistently getting the texture bug after 30 minutes normal play, stayed on new romulas walking everywhere not using transporter over one and a half hours no problem, beamed to my ship instant texture bugs.
Taco you've said the team are looking into this any progress?
I did bring it up, and we're working on reproducing this problem in house. This is often why bugs slip through. We can test all we want, and still not end up with the exact circumstances that cause something to occur. Then, once it's sent out to thousands of people, there can be many people who happen to fit that criteria perfectly. Unfortunately, it's not always clear what that is.
Can you folks who are affected post a little info about your systems? Specifically, what video card you are using?
One in each PC, nvidia GTX 660 2GB, (one is from Galaxy, the other Gigabyte [GV-N660OC-2GD])
The Galaxy is slotted in a PCIex16 2.1, the Gigabyte is in a PCIex16 3.0 and that's the one with issues.