3.0 is scheduled to include Entity Update Component Scheduler which should help with framerate. This feature simply gives less updates for objects that are farther away from your position. It is not quite as useful as network culling but it will save a considerable amount of server CPU time and bandwidth.
There are many bits on network rewrites that are to improve and allow the scale SC needs for its PU.
As it shows the network is taking longer, they seem to have got the point they have to release 3.0 and the network to support things like the planets and such in a performing matter is not here yet, this is why of the discussion if the servers will be capable of performing on 3.0 before the big network rewrites hit the game.
The one you mentioned is one of them, the network bind/unbind is clearly a core thing, releasing one solar system and/or expanding the player count without it means one overwhelming amount of unnecessary updating.
Mission Givers moved from 12th May to 2nd June > "Sliding this back to take in account for new requirements for additional desired behaviors"
Delamar Landing zone moved from 1st June to 30th June > "Following meetings on what we could aim to achieve for 3.0.0, we have moved our date out to accommodate this goal."
Insurance moved from 12nd May to 26th May > "Work on this feature cannot be started yet due to additional design feedback and incomplete persistence tasks that create the base for the insurance system."
Entity Owner Manager moved from 31st May to 12nd June > "Feature on hold temporarily due to network system persistence dependencies."
KIOSK UI moved from 10th May to 25th May > "Work for this feature is temporarily on hold until the Game Code is at a place for UI work to continue."
StarMap App moved from 11nd May to 19th May > "Some of the tasks required for this feature have taken longer than initially anticipated."
Solar System Mission Service moved from 12nd May to 25th May > "Currently working through the remaining blocking issues for this initial implementation."
MISC Prospector moved from 12nd May to 19th May > "Slight delay in the VFX work for this ship."
New Tasks:
Rover and Dragonfly in Ships > "The work for this has finally been fully scoped out. Players will be able to transport the Ursa Rover and the Dragonfly inside ships that are big enough to hold them"
"We all do the best we can based on life experience, point of view, and our ability to believe in ourselves." - Naropa "We don't see things as they are, we see them as we are." SR Covey
Mission Givers moved from 12th May to 2nd June > "Sliding this back to take in account for new requirements for additional desired behaviors"
Delamar Landing zone moved from 1st June to 30th June > "Following meetings on what we could aim to achieve for 3.0.0, we have moved our date out to accommodate this goal."
Insurance moved from 12nd May to 26th May > "Work on this feature cannot be started yet due to additional design feedback and incomplete persistence tasks that create the base for the insurance system."
Entity Owner Manager moved from 31st May to 12nd June > "Feature on hold temporarily due to network system persistence dependencies."
KIOSK UI moved from 10th May to 25th May > "Work for this feature is temporarily on hold until the Game Code is at a place for UI work to continue."
StarMap App moved from 11nd May to 19th May > "Work for this feature is temporarily on hold until the Game Code is at a place for UI work to continue."
Solar System Mission Service moved from 12nd May to 25th May > "Currently working through the remaining blocking issues for this initial implementation."
MISC Prospector moved from 12nd May to 19th May > "Slight delay in the VFX work for this ship."
New Tasks:
Rover and Dragonfly in Ships > "The work for this has finally been fully scoped out. Players will be able to transport the Ursa Rover and the Dragonfly inside ships that are big enough to hold them"
Hey guys, CR here...we cant finish the stuff we promised but no worries, we are going to add a new task. This wont impact anything, trust me.
Hey guys, CR here...we cant finish the stuff we promised but no worries, we are going to add a new task. This wont impact anything, trust me.
If you want to see only negatives you will. They could opt to just highlight the positives.
Completed this past week:
Quantum Drive Conversion. (Gameplay // Item 2.0).
UI Owner Component. (UI framework for apps)
Solar System Shop Service. (backend // tech)
Drake Dragonfly. (ship)
RSI Constellation Aquila. (ship)
And CR specifically will have almost nothing to do with this. He will get updates sure - almost as we are! Maybe he OK's the addition of the new item but this is low level stuff. And he would certainly like all the estimates to be 100% accurate. As they say in the notes however they are going with best guess aggressive dates. So there will be slip. No slip means people are padding.
And kudos to them for being brave enough to show it as it is. Especially as some items have slipped more than once. (There's a part of me that wishes they were more accurate with their time estimates but good estimating is a skill.)
One by one work elements scheduled for 3.0.0 are being ticked off as complete however. And no major disasters have been announced. Its like watching paint dry but that is just the way it is. Graft pure and simple.
If you want to see only negatives you will. They could opt to just highlight the positives.
Yup, people that only want to see the negatives will only see the negatives.
And yes they could very well just say what they have completed and keep the rest hidden, but instead, they are showing the entire process to the public.
They finally completed ships that they showcased MONTHS ago...congrats. I guess as long as it can be spun as a positive they have to grasp at something. They claimed to have Dragonflies AND the new 'addition' of being able to unpack them and fly them out of ships in What Aug last year according to that fake video they showed? So why is THAT an addition when they supposedly already had it? As well as the dragonfly. Yup that positive is something that just raises more red flags with what they claim and what they deliver. There is also no 'evidence' anything they claim to have done is actually done other than their say so which we all know by now is meaningless. But because theyre 'updating' the list and showing a lot of delays then theyre being 'honest'.
The other three things they completed two of those directly relate to Amazon network. And the third one more than likely was a transfer over, so no actual 'work' had to be done on that either just a 'conversion' to lumberyard. (even though they have claimed to have been working with LY for over a year now). These little 'fixes' are definitely related to them going from whatever they had to what Amazon has.
At this point all of this is just more sales 101 and doesnt mean anything, until its in the test bed where everyone can play it or test it or whatever then it doesnt exist no matter what claims they make.
The other three things they completed two of those directly relate to Amazon network. And the third one more than likely was a transfer over, so no actual 'work' had to be done on that either just a 'conversion' to lumberyard. (even though they have claimed to have been working with LY for over a year now). These little 'fixes' are definitely related to them going from whatever they had to what Amazon has.
This is absolutely delusional. Do you have any idea what you are even talking about?
Your post shows how little do you know of what you talk about, and how you build this entire posts from what you think and assume things are.
Because for certain you didn't base your claims on your knowledge of what these SC features/tech are and knowledge of Lumberyard's features/tech.
The other three things they completed two of those directly relate to Amazon network. And the third one more than likely was a transfer over, so no actual 'work' had to be done on that either just a 'conversion' to lumberyard. (even though they have claimed to have been working with LY for over a year now). These little 'fixes' are definitely related to them going from whatever they had to what Amazon has.
This is absolutely delusional. Do you have any idea what you are even talking about?
Your post shows how little do you know of what you talk about, and how you build this entire posts from what you think and assume things are.
Because for certain you didn't base your claims on your knowledge of what these SC features/tech are and knowledge of Lumberyard's features/tech.
UI Framework and back end data is LY conversion based.
The game play (assuming improvement) of the other can be debated. Considering its something that has been in the test bed for over a year and is now finally getting improved a logical conclusion is they used the LY set up to improve it. Or at least streamline it.
It isnt a hard jump to think the SC version on CE is filled with crap thats redundant or over coded. Especially considering it never really worked in the first place. But people will debate that as well.
Either way its more and more delays and a very few things actually being completed. Once we start seeing things delayed a second or third time beyond their initial guess on when they would be ready the thread will really unravel. Which is going ot happen because they have completed (according to them) about 15% on time, therefore with 85% delayed that delays everything else going forward.
So once again even making this schedule was more marketing, and one in the real world would be a total disaster but because its SC it will be spun by all the spin masters as meaningless.
UI Framework and back end data is LY conversion based.
No, it is not.
The conversion is not from LY, it's towards their own systems that they have been in-dev. Many of those tasks relate to Item 2.0, in development since 2015, especially the interaction, interfacing, modularity and customization systems.
They rewrote the chunk of CE's that deals with this entire aspect of the game, it is not work made by Lumberyard that CIG is implementing.
Ideas are important, but with many "high profile" devs you notice once they left the company where they became famous, they never really anything even close. I took a look at the games released by David Brevik, former president of Blizzard North, responsible for games like Diablo and Diablo II.
What did he do after leaving Blizzard? Flagship Studios. So Hellgate London. Then working for Turbine for a year or two, in which nothing much happend. Afterwards, Gazillion Entertainment / Secret Identity Studios -> Only game in that time was Marvel Heroes. Since October 2016 he's apparently at Grinding Gear Games (Path of Exile) for their launch in China.
So he changed company like every two to three years and had one game release. And that in soon 15 years since Blizzard. Not exactly an inspiring career, even if it apparently didn't hurt his image in the industry.
Many others are similar. Ideas are important, but you also need the people who make it happen. Or maybe the idea guy isn't the only one with an idea. Or maybe not even *the* idea guy. Maybe it was someone else, and by virtue of being founder, president, CEO or already well known the guy we know as idea guy become known for this or that game?
No idea where Chris Roberts fits into this, but he's probably less important than most (including himself) think, especially now that the project is well underway.
Brevik spent MANY years helping to oversee development of MH and later as CEO. I'm pretty sure Brevik never worked at turbine. He is also just a consultant at GGG, advising them on their asian launch. He currently has a one man studio where he is making a mobile game.
If he only ever created D1 and D2 he'd have something to be VERY proud of. Although I do believe he does have a history of pushing out unfinished games since leaving blizzard.
UI Framework and back end data is LY conversion based.
No, it is not.
The conversion is not from LY, it's towards their own systems that they have been in-dev. Many of those tasks relate to Item 2.0, in development since 2015, especially the interaction, interfacing, modularity and customization systems.
They rewrote the chunk of CE's that deals with this entire aspect of the game, it is not work made by Lumberyard that CIG is implementing.
Youre backwards as usual. If theyre running on the LY version then they have to convert THEIR version to the LY version. There is a reason why they shit canned everything they did and redid and went with Amazon version. And in reality that still wont be enough, but it made for a good press release.
Either way the list of things they have done on time is pathetic. Regardless of the semantics argument you want to have (which is still wrong)
Youre backwards as usual. If theyre running on the LY version then they have to convert THEIR version to the LY version. There is a reason why they shit canned everything they did and redid and went with Amazon version. And in reality that still wont be enough, but it made for a good press release.
No, you are who is backyards here.
They did not shitcanned their game engine, they have modified over 50% of Cryengine's stock code, that code is as it was.
The big majority of Lumberyard's codebase is still Cryengine's code that is also the same branch of SC's CE (3.8).
They are the same engine to the core, hence why what CIG is doing is picking stuff from LY has that they want, into their modified engine, volumetric fog is one example as seen on the last dev update:
Mission Givers moved from 12th May to 2nd June > "Sliding this back to take in account for new requirements for additional desired behaviors"
Delamar Landing zone moved from 1st June to 30th June > "Following meetings on what we could aim to achieve for 3.0.0, we have moved our date out to accommodate this goal."
Insurance moved from 12nd May to 26th May > "Work on this feature cannot be started yet due to additional design feedback and incomplete persistence tasks that create the base for the insurance system."
Entity Owner Manager moved from 31st May to 12nd June > "Feature on hold temporarily due to network system persistence dependencies."
KIOSK UI moved from 10th May to 25th May > "Work for this feature is temporarily on hold until the Game Code is at a place for UI work to continue."
StarMap App moved from 11nd May to 19th May > "Some of the tasks required for this feature have taken longer than initially anticipated."
Solar System Mission Service moved from 12nd May to 25th May > "Currently working through the remaining blocking issues for this initial implementation."
MISC Prospector moved from 12nd May to 19th May > "Slight delay in the VFX work for this ship."
New Tasks:
Rover and Dragonfly in Ships > "The work for this has finally been fully scoped out. Players will be able to transport the Ursa Rover and the Dragonfly inside ships that are big enough to hold them"
I love the amount of delays 1 month after they announced their super bulletproof completely solid schedule...imagine the mess in 3 months lol
I think I actually spent way more time reading and theorycrafting about MMOs than playing them
I think CIG should be congratulated for being the most open development game ever while at the same time publishing their internal schedule so we get to see how delays are made in the gaming industry.
Especially from a company who is so incredibly talented in delaying everything all the time.
I think CIG should be congratulated for being the most open development game ever while at the same time publishing their internal schedule so we get to see how delays are made in the gaming industry.
Especially from a company who is so incredibly talented in delaying everything all the time.
If you can't handle to watch the sausage being made because it's not a pretty process, then don't watch it.
Easy is figuring the reason companies keep this process behind closed doors by default.
Comments
As it shows the network is taking longer, they seem to have got the point they have to release 3.0 and the network to support things like the planets and such in a performing matter is not here yet, this is why of the discussion if the servers will be capable of performing on 3.0 before the big network rewrites hit the game.
The one you mentioned is one of them, the network bind/unbind is clearly a core thing, releasing one solar system and/or expanding the player count without it means one overwhelming amount of unnecessary updating.
https://robertsspaceindustries.com/schedule-report
Diffchecker: https://www.diffchecker.com/DYdsr7Rb
Completed this past week:
Updated Deadlines:
> "Sliding this back to take in account for new requirements for additional desired behaviors"
> "Following meetings on what we could aim to achieve for 3.0.0, we have moved our date out to accommodate this goal."
> "Work on this feature cannot be started yet due to additional design feedback and incomplete persistence tasks that create the base for the insurance system."
> "Feature on hold temporarily due to network system persistence dependencies."
> "Work for this feature is temporarily on hold until the Game Code is at a place for UI work to continue."
> "Some of the tasks required for this feature have taken longer than initially anticipated."
> "Currently working through the remaining blocking issues for this initial implementation."
> "Slight delay in the VFX work for this ship."
New Tasks:
> "The work for this has finally been fully scoped out. Players will be able to transport the Ursa Rover and the Dragonfly inside ships that are big enough to hold them"
"We all do the best we can based on life experience, point of view, and our ability to believe in ourselves." - Naropa "We don't see things as they are, we see them as we are." SR Covey
Hey guys, CR here...we cant finish the stuff we promised but no worries, we are going to add a new task. This wont impact anything, trust me.
And CR specifically will have almost nothing to do with this. He will get updates sure - almost as we are! Maybe he OK's the addition of the new item but this is low level stuff. And he would certainly like all the estimates to be 100% accurate. As they say in the notes however they are going with best guess aggressive dates. So there will be slip. No slip means people are padding.
And kudos to them for being brave enough to show it as it is. Especially as some items have slipped more than once. (There's a part of me that wishes they were more accurate with their time estimates but good estimating is a skill.)
One by one work elements scheduled for 3.0.0 are being ticked off as complete however. And no major disasters have been announced. Its like watching paint dry but that is just the way it is. Graft pure and simple.
Yup, people that only want to see the negatives will only see the negatives.
And yes they could very well just say what they have completed and keep the rest hidden, but instead, they are showing the entire process to the public.
The other three things they completed two of those directly relate to Amazon network. And the third one more than likely was a transfer over, so no actual 'work' had to be done on that either just a 'conversion' to lumberyard. (even though they have claimed to have been working with LY for over a year now). These little 'fixes' are definitely related to them going from whatever they had to what Amazon has.
At this point all of this is just more sales 101 and doesnt mean anything, until its in the test bed where everyone can play it or test it or whatever then it doesnt exist no matter what claims they make.
Your post shows how little do you know of what you talk about, and how you build this entire posts from what you think and assume things are.
Because for certain you didn't base your claims on your knowledge of what these SC features/tech are and knowledge of Lumberyard's features/tech.
The game play (assuming improvement) of the other can be debated. Considering its something that has been in the test bed for over a year and is now finally getting improved a logical conclusion is they used the LY set up to improve it. Or at least streamline it.
It isnt a hard jump to think the SC version on CE is filled with crap thats redundant or over coded. Especially considering it never really worked in the first place. But people will debate that as well.
Either way its more and more delays and a very few things actually being completed. Once we start seeing things delayed a second or third time beyond their initial guess on when they would be ready the thread will really unravel. Which is going ot happen because they have completed (according to them) about 15% on time, therefore with 85% delayed that delays everything else going forward.
So once again even making this schedule was more marketing, and one in the real world would be a total disaster but because its SC it will be spun by all the spin masters as meaningless.
The conversion is not from LY, it's towards their own systems that they have been in-dev. Many of those tasks relate to Item 2.0, in development since 2015, especially the interaction, interfacing, modularity and customization systems.
They rewrote the chunk of CE's that deals with this entire aspect of the game, it is not work made by Lumberyard that CIG is implementing.
If he only ever created D1 and D2 he'd have something to be VERY proud of. Although I do believe he does have a history of pushing out unfinished games since leaving blizzard.
Either way the list of things they have done on time is pathetic. Regardless of the semantics argument you want to have (which is still wrong)
They did not shitcanned their game engine, they have modified over 50% of Cryengine's stock code, that code is as it was.
The big majority of Lumberyard's codebase is still Cryengine's code that is also the same branch of SC's CE (3.8).
They are the same engine to the core, hence why what CIG is doing is picking stuff from LY has that they want, into their modified engine, volumetric fog is one example as seen on the last dev update:
I think I actually spent way more time reading and theorycrafting about MMOs than playing them
Especially from a company who is so incredibly talented in delaying everything all the time.
..Cake..
Easy is figuring the reason companies keep this process behind closed doors by default.
¯\_(ツ)_/¯
I was actually saying that watching the sausage being made is very entertaining and you should buy more Idrisis so that the show can continue.
I wouldn't want any other company than CIG showing us how to make the sausage.
They are perfect.
..Cake..
And that was already made for the case of Apple.
The process of showing what you're doing behind the scenes is already quite widely spread in the industry. Especially in the indie scene.
The criticism is against CIG's incompetence, lies and greed.
Oh not criticism.. I meant HATE... yes.. HATE, so much HATE....
Hate everywhere!
..Cake..