If the wiki/available info on C391's is correct then they should be 24 hour WH's. However, this one still shows over 24 hours "has not yet begun natural cycle" after at least 2 hours.

I'm not sure if this means C391's are supposed to live over 24 hours and the wiki is wrong, or it's a bug.

I think there are a few other classes displaying the same behavior.

It seems like POS mechanics related to the revamped industry system were poorly tested. I can't fault anyone on the test server for this, since few would stop and think that maybe they should drop a tower and test the industry there, instead of in a station.

Either way, here's my list from the feedback thread. So far, only the job cost ISK sink coming out of corp wallets has been mentioned that I have seen:

https://forums.eveonline.com/default.aspx?g=posts&m=4831550#post4831550

In addition to those:

1) The industry window doesn't remember previous settings such as position, size, column sorting, etc.

2) Include the Job ID somewhere with the job itself, ideally as a new column. This will help with tracking down jobs without having to resort to the API (for example, to watch for Director or Accountant skimming).

3) Include the seconds in Job Start time and Job Completion time, for the above job tracking reasons and for more accurate user feedback.

4) Add the installer's name in the "Manufacturing" wallet journal entry in the parentheses next to the Job ID for corp jobs.

5) Have the blueprint list honour hangar and facility access permissions. Someone in corp was looking through the list of available blueprints last night, and started naming some from director towers. This person does not have Starbase Config, nor did he have it last night. While it is possible that the facility permissions in the director's tower were lowered, this is unlikely.

I'm sure more will come to me later :)

1 to 4 arent really bugs more stuff that could be improved

5 could be a bug.

is there anyway you can check number 5 just to make sure its not like pos setting being lowered temporarily.

a known issue is you need corp wallet access to do corp jobs (both me and sugar didnt spot this as we are both either directors or ceo of our alt corp we used)

.

I believe you needed a complex combination of factory roles, but not wallet access. That is, Factory manager and Rent Factory Facility.

Industry at a pos has always taken an active corp wallet division but it probably was not noticeable as your corp leader could have taken one of the seven divisions and given everyone access to it while never putting any money into it. Now because there are fees the industrialist will need to participate in the engaging gameplay of figuring out what the fees are and depositing enough isk to cover them.

Perhaps a better solution would be if people could run private jobs at a corp tower rather than making them all corp jobs. That way the menus and isk are specific to the individual.

I know when I had people doing indy I just had an empty division assigned to the role like you said.

Will probably require people donating money into corp now in order to run jobs then having someone with wallet access moving the funds... Unless you can deposit to a specific division if you have access to it.

They can specify which division to give money to. It works, it's just extra steps in the process.

More steps for the indy guy, but none for leadership, so at least the jobs can continue without needing leadership on to move the funds around. I'm sure it's annoying, but at least it's not completelyfucked

Just wait for them to start depositing money in the wrong division in much the same way as they drop their stuff into the wrong hangar...

More steps for the indy guy, but none for leadership, so at least the jobs can continue without needing leadership on to move the funds around. I'm sure it's annoying, but at least it's not completelyfucked

It can lead to quite a bit of confusion and has potential for abuse by less scrupulous corp members. Figuring that a fix would be forthcoming (confirmed), we just took a hands-off approach: "We don't recommend you do this and instead wait for the fix, but if you do, don't come crying if it doesn't work out cause we won't fix it for you."

If you are on the system map and activate a cloak then turn off the system map your ship will briefly appear to be going through the cloaking animation and graphic as if it was not cloaked before.

While this is just a graphical hiccup its very unnerving.

Its possible, I just don't remember noticing it before.......

If you are on the system map and activate a cloak then turn off the system map your ship will briefly appear to be going through the cloaking animation and graphic as if it was not cloaked before.

While this is just a graphical hiccup its very unnerving.

1. Corp members with no access to or roles can see every installation, and blueprints at every POS in the WH. I dont want my grunts knowing about all my t2 ship bpos.

Hey guys. We've confirmed an issue that was causing the new K-space to C6 wormholes to spawn more often than was intended. We have an internal fix and will be getting it out as soon as possible.

The passworded can protecting BPs from view is an intentional feature, I'm not sure if any alternative methods for doing the same thing might be implemented in the future.

You mentioned above that the new C6 to K-space wormhole mechanic was causing an increased spawn rate. Is this also the cause of the exceedingly long wormhole lifetimes as well? Related?

Thanks

The K-space to C6 WHs should have a 48h lifespan, we're investigating the reports that some are lasting unusually long.

Reverse_Chance = Base_Chance * (1 + (0.01 * Reverse_Engineering_Skill_Level)) * (1 + (0.1 * (Datacore_1_Skill_Level + Datacore_2_Skill_Level)))

Added glue for visibility and support. As Corbexx stated in the beginning of his OP, please keep all comments, issues, and discussion constructive and in keeping with the forum rules.

Thank you.

The K-space to C6 WHs should have a 48h lifespan, we're investigating the reports that some are lasting unusually long.

I have one I haven't seen mentioned, related to industry and RE

When trying to install a Reverse Engineering job on the item "Intact Armor Nanobot", I get a red start button, and it tells me two different things:

1) "The selected team of workers does not match the selected blueprint activity"

2) "The selected team of workers is not in the same solar system as the current facility"

I am not seeing anywhere where there is a team of workers assigned to the job. AFAIK there weren't any teams yet for RE, so I wonder what's going on here.

This only is happening with this particular relic. Again, I haven't assigned a team to this job, and don't see how this can be undone.

Not in a wormhole but I am also getting this error when trying to do invention on a rig bpc, submitted a petition, have not heard anything.

FIXES:
Exploration:

Wormhole C391 has had its mass per jump corrected.
K-space to C6 wormholes have calmed down a little and are now appearing at a more relaxed rate.

I like how now I can fit T2 rigs or other rigs and don't have skills for it. Working as intended?

The K-space to C6 WHs should have a 48h lifespan, we're investigating the reports that some are lasting unusually long.

Lost a ship today and was able to loot it multible times while it still shows as wreck with content in space...

i'll try get some more info on the above two.

can you please both put in bug reports about them with as much info as possible

Reverse enginering show me that i have 82 percent chance of success for intact hull section

It have 40% base (as shown in tooltip (-60%))

and have all skills to 5. Formula should be acorning to the http://games.chruker.dk/eve_online/eve_math.php and many other sources:


So:
Reverse Chance = 40% * (1 + (0,01 * 5)) * (1 + (0,1 * (5 + 5))) = 40% * 1,05 * 2 = 84%

ofc the formula available on the net may not be acurate, but can You check this one out?

Jumped through a hole tonight, into a fleet that suddenly grew a little more than expected, nicely done Guys, GF

However I Might have had a chance of survival if after jumping back out, my overview had actually showed me the ships that were firing on me rather than the ships in the hole I had just apparently left?
Because it seemed to jump me right back in? Which is of course impossible due to polarisation

It is somewhat confusing when the entire client is lying to you, and you are left puzzling what the hell is going on?

Or have CCP introduced an undocumented "fog of war feature?"

Anyone else had the same or similar experience, I have naturally reported it, but I was wondering If I had gone completely insane, or the overview had ?

But either way GF and well done, you got a well deserved kill, look forward to meeting you again, hopefully with a working client.

Yesterday I had an interesting "lag" incident appear.

I was in a scanning Cov-ops, PI interface window open, and I logged out. I changed to another character, and after my login was complete some of the windows on my screen were showing data from the previous character on the same account. I closed the game client and reopened it via the launcher. With the new client open my PI planets were showing the ones from the previous character. It updated not after closing and reopening the PI interface window, but after I viewed a planet in planet mode. I was extremely confused as one planet that should have been there was evidently missing for over a minute despite session changes and window closure and reopening. Closing and reopening a window has resolved crashes to the hanger or cargohold window, as welll as some sticking associated with some camera features that apparently crash during alt-tab use.

Coupled with what epicurus has stated, I suspect there is an error causing the client to not be updated as session changes occur, such as normally happens with a gate jump or when logging in. This is extremely alarming.

Seeing some serious issues with C3 site spawning. We have had only 2 combat sites spawn since Crius release. Relics/data/gas are no better. have had 1 data, 1 relic, and no gas. The only thing I'm seeing is usually our Highsec static and a few other WH's. It's one thing to increase the connections to WH space w/ more WH's but this lack of sites is seriously harming our business model and we may de-anchor our POS if this stuff isn't sorted.

wormhole sites now have a small chance of spawning on top of previously spawned sites it seems

https://forums.eveonline.com/default.aspx?g=posts&t=361926&find=unread

on 2014.09.12 I bookmarked our c4 static (x877), noting its signature ID in the bm. Yesterday the signature was still there, at the same bm but the wh system on the other side had changed. Today, same thing. Yesterday's hole was eol at 07:15 and yet the sig was still there at 18:00, at the same bm location but with a different wh system on the other side.

on 2014.09.12 I bookmarked our c4 static (x877), noting its signature ID in the bm. Yesterday the signature was still there, at the same bm but the wh system on the other side had changed. Today, same thing. Yesterday's hole was eol at 07:15 and yet the sig was still there at 18:00, at the same bm location but with a different wh system on the other side.