> > > Hi Captains! The team continues to investigate an issue where some players may be stuck on a loading screen. We appreciate your continued patience! < < <
Jolan tru Captain!
Welcome to Legacy of Romulus!
If you have purchased a Legacy or Starter Pack, please see this thread for instructions on how to claim your items in-game. (Please see the yellow text in the linked thread for instructions on creating a Reman.) (Not seeing your pack in-game? Please see the lime-green text in the linked thread above for information.)
If you have additional questions about the Legacy or Starter pack, please read this FAQ.
Thanks SO MUCH for all your support, and we'll see you in-game!
- The Star Trek Online Team
"Login failed for unknown reason" error
Missing additional character slot for current/ lapsed Gold Members
Slow patching in the launcher
A bug that involved Romulan Liberated Borg captains and their skills once they chose an ally
Fatal error: There is not enough available video memory. Please choose lower resolution settings or close other graphics applications.
Technical details: D3DRR_OUTOFVIDEOMEMORY while creating 2D render target texture size 2048 x 2048 (D3DFMT_NVIDIA_INTZ_DEPTH_TEXTURE_FCC)
Phenom II 955
30" Dell LCD 2560x1600
Windows 7 Ultimate
I have disabled dynamic lighting and have updated to the Feb DirectX update and updated my drivers from 9.11 to 10.1.
The game crashes almost every time I have some kind of scene change i.e. loading any new map. Surface to ship, sector to sector, station to space, whatever. Then I have to sit through the verifying process for about 4 minutes.
Any ideas on what could be causing this and how to make it stop? As it stands now I can't play at all.
Same issue here. Running the game on an ATI 4850 @ 1280x960 on Win7. It started giving me this error about a month ago after a patch was deployed (before everything was fine). Happens when changing maps and sometimes when using Alt-Tab, usually after playing some 20-30 mins.
Reinstalling the game (including deleting old settings) didn't help, lowering graphic settings didn't solve the problem, too. No errors of that kind in other games so far.