fmedges

Kind enough? I don’t believe you understand how business works. Who reiterated over and over about which lot and which nations hornet they were making? The customer, or the business?

Last night my group and I were on the SC. Some from the ramp and some from previously landed. Request launch worked for all the parked planes and for about half of the landed planes. In total we had about 8 on deck. As planes took off the were able to request launch and have it work except one. Is there a limit to how many can request launch and does this dictate the order that they have to go in? A side effect of removing the taxi to cat text is that when I request a launch I get no feedback as to whether the SC has received my request. Maybe have a queue list for the cats or something?

Wouldn’t ED having the info to begin with be an export as they are not a US company?

@NineLine would you pass this to the team?

It’s weird that ED was very adamant about what lot of US Navy hornet they were making and what they were not making (foreign hornets with ils for example). Now it seems we’re getting listening pods with foreign export symbology. It’s an odd choice if that’s true.

My warthog is at 100% exactly at the detent

MSAA seems to be the issue for me as well. Turning it off resolved this and unfortunately the game looks like crap now, but oh well.

Thanks, I’ll try this

that's it thanks

After trapping, how can I get the launch crew to hook me up to the cat? Currently they are still in recovery ops. I am the only plane in the created mission.

Sanity check. I flew some absolute horrific case 1 patters this afternoon and something feels different with the throttles. Am I crazy?

@BIGNEWY From the man himself Jell-O.

I have found this to be the case as well

Exactly this. This is still a problem see attached photos.

I don’t like it so you can’t have it, thanks Karen.

I don’t believe that they need to expose their dates but more so their roadmap and what they are currently working on to have the community feel in the loop. Honestly just don’t say something is done and coming out until it’s 100% solid and tested and is actually going to come out. Most people here want them to succeed, but hate that they feel constantly duped.

Honest question why not take a few releases off to build a buffer between active development and what is completed, so in the future when issues arrive you can use some of that to meet your planned dates? For instance what gets released tomorrow would of actually been completed a month ago. Not only could you give yourselves some breathing room, but the bad optics of constantly skipping features could go away.

It’s good according to their statement that they found issues with the new implementation and pulled it. I think they they are in a bad position in that they are always working to these two week releases seemingly right up until that date. They should modify their process so that there is a buffer between when work is completed and when it gets released into the beta branch. This would give them time in their planning to fix issues and also to hit their target releases more consistently. Once implemented for instance the work that gets released tomorrow would of actually been completed a month ago.

It’s easy. Don’t say a feature is in until it’s in. You can say we’re working on this and that but the problem they keep running into is saying this is in when it’s not. Everything in the software development world is dates. Bug fixes have target fix dates, features have dates, iterations have dates, releases have dates. All of the planning and work is towards dates. If they are uncomfortable with meeting dates then their process is flawed and they are in the wrong business to be honest.

As someone who has worked as a machinist and as a software dev I understand where you are coming from but think of it this way. As a software dev you are making the prints and also machining the parts so it’s not a one to one comparison. If the event of a change they would change the design, update the design document and change the implementation all themselves. Completely different then sending plans back for a revision to someone else because they don’t understand tolerance stacking for instance. What I can say about software is they every feature or bug fix I do has a date on it and is tracked on a board. Missing dates happens but only internally. Missing dates to a customer is very bad and in a business software world is usually accompanied by monetary penalties. We would never tell a customer that a feature is in until its merged into the release branch and through QA testing.

They put the pressure on themselves. I didn’t make a post saying it will be released in the next update, they did and they keep doing it. If they don’t want criticism for missing dates then stop posting about dates. Who is setting unrealistic expectations? The consumer or the developer?

What’s the tws bug? I’ve had my tws locking targets while I was weight on wheels, is it related to that?

This is a pretty ignorant comment regarding software development and dates.

Working like the rest of us.

That ball tool is a welcome addition. Jar did an awesome job with the explanations. One of the best case one videos I’ve seen in relation to dcs.