Feedback about communication around CDLC updates

[Darkbelg 4]

Ok, i didn't know artists could leave and then their work remains unfinished. That sounds frustrating. And I'm guessing because this a nice market it is also hard to find a replacement to finish these. Certainly if you can't talk about it publicly.

 

So at the moment I feel like there is like a total blackout on what is going to be in a future update.I’m guessing BI does this so people won't be over promising. For example we are going to make 15 jets and then only deliver one that is broken. If that happens It makes BI look bad and their reputation would take a hit. Of Course they don’t want that.

 

How about instead of saying what you are making we could talk about what has been finished. This is what BI seems to do with their Enfusion engine. They talk about what is and not about what is to come. In some way CSLA is already doing this. They have released mods that are going to be in a future update. The communication around this was bad. I had to ask why this wasn’t in the CDLC. The only purpose seems to be to circumvent the QA and push out content quicker. To me at first it felt weird and illegal. But they haven’t been whistled back by BI. So it does seem to be a valid strategy.

 

Now let’s talk about QA. I know at the end of all your finished work there is still this QA. Honestly i don’t know how to see them as. Is this a wall or a monster you have to get through? Sure, some finished work might not get through the QA. If you did show pictures of work that didn’t make it through. Can’t you just communicate that it will require more work to finish it?

 

That being said if it doesn’t get through. You still seem to have the option to release it as a mod. This makes BI less liable and gives you the ability to test it more and get a better feedback loop. For example if you would be working on something like STABO exfiltration and it’s pretty jank. You could release it as a mod and see what the feedback is.

 

A dev branch could also help in the feedback loop. I guess there are non public dev branches. And with a dev branch I am not talking about the RC two weeks before release. The thing with a dev branch is everything is susceptible to change and does not reflect the final product.

 

To go back to the unfinished work. If you had the ability to post a picture of the model and say:”The artist who was working on this left we are looking for someone to help us finish this.”. This way you are able to show that you are working on something and also showing people that you are lacking some expertise. This way you are lowering expectations while keeping people up to date.

 

The following idea is a bit more out there. But if you are able to talk about certain things you want to do but don’t know how to. It might allow for a bounty program. For example STABO extractions. You could put out a bounty for a proof of concept with some minimum requirements. And then work with that person to a finished product or take it over. You would have a basis that works.

 

I also don’t know how the BI policy is worded. Is it possible to share this publicly? You might have to go back to BI with some feedback on their policy or ask for clarification about the policy. Has the policy changed at all since the release of GM?
This CDLC is also new for them.

 

That is my feedback.
 

[Darkbelg 4]

NVMD it is irrelevant. Would delete the thread if i knew where that button is.