Aircraft Flaps Control On Client

[Opus Software 84]

I hope you can see and understand the dilemma here.

 

The client software will be sending two simultaneous controls to the sim ...

 

The FLAPS HANDLE INDEX control / indication (being always zero) will always be commanding the sim to move the flaps to the fully up position.

 

At the same time ...

 

The Trailing Edge Left/Right signals will be telling the sim to move the flaps to a different position.

 

What will the sim code do ?

 

ALL other aircraft reflect the commanded flap position (0 to 100% = 0 to 255 = Fully Up to Fully Down) using the 'All Aircraft' FLAPS HANDLE INDEX control. I think that really does make it a 'standard' signal, as standard as you are likely to get in FSX.

 

My question was quite simple. Can A2A maintain this standard flap position signal? Using it will NOT limit the flexibility in the aircraft sim although we would still have to relay the Trailing Edge data to allow asymmetric flap deployment. I would have thought updating this signal would require just a couple of line of code since the sim must know what the commanded flap position should be, and what it currently is.

 

Yes, this signal does change as the flaps move, it is not simply reflecting the flap control handle.

 

It always reflects what the current flap position is even whist the flaps are moving.

 

I cannot confirm this is so for all aircraft. Some may use it to reflect nothing more than the control (flap handle). We have had to factor this in to our ButtKicker control though as we have generally found this signal to reflect the actual flap movement. I am only going on memory, I would have to conduct further tests to say for certain.

 

Stephen :smile:

[barryoo 0]

Stephen,

Are you in direct communication with Michael Krawczyk? if so - I should not need to copy your last two posts to the A2A site.

[Opus Software 84]

I'm not, but as I said above I don't mind adding these parameters but before changing both program's and the comms software I would like to know its not going to cause any problems. Many people are using the current flap signal and control with no problems so I'm just a little concerned there might be a conflict on their systems.

 

I would be willing to prepare a special beta for you to try, of course I will do all I can to see that your system works as expected.

 

I am away (flying on a trip to France) for the weekend and busy for the first half of next week but after that I will prepare something for you to try (sending all flap parameters and setting them in the client). Not totally sure what the sim will do, I may even have to treat the A2A as a special case but only if this data can be identified as being handled differently.

 

Seems like a lot of fuss really to just reflect the current flap status (position) in the above variable.

 

I don't even know A2A will be able to answer my question, we may just have to try it and perhaps detect the non-functioning Flap Handle Index control.

 

Stephen :-)

[barryoo 0]

Quote:

If A2A are unwilling to add this variable could you ask them to confirm that they will treat the Trailing Edge Left/Right Percent signals as a control, and not simply as there output signal to show what the flap status is currently. I don't want to implement these changes only to find they are pointless. I will implement it if needed and leave it to you to test the results, but would prefer confirmation from A2A.

 

 

The Trailing Edge Left/Right variables can be used only to read current flaps position. To set them from the client computer, use one of the flaps events (KEY_FLAPS_SET, KEY_AXIS_FLAPS_SET, KEY_FLAPS_INCR etc.).

 

_________________

Michael Krawczyk

[Opus Software 84]

It would be far simpler if you could use the FLAPS HANDLE INDEX control (0 = flaps fully Up, 255 = flaps fully down) like every single other aircraft sim then the controls would not be aircraft specific.

 

You should appreciate many Live View system employ dummy aircraft on the client and setting the actual flap position works with all such aircraft. The only aircraft this standard 'All Aircraft' control does (or may not) not work with is the A2A C172.

 

Stephen

Could you please try loading a standard C172 on the server and your A2A C172 on the client. Then see if the FLAPS HANDLE INDEX control will be accepted by the sim (after all it is operating in FROZEN mode so with a bit of luck the A2A software is completely dormant). If this works there may be a solution.

 

The solution being ... if A2A find it too difficult to update the FLAPS HANDLE INDEX variable then I will maintain it for them.

 

Monitoring ALL the possible aircraft cockpit control events is just ludicrous.

 

Stephen :smile:

[barryoo 0]

Quote:

I hope you can see and understand the dilemma here.

The client software will be sending two simultaneous controls to the sim ...

The FLAPS HANDLE INDEX control / indication (being always zero) will always be commanding the sim to move the flaps to the fully up position.

 

 

As I wrote previously, the Trailing Edge Left/Right variables can be used only to read current flaps position in A2A aircraft. To set them from the client computer, use one of the flaps events (KEY_FLAPS_SET, KEY_AXIS_FLAPS_SET, KEY_FLAPS_INCR etc.).

 

When two flaps related A:variables are set at the same time using simConnect, the result may be unpredictable. We did such tests when we develped this system about six years ago, so I don't remember the details, but the variables will fight each other and one of those will take precedence. That's the reason why we don't use the other variable.

 

_________________

Michael Krawczyk

[barryoo 0]

Quote:

 

Could you please try loading a standard C172 on the server and your A2A C172 on the client. Then see if the FLAPS HANDLE INDEX control will be accepted by the sim (after all it is operating in FROZEN mode so with a bit of luck the A2A software is completely dormant). If this works there may be a solution.

 

The solution being ... if A2A find it too difficult to update the FLAPS HANDLE INDEX variable then I will maintain it for them.

------------------------------

Stephen,

Yesterday, will beating myself to death trying to change variables to get FSXserver to save .CAM files to FSXclient, I destroyed my Opus programs. Relax and enjoy your flight to France or where-ever. I will have an answer when you return.

 

Thanks for your help.

[Opus Software 84]

OK thanks. I do have occasional Internet connection so if you need assistance ... there might be some delay in the response though. We made it to Arras via Abbeville, low level flight all the way in poor weather, return Sunday. Good luck setting those sharing and permissions. Step through the GS Guide instructions carefully.

 

Stephen :-)

[barryoo 0]

Finally back on-line with client and server.

 

Stephens Quote:

 

Could you please try loading a standard C172 on the server and your A2A C172 on the client. Then see if the FLAPS HANDLE INDEX control will be accepted by the sim (after all it is operating in FROZEN mode so with a bit of luck the A2A software is completely dormant). If this works there may be a solution.

 

My Results:

 

When the 172SP is loaded on the server and the Opus server Is running, with colored green OpusFSX client connections, the servers 172SP flaps go up and down as would be expected. When the 172SP is loaded on the client the servers flap commands are received by the client and the flaps, although slightly delayed, go up and down to the servers flap position. Everything works as would be expected.

 

During the same session or during a clean FSX start-up substituting the A2A for the 172SP on the client the results follow:

 

When the 172SP is loaded on the server and the Opus server Is running, with colored green OpusFSX client connections, the servers 172SP flaps go up and down as would be expected. When the A2A c172 is loaded on the client the servers flap control lever commands are not received by the A2A. The A2A flaps do not move.

 

The A2A c172 offers some fairly realistic aircraft fuselage, wing and stabilizer movements from the CLIENTS spot view while running the A2A c172 or the 172SP on the server. The aircraft body will tip down when breaks are applied, the tail of the aircraft vibrates and bounces during taxi ( perhaps too much but usable). One problem I do see is that when the clients A2A is stopped on a taxiway, ramp, etc. it will tend to roll backwards about 6 feet when the servers aircraft flap lever is pushed.

[Opus Software 84]

Many thanks.

 

Unfortunately, I cannot help any more with the A2A C172 aircraft since it seems the aircraft is not responding to the FLAPS HANDLE INDEX control as it should. If it had I would have generated this signal on the client and relayed it to control the flaps correctly. But it now appear any flap control is going to be impossible with this aircraft.

 

Therefore, its a case of either A2A changes their software to use the FLAPS HANDLE INDEX 'All Aircraft' variable and control like every other aircraft sim does or you will have to fly a different 172 if you want the flaps on the client system to be controlled.

 

Sorry I couldn't help any more but its pointless using the other signals which would result in unpredictable results and ruin every single other aircraft sim. These 'All Aircraft' signal are meant to be accommodated by ALL aircraft simulations, which they are of course apart from it seems the A2A aircraft.

 

Nothing more I can do.

 

Stephen :smile:

[barryoo 0]

Copied from A2A Forum:

 

I beat a similar topic to death with flaps and lights not working on the A2A c172 using a server and client computer system with OpusFSX. So for the thousands of FSX users who run more than one computer with OpusFSX or WidevieW I have further bad news for you.

 

With a new FSX build installing all updates, SP1 and SP2 and additionally, as an addon, the latest version of WidevieW. Guess what: The A2A c172 flaps and lights do not work. Surprise, surprise!

 

It's disturbing to find the A2A programmers so uninterested in correcting this deficiency.

[Opus Software 84]

I think I've already covered what they have to do, like ALL other aircraft developers, to get the flap status being relayed and controlled on the client systems.

 

Stephen :-)