A320 FMGS B47

[OmniAtlas]

Ben, after acknowledging the crash, what happens? P3D continues to work normally? what about the WXR?

When AS2017 injects weather there is an automatic simpatcher error and CTD.

[jeehell]

Hi Jean Luc,

I know what you do with starter.ini and I know I must set the right Options on install.
I think you don't know what I mean an so we have a misunderstanding (possible to my english)
I mean the Options at the end of the starter.ini to start external Programms, this entrys are lost.

I will add that kind of options soon hopefully.

> This is PERFECTLY normal. In this picture, you haven't yet entered enough performance data so the verctical profile is not yet
> computed, and the route cannot be drawn with turns etc. it's as real as it gets.

This I don't understand. I Input the Performance data after the flightplan. Is it not right?
I fill the MCDU: INIT -> FPLAN -> RAD NAV -> INIT B -> PERF

What do you mean I do wrong?

I can't tell what you're doing wrong (if you have this same thing when inflight for isntance), or if you just look at the FPLN at a moment when SOPs were not yet finshed for the MCDU initialisation. The "unfinished" legs will start showing their correct form when all computations are correct. This means you must, at least and some more may apply, all weights in INIT B, PERF values and a valid flight plan. It might be on a short leg if T/D is "in conflict" with the T/C then the computation fails.

If you want to file for a refund please do not hesitate...
I am pretty sure I still spend much more time working on the soft than you reconfiguring your sim every now an then...

And this comment I don't understand. I read it an think you mean it is a criticism.
But I mean you need feedback and suggestions from your user.

I develop and support software. And yes, I know what you do and that you spent a lot of time for this.

Regards Dieter

I probably misunderstood your first comments. Sometimes the line between feedback and criticism is thin and I probably got it wrong, sorry for that.

[OmniAtlas]

Hi Jean Luc -- I will continue to use the simpatcher which comes with the installer for now -- weather is not functioning (no wxr files written) but at least we don't have a CTD.

Thank you,

Ben

[startrail]

[QUOTE=OmniAtlas;168424]Hi Jean Luc -- I will continue to use the simpatcher which comes with the installer for now -- weather is not functioning (no wxr files written) but at least we don't have a CTD.

Thank you,

Ben[/QUOTE

Same here

[fisfro]

Hello,

I have started with the update to P3DV4 with the latest fmgs version yesterday, and till now I'm fighting against following Problems:

.) I'm not able to control flaps or thrust Levers in the FDS Flightdeck. The Eicas display shows me, that the levers are in rev-Position - but the aren't. I have calibrate them new and in the fmgs config every axis will response as expected. The flaps positions will work also in the calibration window but there will be no Change in the fmgs.
.) no bin-files will be generated ( I have wait more than 30 minutes without success - usually they will be generated within minutes)

I'm operating V3 and V4 on the same drive. Therefore I have copied the old A320FMGS Directory to a new one with a different Name and then I have done the update to the different Directory. I have to add the config files manually as well as the dll for the Hardware connectmodule.
In P3D V4 the A320FMGS plane is selected - so the intstall to V4 seems to be okay.


So with now I would be happy to start my engines to make a first test flight

Some help would be great!


Thanks!

Robert

[jeehell]

Hello,

I have started with the update to P3DV4 with the latest fmgs version yesterday, and till now I'm fighting against following Problems:

.) I'm not able to control flaps or thrust Levers in the FDS Flightdeck. The Eicas display shows me, that the levers are in rev-Position - but the aren't. I have calibrate them new and in the fmgs config every axis will response as expected. The flaps positions will work also in the calibration window but there will be no Change in the fmgs.
.) no bin-files will be generated ( I have wait more than 30 minutes without success - usually they will be generated within minutes)

I'm operating V3 and V4 on the same drive. Therefore I have copied the old A320FMGS Directory to a new one with a different Name and then I have done the update to the different Directory. I have to add the config files manually as well as the dll for the Hardware connectmodule.
In P3D V4 the A320FMGS plane is selected - so the intstall to V4 seems to be okay.


So with now I would be happy to start my engines to make a first test flight

Some help would be great!


Thanks!

Robert

can you try to delete the c:\A320FMGS\FMGS Server\acontrols.cfg file and recalibrate from scratch?
Try running only FMGS server manually to build the navdata (using Admin rights!!).
Make sure the paths in c:\A320FMGS\navdata\fsscenery.cfg are correct.

[fisfro]

can you try to delete the c:\A320FMGS\FMGS Server\acontrols.cfg file and recalibrate from scratch?
Try running only FMGS server manually to build the navdata (using Admin rights!!).
Make sure the paths in c:\A320FMGS\navdata\fsscenery.cfg are correct.

Hello JH,

okay I will recalibrate.

I have just checked the fsscenery.cfg - and there is a link to the V3 Version instead to V4.
I have changed as following:

[Scenery]
scenery.cfg=C:\Program Files\Lockheed Martin\Prepar3D v4\
FSfolder=C:\Program Files\Lockheed Martin\Prepar3D v4\
AerosoftPath=C:\Users\fro\AppData\Roaming\JeeHellWare
ip=127.0.0.1

but it's also not working now....

[jeehell]

scenery.cfg is most probably in:
C:\ProgramData\Lockheed Martin\Prepar3D v4\scenery.cfg
and you need to fill in the scenery.cfg part of the full path!!!
so:

[Scenery]
scenery.cfg=C:\ProgramData\Lockheed Martin\Prepar3D v4\scenery.cfg
FSfolder=C:\Program Files\Lockheed Martin\Prepar3D v4\
AerosoftPath=C:\Users\fro\AppData\Roaming\JeeHellWare
ip=127.0.0.1

[jeehell]

and post your c:\A320FMGS\logs\logNDB.txt

[fisfro]

and post your c:\A320FMGS\logs\logNDB.txt

here it is:

*10:36:52* Navdata module launched Server
*10:36:52*
*10:36:54*
*10:36:54* Navdata1:
*10:36:54* -ARPTliste:13804
*10:36:54* -NavaidListe:17088
*10:36:54* -FIXliste:254238
*10:36:54* -AWYsegments:96473
*10:36:54* -MarkerList:1586
*10:36:54* -Holds:21098
*10:36:54* -RWYS:34065
*10:36:54*
*10:36:54* Navdata2:
*10:36:54* -ARPTliste:13804
*10:36:54* -NavaidListe:17088
*10:36:54* -FIXliste:254238
*10:36:54* -AWYsegments:96473
*10:36:54* -MarkerList:1586
*10:36:54* -Holds:21098
*10:36:54* -RWYS:34065
*10:36:54*
*10:36:54* server started on port:8006