FSX & Magenta ?? [Archive]

brianwilliamson

11-19-2007, 08:25 PM

To all who are using FSX and Preferably the Airbus FCU software, with the Magenta software, perhaps we could list some of the problems that have been encountered and any fixes.
I am testing at the moment with FSX using the FSX A321 aircraft and the Magenta FCU/MCDU/ and one Glass screen only to try and limit the input/output loads.
I am getting some varied results on the ILS approaches. Sometimes it will intercept the centre line OK, but will not intercept the Slope. These are the little annoyances that are hard to locate, but I suspect it is the FCU causing the trouble. Perhaps others can comment on some of their problems, especially with regard to ILS approaches.
..............Brian W.

Mario Görs

12-13-2007, 05:42 AM

Hello Brian :)

Here is one !

Having Issues with the ILS ,too.

> I am getting some varied results on the ILS approaches

Same here - mostly at around 1800 feet in Glide the Plane
begins to try center the ILS what results in a ongoing
left / right swinging to reach ( - whatever that center ).
This on get`s harder as neerer the Plane reaches the Runway
and so mostly the Plane is not reaching the centerline from the runway.

As a long time PM user i know that Problem from some older Builds over all that Years so i hope PM is reading that and can fix that with coming Builds. I think they have a lot Supportmail about that - shurly.

( Hopefully there are new Builds in near future )

> it is the FCU causing the trouble

I think you right Brian preety shure it is the FCU

Same thing is in Boeing Software , too here the MCP
I think it`s a bit better there but it is there allso.

Tried to resolve that with some tweakings in the Aircraft.cfg
files from my used Planes but the result is not mutch better.
Has to do with the PM software - pretty shure :-|

So hoping for new Builds that solves those Gimmicks..........

regards
Mario Görs ;)

JonathanRichardson

12-14-2007, 04:43 AM

HI

Are you sure this is not system specific and set-up issues? We ran many tests and whole e-mail exchanges with the FCU ILS intercept problems, and two of us cross checked this and found it was to do with FSX aircraft / panel set-ups. I thought the issue was closed? I did not hear anything more.

On the Boeing MCP front, it must be a network or system set-up problem, or even flight model, I perform hundreds of Autolands all the time without any such issues. I suggest really looking hard at your system set-up - possibly even moving the MCP. It only takes the resources of one computer to be over loaded and leaving too little time for the network and this is exactly the stage of flight where you will really notice timing / communication errors because the speed of exchange has to be quick. So, the client that the MCP is on or if the MCP is on the server perhaps MSFS is simply using up too many resources. All computer systems are set-up differently, just because you think it should be fast enough in my experience does not always mean it is. It is normally one little thing that causes problems. Also, typical Autoland problems are caused by the YD setting / gain in the airfiles. When the MCP AP is engaged, the FS YD is set to on, if the YD gain (or whatever that setting is) is set badly or incorrectly in the airfile, it can cause problems with a/c control, especially on the Autoland. So, there are many things to be considered, but the MCP software "in pure form" is working correctly for Autolands.

Regards
Jonathan Richardson

Hello Brian :)

Here is one !

Having Issues with the ILS ,too.

> I am getting some varied results on the ILS approaches

Same here - mostly at around 1800 feet in Glide the Plane
begins to try center the ILS what results in a ongoing
left / right swinging to reach ( - whatever that center ).
This on get`s harder as neerer the Plane reaches the Runway
and so mostly the Plane is not reaching the centerline from the runway.

As a long time PM user i know that Problem from some older Builds over all that Years so i hope PM is reading that and can fix that with coming Builds. I think they have a lot Supportmail about that - shurly.

( Hopefully there are new Builds in near future )

> it is the FCU causing the trouble

I think you right Brian preety shure it is the FCU

Same thing is in Boeing Software , too here the MCP
I think it`s a bit better there but it is there allso.

Tried to resolve that with some tweakings in the Aircraft.cfg
files from my used Planes but the result is not mutch better.
Has to do with the PM software - pretty shure :-|

So hoping for new Builds that solves those Gimmicks..........

regards
Mario Görs ;)

Mario Görs

12-14-2007, 05:20 AM

Hello Jonathan :D

Thanks for that reply

> Are you sure this is not system specific and set-up issues?

Sorry , but can you ever been shure with PC`s and that mutch set ups you need to conect and set Software with FS Sim over a network ??
I wount tell you how many Tousends off hours i spent with that one - and i am shure you know what i speaking from.................but this seems the price for that kind off hobby !!?

Bay the way just to say: My PM Rig is with XP my FSX Rig is with Vista 32 is there anything wrong ??
My conections looks god; PM AP says OK in FSX .
Have ASX over network with simconnect says OK at beginning from FSX - so should look good ?..or !!

What do you mean with YD ?

I assume you mean Yaw Damper !!

What should they set for ........ are these the right settings :

yaw_damper_gain=1.000000

Thanks for that tipp - didn`t know that it is that one important :idea:

You never learn enough..........

regards
Mario Görs ;)

Mario Görs

12-14-2007, 12:24 PM

Hello :(

I give up............before my nervs kill my brain :mad:

Had another flight with the new Posky 747 and ( Boeing Sowftware )

had a superbe flight but at Glide the same jugeling left /right about 1800 feet begins and ended with a not straight coming trough the runway.

So what is a good flight for if you can`t perform a normal landing.......

And now i am shure it is the software.............:-x

I give up before getting crazy - hope you guys can look in the Software
and bring new Builds , think it only have to do with AP`s both
Boeing and Airbus.

regards
Mario Görs :(

JonathanRichardson

12-14-2007, 02:59 PM

>had a superbe flight but at Glide the same jugeling left /right about 1800 feet begins and ended with a not straight coming trough the runway.

Hi

It could be the YD gain, it could be the speed is too slow of your approach, and you are getting into the drag curve - I presume you have thoroughly checked your weight and balance and also you have the correct Netweight= in your CDU type txt folder for a/c type and you have correct payload entered - these are critical.

>So what is a good flight for if you can`t perform a normal landing.......

Fly the a/c manually, see how it feels, is it in the drag curve? Is the power setting correct for the approach and the pitch attitude correct? If it feels all wrong, then the AP will never cope. It could also still be a network problem as well (it is not black and white) as you get near the ground, the server is doing more work, more scenery is drawn - perhaps also try a different airport, also you may want to consider reducing FS frame rate to less than 25fps.

>And now i am shure it is the software.............:-x

I sit in the simualtor with senior pliots, trainng captains, first officers - all types, we can do a full CAT III landing in zero vis with no problems at all. But we follow every single procedure and the a/c is set-up correctly. In my expereince with all this, 90% of the time it is not the software, but something else causing a problem at a critical flight phase.

>I give up before getting crazy - hope you guys can look in the Software
and bring new Builds , think it only have to do with AP`s both
Boeing and Airbus.

That's the problem, I understand it is difficult and frustrating, but to hope the software solves all your problems, it won't, you have to work very hard at this to get a fully operational working sim - it is the last 10% of details that count, it is a combination of skills, knowledge and software / hardware working together. If you give up - you won't get to the end goal, a software update is not always the answer, but certainly do wait for the new builds soon to be released and re-run tests... may be you will be lucky.

Regards
Jonathan Richardson

regards
Mario Görs :([/QUOTE]

Mario Görs

12-14-2007, 05:36 PM

Hello again :)

After some looking in software .ini`s special in
Wideclient and Wideserver i found some settings not like it was in my FS2004
So i corrected those settings.
First small test showed a better landing......:-P but before too mutch
pessimism i have to do more Testflights / Landings.
Hopefully..........:idea:

Goeing to Bed now....i am totally down - report back here after more test
the next days.

regards
Mario Görs ;)

Mario Görs

12-17-2007, 01:26 PM

Hello all , back

to post my findings ;)

After Days and hours off testing i think there`s defently
something goeing on with the GS code in both Boeing and Airbus AP`s

The Boeing is a bit better therefor but was better in some older Days !
For Airbus it is mostly ( not allways ) unpossible to land the plane at centerline from the runway.
I did several Tests here.

So let me explain one experiment:

After a couple off GS flights with PM Airbus AP
and allways have those centerbalancing ; ending with a big Plane
( Overland A380 ) near the runway , i tried something simple.

Shortly before i reached the GS Glidephad i closed PM`s AP
and hurried over to set the AP from the A380.
( It´s a simple Panel with xml coded gauges. )
After that the plane than shortly centers GS from far away
and flies it dow centered allmost witout any moving.
The planes front wheel ( and thats the true ) centers exactly
with the centerline off the runway and steers with that centercourse
off the middelline ; no need to do any rudder action to hold the plane center. :-D

And this guys is impossible with PM`s Airbus AP.

So why , enybody can tell me ????
I am not a Programmer so i don`t know but i realy know it isn`t easy :o
Maybe too mutch special code in there what kills the normal things ??
I don`t know...........

If you want me to try any Beta for test i will do that if it`s needed :)

Just to report back as i said....

regards
Mario Görs

JonathanRichardson

12-18-2007, 03:14 PM

Hi

Thomas and I both ran a series of tests with the FCU a couple of weeks ago with both FSX and FS2004. We found initially some problems only with FSX, which lead to the posting of the NOTAM. After which, everything was / is fine.

I think you probably have a problem with your aircraft model or some conflicts in the panel. Have you tried (just for testing) different a/c types and have you made 100% certain that the NOTAM actions have been taken?

Regards
Jonathan Richardson

Mario Görs

12-19-2007, 04:41 AM

Jonathan :)

> have you made 100% certain that the NOTAM actions have been taken?
this is all set like said there !

Another thing:
can you please post your Wideserver and Wideclient ini`s here in that thread to see maybe something jerkey there in mine ?
Just to compare mine with yours - would be nice ;)

I have not deleted the orginal AP Gauge it´s a xml gauge what have for every switch a entry , but i deactivated the master AP switch
and APPR and some other AP related gauges and have the same result.

I will try some older Builds too , maybe i can found
a solution ; over all that years i have saved all off them i think i have hundrets ( from Airbus and Boeing ) on a save harddrive.

Would you try the aircraft ??

It`s the Overland A380 model ??
I can send you my aircraft .cfg ( this on is modified because the orginal wasen`t that good ) and the airfile i used for it ??
The model if you not get them isn´t a prob at all
Would that be an idea ?! :cool:

PS: This is everything FSX related i not messing around in FS 2004 at this time,
because for that i ordered a new fast PC and therefor FSX run fine for me.

regards
Mario Görs

Thomas Richter

12-19-2007, 08:11 AM

Another thing:
can you please post your Wideserver and Wideclient ini`s here in that thread to see maybe something jerkey there in mine ?
Just to compare mine with yours - would be nice ;)

The way I create a WideClient.ini is by deleting it and starting WideClient, it creates a new one. That's it !
I don't use any "ServerName=" or "ServerIP=" settings!!
The WideClients find the WideServer by it self over the network, it is just itself created ini file with NO changes.
And my Server (FS9/FSX) is running Vista Home Premium 32, Clients are Windows 2000Pro, XP Pro and Vista Home Premium 32.
The WideServer.ini is as well only the self created one, no changes.

I have not deleted the orginal AP Gauge it´s a xml gauge what have for every switch a entry , but i deactivated the master AP switch
and APPR and some other AP related gauges and have the same result.

So you DON'T take care of the announced information! Why not?
The FSX default AP's has its own logic that cannot be overwritten by PM's MCP/FCU !!
If you don't remove, "Really remove", the lines with those logic gauges from your panel.cfg's you will EVER have problems and cry that PM has bugs in there software.

Please give your wife a steering wheel as well when YOU drive the car, if this will work then we are able to drive with two DIFFERENT working AP's !!

Any system gauges in FS9 and FSX has EVER to be removed, if not it would mean you are crying "Please give me a problem, it's so boring". :-)

A/C's
There are also A/C's out they use there own build-in logic, built-in means it is part of its .air file. Like PMDG's 747 has and those A/C models are not useable (see above).
FSX's Airbus has as well a line in its CFG where the build-in FBW is activated and if it is active our FCU cannot control the A/C really effective because this system decreases the FCU controls in special situations where it is needed to control more hard, but then you have again problems.

So it is ever needed to follow our informations / instructions we give, it is not only some rubbish we spray out for fun. We testet those things ever on different places (Jonathan in the SIM, Enrico in Italy and me 500km north of Jonathan) and situations, and this means in many many hours (you know then each "gras-blade" of this test-area).

JonathanRichardson

12-19-2007, 08:44 AM

>can you please post your Wideserver and Wideclient ini`s here in that thread to see maybe something jerkey there in mine ?
Just to compare mine with yours - would be nice ;)

Honestly, it is not necessary and may lead to confusion. I tested this in my office set-up and the simulator - both situations worked.

>Would you try the aircraft ??

Afraid I don't have time. Plus I think the problem is that the FSX AP (as per Thomas' reply) is fighting PM. I would also advise trying a different model - perhaps there is something very bad in its config file - one never knows with third party models.

Regards
Jonathan Richardson

brianwilliamson

12-19-2007, 11:53 PM

I still have not solved the problems yet. Did 4 ILS approaches in a row in FSX all 100 percent, and on the next take-off as soon as I engaged the Auto Pilot the aircraft went into an un-controlled pitch into the Earth !!
I then decided to re-load everything and try FS9, and on the second take-off, it was uncontollable as soon as I hit the Auto-pilot. So at the moment I am waiting to put the FCU on a spare computer, and see if I can find the problem from there.
Cheers..............Brian W.

brianwilliamson

12-20-2007, 01:22 AM

Thomas Richter

12-20-2007, 04:39 AM

While waiting for the key for the FCU to arrive I have been doing some circuits without the FCU. AND still problems. Turns out to be our old favorite............SIMBOARDS again !!
..............Brian W.

Hi

In this case I would first check the Network, WitClient Logs (on that PC) and WideServer Log.
I would not search first for the problem on the SIMBOARDS hardware, the Network is ever the Key.

The problems are really most related to the Network and don't forget the Network works like the "Quiet Post".

Companies with more than 5 PC's in a Network have ever a Specialist on board who does this things at the same time of his normal job.
And greater companies need a Network Administrator who does nothing else than to manage the Network.

EACH software/hardware (PM, AST, Phidgets, Simboards and all others) that works over the Network can ONLY work as good as the Network does !!
And if you build in somewhere a "Funnel" it will only works up to the moment the funnel input is bigger than what can come out of the funnel mouth.
So only a clean and poor Network setup is the base of all.

And a big problem of course is to set up this Network because we/or others can only give a line.
Why ? Easy !!
Every one sets up his PC, sometime (safety, poor, easy ...).
And in any different installation of Windows (with/without/multiple password ...) the Network setup is totally different to give rights for clients, safety Network rights or not and and and ...
And in addition we have to fight with Vista, XP and 2000Pro all in one Network, and all with different needs and rights.

Btw - Our small tool pmFileCheck is not only to check the FsPlans folder and the NetDir folder, it checks the Network connectivity on that PC where it is running to FS-PC.
That means you need to run it on EACH Client when its PM program and FS is running, best is when all Clients and their programs are running at the same time. So you will see in the Logs of pmFileCheck where/on what Client are may be problems.
We see many times that customers have problems to "see" the FsPlans folder or FS folder, but only on one Client. Then they search for hours/days on FS-PC for problems and change things in the Network there. The result is ever that they get more problems because they search on the wrong end. E.g. in those cases the problem is direct on the Client PC (different Network handling) or just there is no right for that PC on the FS-PC. And again that is a indication that the Network setup is tooooo safety, if you need to give special rights. In addition it means that Windows ever checks the rights on communication with clients and that will slow down the communication speed of course.

So all in all, if you ever have problems check first your Network. E.g. transfer a 200 or more MB file from one PC to the other.
Is the transfer speed constant or slowing down up to the end ?
Do you see small pauses ?
All those easy things will help to find problems.

Mario Görs

12-20-2007, 10:05 AM

Hello Thomas :)

Today i deleted / moved my Wideserver.ini in modules Folder
to let em Build a new one and saw after a conection over FSX and
Wideclient with PM ( after close all Progs ) no new one in the modules Folder :???:

Is that normal ??

Did that with Wideclient .ini , too but after shutting down
there was a new .ini build as awaited.

Is Wideserver not making a new .ini File after close FSX ??

And here is my Wideserver .log is there anything wrong here ??

********* WideServer.DLL Log [version 7.205] *********
Blocksize guide = 4096 (double allowed)
Date (dmy): 20/12/07, Time 13:59:35.522: Server name is MARIOGOERS-IQC2
15772 Initialising TCP/IP server
15772 Initialising IPX/SPX server
_______________________________________
Is here something wrong ???
_______________________________________
15772 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family
15772 Failed to start IPX/SPX Server
15772 Initialising UDP/IP server
16099 Broadcasting service every 1000 mSecs
137640 Incoming connection Accepted ok (skt=8504) TCP
137640 Restarting service due to zero reception!
137640 Failed to start IPX/SPX Server
140650 Incoming connection Accepted ok (skt=6992) TCP
140744 Failed to start IPX/SPX Server
143614 Incoming connection Accepted ok (skt=8896) TCP
143895 Connected to computer "939-3500A64" running WideClient version 6.750 (skt=8896) TCP
1756368 Error 10053: client socket disconnected at Client: removing (skt=8896) TCP
1836787 Incoming connection Accepted ok (skt=8764) TCP
1836834 Connected to computer "939-3500A64" running WideClient version 6.750 (skt=8764) TCP
1942790 Error 10053: client socket disconnected at Client: removing (skt=8764) TCP
2034861 Incoming connection Accepted ok (skt=7984) TCP
2034955 Failed to start IPX/SPX Server
2039791 Incoming connection Accepted ok (skt=6992) TCP
2039931 Connected to computer "939-3500A64" running WideClient version 6.750 (skt=6992) TCP
2623235 Close signalled to clients
2624327 Closing down now ...
Memory managed: Offset records: 2408 alloc, 2407 free
Read buffer usage: 18426 alloc, 18426 free, max in session: 1
Write buffer usage: 47859 alloc, 47859 free, max in session: 1
Throughput maximum achieved: 22 frames/sec, 12061 bytes/sec
Throughput average achieved for complete session: 9 frames/sec, 2043 bytes/sec
Average receive rate from "939-3500A64": 9 frames/sec, 997 bytes/sec
********* Log file closed *********

regards
Mario Görs ;)

Thomas Richter

12-20-2007, 10:33 AM

Peter Dowson

12-20-2007, 10:45 AM

Is Wideserver not making a new .ini File after close FSX ??

The FSX version of WideServer is built into FSUIPC4, and, as Thomas says, its parameters are in a section of the FSUIPC4.INI file. You shouldn't have any WideServer files in the FSX Modules folder excepting its Log.

And here is my Wideserver .log is there anything wrong here ??

Probably not. This part:

15772 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family
15772 Failed to start IPX/SPX Server

only means you haven't installed the IPX/SPX protocol in Windows, but that doesn't matter if you aren't using it (which you are not).

This errors:

137640 Restarting service due to zero reception!

is probably only occurring because FSX and WideServer wasn't ready at that time.

143895 Connected to computer "939-3500A64" running WideClient version 6.750 (skt=8896) TCP

It won't be any different for you, I suspect, but there is a later version of WideClient (6.757) available in the Downloads announcements on my Support Forum.

1756368 Error 10053: client socket disconnected at Client: removing (skt=8896) TCP

You had two of these. Were they due to you closing and restarting Wideclient?

Incidentally, the WideServer log is only part of the story. You really need to look at the WideClient log too. Maybe there are errors at that end?

Finally:

Throughput maximum achieved: 22 frames/sec, 12061 bytes/sec
Throughput average achieved for complete session: 9 frames/sec, 2043 bytes/sec

Is your FSX frame rate averaging between 9 and 22 fps? That last figure seems a bit low, but of course that includes two longish periods with no connection. The figures reported in the WideClient log should show something close to your average FSX frame rate.

Anyway, so far, no specific problems to be seen.

Regards

Pete

Mario Görs

12-20-2007, 12:50 PM

Pete :)

Thanks for fast reply

> You had two of these. Were they due to you closing and restarting Wideclient?

I think it was - doeing some testing

> Finally:

Throughput maximum achieved: 22 frames/sec, 12061 bytes/sec
Throughput average achieved for complete session: 9 frames/sec, 2043 bytes/sec

Is your FSX frame rate averaging between 9 and 22 fps? That last figure seems a bit low, but of course that includes two longish periods with no connection. The figures reported in the WideClient log should show something close to your average FSX frame rate.

It looks like this in the Wideclient.log:

6027498 ****** End of session performance summary ******
6027498 Total time connected = 6025 seconds
6027498 Reception maximum: 22 frames/sec, 15215 bytes/sec
6027498 Reception average whilst connected: 18 frames/sec, 538 bytes/sec
6027498 Transmission maximum: 53 frames/sec, 3400 bytes/sec
6027498 Transmission average whilst connected: 37 frames/sec, 156 bytes/sec
6027498 Max receive buffer = 1126, Max send depth = 10, Send frames lost = 0

So looks like this part is not bad ??
maybe should be DL the newer Wideclient for see if ther is something different !

So , Thanks a lot :lol:

regards
Mario Görs

Peter Dowson

12-20-2007, 01:15 PM

It looks like this in the Wideclient.log:

6027498 ****** End of session performance summary ******
6027498 Total time connected = 6025 seconds
6027498 Reception maximum: 22 frames/sec, 15215 bytes/sec
6027498 Reception average whilst connected: 18 frames/sec, 538 bytes/sec
6027498 Transmission maximum: 53 frames/sec, 3400 bytes/sec
6027498 Transmission average whilst connected: 37 frames/sec, 156 bytes/sec
6027498 Max receive buffer = 1126, Max send depth = 10, Send frames lost = 0

So looks like this part is not bad ??

Correct. 18 fps is quite good for FSX -- is that what you are seeing, on average?

There are no connection problems showing up at all, judging by these logs. Did you still notice something awry, or were these just lucky flights?

maybe should be DL the newer Wideclient for see if ther is something different !

I don't think there's anything wrong that it would fix, but I do always prefer folks to be using the latest in any case.

Regards

Pete

brianwilliamson

12-20-2007, 01:47 PM

Thank you Thomas for that good information, and I will do further testing today. The Simboards were an issue as I then deleted the whole Simboard program and re-installed it. The flights were ok then, and I did 5 straight ILS approaches perfectly and the sixth one did not lock onto the Glide Slope properly, so will need to look into why that happened.
It is so time consuming to find where the problems arise, but we have to find the answers by sheer hard work, regardless !!
I will post any further findings as I go.
Cheers...............Brian W.

brianwilliamson

12-20-2007, 02:04 PM

Just so you can see what happened on the last approach, here is a picture of the little circle that locked onto the ILS instead of the normal indicator, which resulted in a glide slope further down the runway.
Brian W.

Mario Görs

12-20-2007, 02:09 PM

Pete Thanks :)

> Correct. 18 fps is quite good for FSX -- is that what you are seeing, on average?

I have looked at 22 frames

So mostly seing around 16 to 22 .

> There are no connection problems showing up at all, judging by these logs. Did you still notice something awry, or were these just lucky flights?

I have those awrys still with on Model ( Overland A380 )
If this on comes not up in GS straight to runway you newer
can touch down very well !!
But i can`t make that with PM`s Airbus AP - it`s impossible
because i get those small left and right turns shortly from Runway

The stupid thing is if i shut down the PM Airbus AP
and set the Planes own AP on - i go down the GS stable like a rock
and setting off exactly on centerline from Runway

I tried tousend things ( chanched comlete airfile and aircraft.cfg
flown witout any panel ( no gauges there at all )
but ............no chance.
So we started this tread and now i can be shure it is not the conection !

So i don`t know anymore - looks like i have to give up now ,
because that can not be the thing to trie 5 days and still got the same results..........
Hopefully there coming up new builds in near future.......
maybe i have some luck and the querrys are gone than................??

Will see :idea:

regards
and thanks for your help
Mario Görs

Peter Dowson

12-20-2007, 03:05 PM

I have those awrys still with on Model ( Overland A380 )
If this on comes not up in GS straight to runway you newer
can touch down very well !!
But i can`t make that with PM`s Airbus AP - it`s impossible
because i get those small left and right turns shortly from Runway

The stupid thing is if i shut down the PM Airbus AP
and set the Planes own AP on - i go down the GS stable like a rock
and setting off exactly on centerline from Runway

It sounds like the data provided to PM about the A380 is not good enough. Did you make the file yourself, or get it from someplace else? The A380 is that new I'm surprised that there are reliable files for it, yet.

To see if it is just a conflict with the A/P not understanding your A380, try a model which is already well configured in PM aircraft files.

Regards

Pete

Thomas Richter

12-20-2007, 04:34 PM

Pete Thanks :)

I tried tousend things ( chanched comlete airfile and aircraft.cfg
flown witout any panel ( no gauges there at all )
but ............no chance.

What is the way you switch OFF the panel gauges?

Thomas Richter

12-20-2007, 04:35 PM

brianwilliamson

12-20-2007, 06:01 PM

Yes Thomas, no fly by wire and no panels.
Cheers..............Brian W.

Mario Görs

12-21-2007, 03:37 AM

Thomas ,

> What is the way you switch OFF the panel gauges?

Oh , i just delete every entry in the Panel file and leave the
Window 00 - but just the Panel BMP file to load !
And i leave the eyepoint section aswell !

So i only have the Panel bitmap to show up - without any gauges !

But that dosen`t help at all i am shure now it has to do wit PM´s AP
Maybe Enrico can look in the Glide code and can make the plane use the Glide
with a straight Heading to the Runway.
As allways as i take a look at the Airbus ND in Glide ( lets say the plane is about
3 NM from runway ) it is not in a straight heading to the runway. I thick that causes
the swinging , because the plane tries to center that mostly at the last 2000 feet
what causes the prob.

The own xml AP off the plane tries to centers the Glide at about 3000 -4000 feet
and fies " rock stable" down the Glide and sets off exactly at the centerline from the runway.
You can not play around with rudders to try a good landing it`s allmost impossible
it`s a big plane - for that the AP has to do that work , but has to do it exactly.

So if there small differences or special things coded in it i think you get problems
with that kind off a big plane.
Don`t forget the plane is mutch bigger than a Jumbo Jet and therfore i assume
it has to do with the AP.
He is not delicate enough for that.

And to say - i have tose small left right jerkeys in every plane Airbus and Boeing ,too
but other planes are smaller and so you have a little more room at it dosen`t hurt that mutch , you still on the runway and you can head the AC to center the runway.

Would be nice for the next builds you can throw a look in the Glide code
i think there can be done something.

I had older Builds with other cods in ; they where mutch exacter therefore ,
but they that old i think they not pretty useable anymore.........

And i will clear here : I AM NOT HERE TO FIGHT WITH PM OR ATTACK THEM ;
JUST TO POST MY FINDINGS ,

to help me and others who have simillar probs to push PM looking in it.

And to say again - if you want me to test them as beta i will glad to do.

regards
Mario Görs

Thomas Richter

12-21-2007, 04:40 AM

By search on different forums I found interesting things special about your Overland Airbus models.
- not really realistic flight dynamics
- auto-trim works much to slow, extremly with Flaps set
- A/C goes to fast down (sinkrate) with Flaps >1 to full
- special problems on Autoland

Did you try the default FSX A32x with your setup, no panel and FbW disabled ?

The flights were ok then, and I did 5 straight ILS approaches perfectly and the sixth one did not lock onto the Glide Slope properly, so will need to look into why that happened.

I the case that Brian (see above), Jonathan and me special THOSE problems don't see and as well never in Boeing suite saw I think it is may be something on your setup related.

Also the Airbussoftware is not designed for A380, we don't have anything for this A/C.
The software supports A319 - A340.

And please don't forget that ALL FSX A/C's has to be updated for the different FSX updates, SP1; SP2; Acceleration because the updated Simconnect versions works very different, Pete can sing a song of this.
If the A/C's you use are not designed for the newer FSX updates you can get strange behaviors.

What's about pmFileCheck logs from all Clients, did you run it?

Mario Görs

12-21-2007, 05:48 AM

Thomas ,

> - not really realistic flight dynamics

I told i did other ones they not bad for me !

> What's about pmFileCheck logs from all Clients, did you run it?

Shows all up normal results did it more times so i think it`s OK

But now i will stop this discussion because i writing and writing
but the results dosen`t bring me forward.

Just to say for your Question`s :
I am in MS Flightsimming over 10 years now and i think using PM Software
since around 2002 ( Not know exactly at the moment , but around this time )
so i can handle stoff with gauges and airfiles and AC .cfg`s ect.

But this discussion is banging out in "searching a tree in a big forrest"
but getting no results - so what now ??

I don`t know............for me i am shure it has to do with PM`s software
but i have what i have ( this software , and can not do anything more )
so it is at it is...and all those writing mails here bought me..........NOTHING!

regards
Mario Görs

PS:
> - A/C goes to fast down (sinkrate) with Flaps >1 to full

Changed this on too they allso not bad now !

> - special problems on Autoland

this isn`t the true i can handle it pretty well !

brianwilliamson

12-21-2007, 03:01 PM

Mario, try only the standard Airbus that is in FSX. I have found that I can do perfect ILS approaches with that aircraft providing that I follow the advice from PM, and do not use FBW and Delete all gauges and panel from the standard Airbus. On occassions I will get a missed ILS lock, but I suspect, as was the main problem I was having previously, was to do with Simboards.
Regards................Brian W.

Mario Görs

12-23-2007, 07:47 AM

Thanks Brian for the tipp
Will try ...........

But other than that :

Wish all PM members and all from this Community ,
Flightsimmers and Treadwatchers

A HAPPY CHRISTMAS and a nice and successful NEW JEAR 2008

regards
Mario Görs

Mart77

05-08-2008, 01:44 AM

Hiya,

Was there a solution to the glideslope capturing problem at all?

I ask as I am flying with PM and am having problems with glideslope capture.

When the plane passes through the glideslope and catures it (displayed on the PM PFD) the plane pitches upwards (very bizzare) and then tracks a glideslope 1000ft above the real one resulting in a landing (or more impact to be fair) at the end of the runway.

This problem seems to crop up more often than not, it seems it doesn't always do this though (even on the same ILS) which makes little or no sense to me.

One thing I did notice in the main panel (before I removed it as directed) was that the vert speed displayed was jumping from say -500 ft to +500 ft every so often. No idea why this is either but I'm pretty sure a lot of the passengers were reaching for their sick bags.

I have removed all the Main panel displays from the cfg file and have added a FiddleMachForPM entry in the FSUIPC ini file as was mentioned for a MCP fix.

The plane I'm flying is the boeing 737 default.

Any help would be much appreciated :)

warvet

05-08-2008, 04:44 AM

Yup I have had the same problem with Airbus FCU for a long time on ILS so i finally just gave up and hand flew it into landings everytime cause when I depend on the AP to handle the ILS it doesnt track properly all te time and it sucks after a 9 hr flight to crash or blow the approach on Vatsim. So I understand you guys prob I agree cause i have same probs in 2004 and FSX but more in FSX. Im just waiting till I can afford AST I guess.

Tim
A340
CAnada

Tim

05-08-2008, 07:24 AM

So, who really knows the status of PM updates?

Last RJ update was eight months ago.

Does anyone really know what is happening or not happening at PM?

Tomlin

05-08-2008, 09:08 AM

Yes, there's several folks waiting for an update to the software, and I too am hoping for an update to the RJ software as well...

mauriceb

05-08-2008, 05:30 PM

I ask as I am flying with PM and am having problems with glideslope capture.

When the plane passes through the glideslope and catures it (displayed on the PM PFD) the plane pitches upwards (very bizzare) and then tracks a glideslope 1000ft above the real one resulting in a landing (or more impact to be fair) at the end of the runway.

This problem seems to crop up more often than not, it seems it doesn't always do this though (even on the same ILS) which makes little or no sense to me.

Same issue with FSX & Boeing's. Some ILS's work fine and some send you up on a steep climb before trying to recover, but it never does recover, so a manual steep dive is needed to salvage the landing.

Some approaches though always seem to work properly, so as you say, it does not make any sense and it has to be an FSX issue and not an MCP issue since my MCP worked perfectly with FS9.

Maurice

Mart77

05-22-2008, 10:20 PM

I'd just like to add to this that I've tried multiple aircrafts (even some taken from FS9), I've tried it with panels displayed and without.

I've tried multiple ILS's for different airports.

I've tried multiple versions of PM.

I don't believe it's a FSX bug in itself as FSX's AP (without PM running) flies pretty darn well.

With some more looking into it, on capture of the glideslope (sometimes) a vert speed of +2500 is requested rather than the normal -400. I'd again like to stress this isn't every time. Some days it will fail more often than not and other days it'll work mostly. Without changing anything (just re-load a flight before glideslope capture) by re-running the same approach sometimes it captures and descends and sometimes it climbs.

Some sort of response past remove gauges and add the mach fix into the FSUIPC ini file would be great.

Alternatively is there a way of telling magenta not to touch approach and vorloc and let flight sim do it?

Regards,

Martin

ricgj

05-23-2008, 02:07 AM

Mart77

05-23-2008, 05:52 PM

Thanks for that RG,

I'll give that a go today. I did post a message to PM on their support address and got this reply:-

Hi

Yes, we know about it. It is a problem with FSX only but it is difficult to reproduce, sometimes it happens sometimes not. The problem is not there in FS2004 and limited to FSX / perhaps to do with MS simconnect. At this stage it is known, but out of our hands re a solution I think.

Regards

Jonathan Richardson

I'll keep looking into the problem, with pete dowsons help, and see if we can come up with something. Maybe it's a problem in FSX similar to the one needing the "FiddleMachForPm". Fingers crossed :)

Regards,

Martin

ricgj

05-23-2008, 06:46 PM

Hi

Another thing I have descovered is that the default 737 in FSX has a unralistic flight model. Generally the nose is too high and it is too powerfull.

I have found that the open sky 737 has a very accurate performance model.

But you need to have a fairly clean panel.cfg file for it to work in FSX, and if using this model your max trim needs to be +- 15 not 20.

I plan to finetune my configuration this week and post my findings.

Richard

Thomas Richter

05-24-2008, 01:55 AM

Hi

I had the same issue, nose up at GS intercept. But I noticed that the trim value was actually jumping up with a large number. I changed to trim setting on the type file, and it looks like it works fine now.

TrimMin=2.1
TrimMax=8.75
TrimScaleMax=20
TrimScaleMin=-20

RG

Hi

This is just the range of the displayed gauge and DOESN'T do anything in PM software or FS!!
So it doesn't matter what ever you set there because nothing will be changed, only the displayed PM trim gauge.

brianwilliamson

09-21-2008, 03:47 PM

Have not solved this problem as yet. Happens on the Airbus and the 737. Have sent emails regarding this to Magenta support, but no concrete replies as yet.
Let me try and explain what I am seeing from the indications on the PFD
screen.
When I get a perfect approach I can always access an intercept going away
from the Localiser at 10 to 14 miles out (at 2000 to 3000 ft.) and it will
do a precision turn straight onto the Localiser without deviation and then
it will come onto the Glide Slope from underneath ( as it should) and as the
indicator diamond starts down the scale towards the centre of the glide
slope scale, the vertical deviation donut is at the top of the scale and
starts to follow the GS diamond down when the diamond is about halfway down
the scale towards the lock on mark. Then at aquisition and lock on of the
GS, both the diamond and the vertical deviation donut are together in the
center.

On a bad approach, the first thing I notice is that either it will not start
to acquire the LOC at all going away, or if it does then the turn and line
up on the LOC will be erratic and not one big smooth turn onto the LOC
heading. It will the finally lock onto the LOC and as we approach the GS to
make aquisition, the GS Diamond will start down but the donut remains at
the top until the diamond reaches midscale and continues right down to the
bottom of the scale, and the donut will then go to the centre scale and lock
on there, the result being a rather large and high overshoot approach.
It would feel from observation that the mathematics of the intercept are
being mismanaged somehow.
If there are any suggestions available I guess we would all appreciate any help in trying to find a solution. Again the difficult part is that it seems so erratic.
................Brian W