Well guys....... I've literally never been away from the A2A forum for the last two days, and here's my observation;

 

We are seeing a cycle between the taking on board of the definitive bugs that some are seeing, and some great work to fix them (eg.... the clickspots, Scott and Lewis), followed by some complete denial of other issues. For example comments that some issues "apply to all aircraft in FSX" where that is definitely not the case...... and incorrect apportionment of blame on the 'stuck brakes' issue as a problem linked to Hardware (Michael at A2A is adamant this is a hardwre issue, despite me running some tests at the request of Lewis A2A and clearly reporting back that the exact issue occurs with no hardware toe brakes assigned, or even plugged in.

 

On that note, Lewis A2A:   You asked me yesterday to undertake those tests with the brakes and the hardware unplugged;  I did so and reported back a lengthy report on the A2A forum, which you've yet to acknowledge...... I will happily do any tests or give any help I can offer, as I ultimately love this product and want to see it in the right shape ......... but it's frustrating to spend time doing a test at the request of a developer, to then not have my results acknowledged or apparantly seen....  

 

If the results had been seen - Michael would not be posting tonight suggesting that the 'stuck brakes' problem is likely down to calibration and null zone settings for hardware.      I will say again, the brakes stick, and one cannot pull away from non-paved areas without using full power;   even when no hardware is assigned to brakes, nor even plugged in.

 

Elevator:   As J van E said earlier, I too am having to not set the trim to the "T/O" marker, in order to get a realistic climb experience. This isn't right.   I have flown 172SP models (albeit not the 'R') and these planes are basic trainers, they do not pitch up on take-off and threaten an immediate and aggresive bleeding of speed and stall     - they just don't!

 

Have you guys read and considered Alexander Metzger's comments about the A2A 172, and the CoG factors? ..... Alex is a legend in the FDE world to the same level that Rob Young is, so the opportunity to get his input should be taken.

 

Today, I find myself obviously very happy that the Clickspot problem has been resolved, but frustrated in equal measure at some (not unanimous) of the denial, and incorrect diagnoses going on on the A2A forum.         The T/O and landing regimes in the FDE just are not right yet ........  and the 'brakes stuck on' is a major issue (on a par with the clickspots) that cannot be played down or blamed on hardware    - especially where tests have shown it to occur where no hardware is used.

 

Dave,

 

just to say that you raised your mark on my ranking of posters here at AVSIM some 500% with this post of your's.

 

I really need to see some of the more then evident problems with the C172 being ackonwledged by A2A. I am also becoming tired of reading nonsense about this & that being exactly as supposed, just like the real think! C'mon guys!!!!

 

There are other problems with the C172, namely with the turn coordinator, where the ball physics parameters have most certainly been edited causing the more sluggish movements and an abnormal "asking for" rudder during corrdinated turns that will always end in the need to cross controls! Yet, they have successfully made the instrument compatible with very precise std rate turns, and this was something I had long asked for and is a very positive aspect about this model for those who need to use it for IFR training. Alec has also pointed this out in one of the threads where he describes some of the problems he found in the C172.

 

A2A is, together with PMDG, RealAir and Bernt Stolle creations, a reference for me in terms of FSX. I am sure they'll solve this problems, but I need to see them acknowledging them too - everyone, naturally even the best, are entitled to make mistakes... what is important is that we're able to recognize and take action to correct it!

J.C., don't mean to sound rude, but I have an impression that you did not read my response above your post, esp. the last paragraph. It may be the language barrier, English it not my native language, so if I ever post something that is hard to understand, let me know

 

In the case of the issue that Dave is complaining about, it has been acknowledged right when he reported it and is still under investigation. It's just a misunderstanding.

The ball physics issue has also been acknowledged and explained on this forum when it was first reported.

 

By posting the videos, Scott is trying to make sure that we are all on the same page. Without that, we can't talk about what is a bug, and what works as intended. Especially in such subjective and hardware dependent area like FM.

First, I have not flown this airplane...hence my questions in another thread.  However, I can say in the airplane that I fly, if you set the trim to the T/O mark it flies all by itself on takeoff and requires considerable forward pressure on the yoke to keep the nose down.

 

I'm flying this weekend....I'll try and get a video.

I agree , on the real world C172 I fly (flight school) I find myself trimming down quickly on climb out for 70kFlaps stage 1. I often wondered if the mark on trim wheel was "off" but never thought to ask an instructor. Maybe I will next day.

J.C., don't mean to sound rude, but I have an impression that you did not read my response above your post, esp. the last paragraph. It may be the language barrier, English it not my native language, so if I ever post something that is hard to understand, let me know

 

In the case of the issue that Dave is complaining about, it has been acknowledged right when he reported it and is still under investigation. It's just a misunderstanding.

The ball physics issue has also been acknowledged and explained on this forum when it was first reported.

 

By posting the videos, Scott is trying to make sure that we are all on the same page. Without that, we can't talk about what is a bug, and what works as intended. Especially in such subjective and hardware dependent area like FM.

 

Well, as far as the language barrier goes, I can't really be better than you - I am portuguese :-) and my english comes from what I learned at the highschool. 30 yrs ago :-) 

 

The problem was rather due to another problem, and one that I sometimes have... Not reading all of it... Sorry :-/

 

I didn't take the time to read all of the messages here and at A2A's forum, and that's certainly my fault ....

 

Anyway, I bought the C172 for at least three good reasons:

 

1) Because I have A2A in the highest standards, since I bought your first add-on, for fs9, around 2005, after having also played and enjoyed BoB quite a lot!

 

2) Because I am sure it'll get fixed - all of the problems with this C172

 

3) Because I acknowledge the other important steps you gave with this simulation in terms of making it didactic as well as recreational.

 

Thank you for stepping in and make me look back at what I did not read ;-)

You're right, I apologize for the jab.

 

I just have to be a contrarian and disagree for disagreements sake hence my previous post.

 

But I wonder if you wouldn't mind trying something with your Saitek pedals. I too was experiencing issues with sticking brakes and followed Mike's post about null zones and sensitivity level. I set them as per his screen shot. I then proceeded to hit Calibrate, select my rudder pedals, hit properties, hit the settings tab, hit Calibrate, and proceed through the Windows Calibration wizard. After going through that, my sticky brakes are gone.

 

No probs :lol:

 

I do have the same settings as those suggested by A2A Michael, and did calibrate outside of FSX (Windows level) at that time, but I'll run the calibration again within FSX, just on the off-chance it fixes the issue....  Thanks  :good:

Over 24 hours later is immediate to you?   :wink:

 

No and I apologised for this. Please be aware we are dealing with lots of customers so please bare with us we are a small team so its taking time to get through the mass of forum posts good and bad. We cannot acknowledge everything but our forums are open to all to see for the reason that we like to a transparent developer in this regard. Everything as 'some1' has noted is being read and noted down on a bug tracker for further investigation and to be fair to 'some1' is did post that is will not fix issues for all but will help some.

 

All of the fixes so far posted have helped users, I am sorry they have not yet helped you on all cases but nonetheless they have helped others.

 

thanks,

Lewis - A2A

 

 

I don't think there is any problem with the pricing. 

 

I was expecting it to be more expensive.

But I wonder if you wouldn't mind trying something with your Saitek pedals. I too was experiencing issues with sticking brakes and followed Mike's post about null zones and sensitivity level. I set them as per his screen shot. I then proceeded to hit Calibrate, select my rudder pedals, hit properties, hit the settings tab, hit Calibrate, and proceed through the Windows Calibration wizard. After going through that, my sticky brakes are gone.

 

Hey,

 

Ok just re-calibrated all axis on my pedals in FSX, and confirmed that all settings are as suggested in the A2A forum.

 

I went to Orbx OG39 (Longview Ranch);-

 

• On first loading the aircraft, getting it rolling was fine; taking about 40% power to start smoothly rolling which is very realistic from my experience.
• As soon as I braked at all, then stopped, when I came to pull off it took 100% power + 3 seconds to begin rolling (at a snails pace), although speed does slowly build up.
• Toggling the parking brake on then back off (and then not touching the brakes) returned normal ability to get rolling, without needing 100% power + 3 secs.
• But as soon as the brakes are used, the 'stuck' issue will exhibit again when trying to pull off.

 

I then unassigned the toe brakes and parking brake in FSX Controls menu and pulled the USB plug out from the PC..... I repeated the above and exactly the same issues applied, when using keys for the brakes and parking brake.

 

So the issue is very real, even after the recommended hardware settings and calibration. 

 

A2A Lewis & "Some 1" - I'm not here to crucify you in any way or display overly high expectations from you.  I appreciate what you guys are doing to get the aircraft fixed into an acceptable state.     But some of the language on the A2A forum sometimes reads a bit dismissive to some people's reports........  When that happens, and people have real problems (such as this one not being hardware related), they are going to twist and shout, :lol: because what you are telling them, defies what they are seeing on their screen... :smile: ... and because some of the language makes it look like avenues are not being explored;  a la   Ok, the stuck brakes was Saitek Pedals related, that's that solved..... next!

 

Good luck with the rest of the problem solving and thanks for your efforts to resolve this  -  there has to be a reason why out of the 32 aircraft I currently have installed in my FSX, this one is the only one to be exhibiting a 'stuck brakes' effect on non-paved surfaces...........  I'm sure you'll get to the bottom of it.

If you keep telling them how you have other planes that don't do it and the 172 does, hopefully eventually they will realize that you have a problem.  Keep at it! If you first don't succeed, try and try again as I always say.

 

:rolleyes:

Is that the best you can do Mol? .....common or garden sarcasm again huh?    :wink:   ..... haven't you put me in your 'Ignore List' yet? .... that's what it's there for.... Top right, under Your Profile   :wink:
 
 
Ok,
 
I just mentioned something on the A2A forum, in reponse to another guy who was trying to help......  it is something that 100% demonstrates that the 'stuck brakes' issue that I (and others) have is not a stuck brakes problem that is hardware related ........(that others perhaps had).
 
Here we go ... (Drum Roll) :-
 

When I fly on paved runways, I do not have any 'stuck brakes' problem at all.    When I pull off it always just takes 40% power (realistic), even when I have been using the brakes.

 
So there we are... if the problem can not happen in any scenario, then it's not the hardware.   My hardware config does not change between paved runways and non-paved ................ but perhaps the C172 does ?  
 
I am also flying all of these tests in Orbx sceneries, almost all non-paved.
 
Does anyone else have Orbx OG39? (Longview).......... It would be great if someone else could start a flight there, start the engines, pull off (should be normal), press the brakes (foot brakes, not parking brake) and come to a stop ............. then try to pull off again, and see if you need 100% power and considerable time....
 
If I was flying from paved runways all the time, I wouldn't be talking about this issue either. :smile:

A2A personally came here (2 members) and told you they realize your problem may not be hardware related and continue to examine your feedback and working to fix the issue.  Also, I saw a post by Scott last night that the friction is being readjusted because they found one of the trainers they were using for flight testing purposes had sticking brakes requiring more power than normal to taxi.

 

I just don't get why you keep asserting that they are ignoring you and trying to cover up your problem when they personally acknowledged you..

 

For what it's worth, I have the same off-apron dirt/grass "sticky" issue too. I saw it was being reported, I saw A2A tried some solutions and mentioned they are working on it.  For me that's enough, but to each their own I guess. I am willing to believe they will do what they say.

Hey guys,

 

For anyone who has had any disappearing clickspots (even just rarely) A2A have released the Hotfix publically now, so go and grab it :smile:

 

This completely eradicated the issue for me and many others, so great result. :cool:

 

http://a2asimulations.com/forum/viewtopic.php?f=108&t=35927

 

:smile:

Just wanted to say that I have every Accu-sim aircraft A2A has sold, including the C172. I'm not having any problems (sorry for those that are) and am loving the plane. I have hundreds of hours in this plane in the RW. This version is incredibly well done, I think, and I am pleased to know that the team continues to work on bringing further modeling of realistic behavior into the Accu-sim engine in future updates. My only reason for writing is to call attention to what is without a doubt the absolute best customer service I've ever seen for an FSX product (and, basically, any product) as evidenced in this thread. Not only is the team responding in an incredibly timely fashion to every issue (with fixes coming fast and furious), but they are doing so with a patience and what seems a genuine goodwill I find almost unbelievable, particularly when the reporting of the issues by end users often falls very short of the exhibiting the same good will (frankly, the FSX community can be a demanding a fickle bunch).

 

Well done, A2A!

It's true. Their support has been excellent so far.

 

I'm anxious to see what they will come up with in the upcoming patch. Hopefully it will fix many of these issues we're all reporting.

Here's a very short video I made.... Now, because certain people come here to contribute nothing other than to tell others what they can and cannot post, I will make it clear that I know that A2A are on to the problem, and as I have said 6 times in this thread, I appreciate their hard work, own all of their products and am a big supporter.

 

I am posting this vid of the 'friction' problem so that others can assess it and decide whether it is, or is not the same bug that they are having (as it has been established that there may be different causes for a friction bug; eg hardware and non-hardware).

 

Here we go;

 

This is at Orbx OG39

 

http://youtu.be/DAcZIERjJXk

 

So as you can see, it is requiring full power to get moving.

 

This is the only remaining issue I have with this aircraft, and when it's resolved, it'll be the best GA single ever released for FS.    Honestly, if you think I am bashing A2A, I have actually uninstalled a whole pack of piston singles from FSX today because they just have no place any more, as 'flying textures', when this wonderful aircraft of such substance, is fully fixed up.