Hi there my game since the update to LOR is intermittently crashing with the following error msg
Fatal error: There is not enough available video memory(D3DERR,OUTOFVIDEOMEMORY) While while creating a render target texture. Please choose lower resolution settings, or close other graphics application.
Techencial Details: D3DERR.OUTOFVIDEMEMORY while creating 2d render target texture size 3072x2048 (RTEX_NVIDIA_INTZ_)
Note the bit in red changes in size
This is occurring in social zones such as new romulus, ESD, or orbit outside DS9, K-7 or ESD and also in sector space and occasionally when changing maps. Note never disconnects when launching into a Fleet action or starting a Feature episode.
Clocked frame rates, and in space average is 60 fps floats between 56-79 fps
Ground is steady at 31 fps but varies between 22-43 fps
I've been using the same graphics settings for the past 2 years and never had this issue once in the whole time in fact my card before LOR could handle the game maxed out with slow down in heavy space combat, i lowered my graphics in game to the lowest possible settings and still it can DC on me. It could be 30 mins or a couple of hrs of gameplay. I've run performance and bug tests on Windows and also on the Mac OS side (Running game in windows boot camp on a Imac late 09 version) no issues found. The card is capable of handling and running Blu-ray and high definition video
Specs of the Machine
Windows 7 32 bit
I5 Quad core processor 2.66 GHz
8GB Ram only 3GB usable to windows
ATi Radeon 4850 HD Graphics card 1.5GB shared memory 512MB dedicated video memory
Any suggestions other than uninstalling the game and reinstalling.
Same problem here. But only when beaming down on New Romulus' Staging Area. I installed everything again and defragg the hd but the problem is still there.
Prior, whenever my Romulan character beamed down to either the Command Center or the Staging area on New Romulus, i was getting these DirectX errors.
Also, one of my Fed characters, beaming down to the Defera Invasion zone, would get the same thing.
Now, someone found out that a recent MS update, KB2670838, was the culprit for them.
So, I uninstalled this update. And the DirectX errors stopped... BUT
Now, whenever these characters beam down to these zones, the game crashes completely.
When I restart the client, it may stall, and I have to close it out again and start up. The second time usually gets me back in.
I have also found out that even standing around or watching the cutscene videos on New Romulus will also crash the game.
I get this more or less, main culprit is New Romulas Command Center, and Flotilla, also i tried to get to do the Vault on my Romulan but when i get the Romulan Popup dialogue that you get upon arriving at the Vault it crashes.
Makes me wonder if it is something to do with the uniforms, i also get it randomly in Sol Spacedock, again Rom Uniforms could be present.
It is anoying, i paid to be a Lifer, brought LoR pack, spend a fortune on Zen yet they wont even respond to this bug, ive since stopped spending money on it as they seem to be sticking up two fingers and dont care one bit.
At least a Dev could aknowledge this, typical Cryptic it really is.
I think Cryptic is well aware of this issue... just do a Google search of this error msg: Fatal Error: Direct3D driver returned error code (E_OUTOFMEMORY) while creating a texture. Lots of reports all related to PWE, also including Neverwinter.
SOME TESTING DONE AND...
Well, I tried a few things that SO FAR are working. First of all, when I checked under OPTIONS/VIDEO/DISPLAY MODE I discovered that Fullscreen wasn't selected by default as in the past. Only a Max Windows screen. I changed that to Fullscreen.
On that very same tab, I went all the way down to TROUBLESHOOTING. On the first option you can change between AUTO, DirectX 9 and DirectX 11 beta. I selected DirectX 9 because I wasn't sure about the default setting. The option needs a game restart, so I did.
I tried beaming up and down New Romulus' Staging Area several times with my three characters (1 Fed, 1 Klingon and 1 Romulan) and SO FAR no crashes. I'll keep testing.
I think Cryptic is well aware of this issue... just do a Google search of this error msg: Fatal Error: Direct3D driver returned error code (E_OUTOFMEMORY) while creating a texture. Lots of reports all related to PWE, also including Neverwinter.
SOME TESTING DONE AND...
Well, I tried a few things that SO FAR are working. First of all, when I checked under OPTIONS/VIDEO/DISPLAY MODE I discovered that Fullscreen wasn't selected by default as in the past. Only a Max Windows screen. I changed that to Fullscreen.
On that very same tab, I went all the way down to TROUBLESHOOTING. On the first option you can change between AUTO, DirectX 9 and DirectX 11 beta. I selected DirectX 9 because I wasn't sure about the default setting. The option needs a game restart, so I did.
I tried beaming up and down New Romulus' Staging Area several times with my three characters (1 Fed, 1 Klingon and 1 Romulan) and SO FAR no crashes. I'll keep testing.
In short....Cryptic screwed up....AGAIN! They knew about this problem BEFORE LoR went live and still made the choice of releasing it the way it was.
BRANFLAKES! Get your *** down here and explain this SNAFU!:mad:
The PWE/Cryptic sweatshop...not where the game is made,but where the game is played!
Take back your home,end the grind!
Volunteer moderators policing the forums is like a mall cop trying to solve a murder.
Same problem here. But only when beaming down on New Romulus' Staging Area. I installed everything again and defragg the hd but the problem is still there.
'Fatal Error: Direct3D driver returned error code (E_OUTOFMEMORY) while creating a texture.
Technical Details: E_OUTOFMEMORY while creating 2D texture size 1024x1024 (11 mips, RTEX_DXT5), 954.00 MB, 87.60 MB virtual space available.'
I'm getting that exact same error, down to the file/memory sizes, was beginning to think it was my machine but apparently not. At first it was just NR, but now it's happening at any social hub.
Delirium Tremens
XO of Training
Tier 5 Starbase, Tier 3 Embassy, Tier 3 Dilithium Mine, Tier 3 Spire
Join us at www.dtfleet.com
The only things i can recommend to you all is to change the world texture quality and character texture quality. when the graphics engine is pushing the textures into ram on the gpu it is running out of space.
the other option is to turn down detail distance and it will lessen the load on the video card. I run at 5760x1080 at max settings and use 2.3GBGB of video ram on mt GTX 670. I hope this helps. The other
option is under trouble shooting which is changing the video memory limit to a lower value.
I think Cryptic is well aware of this issue... just do a Google search of this error msg: Fatal Error: Direct3D driver returned error code (E_OUTOFMEMORY) while creating a texture. Lots of reports all related to PWE, also including Neverwinter.
SOME TESTING DONE AND...
Well, I tried a few things that SO FAR are working. First of all, when I checked under OPTIONS/VIDEO/DISPLAY MODE I discovered that Fullscreen wasn't selected by default as in the past. Only a Max Windows screen. I changed that to Fullscreen.
On that very same tab, I went all the way down to TROUBLESHOOTING. On the first option you can change between AUTO, DirectX 9 and DirectX 11 beta. I selected DirectX 9 because I wasn't sure about the default setting. The option needs a game restart, so I did.
I tried beaming up and down New Romulus' Staging Area several times with my three characters (1 Fed, 1 Klingon and 1 Romulan) and SO FAR no crashes. I'll keep testing.
UPDATE: So far, one crash after 6 hours playing.
I'll give these a shot.
It actually crashed quite a bit over the weekend.
Something else I found out too, doesn't matter how you get to the Staging Area.
I was being from, I think Phaeros Crater, to the Staging Area, and the game crashed. One time, exited the Command Center, and right there on the steps it crashed.
[SIGPIC][/SIGPIC] @Aquitaine985 Lag Industries STO PvP Fleet - Executive
A Sad Panda of Industrial calibre. 2010: This is Cryptic PvP. Please hold the line, your call is very important to us...
Hi everyone in this thread - you can add me to the list of people with these annoying game-crash problems. So far these are the game-crashes I've had: :mad:
* I am online nearly every day and seems like not a day goes by without it crashing at least once or twice (usually several hours apart though)
* It randomly crashes when i'm barely doing anything at all - like just standing there reading something in zone chat (usually a few moments after I have entered a new instance somewhere) - other times I'm not doing anything major except opening a window like the character screen, or the duty-officer screen or any of those and it randomly crashes
* Sometimes if i turn my camera view around a bit too fast and sharply (i use a mouse) then it crashes or freezes everything
* Many times when it crashes I get the "Fatal Error: Direct3D driver returned error code (E_OUTOFMEMORY) while creating a texture" error message
* Other times I get NO error message after it has crashed
* Most game crashes for me so far have been when beaming down/entering New-Romulus - though they have also occured seemingly randomly throughout the whole game - certainly the "large-instances" with lots of stuff in them like New-Romulus and the Risa-Event are places it has occured a lot. Oh and it crashed during watching a cutscene on New-Romulus as well (seems like everytime I reload my game however it loads perfectly fine into New-Romulus or wherever it last crashed)
* Other times it has totally locked up my game on the loading-screens (any location anywhere in game randomly again it seems) - I cannot activate windows task-manager to force-quit the game - yet strangely enough when I have ventrillo running in the background, despite the game having locked, I can still hear/talk with my fleet buddies on vent - weird. Oh and as a result of this happening I am forced to manually-restart my computer at the power-button, rather than a proper shutdown/restart in windows.
* It has at least once or twice totally frozen my game, computer and everything, again forcing me to manually power-switch-off/restart - oh and it even once did this to me on the character-screen when I tried to go into the options to turn down my video settings before loading into the main game!!! (also my character screen always seems laggy) **hint hint** - possibly these texture out of memory bug things are due to character costumes - but who knows? I think the majority of crashes I've had were on ground instances......
* Possibly the worst thing it has done so far (once) was both my game and computer crashed and my computer restarted on its own (it might have blue-screened but it restarted so fast i don't know) - then it got stuck in some sort of constantly rebooting cycle and refused to load the bios (my screen remained blank, though i could hear the fans inside wirring speeding up each time as if it was getting ready to start loading the motherboard and everything, but seconds later they slowed down, then sped up again, repeatedly - all the time with no bios or anything loading on screen). Yet again I was forced to manually power-switch-off to stop it. Luckilly, (at least I HOPE) it was some sort of memory issue, since I left it turned off for a couple of hours, and when I came back it loaded up windows fine again AND the game too!
I can only hope it didn't cause any serious damage to any of my components. Also I hope none of them were already on the way out to fail anyway - especially given all the above mentioned problems I've been having. Though I doubt it given the fact, like many other people have mentioned, I did not have ANY of these problems before the Legacy of Romulus new season came out. Before the season, I was running full (almost totally maxed out) graphics settings in game, i'm still using the same graphics card, same OS XP-home-32bit, same all other components, all for about a year i think and had no problems (maybe the very rare game crash but that's all). Oh and someone suggested in the video options, under troubleshooting, to set your Video Memory Limit to Auto - mine was already set at Auto, and it was still crashing - i lowered my settings and it auto-changed to something else itself and it still crashes.
I've been forced to set my in game graphics settings to the default minimum since even mid-way between minimum and recommended settings seems to crash the game occasionally. I think at this level, despite my game graphics appearing utterly rubbish, the game is for now at least no longer crashing on me - though I only played for a few hours on this setting with no problems (particularly New-Romulus was NOT crashing) I need to play a lot longer to know for sure though. :eek:
Oh and I have NO problems doing or running anything else on my computer, I've got all up to date graphics-card-drivers etc, am pretty sure my comp is totally free of viruses and useless memory guzzling rubbish programs running in the background - so all these problems definitly point towards this obviously malfunctioning online game rather than my own equipment or software.
PLEASE PLEASE PLEASE WILL CRYPTIC DO SOME SERIOUS BUG FIXING ASAP!!!!!!!!
******
UPDATE
******
Well, first off and probably most importantly I have increased my computer VIRTUAL MEMORY and it seems to have slightly improved things for me. I don't seem to be getting quite so many crashes as I was I THINK, and the severity of the crashes doesn't seem quite so bad anymore (at least my game and computer isn't force rebooting itself anymore, and the game/computer doesn't lockup on me after a game crash.... much).
Sadly however the game IS STILL CRASHING (at least once or twice every time I have it on) randomly anywhere in game, though mostly around high "population" instance zones. Also New Romulus seems to remain a key location where it occurs more often than the rest of the game, but I must admit the frequency of crashes even here seems to have reduced since i increased my computer virtual memory.
Some people have mentioned to try to lower the in-game graphics (like "texture") and change some other graphics related settings in troubleshooting and stuff. Well, I can't personally say that this works, but get this:
Some time ago I got really fed up with these multiple crashes that i set all my in-game graphics to the absolute MINIMUM to test it out (the game really looks aweful of minimum setting lol). For a while it seemed to improve things - I wasn't getting any crashes.... The suddenly one day I log back in the game and BAM the game crashes, locks-up and locks my computer too (i can't remember where I was though - I THINK i was at QO-NOS academy!). It crashed on THE LOWEST DAMN GRAPHICS SETTINGS!!!! Also, someone suggested setting the DirectX option in "troubleshooting" to Auto - well I THINK mine was and always has been set to auto (though I'm not sure). So, it seems even setting your in-game graphics to minimum etc might not necessarily improve things. NOTE: THIS WAS BEFORE I INCREASED MY COMPUTER VIRTUAL MEMORY.
Like i said, increase virtual memory seems to have sort of improved things for me, but in the end it's not perfect and not even barely adequate - WHAT WE NEED IS THIS TEXTURE / DIRECTX / GRAPHICS / WHATEVER BUG THING FIXED (in BOTH games!!!!)
I had same problem. I ended up upgrading to windows 7 64 bit and increasing memory to 16G. Unfortunately upgrading from 32bit to 64bit requires a clean install and is time consuming. I have not crashed while on Romulus since I upgraded.
Vice Admiral James "Paladin" Taggart
Captain - U.S.S. Tiger's Claw
TOS Veterans Fleet
I got this when creating a new fleet emblem, and now it tells me if I try to use a fleet emblem on any uniform that it is an invalid part and won't place it on my character. So I got a double whammy for my error.
This game is insane. It forever crashes and forces a a total re-boot of my PC. Game usually crashes when is ship to ship combat, but does crash at any time really.
About time this was totallt fixed as for me, the game is unplayable. Not good enough guys!
Shame, as the game is very good - but you cannot have constant error and crashes with games of this type - it makes them pointless. People will unsubscribe and not pay for upgrades, nor trust the programmers again.
So far i know they have updated the Textures to an higher level with the Release of LOR.
I mean Cryptic sleep not they try to update the Graphics as well to match the todays technicaly Hardware level.
That mean older Systems (older graphic Cards) get suffered.
The first thing what you schould doe update your Graphic Card with the newest Driver, in some case that can help.
If not than you must make a compromise and lower the Details to an level that your Graphic Card can match.
If it too not help and the crashes still persist (than you should read the troubleshooting)
Its impossible to run the newest Graphics with High Details on a old Card.
That work in no Game.
A Star has died in a massive Supernova Explosion,at the same time he gave us the life.
Yes we are all just made of Stardust.
After a certain time the Stardust starts even to think.
Is that not fantastic?
Fatal Error: Direct 3D driver returned error code
(E_OUTOFMEMORY) while creating a texture.
Technical Details: E_OUTOFMEMORY while creating 2D texture
size 2048x2048 (12 mips, RTEX_DXT5), 810.91,76.56
MB virtual space available.
I have narrowed it down to New Romulus only. Whether I am beaming down or signing on and the toon is already there, the game crashes if I try to play the New Romulus map, particularly the Staging Area.
People,first of all,if the game worked fine before LoR and now crashes every time,the problem is not with your hardware.I have seen posts on this forum suggesting the game is crashing because you have an older graphics card,that is not true,people with the latest graphics cards have the same issues.
The problem is with a piece of DirectX code they added with LoR (it's the same piece of code they used for Neverwinter,people are reporting the exact same issues there!),as some of you may have noticed they have added a DirectX 11 option (which is still in Beta) to STO.
There is a way to stop your game from crashing,go to options,select video and scroll all the way down to 'troubleshooting',the first option there will be for your graphics card.Set DirectX to 'auto'.
This solution isn't perfect,2D textures might take a hit (not as pretty or floor panels showing up as black),but it will stop the game from crashing.
This will have to do till Cryptic gets their act together and fixes this DirectX mess they created.
The PWE/Cryptic sweatshop...not where the game is made,but where the game is played!
Take back your home,end the grind!
Volunteer moderators policing the forums is like a mall cop trying to solve a murder.
Comments
Dxdiag follows:
System Information
Time of this report: 6/9/2013, 20:29:46
Machine name: DANAE
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
Language: English (Regional Setting: English)
System Manufacturer: alienware
System Model: Area-51 7500 R6
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz (4 CPUs), ~2.8GHz
Memory: 8192MB RAM
Available OS Memory: 8190MB RAM
Page File: 2273MB used, 14105MB 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.01.7601.17514 32bit Unicode
DxDiag Notes
Display Tab 1: No problems found.
Display Tab 2: No problems found.
Sound Tab 1: No problems found.
Input Tab: No problems found.
DirectX Debug Levels
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
Display Devices
Card name: NVIDIA GeForce GTX 560 Ti
Manufacturer: NVIDIA
Chip type: GeForce GTX 560 Ti
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_1200&SUBSYS_15633842&REV_A1
Display Memory: 4050 MB
Dedicated Memory: 978 MB
Shared Memory: 3071 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: S230HL
Monitor Id: ACR0282
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: HD15
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 9.18.0013.1106 (English)
Driver Version: 9.18.13.1106
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 2/26/2013 00:32:38, 18055184 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
Device Identifier: {D7B71E3E-5140-11CF-A05F-6E351CC2C435}
Vendor ID: 0x10DE
Device ID: 0x1200
SubSys ID: 0x15633842
Revision ID: 0x00A1
Driver Strong Name: oem118.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section022:9.18.13.1106:pci\ven_10de&dev_1200
Rank Of Driver: 00E02001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
D3D9 Overlay: Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
Card name: NVIDIA GeForce GTX 560 Ti
Manufacturer: NVIDIA
Chip type: GeForce GTX 560 Ti
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_1200&SUBSYS_15633842&REV_A1
Display Memory: 4050 MB
Dedicated Memory: 978 MB
Shared Memory: 3071 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Acer X233H
Monitor Model: X233H
Monitor Id: ACR009A
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: HD15
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 9.18.0013.1106 (English)
Driver Version: 9.18.13.1106
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 2/26/2013 00:32:38, 18055184 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
Device Identifier: {D7B71E3E-5140-11CF-A05F-6E351CC2C435}
Vendor ID: 0x10DE
Device ID: 0x1200
SubSys ID: 0x15633842
Revision ID: 0x00A1
Driver Strong Name: oem118.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section022:9.18.13.1106:pci\ven_10de&dev_1200
Rank Of Driver: 00E02001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
D3D9 Overlay: Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
Sound Devices
Description: Speakers (Realtek High Definition Audio)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0883&SUBSYS_1043829E&REV_1000
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.5506 (English)
Driver Attributes: Final Retail
WHQL Logo'd: n/a
Date and Size: 6/27/2008 17:21:44, 1296280 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Basic
Cap Flags: 0x0
Min/Max Sample Rate: 0, 0
Static/Strm HW Mix Bufs: 0, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Sound Capture Devices
Description: Microphone (Realtek High Definition Audio)
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.5506 (English)
Driver Attributes: Final Retail
Date and Size: 6/27/2008 17:21:44, 1296280 bytes
Cap Flags: 0x0
Format Flags: 0x0
DirectInput Devices
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Keyboard
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: HID-compliant device
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x0B38, 0x0010
FF Driver: n/a
Device Name: HID-compliant consumer control device
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x0B38, 0x0010
FF Driver: n/a
Device Name: Razer Naga
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x1532, 0x002E
FF Driver: n/a
Device Name: Razer Naga
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x1532, 0x002E
FF Driver: n/a
Poll w/ Interrupt: No
USB Devices
+ USB Root Hub
| Vendor/Product ID: 0x10DE, 0x026D
| Matching Device ID: usb\root_hub
| Service: usbhub
Gameport Devices
PS/2 Devices
+ HID Keyboard Device
| Vendor/Product ID: 0x0B38, 0x0010
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
|
+ HID Keyboard Device
| Vendor/Product ID: 0x1532, 0x002E
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
|
+ HID-compliant mouse
| Vendor/Product ID: 0x1532, 0x002E
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
Disk & DVD/CD-ROM Drives
Drive: C:
Free Space: 27.5 GB
Total Space: 226.2 GB
File System: NTFS
Model: ST325041 0AS SCSI Disk Device
Drive:
Free Space: 1816.7 GB
Total Space: 1907.7 GB
File System: NTFS
Model: ST2000DL 003-9VT166 SCSI Disk Device
Drive: G:
Model: HL-DT-ST DVD-RAM GH22NP20 ATA Device
Driver: c:\windows\system32\drivers\cdrom.sys, 6.01.7601.17514 (English), , 0 bytes
System Devices
Name: PCI standard PCI-to-PCI bridge
Device ID: PCI\VEN_10DE&DEV_05BF&SUBSYS_00000000&REV_A2\5&428D74C&0&100018
Driver: n/a
Name:
Windows 7 Ultimate 32 bit, AMD Athlon II X3 455 Processor, 4 Gb RAM, NVidia GeForce GT 430 (1 Gb DDR).
Never have a problem BEFORE LoR.
'Fatal Error: Direct3D driver returned error code (E_OUTOFMEMORY) while creating a texture.
Technical Details: E_OUTOFMEMORY while creating 2D texture size 1024x1024 (11 mips, RTEX_DXT5), 954.00 MB, 87.60 MB virtual space available.'
It's time Cryptic took this issue serious and stop ignoring this,the game is unplayable like this.
Take back your home,end the grind!
Volunteer moderators policing the forums is like a mall cop trying to solve a murder.
Division Hispana
www.divisionhispana.com
But something has changed over the weekend.
Let me explain...
Prior, whenever my Romulan character beamed down to either the Command Center or the Staging area on New Romulus, i was getting these DirectX errors.
Also, one of my Fed characters, beaming down to the Defera Invasion zone, would get the same thing.
Now, someone found out that a recent MS update, KB2670838, was the culprit for them.
So, I uninstalled this update. And the DirectX errors stopped... BUT
Now, whenever these characters beam down to these zones, the game crashes completely.
When I restart the client, it may stall, and I have to close it out again and start up. The second time usually gets me back in.
I have also found out that even standing around or watching the cutscene videos on New Romulus will also crash the game.
I get this more or less, main culprit is New Romulas Command Center, and Flotilla, also i tried to get to do the Vault on my Romulan but when i get the Romulan Popup dialogue that you get upon arriving at the Vault it crashes.
Makes me wonder if it is something to do with the uniforms, i also get it randomly in Sol Spacedock, again Rom Uniforms could be present.
It is anoying, i paid to be a Lifer, brought LoR pack, spend a fortune on Zen yet they wont even respond to this bug, ive since stopped spending money on it as they seem to be sticking up two fingers and dont care one bit.
At least a Dev could aknowledge this, typical Cryptic it really is.
I also did this and crashes appears less... but still happens.
UPDATE: Same problem reported here: http://sto-forum.perfectworld.com/showthread.php?t=692601
I think Cryptic is well aware of this issue... just do a Google search of this error msg: Fatal Error: Direct3D driver returned error code (E_OUTOFMEMORY) while creating a texture. Lots of reports all related to PWE, also including Neverwinter.
SOME TESTING DONE AND...
Well, I tried a few things that SO FAR are working. First of all, when I checked under OPTIONS/VIDEO/DISPLAY MODE I discovered that Fullscreen wasn't selected by default as in the past. Only a Max Windows screen. I changed that to Fullscreen.
On that very same tab, I went all the way down to TROUBLESHOOTING. On the first option you can change between AUTO, DirectX 9 and DirectX 11 beta. I selected DirectX 9 because I wasn't sure about the default setting. The option needs a game restart, so I did.
I tried beaming up and down New Romulus' Staging Area several times with my three characters (1 Fed, 1 Klingon and 1 Romulan) and SO FAR no crashes. I'll keep testing.
UPDATE: So far, one crash after 6 hours playing.
In short....Cryptic screwed up....AGAIN! They knew about this problem BEFORE LoR went live and still made the choice of releasing it the way it was.
BRANFLAKES! Get your *** down here and explain this SNAFU!:mad:
Take back your home,end the grind!
Volunteer moderators policing the forums is like a mall cop trying to solve a murder.
I'm getting that exact same error, down to the file/memory sizes, was beginning to think it was my machine but apparently not. At first it was just NR, but now it's happening at any social hub.
XO of Training
Tier 5 Starbase, Tier 3 Embassy, Tier 3 Dilithium Mine, Tier 3 Spire
Join us at www.dtfleet.com
the other option is to turn down detail distance and it will lessen the load on the video card. I run at 5760x1080 at max settings and use 2.3GBGB of video ram on mt GTX 670. I hope this helps. The other
option is under trouble shooting which is changing the video memory limit to a lower value.
I'll give these a shot.
It actually crashed quite a bit over the weekend.
Something else I found out too, doesn't matter how you get to the Staging Area.
I was being from, I think Phaeros Crater, to the Staging Area, and the game crashed. One time, exited the Command Center, and right there on the steps it crashed.
Wish you good luck... I still get crashes at New Romulus' Staging Area. It's still the only place where the game crashes for me.
My patience with Cryptic is gone!:mad:
Take back your home,end the grind!
Volunteer moderators policing the forums is like a mall cop trying to solve a murder.
"If you wish to make an apple pie from scratch, you must first invent the universe." - Carl Sagan
@Aquitaine985
Lag Industries STO PvP Fleet - Executive
A Sad Panda of Industrial calibre.
2010: This is Cryptic PvP. Please hold the line, your call is very important to us...
I wound up playing CO instead today.....
In the video options, under troubleshooting, set your Video Memory Limit to Auto.
Daft I know but I've been crash free since then...
"If you wish to make an apple pie from scratch, you must first invent the universe." - Carl Sagan
* I am online nearly every day and seems like not a day goes by without it crashing at least once or twice (usually several hours apart though)
* It randomly crashes when i'm barely doing anything at all - like just standing there reading something in zone chat (usually a few moments after I have entered a new instance somewhere) - other times I'm not doing anything major except opening a window like the character screen, or the duty-officer screen or any of those and it randomly crashes
* Sometimes if i turn my camera view around a bit too fast and sharply (i use a mouse) then it crashes or freezes everything
* Many times when it crashes I get the "Fatal Error: Direct3D driver returned error code (E_OUTOFMEMORY) while creating a texture" error message
* Other times I get NO error message after it has crashed
* Most game crashes for me so far have been when beaming down/entering New-Romulus - though they have also occured seemingly randomly throughout the whole game - certainly the "large-instances" with lots of stuff in them like New-Romulus and the Risa-Event are places it has occured a lot. Oh and it crashed during watching a cutscene on New-Romulus as well (seems like everytime I reload my game however it loads perfectly fine into New-Romulus or wherever it last crashed)
* Other times it has totally locked up my game on the loading-screens (any location anywhere in game randomly again it seems) - I cannot activate windows task-manager to force-quit the game - yet strangely enough when I have ventrillo running in the background, despite the game having locked, I can still hear/talk with my fleet buddies on vent - weird. Oh and as a result of this happening I am forced to manually-restart my computer at the power-button, rather than a proper shutdown/restart in windows.
* It has at least once or twice totally frozen my game, computer and everything, again forcing me to manually power-switch-off/restart - oh and it even once did this to me on the character-screen when I tried to go into the options to turn down my video settings before loading into the main game!!! (also my character screen always seems laggy) **hint hint** - possibly these texture out of memory bug things are due to character costumes - but who knows? I think the majority of crashes I've had were on ground instances......
* Possibly the worst thing it has done so far (once) was both my game and computer crashed and my computer restarted on its own (it might have blue-screened but it restarted so fast i don't know) - then it got stuck in some sort of constantly rebooting cycle and refused to load the bios (my screen remained blank, though i could hear the fans inside wirring speeding up each time as if it was getting ready to start loading the motherboard and everything, but seconds later they slowed down, then sped up again, repeatedly - all the time with no bios or anything loading on screen). Yet again I was forced to manually power-switch-off to stop it. Luckilly, (at least I HOPE) it was some sort of memory issue, since I left it turned off for a couple of hours, and when I came back it loaded up windows fine again AND the game too!
I can only hope it didn't cause any serious damage to any of my components. Also I hope none of them were already on the way out to fail anyway - especially given all the above mentioned problems I've been having. Though I doubt it given the fact, like many other people have mentioned, I did not have ANY of these problems before the Legacy of Romulus new season came out. Before the season, I was running full (almost totally maxed out) graphics settings in game, i'm still using the same graphics card, same OS XP-home-32bit, same all other components, all for about a year i think and had no problems (maybe the very rare game crash but that's all). Oh and someone suggested in the video options, under troubleshooting, to set your Video Memory Limit to Auto - mine was already set at Auto, and it was still crashing - i lowered my settings and it auto-changed to something else itself and it still crashes.
I've been forced to set my in game graphics settings to the default minimum since even mid-way between minimum and recommended settings seems to crash the game occasionally. I think at this level, despite my game graphics appearing utterly rubbish, the game is for now at least no longer crashing on me - though I only played for a few hours on this setting with no problems (particularly New-Romulus was NOT crashing) I need to play a lot longer to know for sure though. :eek:
Oh and I have NO problems doing or running anything else on my computer, I've got all up to date graphics-card-drivers etc, am pretty sure my comp is totally free of viruses and useless memory guzzling rubbish programs running in the background - so all these problems definitly point towards this obviously malfunctioning online game rather than my own equipment or software.
PLEASE PLEASE PLEASE WILL CRYPTIC DO SOME SERIOUS BUG FIXING ASAP!!!!!!!!
******
UPDATE
******
Well, first off and probably most importantly I have increased my computer VIRTUAL MEMORY and it seems to have slightly improved things for me. I don't seem to be getting quite so many crashes as I was I THINK, and the severity of the crashes doesn't seem quite so bad anymore (at least my game and computer isn't force rebooting itself anymore, and the game/computer doesn't lockup on me after a game crash.... much).
Sadly however the game IS STILL CRASHING (at least once or twice every time I have it on) randomly anywhere in game, though mostly around high "population" instance zones. Also New Romulus seems to remain a key location where it occurs more often than the rest of the game, but I must admit the frequency of crashes even here seems to have reduced since i increased my computer virtual memory.
Some people have mentioned to try to lower the in-game graphics (like "texture") and change some other graphics related settings in troubleshooting and stuff. Well, I can't personally say that this works, but get this:
Some time ago I got really fed up with these multiple crashes that i set all my in-game graphics to the absolute MINIMUM to test it out (the game really looks aweful of minimum setting lol). For a while it seemed to improve things - I wasn't getting any crashes.... The suddenly one day I log back in the game and BAM the game crashes, locks-up and locks my computer too (i can't remember where I was though - I THINK i was at QO-NOS academy!). It crashed on THE LOWEST DAMN GRAPHICS SETTINGS!!!! Also, someone suggested setting the DirectX option in "troubleshooting" to Auto - well I THINK mine was and always has been set to auto (though I'm not sure). So, it seems even setting your in-game graphics to minimum etc might not necessarily improve things. NOTE: THIS WAS BEFORE I INCREASED MY COMPUTER VIRTUAL MEMORY.
Like i said, increase virtual memory seems to have sort of improved things for me, but in the end it's not perfect and not even barely adequate - WHAT WE NEED IS THIS TEXTURE / DIRECTX / GRAPHICS / WHATEVER BUG THING FIXED (in BOTH games!!!!)
Captain - U.S.S. Tiger's Claw
TOS Veterans Fleet
Praetor of the -RTS- Romulan Tal Shiar fleet!
About time this was totallt fixed as for me, the game is unplayable. Not good enough guys!
Shame, as the game is very good - but you cannot have constant error and crashes with games of this type - it makes them pointless. People will unsubscribe and not pay for upgrades, nor trust the programmers again.
I mean Cryptic sleep not they try to update the Graphics as well to match the todays technicaly Hardware level.
That mean older Systems (older graphic Cards) get suffered.
The first thing what you schould doe update your Graphic Card with the newest Driver, in some case that can help.
If not than you must make a compromise and lower the Details to an level that your Graphic Card can match.
If it too not help and the crashes still persist (than you should read the troubleshooting)
Its impossible to run the newest Graphics with High Details on a old Card.
That work in no Game.
Yes we are all just made of Stardust.
After a certain time the Stardust starts even to think.
Is that not fantastic?
http://sto-forum.perfectworld.com/showthread.php?t=788951
Fatal Error: Direct 3D driver returned error code
(E_OUTOFMEMORY) while creating a texture.
Technical Details: E_OUTOFMEMORY while creating 2D texture
size 2048x2048 (12 mips, RTEX_DXT5), 810.91,76.56
MB virtual space available.
I have narrowed it down to New Romulus only. Whether I am beaming down or signing on and the toon is already there, the game crashes if I try to play the New Romulus map, particularly the Staging Area.
The problem is with a piece of DirectX code they added with LoR (it's the same piece of code they used for Neverwinter,people are reporting the exact same issues there!),as some of you may have noticed they have added a DirectX 11 option (which is still in Beta) to STO.
There is a way to stop your game from crashing,go to options,select video and scroll all the way down to 'troubleshooting',the first option there will be for your graphics card.Set DirectX to 'auto'.
This solution isn't perfect,2D textures might take a hit (not as pretty or floor panels showing up as black),but it will stop the game from crashing.
This will have to do till Cryptic gets their act together and fixes this DirectX mess they created.
Take back your home,end the grind!
Volunteer moderators policing the forums is like a mall cop trying to solve a murder.