He said at 1000 RPM, if he forgets to put the brake on during his checklist, it will start to roll right away. Not fast but it will start moving forward for sure. 

 

 

And that's exactly how the A2A 172 behaves for me (at Orbx airstrips no less), so it's not a global problem that all users experience. I sure hope you guys get your taxiing problems sorted out with the update.

That's nothing compared to the problems with the FBW system, that will certainly take a LOT of time to track and correct :-/, and they had a huge team of beta testers, including 777 pilots ( or at least FOs)...

 

Which 777 are we talking about here?

 

Sent from my ME172V using Tapatalk 2

 

 

I respect your point of view TJ, but you don't need to point out that developers can't detect every issue. :lol:  No kidding, of course I know that!  But some of these problems people are seeing are not some obscure error like the one you cited with the 777, they are things that really seem like they should have been caught, like with Orbx, and I simply don't see any excuse to be made.   Thumbs up to them for working hard to making things right, but I'm not as inclined as you are to give developers, be it A2A or anybody else, a pass on having a rocky release in the first place. As a generalized comment,  it happens all too often these days, I'm sure I'm not the only one getting sick of it, and they should do better, that's all.

 

True, but no one is forcing you to buy it as soon as it is released.  777 has bugs, PFPX has bugs, 172 has bugs.  The FW190D project that I am beta testing on will no doubt have some bugs after release.  It is inevitable. 

 

I try not to buy the pretty looking Alabeo/Carenado releases until they go to the F1 wrapper.  By then they usually have most of the big bugs worked out, and I will have the F1's 30 day return policy to boot.   Waiting a few weeks after release isn't a bad idea if you want to avoid bugs. 

 

LOL look at the first customers of the real Boeing 787.  The 787 will no doubt be a fine plane, but it certainly has it's fair share of release 'bugs'. 

 

If everyone had the same hardware setup, the same FS configuration, the same collection of addons, it would be a lot simple, but that is the beauty of FSX, there is virtually an unlimited combination of hardware/FS setups that can be tailored for each user.

 

The 172 works fine for a lot of people too.  The people who have problems tend to be vocal, as they should be.  Being vocal, pointing out bugs is expected, as long it is done in a respectful way .  The people who are satisfied tend to be less vocal probably because they are too busy flying it lol.   

Bugs they all have. A support team that respect the costumers and work on fixing them before announcing and releasing another product, that's what makes the difference between them!

Some have more bugs, or bigger bugs, than others, so I'm not sure we can so easily brush it off the shoulder with the well they ALL have bugs, even the t7 rationale.  But whatever, I hope they get the problems fixed, and they're on it, so I guess that's whats worth concentrating on now. 

I mean...A2A could have anticipated the issues with EZCA users, sheesh. Luckily the problems were solved by the community.

What is annoying is that the flight models "feels" broken for many users. The excuse is that the joysticks we use are not a close enough match to a real Cessna yoke. So we have pages of explanation about how they are developing a new system.

 

Since the vast majority of us dont have a yoke that has the correct feel, They could simple say, they got it wrong, we need to fix it so the aircraft feels correct with out flimsy, zero feedback plastic joysticks. It's basically a user fault that they have to compensate for!

 

If we dare mention any problems on their forums, the world falls apart. I don't think I will post their anymore, after what happened to some others. But it is ironic, the flight models perfect, but we are also going to fix it...!

What is annoying is that the flight models "feels" broken for many users. The excuse is that the joysticks we use are not a close enough match to a real Cessna yoke. So we have pages of explanation about how they are developing a new system.

 

Since the vast majority of us dont have a yoke that has the correct feel, They could simple say, they got it wrong, we need to fix it so the aircraft feels correct with out flimsy, zero feedback plastic joysticks. It's basically a user fault that they have to compensate for!

 

If we dare mention any problems on their forums, the world falls apart. I don't think I will post their anymore, after what happened to some others. But it is ironic, the flight models perfect, but we are also going to fix it...!

 

Flight model is not broken... at least with my setup I am getting damn near the real thing.  Only problem I have had is once in awhile the brakes get a little sticky when differential braking The problem is in our non feed back controls we can't FEEL how hard to pull. Maybe I am lucky but mine feels pretty spot on to me with my rubber band modified saitek yoke.  

 

Just curious do you have late model 172 time?  I only have a tiny bit myself since I had to take a break from lessons but this is the closest I have felt to the real thing..  

Flight model is not broken... at least with my setup I am getting damn near the real thing.  Only problem I have had is once in awhile the brakes get a little sticky when differential braking The problem is in our non feed back controls we can't FEEL how hard to pull. Maybe I am lucky but mine feels pretty spot on to me with my rubber band modified saitek yoke.  

 

Just curious do you have late model 172 time?  I only have a tiny bit myself since I had to take a break from lessons but this is the closest I have felt to the real thing..  

I have no opinion whether the flight model is broken. It just feels awkward when the tiniest of movements on the elevator INSTANTLY makes the ac point the nose towards the sky.  At the same time, the ac I fly IRL is so sensitive on the trim that I can't move it with my hand, I have to just slightly tap it with one finger to get the desired trim change!

I have no opinion whether the flight model is broken. It just feels awkward when the tiniest of movements on the elevator INSTANTLY makes the ac point the nose towards the sky.  At the same time, the ac I fly IRL is so sensitive on the trim that I can't move it with my hand, I have to just slightly tap it with one finger to get the desired trim change!

 

 

I wonder if only some people are getting the very high sensitivity. My experience with this plane is nothing like that.Do you by any chance use OPUS? and if you do check the bump aircraft settings.   I had some odd behavior with this plane using opus.  

Anyone use Saitek FIP panel and get the altimeter knob on the Cessna to correspond to turning it on the FIP? 

 

Thanks

 

Mike

And that's exactly how the A2A 172 behaves for me (at Orbx airstrips no less), so it's not a global problem that all users experience. I sure hope you guys get your taxiing problems sorted out with the update.

 +1. I have no Orbx add-on airfields, but my A2A 172 starts rolling very easily at the Orbx airfields in their Scotland scenery and in their North American scenery, so the Orbx "problem" doesn't seem to be as fundamental to the C172 as some of the above posts seem to be suggesting. I do sympathise with those who are having the problem, but I can't see any reason to heap blame on A2A for not spotting it before release.

 

Dugald

I wonder if only some people are getting the very high sensitivity. My experience with this plane is nothing like that.Do you by any chance use OPUS? and if you do check the bump aircraft settings.   I had some odd behavior with this plane using opus.  

Mike, while I do have Opus I don't use it since I prefer FS Global Real Weather.  As long as I look straight forward I can manage if I'm very gentle on the yoke but once I look to the side (I have TrackIR) in a turn I usually lose all my bearings. Tried a night landing in pretty bad weather at Diamond Point (ORBX) last night and I went from stall warning to overspeed to stall warning allt the time in just a few seconds...  Felt like I was using the sim at 4x sim rate - that was intense!

I do sympathise with those who are having the problem, but I can't see any reason to heap blame on A2A for not spotting it before release.

 

Yeah, as I mentioned before somewhere: most people don't experience that problem (or the A2A forums would be much, much, much busier at this time), so if thousands of people don't experience that problem, how big is the chance that a few beta testers experience it in order to catch the problem in time?

 

I'd say it's very unlikely, and that's why any kind of software will always show problems on wide release, especially when a multitude of different hardware comes into play that can't possibly be covered by a beta team short of a big publisher's QA department, which of course is impossible to have for a small FSX add-on company.

Yeah, as I mentioned before somewhere: most people don't experience that problem (or the A2A forums would be much, much, much busier at this time), so if thousands of people don't experience that problem, how big is the chance that a few beta testers experience it in order to catch the problem in time?

 

It's one of the reasons why the current trend of selecting beta testers from a select group of 'insiders' tends to be a really bad idea. You end up with a majority of your testers being the ones that are most likely to have perfect setups and 'most realistic' hardware, rather than people likely to have the more varied hardware and setups that may illustrate weirdness.