Backstage - OOC Forums

Please login or register.

Login with username, password and session length
Advanced search  

News:

Ladette Russeot is a Gallentean woman who in YC106, at age 17, hacked the code used by deadspace warp beacons that had been proclaimed unhackable just days before.

Author Topic: POS Research Lab Question, or “Why can’t those fools design a functional interfa  (Read 2750 times)

Orthic

  • Wetgraver
  • Offline Offline
  • Posts: 58
POS Research Lab Question, or “Why can’t those fools design a functional interfa
« on: 09 Mar 2011, 15:26 »

So I’ve got a POS. It’s got labs on it. It’s got more lab slots than I have skills to make use of.

I’ve got alts. They have research skills. They aren’t in my corp.

Based on the options that come up when I hit “Manage Assembly Line,” it looks like I should be able to grant access to the labs to other people based on standings and such like. However, when I attempt to do so, it fails miserably.

Does anyone know if what I’m trying to do is possible, or if it’s just a pipe dream? Is there a workable guide to it somewhere that I haven’t found yet?


Logged

DosTuMai

  • Dirty Pirate Bitch
  • Omelette
  • Offline Offline
  • Posts: 255
  • Yarrr~~
    • Ravings of a Lunatic
Re: POS Research Lab Question, or “Why can’t those fools design a functional interfa
« Reply #1 on: 09 Mar 2011, 15:55 »
Usually setting the person/Corp blue fixes that. Also knowing the bubble password helps a lot with any issues regarding skill-enabled ranges. If in doubt, pick up and move the crap over yourself and use the tower in-situ on the alt(s).
Logged
do { aLittleDance(); make(aLittleLove&); cin.get(down); } while(tonight);
Quote from: Raynman37
Go down to the end, take a left at etc and you should see usr right there in front of you.

Orthic

  • Wetgraver
  • Offline Offline
  • Posts: 58
Re: POS Research Lab Question, or “Why can’t those fools design a functional interfa
« Reply #2 on: 09 Mar 2011, 20:13 »
Doesn't seem to have worked. I've had the standings sorted for a while. The bp I want to research is in the same system with the pos and labs. I've tried doing it from the personal hangar and from a corp hangar. When I try to select a location for the research, the pos labs simply don't show up for the alt.
Logged

Casiella

  • Demigod
  • Offline Offline
  • Posts: 3723
  • Creation is so precious, and greed so destructive.
Re: POS Research Lab Question, or “Why can’t those fools design a functional interfa
« Reply #3 on: 09 Mar 2011, 20:18 »
I do believe they need to be in the same alliance for ME/PE research. (Invention and copying requires corp membership.) It's been a few years since I dabbled in this, however.
Logged

Mithfindel

  • (a.k.a. Axel Kurki)
  • Pod Captain
  • Offline Offline
  • Posts: 695
Re: POS Research Lab Question, or “Why can’t those fools design a functional interfa
« Reply #4 on: 10 Mar 2011, 00:35 »
People in the same alliance with Scientific Networking can remotely use the labs for ME and PE research. BPO in a station-side office on the same system, research away. I have not tried, but I believe that the POS settings may be broken in this regard.
Logged

Jocca Quinn

  • Wetgraver
  • Offline Offline
  • Posts: 93
Re: POS Research Lab Question, or “Why can’t those fools design a functional interfa
« Reply #5 on: 10 Mar 2011, 04:54 »
If you want the alts to do ME and PE (tech 1) research they have to be (at least) in the same alliance. The bpos they work on have to be in one of their corp offices in the same system as the POS.

If you want them to do Copying, Invention, Reverse Engineering or any ME / PE research that uses consumables (ie some t2) then they have to be in your corp (the corp that put up the POS) as those jobs require access to the POS lab hanger.

The settings on the labs that say "public use" do not work and never have. My guess would be that those settings were put into the interface when POS were first released so that when the backend coding of those features was completed it would be easier to tie to the interface.

TLDR. CCP and none iteration of features .....
Logged