A320 FMGS B47

[OmniAtlas]

in your file c:\A320FMGS\FMGS Server\PERF\PA320\Aircraft.ini add the line:
LinkISISQNHtoCPT=yes

This is a very helpful.

I should start adding an FAQ with all these hidden options, thanks JL :)

[jeehell]

HI All

A new update is available.
http://www.jeehell.org/A320FMGS_B47.3.exe or through auto update.



What's new in B47.3:
----------
-Added MCDU and PFD DECELERATE message
-Added MCDU and PFD MORE DRAG message
-Added MCDU TOO STEEP PATH AHEAD message and pseudo waypoint
-Added back on profile prediction arrow on ND
-Corrected some DES profile computations issues (particularly on non precision and RNAV approaches)
-Corrected ALTN FPLN issues when activating the ALTN (wrong procedures in the new destination airport).
-Corrected some CSTR management during DES/APPR
-Corrected high altitude go around FMA modes sequencing
-Corrected ALT*/ALT below ACC ALT during takeoff
-Added SPDBRK arming via analog range
-Corrected WXR/TERR dimmer pot detection in FMGS config
-Corrected double box in FMA column
-Corrected ARPT bug issues on ND (number displayed reducing over time, probably affected also VORs/NDBs/FIXes)
-Corrected FSUIPC DECEL bug
-Corrected APU EGT at 0°
-Corrected EGPWS terrain mis alignment (due to magnetic variation)

JL

[asessa]

wow! thanks JH!

[jcostabal]

Hi JL,

Thanks for that update. I just installed it. However, the Thrust levers and speedbrake lever stop working (FSCockpit). I Can't find them in the FMGS Config app. They are connected to the PC since I can see them with the FS Cockpit App and the work properly.

Please help

[Beret]

Hi Jeehell

With the WX I have some probleme. I can't set the TILT value positive. There are always a - in front.

[Leonidas]

Hi JL,
Thanks for that update. I just installed it. However, the Thrust levers and speedbrake lever stop working (FSCockpit). I Can't find them in the FMGS Config app. They are connected to the PC since I can see them with the FS Cockpit App and the work properly.
Please help

It has nothing to do with this update. I have the same THR LVR and work properly.

[pete_fuss]

Hello JL,
thanks for this update!

But in the MCDU i can not arrive the prog and pref page!

This errormessage is on the display " MCDU DISPLAY Problem, Please report issue"

Regards Peter

[jeehell]

Hello JL,
thanks for this update!

But in the MCDU i can not arrive the prog and pref page!

This errormessage is on the display " MCDU DISPLAY Problem, Please report issue"

Regards Peter

more details required, at least flight phase, what data was filled in MCDU etc...

[pete_fuss]

Hello JL,

the next problem i have is: the throttle lever don`t work!
In the fmgs_config i cannot assign the joystick axis ! it`s a bodnar controller!
in the last version it works fine !

regards Peter

[pete_fuss]

more details required, at least flight phase, what data was filled in MCDU etc...
Hello JL,

i start to fill up first the two int pages, then i will go to the pref page to fill in V1 VR and V2 and then this errormessage is in the display of the mcdu!

Regards peter

[jeehell]

Hello JL,

the next problem i have is: the throttle lever don`t work!
In the fmgs_config i cannot assign the joystick axis ! it`s a bodnar controller!
in the last version it works fine !

regards Peter

what happens exactly? I cannot guess errors and bugs, I need detailed information on what you attempted or I cannot help you.

[jeehell]

Hello JL,

i start to fill up first the two int pages, then i will go to the pref page to fill in V1 VR and V2 and then this errormessage is in the display of the mcdu!

Regards peter

Did you rebuild the navdata?

[pete_fuss]

Did you rebuild the navdata?
Hello JL,

sorry, i just rebuild the navdata, but i forgot to copy it to the client pc where my mcdu`s are running!
Now it works as bevor, great support!

now i run also the fourst time the fmgs_config program and at this time, i don`t no why, i can calibrate my throttels, it also now works fine!

Sorry for the circumstances!

Regards Peter

[Leonidas]

Did you rebuild the navdata?

Same to me. PROG and PERF pages :-(
Rebuild navdata and copy bin files yesterday. After that it was OK, but today MCDU DISPLAY PROBLEM...

[EDIT]
It's OK, I fix it :D

[jcostabal]

Fixed!, I had to set all the flight controls again and it worked.

Already tryed the B47.3 and is working perfectly so far!

Thanks JL

[jeehell]

Same to me. PROG and PERF pages :-(
Rebuild navdata and copy bin files yesterday. After that it was OK, but today MCDU DISPLAY PROBLEM...

[EDIT]
It's OK, I fix it :D
wait I am lost now.
You rebuilt the navdata a second time and now it works correctly??

JL

[Leonidas]

wait I am lost now.
You rebuilt the navdata a second time and now it works correctly??
JL

No, I have a problem with my THR LVR every time I setup FMGS with clean installation. I decide to run fmgs-config (eventhough I have config backup file) to setup THR LVR again. So, after that THR LVR indeed worked and the 2 MCDU pages worked at the same time. It is mabe just coincidence. I don't know :roll:

[pete_fuss]

Hello JL,

one very little thing, the starter.exe shows the version number 47.2!

nice weekend

regards Peter

[OmniAtlas]

Hi JL -- thanks for the update. Managed to finally test it this weekend -- here are my findings:

1. Database loading screen on startup (MCDU) -- this persist, although after ADRS alignment I can still load departure and arrival ICAO and even a flight plan. I have not rebuilt the database -- are we suppose to for each new version?
http://www.mycockpit.org/forums/attachment.php?attachmentid=12317&stc=1

2. There is a line drawn on the aircraft ND symbol YBCG depart -- this line was present for most of the simulated flight.

http://www.mycockpit.org/forums/attachment.php?attachmentid=12318&stc=1

3. Despite having an analogue arm switch for the speedbrake I am still unable to arm - I believe this is because the arm state does not have a threshold on an axis (it is either arm, or disarm -- and the axis numbers jump around) - is it possible to set a range for the brake arm, or an error % ?

4. On climbing I got a message 'MORE DRAG' -- this was after I changed the altitude from FL160 to FL150 as I intended it to be as I input on the MCDU. I did not see the MORE DRAG message when descending even when I was above the donut.

5. Managed flight plan route is....strange. This is an ILS straight in approach.

http://www.mycockpit.org/forums/attachment.php?attachmentid=12319&stc=1

[jeehell]

Hi JL -- thanks for the update. Managed to finally test it this weekend -- here are my findings:

1. Database loading screen on startup (MCDU) -- this persist, although after ADRS alignment I can still load departure and arrival ICAO and even a flight plan. I have not rebuilt the database -- are we suppose to for each new version?


2. There is a line drawn on the aircraft ND symbol YBCG depart -- this line was present for most of the simulated flight.



3. Despite having an analogue arm switch for the speedbrake I am still unable to arm - I believe this is because the arm state does not have a threshold on an axis (it is either arm, or disarm -- and the axis numbers jump around) - is it possible to set a range for the brake arm, or an error % ?

4. On climbing I got a message 'MORE DRAG' -- this was after I changed the altitude from FL160 to FL150 as I intended it to be as I input on the MCDU. I did not see the MORE DRAG message when descending even when I was above the donut.

5. Managed flight plan route is....strange. This is an ILS straight in approach.




1. I think the XXXX are clear enough that you need to rebuild the database... I cannot say on every release it is required (it hasn't been for some time). But it's always bets, and it will be in the few next I think due to some changes in the format.

2. weird, never seen that. report if it happens again.

3. the same % range as the retracted position is used.

4. Doing that you changed your FMGS from CLB mdoe to DES mode (probably closer than 200NM from DEST). You can change again to CLB or CRZ in the MCDU PROG page by forcing the CRZ FL in the 1L field.

5. Probably linked ot navdata ...

[Leonidas]

Hi
Suddenly Ground Spoilers connected to FDS card doesn't work properly, when I arm the ECAM message just turn on and off, doesn't stay in arm position. I've checked wiring via IITCreator and seems OK. I use legacy drivers for FDS. Should I try the new ones?
Regards

[OmniAtlas]

1. I think the XXXX are clear enough that you need to rebuild the database... I cannot say on every release it is required (it hasn't been for some time). But it's always bets, and it will be in the few next I think due to some changes in the format.

2. weird, never seen that. report if it happens again.

3. the same % range as the retracted position is used.

4. Doing that you changed your FMGS from CLB mdoe to DES mode (probably closer than 200NM from DEST). You can change again to CLB or CRZ in the MCDU PROG page by forcing the CRZ FL in the 1L field.

5. Probably linked ot navdata ...

I updated the navdata, and rebuilt -- everything seems to be working fine now.

2. Seems to be resolved, did see the graphical glitch again when turning into an ILS approach, I think it is the way the graphical draws are handled when the managed mode FMGS is trying to redraw a curve.

[emulov]

Hi
Suddenly Ground Spoilers connected to FDS card doesn't work properly, when I arm the ECAM message just turn on and off, doesn't stay in arm position. I've checked wiring via IITCreator and seems OK. I use legacy drivers for FDS. Should I try the new ones?
Regards

Hi Leonida,


If you use a button to ARM the Ground Spoilers, you have to make sure that the option "ARM as analog range" is NOT ticked.

http://www.mycockpit.org/forums/attachment.php?attachmentid=12323&stc=1

Regards,
Isak

[Leonidas]

Hi Leonida,
If you use a button to ARM the Ground Spoilers, you have to make sure that the option "ARM as analog range" is NOT ticked.
Isak

That's recenlty added I think. Thanks Isak.

[jeehell]

Hello

I just put a small update to fix an issue Awith ATHR staying at idle in certain conditions (with eng anti ice on, and if engines were spooled all way down to idle).

JL

[jpromeroa]

Dear JL,

I have been dealing with an issue for a while now with the presentation of the flight plan green line on the ND of the flight plan inserted on the MCDUs.

A month ago I updated the nav data cycle and the issue started. It presented like this: IR already aligned, ND on map to review the flight plan green line and constrains, the after I inserted the route all was fine but then I inserted a different route and the old one it stayed and the new one did not displayed on the ND. After TO the aircraft flew the route inserted on the MCDU but the ND didn't displayed it.

Then I updated the Nav Data again and it started to work fine again. However, when I reboot the computer next day, again the issue with the ND green line but this time only the runway presented on the ND but no green line, fix or constrains on the screen. I updated again the Nav Data, worked fine for one flight and then it stoped during the flight.

I don't know which is the problem, the Nav Data or something regarding a file that I may erased unintentionally form the Navdata directory or something with the Client or Server computer. I have been tryin all for a month, and no fix.

Do you have an idea of what is happening with this? Other that this all systems are working in perfect conditions with the update. I really need your help on this.

Best regards,
JP

[jeehell]

What you experience is either a problem with your installation somehow, or with your Network.

[filippoporcari]

hi jl,
running 47.3 with latest autoupdate but both ND when using eis2 option still cannot be resized to show all infos (dme of vors and top line still out of the mip window...tried to resize but the lines are always cut.
with old eis style everything is perfect.
am i the only one?
regards
fil

[jeehell]

the window must be square.
you can manually adjust the width/hieght in the ini files for each EIS.

[Miatanet]

Hi
having Problem after update to latest Version starting my bus. APU does not come up, both korry led's go off after 30 sec. And no power is available for ND/MCDU etc.

Any idea?

Br
Stefan

[jeehell]

enough Fuel?

[filippoporcari]

thx for the cue jl...solved as usual!
fil

[filippoporcari]

sorry to disturb again hl....not using the sim for LONG time and now facing a second weird thing:
versions are updated on both server and client....the network is fine (the displays on the client "reacts" on input from the server but no way to have the flightplan displayed: no airport, no route, pushing VOR, NBD, APT show nothing.
of course the database has been rebuilt MANY times and the 10 bin files copied to the client....
never experienced this kind of problem i'm a bit lost.
tried also a clean installation on both sides.
am i missing something from this latest version?
using navigraph data as usual...
tried also the very old free set of navdata on ben site but nothing.
any idea?
sorry again
fil

[Mitch95]

Hello Fil,


Try to take more time during ADR initialization : ADR1 ==> wait "ON BAT" becomes OFF, and do the same for ADR3 and ADR2.
Then, if you doesn't wait for 10 minutes, take your time while switching "OFF / NAV" for the 3 ADR.

Maybe it has a consequence on the display, I have this feeling... Rightly or wrongly ;-)

Please tell me your feedback about this...

Michel

[filippoporcari]

thx michel...
...tried what u suggested but dis not solve my issue
regards
fil

[tcane]

Hi Jeehell,
Prepare 3D V4 is coming out on 30.05. and it has 64 Bit.
Can we expecting also an update from you for the 64Bit System? Or works already with the actual Version?

Cheers
Florian

[jpromeroa]

Ok, it actually is a Network problem but only for ND green flight plan line. When this issue happens I opened an ND on the server computer and is showing all correct flight plan line on the screen while the Client ND green line is stuck or doesn't show anything.

Any ideas to solve this?

[jpromeroa]

What you experience is either a problem with your installation somehow, or with your Network.

Ok, it actually is a Network problem but only for ND green flight plan line. When this issue happens I opened an ND on the server computer and is showing all correct flight plan line on the screen while the Client ND green line is stuck or doesn't show anything.

Any ideas to solve this?

[OmniAtlas]

Hi Jeehell,
Prepare 3D V4 is coming out on 30.05. and it has 64 Bit.
Can we expecting also an update from you for the 64Bit System? Or works already with the actual Version?

Cheers
Florian

I don't think there should be any issues as FMGS plugs into simconnect. Thats if Project Airbus has no compatibility problems.

---

After reading more into P3D v4 it seems FSUIPC may not be compatible -- for those dependent on FSUIPC (such as mobiflight, or using offsets) that maybe an issue.

[filippoporcari]

what i find VERY strange about this: if it was a network problem all the displays (running all on 1 client computer) would not connect to the server or loose connection and they would not "react" to server inputs.
all the displays are instead solid connected to the server, they react to inputs (i.e. if i switch adf or vor on the fcu they appear in the lower corners of the ND)....only issue is with database data not being shown on ND (flightplan, airports, VORs, NDBs).
JL any idea? something i should look for?
i tried to build the database again...waiting 20 mins after bins appear in the folder then oves them to the client.
regards
fil

[OmniAtlas]

...only issue is with database data not being shown on ND (flightplan, airports, VORs, NDBs).
JL any idea? something i should look for?
i tried to build the database again...waiting 20 mins after bins appear in the folder then oves them to the client.
regards
fil

When you first start FMGS - on the MCDU what does it say? Database loaded? The dates should corroborate with your navdata.

And what hardware FCU are you using?

[filippoporcari]

ho ben,
thx for the interest.
yes on both mcdus the database are loaded and consistent with the navdata cycle.
i'm totally lost...first time in nearly 5 years of use of fmgs.
to add something: if i access the mcdu data page i can recall rwys, vors and ndbs infos which i think means the database is there.
only missing the route and all db infos on ND!
cheers
fil

[OmniAtlas]

ho ben,
thx for the interest.
yes on both mcdus the database are loaded and consistent with the navdata cycle.
i'm totally lost...first time in nearly 5 years of use of fmgs.
to add something: if i access the mcdu data page i can recall rwys, vors and ndbs infos which i think means the database is there.
only missing the route and all db infos on ND!
cheers
fil

On the server computer can you try running the software FCU and ND and see if that works? If it does then we know there is something related to the network, or database files.

[Mitch95]

Hello,


@ Fil : Very strange....

Are you sure you're running the same JeeHell version on each PC ?
After B47.3 installation, autoupdate brought a small EIS update ==> Are you sure all is up to date on each PC ?

Be careful to firewall and antivirus too, maybe some files could be removed...


Michel

[filippoporcari]

michel of course checked and rechecked everything: never had antivirus on my sim...firewall always off on all pcs...same versions and updated on both.
i tried as ben suggested and yes if running ND on main pc where p3d and server are running everything is fine with the route.
what's wrong on the client side?
regards
fil

[OmniAtlas]

try copying the whole Navdata folder and try again.

another thing make sure your video drivers are updated.

[sstusek]

ho ben,
thx for the interest.
yes on both mcdus the database are loaded and consistent with the navdata cycle.
i'm totally lost...first time in nearly 5 years of use of fmgs.
to add something: if i access the mcdu data page i can recall rwys, vors and ndbs infos which i think means the database is there.
only missing the route and all db infos on ND!
cheers
fil

Hi Filip,

I have exactly the same problem with ND route as you. I thought that I was crazy but I see that I am not the only one.
I never had any problems until B47? I tried every trick I could think of and still not working, I compiled / copied bin files like thousand times with old airac, new airac you name it, totally lost... Also the autopilot will fly the route it just won't show it on client PC ND. It must be something win network related as ND installed on server PC works normally! It is strange that radar works on client PC ND but route is not displayed. I installed ND on another PC with fresh win7 install (no firewall or antivirus) and it worked normally for the first time, I thought this is it... After restarting it went back to no route?! I am wondering which data will draw the route on ND?

Simon

[filippoporcari]

thx ben but that's exactly what i do every time (copying the whole navdata folder to client).
video drivers could be an idea...going to check soon!
thx
fil

[filippoporcari]

found the solution!
video drivers were not responsible.
windows update on client made the trick! i have not being updating its win7 for LONG time
thx to all
fil

[OmniAtlas]

Hi Filip,

I have exactly the same problem with ND route as you. I thought that I was crazy but I see that I am not the only one.
I never had any problems until B47? I tried every trick I could think of and still not working, I compiled / copied bin files like thousand times with old airac, new airac you name it, totally lost... Also the autopilot will fly the route it just won't show it on client PC ND. It must be something win network related as ND installed on server PC works normally! It is strange that radar works on client PC ND but route is not displayed. I installed ND on another PC with fresh win7 install (no firewall or antivirus) and it worked normally for the first time, I thought this is it... After restarting it went back to no route?! I am wondering which data will draw the route on ND?

Simon

Update your video drivers Simon...

[Niklas]

Yesterday in thunderstrom the ND works perfect, but the engines showed TOGA but there was no TOGA. There was no Thrustlever reaction as well.
We have had G-Force of more than 3G.

[Leonidas]

Yesterday in thunderstrom the ND works perfect, but the engines showed TOGA but there was no TOGA. There was no Thrustlever reaction as well.
We have had G-Force of more than 3G.

Same to me. Thrust reduced little by little without any message during climb or cruise mode until A-Floor. No THR LVR reaction. Crash after very long time... I haven't run out of fuel... :(

[spiliot]

Engine Anti Ice was ON?

[Leonidas]

Engine Anti Ice was ON?

No, ENG AntiICE OFF...

[spiliot]

You probably missed it, in the latest versions engine icing is simulated properly, so next time you fly in known icing conditions turn your Engine AI on as you would in the real aircraft :)

And since on the subject, does anyone know if airframe icing is simulated and/or if wing anti-ice has any effect on icing or performance?

[jeehell]

You probably missed it, in the latest versions engine icing is simulated properly, so next time you fly in known icing conditions turn your Engine AI on as you would in the real aircraft :)

And since on the subject, does anyone know if airframe icing is simulated and/or if wing anti-ice has any effect on icing or performance?
looks like you did not try before asking ;-)

[Leonidas]

You probably missed it, in the latest versions engine icing is simulated properly, so next time you fly in known icing conditions turn your Engine AI on as you would in the real aircraft :)
And since on the subject, does anyone know if airframe icing is simulated and/or if wing anti-ice has any effect on icing or performance?

Who spoke about icing conditions? I met no precipitation too...

[spiliot]

Who spoke about icing conditions? I met no precipitation too...
Well the previous post mentioned thunderstorms and you replied "me too". But do try E-AI and see if there's any difference.

Also, I've seen a few times the ground temperature staying constant in higher altitudes (i.e. +20oC degrees at 25k feet). This huge difference from expected would make the engines gradually loose power as you climb. Restarting the weather program fixes it for me.


looks like you did not try before asking http://www.mycockpit.org/forums/images/smilies/icon_wink.gif

Well I did try, but couldn't see any notable difference between performance with wing ai on or off (while engine AI was on) so I was wondering if it works. But I didn't test extensively either.

JL, would you care to elaborate how structural icing affects aircraft performance, when you apply that logic and how to detect it from a crew perspective?

To my knowledge crews avoid the use of wing AI unless they have clear cues of ice build up (there's a small aerial just out of the center of the cockpit which is the first place to notice ram icing) or flying at night and weather reports showing severe icing, freezing rain, etc for the area flown.

[jeehell]

Structural icing will increase the drag produced by the wing, which means AoA will increase (so in CRZ for instance, pitch will increases to keep level flight at the same IAS). It is quite slow, and I made it not go up to stall (for most conditions).
You cannot really detect it from crew perspective, this is a sim so no icing probe... So if you fly in icing conditions (ie visible moisture and negative temperatures) then turn on AI.

[jeehell]

Who spoke about icing conditions? I met no precipitation too...
icing does not mean rain, it means flying in clouds or in rain, with low temperatures. Using ASN, the icing conditions are given by ASN itself, nor my soft nor P3D.

[Miatanet]

nope, left tank was empty, grrrrr. Thank you for the hint. Now it works, having fun with you soft JL :-)
Best regards
Stefan

[Leonidas]

icing does not mean rain, it means flying in clouds or in rain, with low temperatures. Using ASN, the icing conditions are given by ASN itself, nor my soft nor P3D.

I turn on Engine and Wing AI when TAT is between -10 and 10 and SAT greater than - 40. Wing AI never on ground and of course when there is precipitation (black cloud, rain, snow, moisture in general).
In this case I was above clouds in a very clear sky.
Anyway, fortunately there was no one else in the plane...

[tcane]

Hello JH,
Today i like to install your new update Version 47.3. After download and in the installation process i got a Virus Warning from Avira:
Found Adware/Agent hvnmv
I deactivated the Virusscanner but the A320FMGS_47.3 installationdata is infected with this Virus and can´t install your latest Version. On all three Computers are still the same problem.
Can you check this maybe?

Cheers
Florian

Edit: The Adware was find in the Starter.exe

[jeehell]

No I cannot check it.
But you can add exceptions to your antivirus. Or change your antivirus.

[tcane]

No I cannot check it.
But you can add exceptions to your antivirus. Or change your antivirus.

Hi,
Ok, so you mean this is normal and the Adware comes from you?

[jeehell]

I also steal your bank account credentials... :roll:

this is a false positive. There is nothing I can do about it... there is no virus or adware or whatever intentionally put in the package.
If you prefer to believe your antivirus, do so of course. But I can not change the software to comply with stupid antivirus definitions.

[iwik]

tcane,
If you are ever in doubt then there are plenty of online sites that will give you a check of the file. I had avira but it gave me to many false positives so i dumped it.
Les

[tcane]

Sorry JL, it was not meant like that. Thought it might be outfitted and wanted to give you modest. But all fine in this case. I ignore now the message and deactivate the "search for Adware" point. This was my first false positives with Avira and i thought it´s something bigger. So sorry for nerves, I certainly did not want to impute you anything.

Salü
Florian

[Mitch95]

Hello Florian,


Some parts of the software are also frequently blocked or removed by several antivirus suites.
I made experiences with Avast in the past years..., and now Norton Security which talks about an "heuristic risk".


These are known points, you can read about this in the Installation Guide, point 4.1.


This is the case with Updater.exe, WideFMGS.exe, EIS.exe and recently Starter.exe.
And Throttle Panel software too...


For information, I get exactly the same message from Norton at every Navigraph AIRAC update for PFPX / TOPCAT...


Regards,

Michel

[OmniAtlas]

You guys need to get a better virus scanner. I've had no issues with ESET NOD.

[spiliot]

I had quite the opposite experience with NOD, it was messing up with the computer network stack causing random programs to crash in semi-random conditions, despite being or not in its whitelist (i.e. vpilot when I pressed the push to talk). Disabling it didn't do anything, had to uninstall AND restart to figure out it was indeed NOD causing this. Lost two days back then on it.

Don't forget FMGS asks for administrator permissions; if JL wanted to bundle malware there wouldn't be much any antivirus software could do to detect it until too late.

[dkreiskott]

Hi Jean Luc,

beginning of the month I wrote you for the Problems with navigraph AIRAC. This Weekend i buy the new AIRAC from Navigraph and from Aerosoft.

I install the Navigraph cycle and have the same Problem. All LOC are any meters left or right from the center line of the runway. And this on ALL Airports, the Default too.

I don't change the configuration of fsscenery.cfg, but I install the Aerosoft cycle and all works fine. But this not the solution for me. I will change from Aerosoft to Navigraph.

I don't know, what I can do wrong? I few Informations for you.

1. FMGS Server is a dedicated Computer and not the FSX Computer
2. The Path for scenery.cfg is in UNC Format and a share from the FSX Computer like "\\FSX\myShare" in fsscenery.cfg
3. The IP Adress in Fsscenery.cfg is the IP from the FSX Computer
4. The Aerosoftpath in fsscenery.cfg is the same as for Navigraph

I do not understand why the AIRAC from Aerosoft works and from Navigraph not.

I hope you can help.

Regards Dieter

[OmniAtlas]

Dieter - can you set your aircraft at YSSY 16R and turn on ILS and take a photo of your ND and PFD.

[dkreiskott]

Hi Omni,

yes I can do that. I will try to do this in the evening, but this week I'm very busy.

Dieter

[jeehell]

Hi Jean Luc,

beginning of the month I wrote you for the Problems with navigraph AIRAC. This Weekend i buy the new AIRAC from Navigraph and from Aerosoft.

I install the Navigraph cycle and have the same Problem. All LOC are any meters left or right from the center line of the runway. And this on ALL Airports, the Default too.

I don't change the configuration of fsscenery.cfg, but I install the Aerosoft cycle and all works fine. But this not the solution for me. I will change from Aerosoft to Navigraph.

I don't know, what I can do wrong? I few Informations for you.

1. FMGS Server is a dedicated Computer and not the FSX Computer
2. The Path for scenery.cfg is in UNC Format and a share from the FSX Computer like "\\FSX\myShare" in fsscenery.cfg
3. The IP Adress in Fsscenery.cfg is the IP from the FSX Computer
4. The Aerosoftpath in fsscenery.cfg is the same as for Navigraph

I do not understand why the AIRAC from Aerosoft works and from Navigraph not.

I hope you can help.

Regards Dieter

which version of the software do you use?
I am not sure a network share will work in this case.
It can be aerosoft pre process ILS data themselves, I see no other reason.

I will need to have a look at the logndb.txt file (located in c:\A320FMGS\logs), just after rebuilding the navdata with aerosoft and then with navigraph (I insist you must rebuild the navdata again so the log means anything). Also, add this line to your FSScenery.cfg:
monitorARPT=YSSY
(or whatever airport where you have a significant difference).

[dkreiskott]

Hi Jean Luc,

I use the 47.3 and I have updated all five Computer.

If I use the Aerosoft Cycle, the network share seems to work. But I can change it to a network drive.
OK, I create the both navadat new and set the Option bevor.
Do you need only the both logndb.txt, or some other files from me?
I will do it with EDDL, 05R is left of the Center line.

I hope I can do it in the evening.

OK, I don't know if it is importent, the home cockpit works with six Computer
1. Computer only for FMGS Server, AP/FBW
2. Computer for FSX and only sound modul
3. Computer for software Overhead and SD/EWD
4. Computer for CPT with MCDU1 ND / PFD
5. Computer for FO with MCDU2 ND / PFD


Usually I don't use network drives, only shares and UNC path.
If you need further information of my configuration, please let me know.

Thanks for help.

[Leonidas]

Dieter - can you set your aircraft at YSSY 16R and turn on ILS and take a photo of your ND and PFD.

This is mine. It seems OK, but I have same problem in other RWYs such as in Kopenhagen (EKCH) in all directions!!! I also use Navigraph.
http://www.mycockpit.org/forums/attachment.php?attachmentid=12331&stc=1

[jeehell]

OK, I create the both navadat new and set the Option bevor.
Do you need only the both logndb.txt, or some other files from me?
I will do it with EDDL, 05R is left of the Center line.

for now only logndb.txt, after each rebuild (aerosoft then navigraph)

[jeehell]

and really, if there was an issue with navigraph I would know, since I only use theirs data...

[dkreiskott]

OK I'm in Progress, it's a time consumption process

I check EDDM, EKCH and YSSY


But I'm confused ft this:

*17:27:17* -BGL scan:
*17:27:17* -ScenerycfgPath:\\FSX\FSXScenery
*17:27:17* -FSroot:\\Fsx\fsx
*17:27:18* -Folders Nb:0
*17:29:28* -Monitoring:EDDM
*17:29:28* -Total ILS in FS for EDDM: 0
*17:30:13* -Total ILS in Navdata for EDDM: 4

This is with Aerosoft

[jeehell]

This is what I suspected. UNC pat hwon't work. I have to look into it, I think it's just a parsing issue but it won't work.
It's purely luck aerosoft DB works better for you. They either process the rawdata with FS data OR their provider has a different data than navigrpah which fits FS/P3D better...
But you will not get 100% good quality for the navdata anyway.

JL

[dkreiskott]

No, the UNC Path is not the Problem. I made 2 Shares with drive letter and it doesnt work.

look here:

*18:36:44*
*18:36:44* -BGL scan:
*18:36:44* -ScenerycfgPath:y:\
*18:36:44* -FSroot:x:
*18:36:44* -Folders Nb:0
*18:38:41* -Monitoring:EDDM
*18:38:41* -Total ILS in FS for EDDM: 0
*18:38:41* -Total ILS in Navdata for EDDM: 4

[dkreiskott]

OK, I have no idea what I can test too.

I copy my scenery.cfg local to fmgs Server and set a local path. But the result is the same.

I don't know how you are need the Path for FSX, what file(s) do you need?

[dkreiskott]

Hi JL,

one idea I have tested.

I install FMGS Server on my FSX PC. But this doesn't work too.

*19:47:15* -BGL scan:
*19:47:15* -ScenerycfgPath:C:\ProgramData\Microsoft\FSX
*19:47:15* -FSroot:C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X
*19:47:15* -Folders Nb:0
*19:48:01* -Monitoring:EDDM
*19:48:01* -Total ILS in FS for EDDM: 0
*19:48:01* -Total ILS in Navdata for EDDM: 4

It seems, the Problem is not the scenery.cfg

I hope you have any idea

What means "Folders Nb:0"

Regards Dieter

[dkreiskott]

I promise to test EKCH and YSSY.

YSSY is a stock Airport in my sim and on both Airports I have the same Problem.

I have now tested in fsscenery.cfg to set the path for FSX as: -FSroot:"C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X (http://www.amazon.de/s/ref=nb_sb_noss?__mk_de_DE=%C5M%C5Z%D5%D1&url=search-alias%3Dvideogames&field-keywords=flight simulator x)" but this doesn't work too.

And the Screenshots from EDDM. If the ILS is on center, the Aircraft is on the left side.

http://www.mycockpit.org/forums/attachment.php?attachmentid=12333&stc=1
http://www.mycockpit.org/forums/attachment.php?attachmentid=12334&stc=1

Omni, is it possible you use the line "monitorARPT=EDDM" in your FSscenery.cfg and test with this?

Regards Dieter

[jeehell]

Network drive is probably not working because Windows sandboxes the network drive between normal and admin sessions. You are normally running FMGS with admin rights so unless you created the netowrk driver with a batch file ran with admin rights, it won't work.
For now, the best is to have a local FSX copy and make sure you have correct paths in FSScenery (both for FS root and scenery.cfg).
Then, close down FSX (it may block access tothe files) and run the FMGS server with admin rights.

[jeehell]

Regarding EDDM, I think some users had issues there.
Do you use the fixes made by Hervé Sors? This helps a lot (https://www.aero.sors.fr/navaids3.html I am talking of the ILS/RWY updates).

Any way, you will it worked mostly when
-Folders Nb: is different than 0
-Total ILS in FS for EDDM: is different than 0
etc...

[jeehell]

I corrected the UNC naming issue with the navdata module, it should work on next version.
Though I understand now why you say it's a long process... of course, accessing 1000 bgl files over the network is much slower than on the local hard drive.
Also, doing so is fine as long as your scenery is installed inside FSX folder. But this might not be the case with P3D new recommendations for addons etc... So I still do not recommend this kind of setup.

[dkreiskott]

Hi Jean Luc,

what a evening, 6 hours for generating navdata :???:

OK, I have found the problem. The first error is from me. I forgot to write the file Name of the end from scenery.cfg path.
I have this error since my first install about for four years. Incredible :roll:

But you are right, UNC path doesn't work. If I use drive letter for the Network Shares all works fine.
I have tested any Airports and all ILS are OK.

At this moment, I think the Airac from Navigraph works.

And please please, can you check the Problem with UNC path. Network drive letter under Windows are a problem. They often disconnect, but UNC path works in all situations.

A little excitement from programmer to programmer. If you use an external file with your Software and it can't be found, give the user a message. It helps for dummys :oops:


@Leonidas

You are right EKCH has an error in ILS. I use an older Payware Scenery for EKCH and i look with ADE in the BGL File.
The ILS is not in all directions in center.
What scenery for EKCH do you use?

Thanks for all our help

Regards Dieter

[dkreiskott]

Aah OK, I don't see your post.

Yes with P3D it is not possible, but you have only one path for scenery.cfg.
Since P3D there are two files, or not?

I'm using the FSX and for scenery compatibility (I have 100 scenerys or so) I don't use P3D. But I know what you mean.

No the long process ist in another way. After deleting the BIN files I wait 3 Minutes and all is OK. But the FMGS Server has no Monitor and I use RDP, but this disconnects your Software from FSX. So I must restart the FMGS Server Computer to work with FSX.

And for me it is a great work from you, that FMGS Server can run on a Computer other than the FSX is installed. And in this situation I must use Network Shares for the navdata module.

Or do you have any other Suggestion?

[Leonidas]

@Leonidas
You are right EKCH has an error in ILS. I use an older Payware Scenery for EKCH and i look with ADE in the BGL File.
The ILS is not in all directions in center.
What scenery for EKCH do you use?
Thanks for all our help
Regards Dieter

No other scenery, just P3D v.3.4... :roll:

[dkreiskott]

No other scenery, just P3D v.3.4... :roll:

OK, i check the stock Airport in FSX.

But look at here: https://flyawaysimulation.com/downloads/files/14099/afcad-file-update-for-ekch/
I don't know if it helps.

[dkreiskott]

Hi JL,
some things take longer. :cool:


In the morning I read your post from yesterday, and at this time I understand what you tell me.
If I understand you and the process for creating navdata right, then network is not possible at all.
My scenerys not all installed in FSX. In this case your module read a path from scenery.cfg e.g. "D:\Scenery\..."
And this path is not readable over the network in this moment of course.
I did not think about the process of creating the navdata.
What is your recommendation for users he has a dedicated FMGS Server?
Install FMGS Server on FSX / P3D Computer too, but only for creating the navdata?


Regards Dieter

[jeehell]

Regarding EKCH, there are many ILS/RWYs. They probably changed the frequency and the rwy names since the FSX/P3D scenery was built. SO it is difficult to extract the BGL data.
Did you both use the ILS update tool from Hervé Sors? this is probably the ONLY useful addon other than my software (ahah).

@dkreiskott: next version will support the UNC path (was not a big change). But this will not take into account the addon scenery outside FSX folder.
If you really want to use the shared path, you may try to change the paths in your Scenery.cfg to UNC paths for each addon scenery... This may be a tedious work...
What I personally do is install the FMGS Server on the FSX/P3D computer (or even just copy the FMGS server folder...) to build the navdata there. Then I share the navdata folder, so it is rather straight forward to copy the bin files afterwards on each PC.
You could even probably make some batch file to copy them for you.
I plan to improve the navdata sharing, but it's not a top priority item right now.

[Leonidas]

Regarding EKCH, there are many ILS/RWYs. They probably changed the frequency and the rwy names since the FSX/P3D scenery was built. SO it is difficult to extract the BGL data.
Did you both use the ILS update tool from Hervé Sors? this is probably the ONLY useful addon other than my software (ahah).
..........................
it's not a top priority item right now.

No I didn't, but I'm going to use it...
What's top priority right now? :D

[jeehell]

What's top priority right now? :D
it's top secret ;-)

[dkreiskott]

Regarding EKCH, there are many ILS/RWYs. They probably changed the frequency and the rwy names since the FSX/P3D scenery was built. SO it is difficult to extract the BGL data.
Did you both use the ILS update tool from Hervé Sors? this is probably the ONLY useful addon other than my software (ahah).

@dkreiskott: next version will support the UNC path (was not a big change). But this will not take into account the addon scenery outside FSX folder.
If you really want to use the shared path, you may try to change the paths in your Scenery.cfg to UNC paths for each addon scenery... This may be a tedious work...
What I personally do is install the FMGS Server on the FSX/P3D computer (or even just copy the FMGS server folder...) to build the navdata there. Then I share the navdata folder, so it is rather straight forward to copy the bin files afterwards on each PC.
You could even probably make some batch file to copy them for you.
I plan to improve the navdata sharing, but it's not a top priority item right now.


Hi JL,

I think I install FMGS Server on the FSX Computer then the Update is in function correct.
I suspect the *.dll Files are importent to create the navdata?

And I think I can help you, if you want.
I have for me in the home cockpit written a little tool to distribute the *.BIN Files and the Navdata1 and Navdata2 Folder to the Clients after Airac Change or update your Software.

What does it do

It works on Network, inkl. UNC Shares

Checks the Folder for new Airac
Deletes the BIN Files in Navdata Folder from FMGS Server
Starts FMGS Server and wait if all Files created
Then close FMGS Server
Copy all *.BIN Files and Navdata Folders to the Client

The Tool is in english and fully configurable.

[dkreiskott]

Ups, some text is missing in my post


If you interested, I can send you a copy for testing.
And if it is OK for you, you can distribute it for free with your Software.

Regards Dieter

[dkreiskott]

> Did you both use the ILS update tool from Hervé Sors? this is probably the ONLY useful addon other than my software (ahah).

Did you mean the Navaid Update on this Website? http://sors.fr/aero/navaids3.html

[OmniAtlas]

Probably wise to do all the navigation updates from Sors website, but the only one I've done is the Magnetic Variation (to save time) - http://www.aero.sors.fr/navaids.html

Hopefully with P3D V4 this will be updated.

[OmniAtlas]

I promise to test EKCH and YSSY.

YSSY is a stock Airport in my sim and on both Airports I have the same Problem.

I have now tested in fsscenery.cfg to set the path for FSX as: -FSroot:"C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X (http://www.amazon.de/s/ref=nb_sb_noss?__mk_de_DE=%C5M%C5Z%D5%D1&url=search-alias%3Dvideogames&field-keywords=flight simulator x)" but this doesn't work too.

And the Screenshots from EDDM. If the ILS is on center, the Aircraft is on the left side.


Omni, is it possible you use the line "monitorARPT=EDDM" in your FSscenery.cfg and test with this?

Regards Dieter

I will see if I can catch up over the weekend and do some testing -- trying to figure out ARINC 429 at this stage :-|

Make sure your magnetic variation is updated.

I haven't messed with FSscenery.cfg -- in fact, I don't really know what it does.

[jeehell]

Probably wise to do all the navigation updates from Sors website, but the only one I've done is the Magnetic Variation (to save time) - http://www.aero.sors.fr/navaids.html

Hopefully with P3D V4 this will be updated.

I thought I had said it somewhere already.

It is USELESS to do the magnetic variation update, at least in regards to my software. I do all the magnetic variation computations myself in the application, not using the variable from FS/P3D.

The ONLY update which is useful is the ILS/RWY update.

[dkreiskott]

Hi Jean Luc,

I have installed FMGS Server on the FSX PC too.
Thats the result, I think looks good.

*19:11:29* Navdata module launched Server
*19:11:29* No Navdata1: copying new dataset to Navdata2 as well
*19:11:29* New Data set available
*19:11:29* Copying Navdata1 to Navdata2
*19:11:29*
*19:11:29* -BGL scan:
*19:11:29* -ScenerycfgPath:C:\ProgramData\Microsoft\FSX\scenery.cfg
*19:11:29* -FSroot:C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\
*19:11:30* -Folders Nb:289
*19:12:03* -FS ILS Nb:5054
*19:12:51* -Monitoring:EDDL
*19:12:51* -IDSE layer:320
*19:12:51* -IDNE layer:320
*19:12:51* -IDNW layer:320
*19:12:51* -IDSW layer:320
*19:12:51* -IDSE layer:54
*19:12:51* -IDSW layer:54
*19:12:51* -IDNE layer:54
*19:12:51* -IDNW layer:54
*19:12:51* -Total ILS in FS for EDDL: 8
*19:12:51* -Total ILS in Navdata for EDDL: 4

Now I have another question. Needs FMGS Server (on the dedicated Server) the Navdata or is it only importend for the clients?

Regards Dieter

[dkreiskott]

Hi Leonidas,

I use the ILS Tool from Hervé Sors as Jean Luc suggest.
For me all ILS in EKCH works correct.

Thanks JL

[OmniAtlas]

I thought I had said it somewhere already.

It is USELESS to do the magnetic variation update, at least in regards to my software. I do all the magnetic variation computations myself in the application, not using the variable from FS/P3D.

The ONLY update which is useful is the ILS/RWY update.

Its for other software - I haven't run into too much of a problem with fmgs (do minimal flying now a days). J will update ILS/ RWY.

Merci

Ben

[Leonidas]

Hi Leonidas,
I use the ILS Tool from Hervé Sors as Jean Luc suggest.
For me all ILS in EKCH works correct.
Thanks JL

I run it too, but ILS at 4L not corrected. Maybe I had to try it after reboot. Anyway, I didn't spend more time about it the day P3D v.4 is arriving. :D
Thanks Dieter

[sstusek]

found the solution!
video drivers were not responsible.
windows update on client made the trick! i have not being updating its win7 for LONG time
thx to all
fil

Hi,

None of the windows or graphic updates worked for my ND client setup! Any way, yesterday I finally found the ND route "error" solution. This time I was focused only on network. I tried many things related to network and home group settings but nothing helped?! Why it was working before version B47.1 ... then I remembered, I installed the wireless USB adapter to make auto updates! I uninstalled the driver and after restart ND finally started working, now I can see the green route line again :D.
I hope this might help anyone else with similar network problem.

I also have a question regarding weather radar and hardware use. I guess it is not high on priority list but I am wondering if some sort of hardware interface for radar panel is planed (FSUIPC, SIOC creator, joystick buttons)? Thanks.

Cheers,
Simon

[Leonidas]

Hi
I've installed P3D v.4 in a new PC with last FMGS for v.3.4 just for a test and despite FMGS addons appears in P3D menu, is says "FMGS server not connected". Is there something easy to configure or should I wait for FMGS update?
Regards

[jeehell]

you might need to configure simconnect.xml manually.
It does work, I tested... only simpatcher is not compatible.

[Leonidas]

you might need to configure simconnect.xml manually.
It does work, I tested... only simpatcher is not compatible.

Thanks JL, but I can't find it. Where could I find simconnect and what configuration need for this?

[anzabon]

Ehm, is FSUIPC 5 already released?

[Gregor]

Hi Leonidas

It's in the directory where you have the sim installed in the \redist\interface subfolder.

http://www.mycockpit.org/forums/attachment.php?attachmentid=12338&stc=1

For P3D you will need the "FSX-SP2-XPACK"-version.
Probably you have to install it first manually.

Cheers
Greg




Thanks JL, but I can't find it. Where could I find simconnect and what configuration need for this?

[Leonidas]

Hi Leonidas
Probably you have to install it first manually.
Cheers
Greg

Thanks Greg. I've installed it, but do you know where is simconnect.xml and what configuration needed?
Regards

[Leonidas]

Ehm, is FSUIPC 5 already released?

I can't find it...

[Gregor]

Hi Leonidas

My simconnect.xml is in C:\Users\[USERNAME]\AppData\Roaming\ and looks like

<SimBase.Document version="1,0" Type="SimConnect">
<Descr>SimConnect</Descr>
<Filename>SimConnect.xml</Filename>
<Disabled>False</Disabled>
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>IPv4</Protocol>
<Scope>local</Scope>
<Address>127.0.0.1</Address>
<MaxClients>64</MaxClients>
<Port>9017</Port>
<MaxRecvSize>4096</MaxRecvSize>
<DisableNagle>True</DisableNagle>
</SimConnect.Comm>
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>IPv4</Protocol>
<Scope>global</Scope>
<Address>172.20.10.3</Address>
<MaxClients>64</MaxClients>
<Port>9017</Port>
<MaxRecvSize>4096</MaxRecvSize>
<DisableNagle>True</DisableNagle>
</SimConnect.Comm>
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>IPv4</Protocol>
<Scope>global</Scope>
<Address>172.20.10.2</Address>
<MaxClients>64</MaxClients>
<Port>9017</Port>
<MaxRecvSize>4096</MaxRecvSize>
<DisableNagle>True</DisableNagle>
</SimConnect.Comm>
</SimBase.Document>

Probably you have to check ip-adresses and ports.

Cheers Greg



Thanks Greg. I've installed it, but do you know where is simconnect.xml and what configuration needed?
Regards

[OmniAtlas]

Ehm, is FSUIPC 5 already released?

Yes, FSUIPC5 is now released - http://forum.simflight.com/topic/80977-updated-modules/

[Gregor]

Hi OmniAtlas

Do I need FSUIPC for JeeHell and Skalarki only?

Cheers
Greg

[OmniAtlas]

I am not too sure about Skalarki, best if you e-mail Marcin.
I believe you need FSUIPC if you use Opencockpit and of course mobiflight (adruinos).

[Leonidas]

Hi Leonidas
My simconnect.xml is in C:\Users\[USERNAME]\AppData\Roaming\ and looks like
....................................................................
Cheers Greg


Thanks Greg. Finally I've installed P3D v.4 to my main system without uninstalling v.3.4 and it works great without simconnect.xml change! I'm going to have both versions until AS16 upgrades for P3D v.4.
Regards

[SSO]

Thanks Greg. Finally I've installed P3D v.4 to my main system without uninstalling v.3.4 and it works great without simconnect.xml change! I'm going to have both versions until AS16 upgrades for P3D v.4. Regards
Did you manage to get P3Dv4 to load the bus? For some reason it does not show up on my Airplane list despite the fact that I have copied the C:/Users/<USER>/AppData/Local/Lockheed Martin/Prepar3D v3/simobjects.cfg to C:/Users/<USER>/AppData/Local/Lockheed Martin/Prepar3D v4/
I also tried copying the full A320-214 directory into the V4 Airplanes directory.

Solved (not sure what did it...)

[jeehell]

Did you manage to get P3Dv4 to load the bus? For some reason it does not show up on my Airplane list despite the fact that I have copied the C:/Users/<USER>/AppData/Local/Lockheed Martin/Prepar3D v3/simobjects.cfg to C:/Users/<USER>/AppData/Local/Lockheed Martin/Prepar3D v4/
I also tried copying the full A320-214 directory into the V4 Airplanes directory.
I did, without any problem, so your problem is probably elsewhere??

[SSO]

Solved :-)
Not sure why or if I just missed the 320 on the list first time around.

I have Skalarki up and running as well.
And my CockpitSonic RMP...

Looking good.

[jeehell]

By the way, do not try to use Simpatcher from previous versions it will fail.
I will post a fully compatible installer in the very next days, which will have the updated simpatcher.

[SSO]

I did, without any problem, so your problem is probably elsewhere??
Jean Luc,

Do you see your Airplane from exteriour view? I do not...

[Leonidas]

Jean Luc,
Do you see your Airplane from exteriour view? I do not...

I saw it, it seems OK. Why?

[SSO]

I saw it, it seems OK. Why?
I dont see it, and wonder why...

[emulov]

Hi,


if you are using the EZdok camera addon, you have to run the "EZCA Config.exe" tool after installing new aircrafts or updated aircrafts. Otherwise you will not be able to see the the aircraft in the external view.


Regards,
Isak

[Firefly77]

Hi,


if you are using the EZdok camera addon, you have to run the "EZCA Config.exe" tool after installing new aircrafts or updated aircrafts. Otherwise you will not be able to see the the aircraft in the external view.


Regards,
Isak

Hi, I dont use ezdok but I have also no visible plane in external view. This is for a longer period now, i think since version b46. It doesnt bother me as i am flying in a homecockpit and do not need external view very often but anyway it is not there anymore.
Cherrs Michael

[Leonidas]

I dont see it, and wonder why...

I just copy A320-214 folder to Simobject folder of P3D installation. Without any cfg file copying.

[jeehell]

Maybe you need to copy the effects from the aircraft folder to your p3d folder....

[tcane]

Hi Jl,
maybe for the next update you think on the Wx Radar integration for SIOC? :)

Merci
Florian

[tuomasho]

Hi all,

have anyone got FMGS, Skalarki's Profiler and new P3D v4 work? My experiment is that V4 and FMGS works, also I have working simconnect and FSUIPC. Skalarki's profiler works, but it doesn't connect to the simulator... Any help?

Best regards

-=Tuomas=-

[cmdr114b]

Tuomas,
I initially had a problem getting P3D V4 working and had to install widefs from the new fsuipc5 installation, using the fsuipc4 registration details. That got all my clients connected.
Secondly I copied my simconnect.xml from p3dv3.4 to p3dv4 directory at C:\Users\...\AppData\Roaming\Lockheed Martin\Prepar3D v4
I hope that helps
John

[tuomasho]

Hi John,

and thank's for your answer. :p So you have Skalarki IOProfiler and that connects to Simulator, FSUIPC and to FMGS? Because I did pretty much the same things than you did. I reinstalled new fsuipc5 to V4 and registered widefs with my registration codes. That works, because IOProfiler tells that it is connected. Also I got simconnect to work from every computer. The problem still exists. All the other connections from IOProfiler are working, only connection to the simulator doesn't work... Does anyone know how the Profiler connects to the sim? With simconnect or how?

My installation is as follows:

Sim computer: P3D V4
Client: FMGS (for two seats, 5 monitors), IOProfiler (throttles and FCU)
Client 2: FMGS (Intercom), IOProfiler (MIP, 2 MCDU's, Pedestal and OVHD), AS16, ASCA and ProAtc
Tablet: FS-Flight Control

Every computer has simconnect and FSUIPC installed and working.

Best regards

-=Tuomas=-

[cmdr114b]

Hi Tuomas,
Yes, I am using all Skalarki hardware with Profiler version 1329.
My system is similar to yours except I use 6 small PC's to load share.
I assume you are using A320FMGS_B47.4.
Initially I could not get any Widefs clients to talk to the server but that was fixed by doing the update I quoted.
Are the entries in the FMGS server green?
I also run wideclients on all machines that use the profiler.
One other question when installing JeehellFMGS did you include "use fsuipc" ?

John

(http://www.jeehell.org/A320FMGS_B47.0.exe)

[SSO]

Hi all,

have anyone got FMGS, Skalarki's Profiler and new P3D v4 work? My experiment is that V4 and FMGS works, also I have working simconnect and FSUIPC. Skalarki's profiler works, but it doesn't connect to the simulator... Any help?

Best regards

-=Tuomas=-
I have everything up running including flying online on VATSIM.
Only issue until now is that the Transponder mode is not transmitted properly from FMGS through V4 to vPilot...
The transponder Code is fine but not the state.

/Stephen

[tuomasho]

Hi,

and thank's for your answers. I don't know what is wrong with IOProfiler. FMGS is working and connected, FSUIPC is connected and Simconnect is installed and have to work, because otherwise FMGS wouldn't work. But, IOProfiler can't connect to simulator... Very annoying! :cry:

Does IOProfiler use fsuipc, FMGS or simconnect to get connection to the simulator?

Thanks guys!

Br

-=Tuomas=-

http://www.mycockpit.org/forums/attachment.php?attachmentid=12346&stc=1http://www.mycockpit.org/forums/attachment.php?attachmentid=12347&stc=1

[skalarki]

Hi,

and thank's for your answers. I don't know what is wrong with IOProfiler. FMGS is working and connected, FSUIPC is connected and Simconnect is installed and have to work, because otherwise FMGS wouldn't work. But, IOProfiler can't connect to simulator... Very annoying! :cry:

Does IOProfiler use fsuipc, FMGS or simconnect to get connection to the simulator?

Thanks guys!

Br

-=Tuomas=-



Hi Tuomas
So far I haven't announced p3d V4 full support... then nobody can expect all will be working from day one. We are working on compatibility. Just a few days ago FSUIPC V5 was released, but couple of weeks ago even Pete couldn't confirm if he will do it or not.
Anyway for p3d V4 compatibility we will not be using FSUIPC any more. SimConnect will be the way to communicate with sim.

Getting back to your current issue, which I can't confirm as i don't want to use FSUIPC any more as I said, connection to sim is done pure via FSUIPC. If you have Profiler installed on remote PC, there is wideFS needed. Are you 100% sure FSUIPC is installed and working in p3d?

[tuomasho]

Hi Marcin,

yes of course I understand that there isn't full support. This is only testing and why I am trying to sort it out is that there is other people and it is working for them. That's why I can't understand why it doesn't work in my system. ;)

My FS clients says that those are connected and also in the P3D v4 left upper corner there is a text that "P3D with wideserver: 3 connected". Only thing is that FSUIPC isn't full version, because when I installed it you couldn't buy it. But WideFS is registered...

Also I started IOProfiler in simulator computer and also in there it says "simulation not connected".

Also in profiler it says that "FSUIPC: Yes". Can it be possible that it is that FSUIPC is not registered or do I have a wrong version of Wideclient in the client computers? Any other things that can cause this?

Best regards

-=Tuomas=-http://www.mycockpit.org/forums/attachment.php?attachmentid=12348&stc=1http://www.mycockpit.org/forums/attachment.php?attachmentid=12349&stc=1

[skalarki]

I know what is wrong. SIMULATION box is just visual representation if we are connected or not. It is red in this case as in current Profiler I am detecting only p3d up to version 3.4
This is the reason why box stay red, but as long FSUIPC says Connected, all should be working. Do not look on red box. Just start profile and all should work.

[tuomasho]

This is what you get when you build your simulator to a container and install new things with Teamviewer from your home... :shock::oops::roll::D

It works!

-=Tuomas=-

[asessa]

Did Someone try the suite with p3d v4 ?

[OmniAtlas]

Did Someone try the suite with p3d v4 ?

A few have; I would wait until the next FMGS release so you can have a working simpatcher.

Dynamic lighting looks spectacular, perhaps something we can figure out how to implement on the aircraft.

[asessa]

A few have; I would wait until the next FMGS release so you can have a working simpatcher.

Dynamic lighting looks spectacular, perhaps something we can figure out how to implement on the aircraft.

So, actually, the only problem is the weather rdx ?

[pete_fuss]

So, actually, the only problem is the weather rdx ?
i can confirm that

regards Peter

[asessa]

i can confirm that

regards Peter

ok thanks guys

[Leonidas]

Hi
Could someone remind me what should I do if A/C decelerates too fast during taxi?
Regards

[richard.long]

How would JL be installed in P3DV4; as the installer does not go beyond V3.4?

Since the Aircraft folder is in the FMGS folder - rather than SimObjects - I don't know how P3DV4 will reference it.

I've got P3DV4 and FSUIPC5 running but no way to get the aircraft into P3D.

Thanks

[masterp]

Hi all,

Anyone got FMGS 47.3 completely freeze with Abeam point in DIR page?
After select Abeam point, and press Insert, my FMGS server is not responding.

[startrail]

B47.3 works perfectly with P3DV4 and Fscockpit

[cmdr114b]

How would JL be installed in P3DV4; as the installer does not go beyond V3.4?

Since the Aircraft folder is in the FMGS folder - rather than SimObjects - I don't know how P3DV4 will reference it.

I've got P3DV4 and FSUIPC5 running but no way to get the aircraft into P3D.

Thanks

Richard try http://www.jeehell.org/A320FMGS_B47.4.exe

John

[spiliot]

Anyone got FMGS 47.3 completely freeze with Abeam point in DIR page?
After select Abeam point, and press Insert, my FMGS server is not responding.

I have this problem since I started using JH, especially when the DIR TO point is quite further away (say at least 150 miles). For shorter distances it usually works, but the further the distance the more you need the abeam function. I've come to stop using it because it usually ruins an otherwise perfect flight :(

[Migelito]

found the solution!
video drivers were not responsible.
windows update on client made the trick! i have not being updating its win7 for LONG time
thx to all
fil

Hyi Fil!

I do have the same behaviour with green NAV line on ND on client. Do you mean a win7 update solved the problem or did the update cause the problem?

Thanks for answer, I´m lost since 3 days, rest is working
Greetings
Michael

[OmniAtlas]

Richard try http://www.jeehell.org/A320FMGS_B47.4.exe

John

I had no idea this was already released.

[jeehell]

It is not. And I strongly suggest you do not install it.

[richard.long]

@startrail,

What procedure have you used to install JL into P3dV4?

[startrail]

@startrail,

What procedure have you used to install JL into P3dV4?


Actually I did not install anything. Just move a320-214 to simobject in P3D V4.
started P3D V4 and then Simconnect followed by A320 FMGS B47.3.

It it did connect exactly as P3D V3.5

Cheers

Mike

[richard.long]

Actually I did not install anything. Just move a320-214 to simobject in P3D V4.
started P3D V4 and then Simconnect followed by A320 FMGS B47.3.

It it did connect exactly as P3D V3.5

Cheers

Mike

Hi Mike, thanks.

My understanding was that the Aircraft folder should remain in the FMGS install directory and that there shouldn't be an instance of it in SimObjects. I did this once before and got conflicts between the two.

I'll give it a try though :-)

Thanks
Richard

[jeehell]

Hi Mike, thanks.

My understanding was that the Aircraft folder should remain in the FMGS install directory and that there shouldn't be an instance of it in SimObjects. I did this once before and got conflicts between the two.

I'll give it a try though :-)

Thanks
Richard

This is why the installer has specific options for each versions of P3D. But if you can't wait a few hours/days you can copy it, just remember to remove it when next release comes out. I hope very soon...

JL

[jeehell]

Version B47.4 is now officially available.
Full support for P3D V4 is included, as well as for Hifi ASP4 (which is still in beta stage).
Also:
-Added energy circle on ND
-Added software ECAM Control Panel
-Added Opencockpits MCDU V3 support
-Updated documentation

Regards
JL

[cmdr114b]

It is not. And I strongly suggest you do not install it.

Jeehell sorry about that, I assumed that because it was on your website that it was freely available.

John

[OmniAtlas]

Hi JL -- it seems if the newer IIT_v2.dll (FDS I/O) is selected for install IITcreator.exe is not installed by default. Should we install the legacy, and then the newer version?

Merci.

[jeehell]

Hi ben

it's a bug in the installer package, I will correct it.
Legacy IIT creator is NOT compatible... you need the V2 one...

JL

[OmniAtlas]

Thank JL - I was wondering why some of the logic of the I/O board was a little off - I was going a bit crazy trying to figure out if there was something Wrong with my wiring.

[OmniAtlas]

Hi JL, FYI -- for some reason Simpatcher does not 'patch' and is not installed onto P3D v4 (not seen in the top menu bar).

When installing I have selected the P3D v4.0, and Master FSX/P3D option for visual computer (P3D).

[jeehell]

Is it in the DLL.xml ?
Do you launch the starter on that computer? this is required to have widefmgs client running there. The addon menu entry will appear only after you have the whole software running.

[OmniAtlas]

Hi JL - there is nothing in the dll.xml file -- is FMGS suppose to edit and insert the simpatcher line on install, or do we do it manually with P3D4?

Yes, widefmgs client runs on this computer (P3D/Visual Generator/Client).

[jeehell]

it should have been done automatically...
I will check

[jeehell]

don't add the simpatcher.dll installed in current installer manually, it will not work. I am updating the installer...

[jeehell]

fix is online (auto update or http://www.jeehell.org/A320FMGS_B47.4.1.exe )

[Beret]

Hi Jeehell

Thanks alot for the new version.
I have a problem with the WXR. It will not work. Ther are no data in the WRX-folder. I have made a clean installation.
May you can help me to?

Best Regards
Guido

[adipdm]

Hello Jeehell

I have also the problem that in the wx folder are no files
Best Regards
Adrian

[jeehell]

Did you install the very latest version? (47.4.1)

[adipdm]

Hello jeehell

yes I have the current version (47.4.1) instaliert!


But unfortunately the wx folder remains empty

Best Regards
Adrian

[jeehell]

Check you have simpatcher in your dll.xml (in the app data/roaming folder)

[Beret]

It is in the dll.xml, and also in the Add-ons menu (Simpatcher B47.4)

[jeehell]

then are you sure you installed ASP4??

[Beret]

Yes, I have installed ASP4.

[Leonidas]

It is in the dll.xml, and also in the Add-ons menu (Simpatcher B47.4)

Me too, but empty WXR folder confirmed.

[jeehell]

ASP4 is up and running, and it can set weather?

[Beret]

Yes it runs and set the weather.

[jeehell]

Sorry but I have to ask: you use P3D V4?
Which version of windows?

[jeehell]

Try this one instead :
http://www.jeehell.org/SimPatcher.dll
(put it in c:\A320FMGS\simpatch on P3D PC).
It should make a log after running the software in c:\A320FMGS\logs\SimpatchLog.txt
I need the log... (after running the full software and ASP4 of course).

JL

[Beret]

Yes, I use V4 on Win 10. Will test it an load the log-file up.

[Beret]

Hi Jeehell

I have make a test with the new files. Now it works...
Here the log-files

[OmniAtlas]

Check you have simpatcher in your dll.xml (in the app data/roaming folder)

Ah, I was checking c:\ProgramData and not the %appdata% folder

Apparently the files are different. I have simpatcher installed now --
<SimBase.Document Type="Launch" version="1,0" id="dll">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Launch.Addon>
<Name>SIMpatcher</Name>
<Path>D:\A320FMGS\SimPatch\Simpatcher.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>as_connect</Name>
<Path>as_srv\as_connect_64.dll</Path>
</Launch.Addon>
</SimBase.Document>

Will test to see if weather is working tonight.

[FwFreak]

Hi JL!

I've installed the B47.4.1 now and SimPatcher is now active in P3D v4 Add-On menu but no files in the WXR folder. Is it correct, that there is a "Module Start 46.1.10" in the SimpatchLog.txt?

[jeehell]

No it is not... Try this one http://www.jeehell.org/SimPatcher.dll. (Only for P3D v4)

[dkreiskott]

Hi All,

yesterday evening I made the update to 47.4.1. After this I do a short and quick flight and found two Problems.

1. On the ND the flight path is not displayed
2. I can turn on Terr on ND and I see it on the ND, but if I turn off Terr on ND it is displayed on the ND. I can't switch off.

Can anyone confirm this Problem?

Regards Dieter

[FwFreak]

No it is not... Try this one http://www.jeehell.org/SimPatcher.dll. (Only for P3D v4)

I tried with your file but when I start ASP4 I get this error messege immediately. Any idea?
http://www.mycockpit.org/forums/attachment.php?attachmentid=12351&stc=1

[FwFreak]

I don't know why, but after getting this error a few times, it works now. No error and .dat files in the WXR folder.

Can it be, that a incompatible addon airport causes such an error? I've disabled Aerosofts EDDL between the tests (it's not made for P3D v3/4).

[OmniAtlas]

Hi JL -- with the latest version interfaceITAPI.dll does not install on default with the new dlls.

Thank you.

[OmniAtlas]

Hi JL -- I am using the older interfaceITAPI.dll -- does the new Jeehell_IIT_v2.dll also require a newer interfaceITAPI.dll?

I am seeing a lot of confusion with the I/O boards -- multiple outputs (on the software) turn on the same LEDs for example, when they are wired to different LEDs. I have recheck the wiring and there does not seem to be any cross over.

I am assuming the old interfaceITAPI.dll is also not compatible?

Would you just suggest using legacy FDS drivers?

Thank you.

[OmniAtlas]

Hi JL -- it seems there was an extra 8+1 ground output wire not connected to anything. For some reason this was interfering with the FDS logic board, so it seems there is nothing wrong with your software :)

I have gone back to using legacy FDS I/O drivers as I do not want to reprogram the switches and output again.

Thank you.

[OmniAtlas]

I tried with your file but when I start ASP4 I get this error messege immediately. Any idea?
http://www.mycockpit.org/forums/attachment.php?attachmentid=12351&stc=1

I also get the same simpatcher error.

No weather radar WXR output with the simpatcher included with the 47.4.1 install version (On the menu bar it says it is installed).

[jpromeroa]

Hi JL,

I found a small issue with the software that makes it crush.

In the Direct To (DIR TO) page of the MCDU, if by mistake you insert a data in the 3rd right prompt (WITH ABEAM PTS->), all hardware stop communicating with Jeehell and you have to reset A320 FMGS to make it work again.

Of course the idea was to insert the data in the RADIAL IN/OUT prompt but by mistake I inserted in the ABEAM PTS prompt and it crushed.

Hope this helps you out!

JP
http://www.mycockpit.org/forums/attachment.php?attachmentid=12364&stc=1

[dkreiskott]

Hi Jean Luc,

I do a test in this evening. The Problem still persists, I ha None flight route on the ND. This problem is since the update from yesterday.

I need your help.

Regards Dieter

[OmniAtlas]

The ABEAM crash issue has been noted on the bug tracker list.

[jeehell]

Hi Jean Luc,

I do a test in this evening. The Problem still persists, I ha None flight route on the ND. This problem is since the update from yesterday.

I need your help.

Regards Dieter
Did you rebuild the navdata?
Did you try restarting the server?

[jeehell]

I also get the same simpatcher error.

No weather radar WXR output with the simpatcher included with the 47.4.1 install version (On the menu bar it says it is installed).
FwFreak and Omniatlas :can you post your c:\A320FMGS\Logs\simpatchlog.txt (on P3D PC)?

[jeehell]

Hi JL -- I am using the older interfaceITAPI.dll -- does the new Jeehell_IIT_v2.dll also require a newer interfaceITAPI.dll?

I am seeing a lot of confusion with the I/O boards -- multiple outputs (on the software) turn on the same LEDs for example, when they are wired to different LEDs. I have recheck the wiring and there does not seem to be any cross over.

I am assuming the old interfaceITAPI.dll is also not compatible?

Would you just suggest using legacy FDS drivers?

Thank you.
interfaceITAPI.dll is the same for both FDS drivers. I will include it in the installer for the V2 option.

[jeehell]

Can it be, that a incompatible addon airport causes such an error? I've disabled Aerosofts EDDL between the tests (it's not made for P3D v3/4).
I don't think it has anything to do with airports addon, at least not from my software point of view.
Either the module from ASP4 is crashing, or mine is crashing because it uses the ASP4 module in a wrong way.
I did not get that error myself so I do not know and will look at it...

[dkreiskott]

Did you rebuild the navdata?
Did you try restarting the server?

Yes on both.

Bevor I made an update, I backup all five Computers. In the Morning I restore all Computers (Folder A320FMGS) to v47.3 and make a testflight. All works.

Then I made the Update to v47.4.1 and make a testflight too. No flightpath on the ND.

At this Point I uninstall all five Computers and install 47.4.1 on all Computers new. Then I create the navdata on the FSX Computer and distribute the files for CPT, FO and FMGS Server computer.

Next I copy the config files from the Backup (*.ini files and acontrols.cfg) to the Computers.

At this moment all works fine. I don't understand why the update doesn't work correct?

And a question, if I must do the update via full installer, I lose some configuration files. For example the starter.ini on all Computers and the aircraft.ini in Folder PERF\PA320.

This is not a good Situation on five computers, especially I use starter.ini to load modules and Programs.

Regards Dieter

[dkreiskott]

And I found another Problem in ND switched to plan. The route is broken, but in FMC all is OK.
The flight is OK too.

You can see it in the screenshot.

http://www.mycockpit.org/forums/attachment.php?attachmentid=12365&stc=1

[jeehell]

Dieter,

Starter.ini configuration is done by the installer depending on what options you selected. If you end up with a different starter.ini file after update, this means you did not select the same options.
There was a change in the FMGS config files, but it should have been backwards compatible. Some people reported that after a reconfiguration of the flight controls it was then working correctly.
Aircraft.ini file: there will be a tool for that in a future version.




And I found another Problem in ND switched to plan. The route is broken, but in FMC all is OK.
The flight is OK too.

You can see it in the screenshot.

http://www.mycockpit.org/forums/attachment.php?attachmentid=12365&stc=1

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 is not a good Situation on five computers, especially I use starter.ini to load modules and Programs.

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...

[FwFreak]

FwFreak and Omniatlas :can you post your c:\A320FMGS\Logs\simpatchlog.txt (on P3D PC)?

Here is my log file.

I only start P3D4 and when ASP4 is injecting the weather the error occurs.


Thanks for your help!


http://www.mycockpit.org/forums/attachment.php?attachmentid=12366&stc=1

[OmniAtlas]

Hi JL -- with the new simpatcher P3D displays the erorr message and regardless if AS 2017 is open or not. Here is what the log file says:

Module Start 47.4
Friction Hack OK
FF Hack OK
SIMCONNECT_RECV_ID_OPEN...
SIMCONNECT_RECV_ID_OPEN OK
found as_connect_64.dll
loaded AIR FIle:D:\A320FMGS\Aircraft\A320-214\cfm56_5B4.air
loaded AIR FIle:D:\A320FMGS\Aircraft\A320-214\cfm56_5B4.air

When AS2017 is loaded P3D hard crashes.

[jeehell]

Hi JL -- with the new simpatcher P3D displays the erorr message and regardless if AS 2017 is open or not. Here is what the log file says:

Module Start 47.4
Friction Hack OK
FF Hack OK
SIMCONNECT_RECV_ID_OPEN...
SIMCONNECT_RECV_ID_OPEN OK
found as_connect_64.dll
loaded AIR FIle:D:\A320FMGS\Aircraft\A320-214\cfm56_5B4.air
loaded AIR FIle:D:\A320FMGS\Aircraft\A320-214\cfm56_5B4.air

When AS2017 is loaded P3D hard crashes.
Ben, after acknowledging the crash, what happens? P3D continues to work normally? what about the WXR?

[FwFreak]

For me, when I quit the error messege with 'Ok', P3D crashes to the desktop immediately. Or what do you mean?

[dkreiskott]

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.



> 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?



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

[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

[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
but the date of this file seems to be old - ist from 26th of March 2017 - so it seems that this info will not help very much - right ?

[fisfro]

here it is:

[QUOTE=jeehell;168439]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
but the date of this file seems to be old - ist from 26th of March 2017 - so it seems that this info will not help very much - right ?

[fisfro]

Hello JH,

bin files have been produced :-) - I have restarted everything and manualy started th fmgsserver
Also recalibration was succesfull - so thanks very much

Robert

[Leonidas]

This ILS LOC again... Almost every runway's LOC is wrong. :sad: :sad: :sad:
What I've done so far:

1. Rebuild 1706 bin files
2. Update fixes, NAVAIDs and Magvar data from www.aero.sors.fr
3. Try 1705 AIRAC
4. Disable scenery addons

Still many meters away from right path!!!
Something else happens, but what?

[spiliot]

Leonidas this might be far fetched but reminds me a similar crazy error from the past. Do you have greek regional number settings on your computer? Would you mind switching everything to english and trying rebuilding everything again? Greek use comma for decimal separation and dot for thousands separation (1.234,56) which messes up calculations with numbers in english (1,234.56) when localization is not taken into account.

[Leonidas]

Leonidas this might be far fetched but reminds me a similar crazy error from the past. Do you have greek regional number settings on your computer? Would you mind switching everything to english and trying rebuilding everything again? Greek use comma for decimal separation and dot for thousands separation (1.234,56) which messes up calculations with numbers in english (1,234.56) when localization is not taken into account.

Wow !!! yes I do, even though the enviroment is English. I had no problem in v.3.4, but anyway I'll try it tomorrow.
Thanks a lot :)

[jeehell]

This ILS LOC again... Almost every runway's LOC is wrong. :sad: :sad: :sad:
What I've done so far:

1. Rebuild 1706 bin files
2. Update fixes, NAVAIDs and Magvar data from www.aero.sors.fr (http://www.aero.sors.fr)
3. Try 1705 AIRAC
4. Disable scenery addons

Still many meters away from right path!!!
Something else happens, but what?
Once again, you need to do the ILS/RWY fix. It is the only fix needed from aero.sors.fr, the other may be nice for your other addons. But my software only needs the ILS/RWY fix https://www.aero.sors.fr/navaids3.html

Also make sure you use admin rights, and your path in the c:\A320FMGS\navdata\fsscenery.cfg are correct.
The scenery.cfg path MUST include the scenery.cfg name!! (so it looks like scenery.cfg=c:\programdata\lockheed martin\prepar3d vx\scenery.cfg usually....)

[Gregor]

Hi JL

What are the correct entries in fsscenery.cfg in a networked configuration?

Cheers
Greg

[jeehell]

The correct entries are the same, because in a network configuration you still must build the navdata on the P3D PC. This setup IS complex, it requires you to manually copy the FMGS Server over to the P3D PC, build the navdata, etc...

[dkreiskott]

Hi All,

I have made a little tool that helps to create the navdata and distribute it to other PC's like FO and CPT Computers.
If a dedicated FMGS Server is in the Network, the tool can distribute the Navdata too.
It also checks the path for the scenery.cfg configured in FSscenery.cfg.
If the scenery.cfg can not be read it informs you.

After an update of the airac the tool can be started.
Then it makes the following steps automatically

1. Checks the fsscenery.cfg
2. delete the old navdata files
3. starts FMGS Server and wait for the process that all *.bin files are created
4. delete the navdata files on the Client computers
5. Copy all the required new files to the computers in the Network

It's easy to configure, only Network Shares are necessary.

For me it works in the Network. I would be glad if someone would like to test the tool.

http://www.mycockpit.org/forums/attachment.php?attachmentid=12372&stc=1

http://www.mycockpit.org/forums/attachment.php?attachmentid=12373&stc=1

Regards Dieter

[cmdr114b]

This sounds very useful and I would be very happy to test it on my system for you.
John

[dkreiskott]

Hi,

I send you a PM with a link for the download.

Dieter

[OmniAtlas]

Hi,

I send you a PM with a link for the download.

Dieter

Please let me know when this comes out of beta and I will put a link on the website, thanks.

[dkreiskott]

Please let me know when this comes out of beta and I will put a link on the website, thanks.

Hi Omni,

yes I will do, but I wait for an information from Jean Luc, to make a little change for users he has a dedicated FMGS Server.
After this i will make it availabe for free at my Website.

Regards Dieter

[cmdr114b]

Hi,

I send you a PM with a link for the download.

Dieter
Thank you Dieter, I will try it out over the weekend.
John

[Leonidas]

Hi
After all is there anyone who's WRX is working under P3D v.4 and how, or we're waiting some update?
Regards

[Beret]

Hi Leonidas

The WXR is working by me. I have load the SimPatcher.dll from Jeehell. http://www.jeehell.org/SimPatcher.dll
Regards

[SSO]

Hi.Just installed 47.4.1.The aircraft loads fine and all connects. :-)When going to an outside view that is behind the main landing lights all is also ok.When moving the "camera" forward of the main landing lights (approximate) P3Dv4 Crashes... It was during night time - at daytime I can slew in front no problem...Anyone else experience this?

[FwFreak]

Hi JL!

Since today the simpatcher.dll crashes my P3D V4 every time I try to start it. I haven't changed something since yesterday where I did a 3 hours flight without any problems (perhaps a hidden windows or .NET runtime update?).

The event log looks like that:


Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 4.0.23.21468, Zeitstempel: 0x59279be2
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.15063.0, Zeitstempel: 0xb79b6ddb
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000001992e
ID des fehlerhaften Prozesses: 0x205c
Startzeit der fehlerhaften Anwendung: 0x01d2e61ba2c94156
Pfad der fehlerhaften Anwendung: D:\Prepar3D v4\Prepar3D.exe
Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll
Berichtskennung: 17085a24-4caf-4d07-8741-9326b11ee4a9
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:


I did P3D rebuild its data files (scenery.cfg/dll.xml/exe.xml) to find the issue and it occurs when adding the simpatcher.dll to the dll.xml file. Without the simpatcher.dll P3D works without problems. The bad file is the dll which Jeehell installed automatically.

If I choose the "new" simpatcher (I've tested to get the WX radar working) the P3D start crash is gone, but I still get an error (with crash) when ASP4 injects the weather.


Do you (or another one) have an idea what I can do?

[jeehell]

I have no idea, I am still looking for the problem since I cannot reproduce it myself...
It could be a win10 update (creator update?) but I do not know at all...

I had an issue once which drove me crazy, I cannot find the reason for it yet but:
Windows applies some sort of compatibility flag on simpatcher module (for unknown reasons), called "IgnoreFreeLibrary".
If this is your issue, you need to look in the registry, in [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers] and remove anything related to simpatcher.dll with "ignorefreelibrary".

Regards
Jean Luc

[Beaufort]

I have P3Dv3.4 and v4.0 installed side by side, also AS16 for P3D (v3) and the new version AS for P3Dv4.
P3Dv3 / AS16 old version injects the WXR##.dat files in WXR folder for JeeHell B47.3 as well as for B47.4.1 (I will tell later to my other problem, why I have both installed for v3). But P3Dv4 / AS16 new version does not inject any file to my JeeHell B47.4.1 installation for v4 (neither to my JeeHell installations for v3). I tried the simpatcher.dll linked above by Beret, no effect. And there are "ignorefreelibrary" flags set in my registry only for FSC (Flightsim Commander), but not for simpatcher.dll .
Another problem: When I use B47.4.1 with P3Dv3, the MCDUs do not load the Navdatabase (bins are made from P3Dv3):
http://www.mycockpit.org/forums/attachment.php?attachmentid=12378&stc=1
I do not have the problem when I use my other installation of B47.4.1 with P3Dv4. Is B47.4 not compatible to P3Dv3 any more?
When I use B47.3 (and this is why I still keep my old installation of that version), the navdatabase is correctly loaded.
Last question: Starting B47.3 the green "Self Test" appears on the screen. This is gone with B47.4. Intentional or only in my system?
THX for help!
EDIT: problem solved, Post 492 + 511

[dkreiskott]

I have P3Dv3.4 and v4.0 installed side by side, also AS16 for P3D (v3) and the new version AS for P3Dv4.

Last question: Starting B47.3 the green "Self Test" appears on the screen. This is gone with B47.4. Intentional or only in my system?
THX for help!

Hi,

you made the update with the full installer?

then you must set the Setting in c:\A320FMGS\FMGS Server\PERF\PA320\Aircraft.ini

EISmodel=2


Regards Dieter

[dkreiskott]

Another problem: When I use B47.4.1 with P3Dv3, the MCDUs do not load the Navdatabase (bins are made from P3Dv3):
http://www.mycockpit.org/forums/attachment.php?attachmentid=12378&stc=1
I do not have the problem when I use my other installation of B47.4.1 with P3Dv4. Is B47.4 not compatible to P3Dv3 any more?
When I use B47.3 (and this is why I still keep my old installation of that version), the navdatabase is correctly loaded.
Last question: Starting B47.3 the green "Self Test" appears on the screen. This is gone with B47.4. Intentional or only in my system?
THX for help!

Hallo Rainer,

eigentlich kann das doch nicht funktionieren, außer Du hättest in beiden P3D Versionen exakt die gleichen Scenerien installiert.
Und wohin zeigt Dein Pfad in der FSscenery.cfg für die scenery.cfg.

Generiere doch mal unter P3D v3 die Navdata. Ich glaube nicht dass es etwas mit der Kompatibilität zu tun hat, da ich noch den FSX nutze und es auch dort funktioniert.

Grüße Dieter

[OmniAtlas]

Hi JL - simpatcher.dll is not listed in [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]

Instead I have the following:

http://www.mycockpit.org/forums/attachment.php?attachmentid=12379&stc=1

I no longer have A320FMGS in C:\ so I will delete these lines.

Perhaps P3D v4 also has to run in admin mode?

[spiliot]

Last year I started seeing sudden P3D crashes in a C++ FS module I had written for my own use. I didn't change anything in the code, it just started happening out of the blue. I went back to code that I knew worked, nothing. I started removing code to see what might be the cause, nothing. The only way P3D would start was to never call anything from my module. Even a simple addition of two numbers would make it crash.

After several lost days of trying everything and nothing making sense, even re-installing P3D fresh, I found that everything would work again if I changed the filename of the module(!!!). The same dll that didn't work before worked fine after renaming to a new file. Rename it back, crash. I couldn't find any entry in P3D files and the registry that would persist the filenames so I gave up.

A few days later, the same thing happened, only then I realized immediately what had happened. I had disabled windows defender and run P3D while defender was disabled. After doing that just once, it didn't matter if windows defender was enabled or not, or if the modules, P3D folder, etc where added to the exclusion list, I would still get the crash and that dll name was "burned" forever in my system. Still today I have about 10 names that I can't use (until I format the computer obviously).

I don't know if this applies to anyone here but worth investigating if you've disabled defender and run P3D at any time.

[FwFreak]

Hi!

For the "new" simpatcher.dll:
I've looked into my registry too, but no entry of the simpatcher. I also tried to deactivate the windows defender but no change.

BUT a friend found a workaround!
- Start P3D and a scenario
- Start ASP4
- When the application error occurs, do NOT click "OK" and switch the focus back to the P3D main window.
- When starting Jeehell the SimPatcher is listed in the AddOn menu, wx files are written (and updating) and wheather is shown at the ND

Perhaps it can help you to find the error.

http://www.mycockpit.org/forums/attachment.php?attachmentid=12386&stc=1

[jeehell]

Hello,

I tried to correct the simpatcher/WXR issue, you can try it here (not yet an official release):
http://www.jeehell.org/A320FMGS_B47.5.exe

Regards
JL

[masterp]

I got EIS.exe lag with 47.4.1. PFD & ND on client computer is lagging (working like slide show photo)
I went back to previous version (47.3+EIS.exe updated via auto-update) and PFD&ND working really smooth as normal.

Anyone got the same problem with 47.4.1?

[dkreiskott]

I got EIS.exe lag with 47.4.1. PFD & ND on client computer is lagging (working like slide show photo)
I went back to previous version (47.3+EIS.exe updated via auto-update) and PFD&ND working really smooth as normal.

Anyone got the same problem with 47.4.1?


I found a similar situation in MCDU.

If I input the FROM/TO Airprts the LSK1R act after 4-5 seconds or I must press the button multiple.
The same is on selecting runway and then SID or STAR.

In 47.3 I can't see this behavier.

[McKoy]

I have the same "problem" since 47.4.1
The ND Compass Rose turns step by step and not so smooth like in the versions before. First i blame it on the windows defender after the last windows update (Creators Update). The defender gives me a CPU workload from about 45 - 50% on the clients. Maybe it isn't the defender.

greetings
Marc