What system can I get one from?
The Drew Wagar system, iirc.
Sarah moved from current project, update no longer coming?
- Thread starter CMDR MyNameIsKodos
- Start date
- Status
The Drew Wagar system, iirc.
Absolutely right. But let's just check that by running it up the flagpole and seeing if anyone salutes it.I was about to say the same thing
I'd love to meet the idiots who come up with these meaningless phrases just as much as I like to ask people what do you mean exactly?
Personally I blame team building companies for bringing so much drivel into the world!
Yes, what do you call those sort of people? Women? I can't remember.
It used to be... <looks downcast...>
She was the only one working on AI to community's knowledge and she was doing a good job and also good job of interacting with us. You stopped both. What do you have her do now. Background simulation?
Where you left it.. behind the Dog's chair...
:O
Careful, not everyone has a sense of humour
The first one gets the oyster, the second one gets the shell.
I was about to say the same thing
I'd love to meet the idiots who come up with these meaningless phrases just as much as I like to ask people what do you mean exactly?
Personally I blame team building companies for bringing so much drivel into the world!
well, I'm sure you manage to do it anyway. atleast you're the expert, right?
[video=youtube;BKorP55Aqvg]https://www.youtube.com/watch?v=BKorP55Aqvg[/video]
First the truisms:
It is very common in development that people work on different elements.
It's also very understandable that AI is a pickle and may be subject to developments in other areas.
I'm not going to go into the employee-employer relationship, that's none of my business technically however I feel about that emotionally.
But what the missing piece of information is: in what way will this affect AI development. Will there be an AI update shortly? In 1.4 perhaps? Should we not expect an AI update soon, but instead get an assurance it's on the todo list for later updates? This is part of the game I bought, and even though I am not entitled to answers, I am at least entitled to that curiosity. And satisfying that curiosity will grant you merits towards the Satisfied Customer Community Goal. Surely as Head of Community Management that's a tasty prospect no?
Summarized: You're explaining the rules of the game man, but we want to know the score!
Last edited:
Yeah, this does happen. When I have my PM hat on I try to protect my devs from that crap, but when the asker is well above your pay grade, not much can be done.
And it doesn't just happen to devs, when I have my application analyst hat on, I often get assigned new projects while in the middle of others. The difference, in my case, is that they don't ask me to stop what I was doing before. Two, three, four jobs for the price of one!
Thanks Zac.
I believe most of us understand how people can get moved around on projects based on demand. But it's the manner in which it happened that has people concerned.
If Sarah had come here on the forums and posted: "Hi everybody. I've been moved off of the AI work for now to focus on more critical game elements, but not to worry, all my hard AI work is not lost and will make it into the game at some point.". Then the backlash probably wouldn't be nearly what it is.
It's the forum gag-order that she's been handed, plus the tone of her twitter posts shows that she clearly didn't sound happy about the change. I think that's why this thread has blown up like it has.
That's easy... your notifications tab is your friend...
Pfft, clearly someone who doesn't read properly (in which case I'm surprised I didn't get rep
) - I made the opposing statements in the same post.
Last edited:
That's easy... your notifications tab is your friend...
If you'd actually read jab's post, you'd know why your post is funny for different reasons than you think.
Edit: And ninja'd by the man himself.
Last edited:
I take your point. People without a sense of humour might think I was a serious misogynist but I didn't think anyone would notice my lack of manners over the noise of the overwhelming sense of entitlement going on here.:O
Careful, not everyone has a sense of humour
The first one gets the oyster, the second one gets the shell.
:O
Careful, not everyone has a sense of humour
Really? Must keep a look out for these people... they must be really good at hiding as a lot of posts I've seen the past few days have had immense comedy value
Pfft, clearly someone who doesn't read properly (in which case I'm surprised I didn't get rep
True I get your point but my advice still stands...
Oh and couldn't rep you as I need to spread the love a bit more...
Last edited:
Shush... we're trying to keep a lid on that one....
Javert
Volunteer Moderator
What may well have happened here is that one developer was working on the AI code improvements for the current release game to improve the AI.
In the meantime, other developers are working, or desperately need to work, on the same blocks of code for another "project". For example, AI behaviour of NPC ships during atmospheric flight (it's just a random example of course).
Those developers have to try to keep their code in sync as they may be working on separate branches or builds.
The intention or hope was that the AI changes would be considered ready enough for implementation that they could be pushed out into the release version or merged into the top secret version by a certain drop dead date. In this context, keep in mind that FD have stated in a recent dev update that they want to reduce the frequency of updates and they have been pushing things out a bit too quickly and too often.
They may have now reached the point where it's too late to wait any longer, and they've taken the decision that the new AI code for the top secret project overrides the existing improvements that are being worked on in another branch, and that that code has diverged from the existing code so much that they cannot now be merged any more.
Possibly, there was a polite debate over whether the changes made by said developer already should be merged into the new top secret development at this point, or whether they should be left separate as they are not yet good enough to be in that branch. The latter point of view won the day.
Hence, all the work that was done on the AI for the current release in the last couple of months will be "lost", in the sense that it cannot be implemented as is. It will not have been completely deleted, but the changes will have to be manually re-coded and re-tested into the new branch and of course may not work with the other changes already made so there will now be rework to do.
They have also decided that they need to reassign said developer to other work for the time being so those changes are effectively shelved for the moment.
Dev was upset that she did a lot of work on this and that it will probably have to be reworked later on as the time has run out. She has probably got over it and moved on by now, as this type of thing happens all the time in software development. It's not ideal, but it can't be avoided sometimes.
In the meantime, other developers are working, or desperately need to work, on the same blocks of code for another "project". For example, AI behaviour of NPC ships during atmospheric flight (it's just a random example of course).
Those developers have to try to keep their code in sync as they may be working on separate branches or builds.
The intention or hope was that the AI changes would be considered ready enough for implementation that they could be pushed out into the release version or merged into the top secret version by a certain drop dead date. In this context, keep in mind that FD have stated in a recent dev update that they want to reduce the frequency of updates and they have been pushing things out a bit too quickly and too often.
They may have now reached the point where it's too late to wait any longer, and they've taken the decision that the new AI code for the top secret project overrides the existing improvements that are being worked on in another branch, and that that code has diverged from the existing code so much that they cannot now be merged any more.
Possibly, there was a polite debate over whether the changes made by said developer already should be merged into the new top secret development at this point, or whether they should be left separate as they are not yet good enough to be in that branch. The latter point of view won the day.
Hence, all the work that was done on the AI for the current release in the last couple of months will be "lost", in the sense that it cannot be implemented as is. It will not have been completely deleted, but the changes will have to be manually re-coded and re-tested into the new branch and of course may not work with the other changes already made so there will now be rework to do.
They have also decided that they need to reassign said developer to other work for the time being so those changes are effectively shelved for the moment.
Dev was upset that she did a lot of work on this and that it will probably have to be reworked later on as the time has run out. She has probably got over it and moved on by now, as this type of thing happens all the time in software development. It's not ideal, but it can't be avoided sometimes.
- Status