Astrogator

I was talking about the usage of Gizmo in CRJ-200, which is obviously not needed as the aerosoft version has not included it. But I don't expect you to understand such a "complex" statement But you can discuss this further with me in a PM as it's not fair to hijack Ben's thread where he do hard work to find a solution for the problem, especially given the fact it's not proven his fault.

A dead soldier is a victim, not a hero. We should change our thinking and stop politicians let die human beings for their personal interests.

Was not my intend, I'm sure you do a great job and it speaks for yourself to publish a powerful tool like Gizmo for free. From my point of view it's also not clear where the problem is, it can be in Gizmo or XSquaw-Box or in X-Plane or.... you know what I mean. My only point is, the CRJ-200 does not need mandatory the Gizmo plugin, it's a decision made by the vendor.

Bit late in answering, but I had the same problem. You can limit the movement when you adapt the "curves" within FaceTrackNoIR. But you need then to save a FaceTrackNOR config file for each plane you use.

You may be right, all I can say: With the CRJ-200 purchased from aerosoft.com you don't have this problems at all as they do not make use of the Gizmo plugin - and the plane is flying too.

after getting a message of Jim, of the developer team what I have to consider as heavy threatening, I decided to delete my post as it was claimed in this PM. Sorry, that I argued you do not act professional. I will not complain anymore and hope I'm now the customer you want to have with me.... Your servant a totally happy and satisfied customer.

Hmm, I'm disappointed and not just a little. Sure, it was my fault to buy the DC-3 without having a look in the support forum. But as professional software developer, it's not my understanding of this job to sell software with well known annoying faults like the compass without any remark or hint on the product page itself. After installation of the DC-3, I really fast discovered this thread, the questions and the answers from developer side. THAT was luck, then in the beginning I said to myself, well it will get a fix, let's buy the Saab-340 instead and have fun until the DC-3 works. But this thread and your answers Goran/Cameron destroyed your most important capital: your credibilty. From my point of view, you are overloaded with work and you are not familiar with standart procedures for software developement and quality assurance. Well no problem so far, but to say we don't give a date for a fix is slapping your customer direct into their face. There's really no need to discuss the quality of the DC-3, its behavior or its look as long it's not useable for its purpose -> long distance flights. At the end, with your advertising you won me as customer, with your DC-3 compass story you have unsettled me and with your answers about a fix date you lost your credibilty. Goran no matter if you bring the fix or if you don't do it, I won't buy anything more from you as it seems to be a high risk. The risk to buy a piece of buggy software, the risk, you are not in the mood or whatever to deliver a fix or to commit yourself to a date for a fix. The forum is full with bugs for each planes where you still not have answered. I found a thread, Goran answered: "I will check it today and write back" - that was in August. This brings miles between you and my understanding of the behavior of an IT professional. Sorry to say, you have the potential to make great planes - but only the potential. A very disappointed customer, and software developer itself in healthcare environment where your understanding of quality and intercourse with customers literally kill people. Regards, Marcel