Don't forget about us please

What happened to the weekly screenshot updates?

(Please don't forget us non FB users :cry: )

+1

This posted on Facebook 3 hours ago but still no word here...

A friend who has Facebook account pointed me to it. Wouldn't have known otherwise...

I'm struggling to understand why ED didn't warn Polychop of the potentially show stopping code changes in advance. Now they say they're having to figure it out for themselves as well. Haven't even been given the details after the fact.

I'm sorry but I have to say that is just a ridiculous situation to put them in. Way to go ED...

I'm struggling to understand why ED didn't warn Polychop of the potentially show stopping code changes in advance. Now they say they're having to figure it out for themselves as well. Haven't even been given the details after the fact.

 

I'm sorry but I have to say that is just a ridiculous situation to put them in. Way to go ED...

This is ED's typical behavior towards 3rd parties unfortunately ... Is it really that hard to update your supposed business partners on obviously important information... Not a surprise they had no clue about the Razbam Harrier dumpster fire or all the issues Heatblur had to deal with concerning getting the Tomcat compatible with the Supercarrier or AIM-54 issues... At what point does ED actually address repeating issues?

ED sits on his SDK like a hen on an egg. Just don't give too much information outside. And if only the bare minimum. Maybe we are doing the 3rd party developers an injustice and you would have to give ED the buck ...

+1

 

This posted on Facebook 3 hours ago but still no word here...

 

A friend who has Facebook account pointed me to it. Wouldn't have known otherwise...

My initial response I had to delete,, I rarely respond to any thread in a negative fashion,,, This is certainly an exception! WHAT THE $%^&

On reflection I can understand why the team only posted on Facebook and didn't get round to posting that news here as well.

They're just still shell shocked and scrambling to figure out how to proceed after having their project properly torpedoed.

To the Polychop team:-

We (I'm sure I speak for the majority here) feel your pain over this setback and wish you all the best in getting yourselves back on track.

Hopefully ED will step up and offer some help in working through the issues. It's the least they can do under the circumstances.

Please do update us here on the forum when you can. We are all keen to see you do well.

You people need to calm down. Sven from Polychop has posted on Facebook that he has spoken to ED and they are working on a fix. So put the pitchforks away.

You people need to calm down. Sven from Polychop has posted on Facebook that he has spoken to ED and they are working on a fix. So put the pitchforks away.

I haven't seen any pitchforks here (well.. maybe one :P).

All I started this thread for, was to kindly ask any of the involved parties to maybe skip 1 FB post and use that time to post something here :)

Sven from Polychop has posted on Facebook that he has spoken to ED and they are working on a fix.

Where did you read that? There is nothing on their FB page to confirm they've spoken to ED. We can hope and assume that they have spoken with them by now, that's all. It is not written anywhere though.

No pitchfork here, just disappointed at the apparent lack of teamwork and communication on ED's behalf. A courteous forewarning could have saved the Polychop team a lot of stress.

To get back to Sirrah's original post - accurate news posted here would help avoid rumours and speculation.

Hi Newy,

Not having a go at you here as I know your job is to keep the peace and maintain some order here - which you do with great aplomb. Cudos and respect to you there. I certainly don't wish to think the worst of ED, not at all. I'm a big fan of the sim.

We can't escape the fact however that the code changes in question weren't something cooked up overnight. ED must have known a good while ago that these could potentially derail the Kiowa project, yet seemingly they didn't reach out to the team early enough... only after the damage was done. Unless we haven't got the full story? If not, please enlighten us.

If ED did mess up, a simple acknowledgement that "Yes, we dropped the ball on this one." would go a long way towards making us feel all warm and fuzzy inside again. Trying to brush it aside like nothing happened and nothing went wrong is bound to raise some hackles.

Honest and open communication is the key to maintaining harmony. People are much more likely to forgive and forget if they are given the truth straight up. If you mess up, fess up. Then we can all move on in peace. I learned that lesson early in life and it has served me well.

Please just keep us updated with honest and accurate news.

I think I've missed some crucial detail lol... the Kiowa module is derailed?

To get back to Sirrah's original post - accurate news posted here would help avoid rumours and speculation.

It would also help if the community would act like adults and not freak the hell out at the drop of a hat @@

The transition from bitmap texture based HUD and MFD graphics to vector based SVG is part of DCS 2.5.6. It is publicly known for months and is already implemented in some modules (F/A-18...). Making such a drama post on FB makes no sense. The change didn't come over night and is just a part of DCS's always ongoing development.

"Drama raising" From someone's.....

Meanwhile Sven on FB put a curated info

Sven here, just to let everyone know, what ever issue happened, please do not speculate. I had a very proactive phonecall with someone from ED. All sides have a good plan for the future and I can only ensure that ED and aswell we as a team, try to solve this as soon as possible. As I said before, on the bright side, all can work out better ways for the future. Issues can only be fixed as soon they happen, what ever the issue is. So, I see it this way, better now, then later, because in terms of the kiowa warrior, it can only benfit from the changes we talked about on the phone. Have a great weekend all

Enviado desde mi RNE-L21 mediante Tapatalk

The good thing about vector based symbology is that everything is scalable now. Nothing is limited by fixed pixel density anymore. This will improve HUD and MFD readability and improves the quality and reduces efforts for dynamic/animated symbology.

Wow!

Some strong words here and there... I wonder where and how this thread got misinterpreted.. One thing's for sure, some folks here need to cool down a bit before they start and type messages...

I merely asked for my weekly dose of Kiowa screenshot..

(At the time of my OP, I hadn't even seen the news on the slight setback at Polychop)

that is the internet for you :)

I guess it is... Almost 40, still naive :P

(Just to make it totally clear, I always had and still have complete trust in ED, and I'm grateful for what it gives us. Closest I'll ever get to flying the real thing :thumbup:)

No need to pick up the pitchforks and torches guys. As BN stated above we are and always have been in contact with ED. The core engine is a constant work in progress, ED has been doing a great job in enhancing it and making it an ever more feature rich environment. The code of a module heavily relies on the core engine, when certain parts of the engine code are changed it might interfere with the module. Both ED and Polychop have been working on a more streamlined way of testing and communication to prevent situations like these over the past months. Even though significant improvements on both internal testing and communications have been made, this one caught us by surprise. Our first priority is to repair the newly introduced bugs while we work out how to prevent this from happening again with ED. Rest assured ED has reached out and is working with us on this.

I don't comment the communications between ED and other studios as it is not our concern as we don't know about it.

But I just wish that Polychop wouldn't make the small (but serious) mistake that not using ED forums as primary communications channel for everything, and only after that going for the third party channels like Facebook, Discord and such.

It shouldn't be too difficult to first write the info on "scratchpad" and then copy-paste it here in new thread (with decision is it locked or not) and then to 3rd party channels.

There are more people who respect those who communicate honestly and directly from all good and bad news, and that they can find the information easily and quickly in official product store forums.

... I just wish that Polychop wouldn't make the small (but serious) mistake that not using ED forums as primary communications channel for everything, and only after that going for the third party channels like Facebook, Discord and such.

AFAIK PC do use ED's forums as their primary means of communication.

People complain there's not enough communication ?

PC add FB and discord, so users can ask informal questions and give their feedback directly.

What would you like PC to do when a user asks a question on discord - ignore the user/question, cross post every answer, hold a meeting to decide if, where and when a answer should be given ?

If you want to know "every" detail, sign up to social media, discord, etc., otherwise don't.