| Pages: [1] :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Reverend John
   |
Posted - 2005.12.17 11:59:00 -
[1]
The new manufacturing has many good points to it but one major issue i can see is having to click on the delivey button when job is done.
Lets say your corp is divided into departments and for security reason you have access to bpo's and bpc limited to a trusted few and those players have been tasked to keep hangers stocked with supplies for the corp.
Now you are having to defend your space from invaders or going out on a op. Or even someone takes all the ammo and you need to build more. The builder starts his jobs up and choose to build 1000 runs. The ammo is not ejected into the corp hanger till all runs are complete. The job is going to take 6 hours.
The builder needs to log. Ok here is where the problem lies. The ammo will not go to the corp till that user comes back and clicks on delivery. So now you have a bp and your ammo tied p till this user gets back online. ans if some rl issue comes up and that user can not play for 3 or 4 days the issue gets worse.
What i think needs to happen is this delivery button needs removed and ammo go directly back into hangars as before. Also one last thing. i have noticed is manufacturing seems to be slower now. I was the only person at the station using manufacturing at that time so all slots where not being used.
|
Nyphur
|
Posted - 2005.12.17 12:03:00 -
[2]
The delivery button suspends lag. Effectively, what they have done is make it so that the only time lag is caused is when a player interacts with the game invironment. Previously, building things meant the server was interacting with itself continually without user input. It was dropping a stack of ammo every minute into a hanger etc. The delivery button is there so that the server is not doing anything with the building mechanisms without user input.
This means server lag is a direct function of player count, which means server solutions would be easier to implement. Upgrades would be easier to target. Building no longer causes unneccecary lag. Aren't you happy?
|
Jorge Kamzell
|
Posted - 2005.12.17 12:16:00 -
[3]
I wasn't a fan of the new system at first but I'm really getting to grips with it now and its far better than the old way. You just need to approach manufacturing in a different way now, it doesn't take long to adjust.
|
Jennai
|
Posted - 2005.12.17 12:17:00 -
[4]
there's no way to register a job to corp so other people can take it out when it's done? that seems like a pretty big oversight.
|
Andrue
|
Posted - 2005.12.17 17:18:00 -
[5]
 Originally by: Jennai
there's no way to register a job to corp so other people can take it out when it's done? that seems like a pretty big oversight.
If you are doing something with BPs from a corp hangar it is seen as a corp job. This is actually a bit annoying because you can only search for one or the other not both. I was about to petition the loss of two BPs and mins today until I spotted the option to filter by corp jobs.
--
(Battle hardened miner)
[Brackley, UK]
WARNING:This post may contain large doses of reality. |
Kai Lae
|
Posted - 2005.12.17 17:23:00 -
[6]
I suspect what people are really asking for is the ability to select an option so that after the run is complete, it is automatically delivered to a certain hangar. This is no different than having them press a button, other than they don't have to be logged on to do that.
|
Gardok
|
Posted - 2005.12.17 17:39:00 -
[7]
Originally by: Kai Lae
I suspect what people are really asking for is the ability to select an option so that after the run is complete, it is automatically delivered to a certain hangar. This is no different than having them press a button, other than they don't have to be logged on to do that.
From a programmers perspective it makes complete sense to not have objects be put into a hanger once a job is completed automatically.
I have been programming middle tier logic quite a bit in my career and the number one rule when doing this is to make sure you don't overload the server with processes. What I think has been done is when you create a job a "time stamped entry" is put into the database. When people queue jobs a timestamp also gets put into the database but the entries are also linked to the job before it. This way the server does not need to be constantly running a process to determine if a job is done. The server only needs to hit the database when a user wishes to view the status of a job, or creates a job. When a user clicks on deliver then a server process kicks in to deliver the item. Basically by doing it this way they are removing a process for every science or factory job which is HUGE for server performance. As for the lag we are experiencing now... You're guess is as good as mine :)
|
Gardok
|
Posted - 2005.12.17 17:47:00 -
[8]
Edited by: Gardok on 17/12/2005 17:48:29
Duplicate Post. Sorry. Damn forum lag :)
|
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |