Voted and really hope they will fix it on this update.

I don't care about cold start the A320, can always take off ready to go, but a lot of plane are right now unflyable with this AP bug, which is game breaking.

I truly hope they don't set priorities based on the vote number, or I and people with poor internet will never get a working manual cache, so we will be stuck with FSX style for a long time.  

I'm starting to think the unthinkable.  How can a team break key features and not know how to fix them?  It's almost like a contract team built the sim, was layed off, and what's left at Asobo is far from the talent that built the core sim.  How else would it be explained looking at the list of the next patch nothing meaningful is getting addressed. With each patch major things are broken.  The Longitude is just in limbo.  Who built the Longitude, why are they dodging fixing it?  I know this may be far fetched but I'm losing confidence in what I'm seeing.  The community shouldn't have to figure out the LOD issue and the CEO of Asobo is looking dumbfounded as to what's causing it in the last live stream.  I hope I'm wrong.  

@Dillon - get over yourself.    As I said before pushing and nagging isn't going to solve things any quicker.  Let the team address this and back off.  If you were part of the development process I wouldn't be saying this but you are out of line IMO.

Regards

bs

2 hours ago, bean_sprout said:

Garmin is going to be doing the Garmin code so give them time to get ramped up.  

Validation?

 

5 minutes ago, bean_sprout said:

Regards

bs

Oh My.

8 minutes ago, bean_sprout said:

pushing and nagging isn't going to solve things any quicker.

It's not about how quickly it will get fixed, but more about the order.

blurry trees, low LOD, rounded mountain, tall building will not make your flight impossible, the AP pitch thing will.

It's easy to understand the frustration when something is broken because of a patch and not on the priority fix list 

1 hour ago, bean_sprout said:

Hmmm - maybe it was a misinterpretation but it makes too much sense not to pursue that route.

Regards

bs

It’s s misinterpretation.  Garmin is not doing any coding for MSFS.

3 hours ago, bean_sprout said:

Garmin is going to be doing the Garmin code so give them time to get ramped up.  

Push all you want but it won't speed up the process.

 

Regards

bs

so  saying nothing  is  going to get  their  attention

1 hour ago, bean_sprout said:

As I said before pushing and nagging isn't going to solve things any quicker.  Let the team address this and back off.  If you were part of the development process I wouldn't be saying this but you are out of line IMO

If they're already working on it then you're absolutely correct. But are they? Is it on their radar? It's a pretty serious issue IMHO and it's not out of line to elevate it to get the attention it warrants. My two cents. Anyway, I voted. No harm in that.

1 hour ago, bean_sprout said:

@Dillon - get over yourself.    As I said before pushing and nagging isn't going to solve things any quicker.  Let the team address this and back off.  If you were part of the development process I wouldn't be saying this but you are out of line IMO.

Regards

bs

Please stop! LOL! And go vote please! 

I reckon its already fixed in the patch. The Thursday update said the patch fixed a number of areas. Just because the forum post is not started (as in no one has looked into it) doesn't mean its not already been taken care of after being spotted by testers or devs. Most of those forum requests posts are badly written and its not even clear on some what they want changed.

Edited October 10, 20205 yr by sanh

5 hours ago, bean_sprout said:

 

Garmin is going to be doing the Garmin code so give them time to get ramped up.  

 

Wait for real? Where’d you hear this? I’m pretty sure this isn’t the case...

Edited October 10, 20205 yr by FlyingInACessna

4 hours ago, Dillon said:

I'm starting to think the unthinkable.  How can a team break key features and not know how to fix them?  It's almost like a contract team built the sim, was layed off, and what's left at Asobo is far from the talent that built the core sim.  How else would it be explained looking at the list of the next patch nothing meaningful is getting addressed. With each patch major things are broken.  The Longitude is just in limbo.  Who built the Longitude, why are they dodging fixing it?  I know this may be far fetched but I'm losing confidence in what I'm seeing.  The community shouldn't have to figure out the LOD issue and the CEO of Asobo is looking dumbfounded as to what's causing it in the last live stream.  I hope I'm wrong.  

Pretty sure they'r Illuminaties too... 

4 hours ago, Dillon said:

I'm starting to think the unthinkable.  How can a team break key features and not know how to fix them?  It's almost like a contract team built the sim, was layed off, and what's left at Asobo is far from the talent that built the core sim.  How else would it be explained looking at the list of the next patch nothing meaningful is getting addressed. With each patch major things are broken.  The Longitude is just in limbo.  Who built the Longitude, why are they dodging fixing it?  I know this may be far fetched but I'm losing confidence in what I'm seeing.  The community shouldn't have to figure out the LOD issue and the CEO of Asobo is looking dumbfounded as to what's causing it in the last live stream.  I hope I'm wrong.  

Their first couple of big patches broke some other things, because they tried to do too much too fast, and they didn't adequately test the patches before they went out.  They quite literally issued a mea culpa for this in the Q&A last week, and it sounded like they were gonna slow things down and be a little more deliberate going forward - hence this next update not looking like it's going to have another changelog a mile long.

The issue of resolving a bug has nothing to do with "not knowing how to fix them", and more to do with searching to try and uncover/reproduce the actual cause of the bug in the first place.  This is another thing they talked about directly in the Q&A last week.  If you issue a patch that didn't intentionally do anything to LODs, and then some users go "what have you done to the LODs!" but you can't reproduce the problem yourself, ithen it requires further investigation to figure out where the adverse code interaction is.  This is why Seb said it's helpful when users are able to isolate what might be causing problems, even though they don't expect users to do this for them.

As for the rest... there is no single person who built the Longitude, and they most certainly aren't "dodging" fixing it, lol.  Development with hundreds of people isn't like development with 10 people in a small office; they'll have teams working on every phase of the creation of the aircraft.  Maybe the Longitude's bugs are considered lower priority.  Maybe there are antecedent problems that need to be addressed first, in order to fix bugs more unique to that aircraft.  We don't know.

People need to chill out and give them some space to work.  Logging things for them to fix is great, but the doomsaying does nothing but heap stress on a team that I'd hazard to guess is probably already putting a lot of pressure on themselves.

Edited October 10, 20205 yr by Scottoest

23 minutes ago, Scottoest said:

Their first couple of big patches broke some other things, because they tried to do too much too fast, and they didn't adequately test the patches before they went out.  They quite literally issued a mea culpa for this in the Q&A last week, and it sounded like they were gonna slow things down and be a little more deliberate going forward - hence this next update not looking like it's going to have another changelog a mile long.

The issue of resolving a bug has nothing to do with "not knowing how to fix them", and more to do with searching to try and uncover/reproduce the actual cause of the bug in the first place.  This is another thing they talked about directly in the Q&A last week.  If you issue a patch that didn't intentionally do anything to LODs, and then some users go "what have you done to the LODs!" but you can't reproduce the problem yourself, ithen it requires further investigation to figure out where the adverse code interaction is.  This is why Seb said it's helpful when users are able to isolate what might be causing problems, even though they don't expect users to do this for them.

As for the rest... there is no single person who built the Longitude, and they most certainly aren't "dodging" fixing it, lol.  Development with hundreds of people isn't like development with 10 people in a small office; they'll have teams working on every phase of the creation of the aircraft.  Maybe the Longitude's bugs are considered lower priority.  Maybe there are antecedent problems that need to be addressed first, in order to fix bugs more unique to that aircraft.  We don't know.

People need to chill out and give them some space to work.  Logging things for them to fix is great, but the doomsaying does nothing but heap stress on a team that I'd hazard to guess is probably already putting a lot of pressure on themselves.

Warning: Your post is much too logical.