These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

Problem with T3 cruisers

Author
Male Helper
Tactical Farmers.
Pandemic Horde
#1 - 2016-06-05 04:29:50 UTC
I have an issue when trying to fly T3 cruisers, wonder if someone has had something similar, or has any tips on how to resolve it.

1) When i board a T3 cruiser of any kind, I can't see the model. If i'm in station - it just shows me whatever previous ship I was in, in space i just see empty space for any T3 cruisers. (this has been happening with various degree of severity for the past couple of years)
2) When I try to eject from the ship in station, client still shows me in that ship. Once I relog, it correctly shows that i'm in a pod.
3) If I try to undock after doing step 2, I either see black screen, or the station environment is still there.
4) After every couple of gate jumps the client gets confused which system I'm in. It shows the system name correctly, however the overview still shows the objects from previous system. If i right click in space, the menu shows objects from current system, however there is no option to warp to them or align. Basically the only way out is to relog. (This has started since Citadel patch)
5) When undocking in T3, quite often the modules will be all gone and I would have to flip showing passive modules on and off to get them to appear. (this seems to have been fixed in Citadel or one of subsequent patches)
6)In the logs i see bunch of exceptions related to T3 ships loading every time there is a session change

Example:

EXCEPTION #13 logged at 06/04/2016 17:20:05 : Unhandled exception in TaskletExt object at 4083c4b0, abps=1001, ctxt='NO CONTEXT^\bound method PlayerShip.Release of destiny.ClientBall object  

Formatted exception info: ValueError: list.remove(x): x not in list

Common path prefix = e:/jenkins/workspace/client_tranquility/branches/release/tranquility

Caught at:
pre /packages/bluepy/__init__.py(46) CallWrapper

Thrown at:
pre /packages/bluepy/__init__.py(35) CallWrapper
pre /eve/client/script/environment/spaceObject/ship.py(172) Release
pre /eve/client/script/environment/spaceObject/ship.py(57) _UnlockT3Loading
pre /packages/uthread/__init__.py(937) UnLock
pre /packages/uthread/__init__.py(236) release
override = False
self = Semaphore (912588240, ('LoadT3Model',)), t:120.508358 at 0x4084d030>


Now since this has been happening over couple of years, there have been multiple graphic cards (all nvidia), driver upgrades etc.
It seems to have gotten much worse since citadel. While previously it was just an inconvenience, now it's just plain unusable.

Tried to blow away eve client and resource cache, didn't seem to help. Tried switching between DX9 and 11, no difference. Wonder if anyone has any tips, before i bite the bullet and blow away Windows and do a complete fresh system install.