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

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

EVE Information Portal

 
  • Topic is locked indefinitely.
 

EVE Online: Retribution 1.1 Issues

First post First post
Author
Previous Topic Next Topic
Xeverius
Xeilias Corporation
#141 - 2013-02-20 01:43:05 UTC
My Legion was also invisible, clearing the cache worked for me. /pewpew

In-game, hit ESC, go to Reset Settings tab and click Clear All Cache Files (clear button).
DeODokktor
Dark Templars
The Fonz Presidium
#142 - 2013-02-20 01:55:00 UTC
Alexis Antollare wrote:
All of my assets and bookmarks are listed as being 2,147,483,647 jumps away. The ONLY exception are the bookmarks for locations in an adjacent system.

Additionally, the route setting to these destinations is not working. I'll tell Aura to set a destination, but the route panel indicates no set destination point. When I re-select it, Aura reminds me that she can't set a destination to the same waypoint twice...even though no route appears. When launching into space, gates and/or stations that should be marked yellow for the route, are not.

The other odd thing is that I think this worked just fine this morning shortly after I patched... it seems to have glitched in the past couple of hours.



If you have "avoids" set for all paths then you would have this problem.
Left click on the "A" next to Route, click "Manage Route" and you should see your waypoints listed.
You can also see, and edit, your avoidance list..

If you managed to avoid all of those sy stems then you might want to keep mum about it, as it's unlikely you could do that manulaly without spotting your problem.....
Tanaka Aiko
Ministry of War
Amarr Empire
#143 - 2013-02-20 01:55:04 UTC
now that we see things as : system -> constellation -> region, some regions are truncated due to system and constell name being too long.

ex : kassigainen -> caldari border zone -> the citadel
I only see "the", so I didn't know on which region I was. And I ******* don't care on which constellation I was, let us remove this information, or makes so no text is ever truncated
Kirichan
Legion Enterprises Inc.
#144 - 2013-02-20 02:03:26 UTC
Kirichan wrote:
Optimize route isn't optimizing your route anymore.


Correction, if you have enough way points that it should give you then warning dialog about how long it could take it does nothing. If you have fewer it seems to work fine (my guess is it isn't opening the dialog window for some reason).
Alexis Antollare
Phoenix Freight
#145 - 2013-02-20 02:04:47 UTC
DeODokktor wrote:
Alexis Antollare wrote:
All of my assets and bookmarks are listed as being 2,147,483,647 jumps away. The ONLY exception are the bookmarks for locations in an adjacent system.

Additionally, the route setting to these destinations is not working. I'll tell Aura to set a destination, but the route panel indicates no set destination point. When I re-select it, Aura reminds me that she can't set a destination to the same waypoint twice...even though no route appears. When launching into space, gates and/or stations that should be marked yellow for the route, are not.

The other odd thing is that I think this worked just fine this morning shortly after I patched... it seems to have glitched in the past couple of hours.



If you have "avoids" set for all paths then you would have this problem.
Left click on the "A" next to Route, click "Manage Route" and you should see your waypoints listed.
You can also see, and edit, your avoidance list..

If you managed to avoid all of those sy stems then you might want to keep mum about it, as it's unlikely you could do that manulaly without spotting your problem.....


Well... that was odd. For the record, the Avoids were NOT the problem... at least I don't think they were, but the issue seemed to resolve with a session change and a log out and back in. Thanks for the feedback!
Dolmance
Sebiestor Tribe
Minmatar Republic
#146 - 2013-02-20 02:38:38 UTC
At the login screen I cannot paste my password. Control-v does not work. Right clicking the text field no longer creates the menu with the "paste" option.

I just can be bother to TYPE my passwords. QQ. Lol

But really. This does suck. Cry
MetroDyne Robinson
Deep Space Mining and Construction
#147 - 2013-02-20 02:41:40 UTC
Everytime today that me and corp mates have done anoms and we get a faction spawn, it dissapears after around 5 seconds. Just gone. Into thin air. This has NEVER happened to us before, so im assuming this is a bug?Sad
OldWolf69
EVE-RO
Goonswarm Federation
#148 - 2013-02-20 02:56:10 UTC
Who was the bright genius wich removed info when you roll your mouse over a target? What does THIS improve? Why not remove info on target completely, if you PvP? This style, we will get this too the next patch...Big smileBig smileBig smile
Phopptimus Prime
A Blessed Bean
Pandemic Horde
#149 - 2013-02-20 03:01:23 UTC
Exact same behavior in Angel Watch. Rat spawns 80+km off beacon and warps off in 10 seconds or less.

S'ini wrote:
Killing the trigger in an exploration complex ends causes the remaining ships to warp out too quickly.

Examples:
When running the Guristas Watch complex, killing the Militant Overseer will trigger the escalation. Killing the overseer is also a trigger for a spawn of ships, which may include the Dread Guristas faction ship. However, all remaining ships warp out of the complex approximately 10 seconds after the Militant Overseer is killed, meaning you have less than 10 seconds to target and kill the DG rat before he warps off.

Another example:
When running the Guristas Hideout complex, killing the tower is the trigger for the escalation. However, there is a (timed?) spawn of ships that come in and the last spawn may include a DG ship. Killing the tower causes near immediate warpout of any remaining ships, and seems to end the timed ship spawns thus preventing the arrival of the DG ship entirely.
Keko Khaan
Center for Advanced Studies
Gallente Federation
#150 - 2013-02-20 03:02:38 UTC  |  Edited by: Keko Khaan
S'ini wrote:
Killing the trigger in an exploration complex ends causes the remaining ships to warp out too quickly.

Examples:
When running the Guristas Watch complex, killing the Militant Overseer will trigger the escalation. Killing the overseer is also a trigger for a spawn of ships, which may include the Dread Guristas faction ship. However, all remaining ships warp out of the complex approximately 10 seconds after the Militant Overseer is killed, meaning you have less than 10 seconds to target and kill the DG rat before he warps off.

Another example:
When running the Guristas Hideout complex, killing the tower is the trigger for the escalation. However, there is a (timed?) spawn of ships that come in and the last spawn may include a DG ship. Killing the tower causes near immediate warpout of any remaining ships, and seems to end the timed ship spawns thus preventing the arrival of the DG ship entirely.


Not just complexes. I got faction spawn from anom and after killing faction bs rest of rats warped away. Which may not mean as much as in plexes. But however 6million bounty from commander doesnt feel so good when the rest 4 rats with 2million buonty each leaves the field. Specially when the faction spawn drops only some useles faction ammo that no one use..
Malkev
Tribal Liberation Force
#151 - 2013-02-20 03:09:55 UTC
MetroDyne Robinson wrote:
Everytime today that me and corp mates have done anoms and we get a faction spawn, it dissapears after around 5 seconds. Just gone. Into thin air. This has NEVER happened to us before, so im assuming this is a bug?Sad

Same thing happening with Sleepers. Last wave warps off or vanishes after you pop a few ships.

Had two Emergent Defenders warp off but they stayed on my overview while doing so. They ended up 5au away according to my overview.
Mike AntHunt
Worthless Carebears
The Initiative.
#152 - 2013-02-20 03:12:00 UTC
Random Disconnections.



Was running incursions tonight.. we finally got enough up for an HQ fleet, had everything perfect.Good logis and everything. Then we started having random disconnections. Every 10 minutes, another ship was DC'ing. Not only was it just random ships, but our logistics pilots were dcing. We tried clearing cache, resetting routers, testing internet connections. Everything showed fine but it was still DC'ing.
TruthState
Pandemic Horde Inc.
Pandemic Horde
#153 - 2013-02-20 03:29:26 UTC  |  Edited by: TruthState
Exactly at the 36.2% while updating with this patch, my computer does this, __________________ Flat Lines. And i have to reboot my computer as it gets frozen.

Has happened 3 times so far while trying to patch the client up.


Getting owned by CCP atm, feels bad man

And no im not dling porn, and my machine is top of the line. So its not a memory/processor issue.

Anyways if this has been reported anywhere and I missed the fix, durka durka
DeODokktor
Dark Templars
The Fonz Presidium
#154 - 2013-02-20 03:33:17 UTC
TruthState wrote:
Exactly at the 36.2% while updating with this patch, my computer does this, __________________ Flat Lines. And i have to reboot my computer as it gets frozen.

Has happened 3 times so far while trying to patch the client up.


Getting owned by CCP atm, feels bad man

And no im not dling ****, and my machine is top of the line. So its not a memory/processor issue.

Anyways if this has been reported anywhere and I missed the fix, durka durka



Try running the repair tool instead or download the offline installer patch (if they still do it?)...
I have used the repair tool a few times and it works okay for problem patches/installs.
Usagi Toshiro
Null Tax Crew
#155 - 2013-02-20 03:35:04 UTC
I am on an ASUS Laptop running Win7 and I've got the high heat issue again that popped up when the expansion launched that was later resolved. Did you break the fix you patched in for that? Question

Trolls are like stray cats. If you feed them they multiply. Please do not  feed the trolls.
Maven Foy
Perkone
Caldari State
#156 - 2013-02-20 04:17:07 UTC
ASUS laptop running win7 blue-screened twice today since updating, citing MEMORY_MANAGMENT...

Has never happened before. :(
Logicycle
Stimulus
Rote Kapelle
#157 - 2013-02-20 04:42:48 UTC
1) Tier 3 Battlecrusier Blueprints will not build at high sec stations.....i get this message: 04:27:25 Info This product cannot be manufactured at this facility.

2) The inventory system is failing again...... When i go from one station to the other secondary windows for Item Hanger & Ship hanger now open Active ship's cargohold by default......

Sigh...
rebecca crow
Caldari Provisions
Caldari State
#158 - 2013-02-20 05:23:18 UTC
since the pach i have had sume problmes running my acounts all at the same time and EVE cuts out i dont under stand why it was working befor the pach or is the server under more stress then usual
codex09
Native Freshfood
Minmatar Republic
#159 - 2013-02-20 06:00:08 UTC

While in fleet a short time ago a lot of us started having our clients crash for no real reason.

At the time of it happening, we were just orbiting a POCO & shooting it.

First of all everything instantly stops moving & then Windows gives the old program Has Stopped Working msgs.

Yonis Kador
KADORCORP
#160 - 2013-02-20 06:04:38 UTC
I guess I should comment since I'm experiencing many of the issues others have stated in this thread:

1) The autopilot ribbon through space is nonexistant. (Disappointing since I think I might like this feature.)
2) Client froze up and dc'd tonight. Had to use the task manager to end the program.
3) When docking at a hub, the screen goes black for about 30 seconds............and then shows your ship in the hangar.
4) The annoying explosion sound on session change doesn't happen every time I dock now but when it does happen (and yes, it's still happening) I think it's even louder than before.
5) In some cases ore isn't being transferred to the ore bay - most notably when warping. Before the patch, I would allign when the ore bay was nearing capacity and when warping out, warp initiation transferred ore into the hold. Now you just warp off.

That's all I've noticed so far. Well I also noticed an unusual number of Hobgoblin I's in Amarr but I think that's working as intended.

If I notice anything else, I'll write again.

YK