A2A CESSNA 172 Main, Starter and Avionic switches

[romair]

Hello Support

my A2A CESSNA 172 installation have problems.

1. Master Switch, Avionic Switch, Starter Switch and the all the buttons are not working. Rudder, Breaks and Flap are working perfect.

2. CESSNA 172 and PIPER Comanche both after a v few seconds Engine is starting automaticly and after a few second the power turns off and the prop stops.

3. Aileron Trim connected to a Rhino switch also not working.

I have a SAITEK Rhino yoke and throttle.

Could SAITEK Rhino cause such trouble ??

I hope for your response and thanks in advance.

Roger

[Nick - A2A]

Hello Roger,

Please can you let us know exactly which host simulator you're using the C172 Trainer in so we can verify if you have the latest version installed.

Thanks,
Nick

[romair]

Thanks Nick for replay

Its a FSX Sim and just changed from Thrustmaster stick to a RHINO stick.

regards Roger

[Nick - A2A]

Thanks Roger,

Sounds like it could be a control conflict of some sort, but to start with, please can you download the latest update for the C172 if you haven't already done this. It's available here.

Regards,
Nick

[romair]

Hello Nick

Thanks for support.

Those switches are still not working (death) by using the mouse.

I made already a fresh installation and I also used the updater A2A_Update_9_16_18.EXE .

I did that already before I contacted A2A experts for help.

I am a supporter for several simmers here in Switzerland with less english speaking experience and only by one person I have this problem. I never became involved in such problems
when installing A2A addons into FSX or P3D versions. My self I installed and operate A2A addons into FSX - P3D3.4 and today 4.4 and of course always successful.

I also tried to use SpadNext but still the same problem.

I hope you can provide additional help to overcome this problem.

regards Roger

[romair]

Hello Nick and possible other A2A experts

I still awaiting your help regarding my last post above!

Roger

[Nick - A2A]

Hello Roger,

Thanks for the added info. Please can you confirm if it's all the mouse click-spots in the virtual cockpit which aren't working?

If so, have you modified your viewpoint in the cockpit at all?

Thanks,
Nick

[romair]

Hello Nick

Yes , its in the virtual cockpit.

There is no 2 cockpit because of the use of Chaseplane.

regards Roger

[Nick - A2A]

Okay, thanks Roger.

It's possible the issue could be caused by shifting your viewpoint with Chaseplane. For example if you moved it back a bit, and it's slightly inside the 3-D geometry of the headrest, this would be one possible explanation for loss of click-spot functions.

Regards,
Nick

[romair]

Nick

Thanks a lot.

I will check this possible cause within today evening.

My client is on the other side of the country and I can connect him by TV this evening.

regards Roger

[Nick - A2A]

Thanks Roger - I'll keep an eye on this topic for any further updates from yourself.

Nick

[romair]

Hello Nick

Herewith the new investigation for the non working switches and buttons.

1. We stopped Chaseplane working after loading A2A-172 and we tried to use standard view withint the FSX.

2. If we want to use the standard cockpit view which have (Chaseplane) within the view name we can not operate those button and switches.

3. If we choose the FSX instruments view (not a chaseplane view and chaseplane is off) we can operate all buttons and switches as usual.

In order to startup engine and operate the buttons we changed the FSX instruments view to a standard cockpit view to able to see the runway and to fly.

Its 100.00 % known that the Chaseplane software causes this problem.

I think you or me should contact Chaseplane support to overcome this problem.
I do hope that you will contact them.

thanks and regards Roger

[Nick - A2A]

Hello Roger,

Thanks for testing and confirming the issue is linked to ChasePlane.

It's certainly possible to use this software with A2A aircraft such as the 172 with no problems and many customers do. it's probably just the way that it's set up in this particular case.

One simple thing to try is to move the viewpoint forwards (towards the instrument panel) to make that it isn't within the 3-D model of the seat.

Otherwise, if you can share some more info on exactly how ChasePlane is configured, we may be able to identify the issue. However, it may be a good idea for you to contact the ChasePlane developer for support.

Thanks,
Nick

[romair]

Hello Nick

Thanks for your answer.

We will try again but I can confirm you that we tried almost every possible window position including
towards the instrument panel.

Anyway I will contact Old Prop Solution staffs for this issue.

We should find a way to delete A2A 172 from the Chaseplane camera positions.

I will keep you informed as soon we get replay from them.

regards roger