open All Channels
seplocked Issues, Workarounds & Localization
blankseplocked Skills not affecting ships
 
This thread is older than 90 days and has been locked due to inactivity.


 
Author Topic

Iniquita
Dreddit
Test Alliance Please Ignore
Posted - 2011.06.23 20:10:00 - [1]
 

I had this happen earlier today trying to jump to a cyno on my carrier pilot:

http://i.imgur.com/mniyO.png

Basically JDC5 carrier pilot unable to jump to a cyno 9 ly away. I had tried docking/undocking and it eventually fixed itself when I relogged.

Radix Salvilines
legion industries ltd
AAA Citizens
Posted - 2011.06.25 13:23:00 - [2]
 

Edited by: Radix Salvilines on 25/06/2011 13:25:09
same thing in here

when boarding a ship in space it does not update with my skills.

On ishtar even the drone bay does not get bigger. If i werent in a close proximity to ship maintenance array i would be stuck as you cant warp with too much drones in the drone bay.

Only fix is docking into a station and relogging.

EDIT: Clearing cache does not help!

CCP Tuxford

Posted - 2011.06.26 21:20:00 - [3]
 

I wasn't able to reproduce this which means that either it's been resolved and not deployed or it only happens in a specific scenario. If you could give me a bug report with as detailed info as you remember about what you did before hand it could help me in resolving this issue.

Pell Grahnm
Posted - 2011.06.27 01:15:00 - [4]
 

Im also having this issue with my muninn, eject in space and reenter to find all mods offlined and no skills applied.

Omara Otawan
Posted - 2011.06.27 02:02:00 - [5]
 

Originally by: Pell Grahnm
Im also having this issue with my muninn, eject in space and reenter to find all mods offlined and no skills applied.


Yea, happens to me everytime I board a ship in space. Docking in a station, leaving ship and boarding again fixes it.

CCP Tuxford

Posted - 2011.06.27 10:24:00 - [6]
 

I think I've found it. The repro I had was

  • be in a ship with drones that have been launched (possibly not necessary but it does insure a 100% repro)

  • Jump to a new system

  • eject from the ship

  • board it again


  • It was a fallout from another fix.

    Deleros Revo
    Posted - 2011.06.27 11:21:00 - [7]
     

    Originally by: CCP Tuxford
    I think I've found it. The repro I had was

  • be in a ship with drones that have been launched (possibly not necessary but it does insure a 100% repro)

  • Jump to a new system

  • eject from the ship

  • board it again


  • It was a fallout from another fix.

    How do things that worked correctly go puf? I mean, It's understandable to happen with new features but something that has been working ok for years? Do you rewrite all EVE's code again in every expansion? I really don't get it. I really would like to know why these issues happen.

    CCP Tuxford

    Posted - 2011.06.27 12:54:00 - [8]
     

    Originally by: Deleros Revo

    How do things that worked correctly go puf? I mean, It's understandable to happen with new features but something that has been working ok for years? Do you rewrite all EVE's code again in every expansion? I really don't get it. I really would like to know why these issues happen.


    When things that used to work break it's always because somebody changed something. In this case what we did was a massive re-factoring of what we call the dogma system. What the dogma system does is handle the attribute on ships, modules and pretty much everything and the modification of them. The system wasn't flawed in the concept it's just a product of years of doing quick fixes.

    Tasks such as this aren't done for the hell of it though and there was a specific need for this work. What we are doing now is to delivering the feature and tech separately. The reason for that is both the feature and re-factoring it technologically risky and this was an effort to reduce that risk.

    I'll be covering this in a dev blog later.

    Pell Grahnm
    Posted - 2011.06.27 15:02:00 - [9]
     

    So your gonna fix it....right? cause this is killing my iskie machine.

    CCP Veritas

    Posted - 2011.06.27 15:18:00 - [10]
     

    Originally by: Pell Grahnm
    So your gonna fix it....right? cause this is killing my iskie machine.


    Yeah, he's on it.

    Mirei Jun
    Right to Rule
    THE UNTHINKABLES
    Posted - 2011.06.27 17:07:00 - [11]
     

    Edited by: Mirei Jun on 27/06/2011 17:10:26
    Edited by: Mirei Jun on 27/06/2011 17:08:17
    There are quite a few skills that are not being applied properly. The following have been verified:

    Jump Calibration
    Jump Portal Generation
    Biology (This was reported on the test server well in advance)

    These have nothing do to with corp hangars in POSes or anything else. It can happen anywhere, and in station. This is definitely hurting PvP.


    Renmazui
    Posted - 2011.06.27 17:56:00 - [12]
     

    yeh i had a strange experiance yesterday,, jumped outa me titan to go grabs skill- upgrade clone put me alt in to titan for safe keeping... he has all lvl 5 skills also btw... all mod's r turned off.. i mean all mods
    i jump back into titan.. all mods still offline..so waddle over to sma onlineing we go..but 3 of me guns have not on lined..because i have only 950 cpu....wutttt .. relog... no diff..leave till after d/t all is good... but wota bluddy performance

    Huroken
    Malevolent Intentions
    Dark Solar Empire
    Posted - 2011.06.27 19:32:00 - [13]
     

    Same problem, occured after a Clone Jump. Some ships "seem" fine, some ships have reduced CPU, Power and Cap.

    Darth Khasei
    Posted - 2011.06.28 13:57:00 - [14]
     

    Edited by: Darth Khasei on 28/06/2011 13:57:46
    Same thing is happening when you change Orca pilots in space(ie. the mods go off and skills are not being applied). This has caused severe logistical problems and is costing my corporation isk. Please fix this fast.


     

    This thread is older than 90 days and has been locked due to inactivity.


     


    The new forums are live

    Please adjust your bookmarks to https://forums.eveonline.com

    These forums are archived and read-only