Jump to content

"PMCO - Pilot Monitoring Callouts" - ask and discuss HERE


NilsUnger

Recommended Posts

Calum Watt
34 minutes ago, NilsUnger said:

Hi Calum,

I think the issue comes from the ini file.

[Auto.FSL_A32X]

x=Lua PMCO  <<<<<< replace x with 1

 

All the rest looks okay to me. You don't need widefs for PMCO to function.

Cheers

Hi Nils,

Excellent. I changed that as you advised and it is working now.

Thank you very much for your help, and for getting back to me so quickly. 

I must say, having just flown a quick circuit with the add on, it reality improves the enjoyment and immersion of the aircraft.

Thanks again!

  • Like 1
Link to post
  • Replies 292
  • Created
  • Last Reply

Top Posters In This Topic

  • NilsUnger

    92

  • Alexander Luzajic

    34

  • Peter Pukhnoy

    15

  • Pat Brooks

    12

Top Posters In This Topic

Popular Posts

This is the right place to ask for support, discuss the matter or maybe even give praise to the creators of the PMCO Lua script. Download it from here:      

Short video showcasing PMCO. Good job gents!  

I have finished my next addition to the script. It is the automatic detection of the default (FSLabs) V1 callout setting. I ran into situations where both V1 callouts were played, the one from PMCO

Posted Images

Steve Foster

Hi Nils,

Since installing the TCA throttle quadrant and keeping the default indents it came with I find that I am not getting a "FLEX SET" call any longer.

Since nothing else has changed in my setup and the PMCO_Sounds folder is intact I'm guessing it's because the default gates possibly do not now line up with the settings in your PMCO lua file.

My A320ThrustLevers.ini settings are:

[GateControls_0]
DIS_270=6144
Min_TLA_RevMax=-10000
Max_TLA_RevMax=-9500
Min_TLA_RevIdle=-8500
Max_TLA_RevIdle=-6000
Min_TLA_Idle=-5500
Max_TLA_Idle=-3500
Min_TLA_CL=-500
Max_TLA_CL=500
Min_TLA_FLXMCT=4500
Max_TLA_FLXMCT=6000
Min_TLA_TOGA=9000
Max_TLA_TOGA=10000
[GateControls_1]
DIS_270=6144
Min_TLA_RevMax=-10000
Max_TLA_RevMax=-9500
Min_TLA_RevIdle=-8500
Max_TLA_RevIdle=-6000
Min_TLA_Idle=-5500
Max_TLA_Idle=-3500
Min_TLA_CL=-500
Max_TLA_CL=500
Min_TLA_FLXMCT=4500
Max_TLA_FLXMCT=6000
Min_TLA_TOGA=9000
Max_TLA_TOGA=10000

The figures above line up perfectly with the default gates on my TCA throttle quadrant after it has been calibrated, with a bit of leeway either side. I'm guessing that it has something to do with the values in your file but I'm not going to play around with it without your permission and I don't really know enough about it anyway to even try.

Any help would be appreciated, thanks in advance.

Link to post
NilsUnger

I will have a look.

Edit:

If I'm not totally mistaken the script reads the position of the actual thrust lever in the virtual cockpit. To be precise, the position of the left thrust lever.

This means it should be completely independent of the user's hardware setup. Please check you really set the levers in the right detent. One more criteria is that N1 needs to be higher than 80%.

If you have a fsuipc.log I could further investigate.

Link to post
Rado Sutto

I have problem with PMCO, it doesn't work. In FSUIPC.LOG i found error :

95110 Aircraft="FSLabs A320X IAE - FSLabs - British Airways (G-EUYE)"
   101719 Starting everything now ...
   101719 *** LUA Error: error loading module 'socket' from file 'socket':
    socket: bad header in precompiled chunk
   101735 ASN active function link set

 

PMCO latest version downloaded yesterday, FSL A320 v151, P3D v4.5 HF3, FSUIPC5.

What is wrong ?

Link to post
NilsUnger
3 minutes ago, Rado Sutto said:

Thx in advance.

Would you mind attaching the full log? You can delete your credentials in the top section. Thanks.

Was it working at some point or are you new to PMCO?

Link to post
Rado Sutto

I'm totally new in PMCO. This is my last log, I started P3D, airport and aircraft has been selected in the main menu, then "OK", when all was loaded, I checked log and found that error. Then I ended P3D session.

********* FSUIPC5, Version 5.103 (26th June 2017) by Pete Dowson *********
Running inside Prepar3D v4
Windows 10 Enterprise 64 Bit reported as Build 18363, Release ID: 1909 (OS 10.0)
Prepar3D.exe version = 4.5.14.34698
        0 System time = 30/04/2021 13:50:07
        0 FLT UNC path = "C:\Users\Rado\Documents\Prepar3D v4 Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 4.5.14.34698
        0             api.dll: 4.5.14.34698
        0        controls.dll: 4.5.14.34698
        0      fs-traffic.dll: 4.5.14.34698
        0             G3D.dll: 4.5.14.34698
        0        language.dll: 4.5.14.34698
        0            sim1.dll: 4.5.14.34698
        0        visualfx.dll: 4.5.14.34698
        0         weather.dll: 4.5.14.34698
        0          window.dll: 4.5.14.34698
        0 ----------------------------------
       15 FS UNC path = "C:\Program Files\Lockheed Martin\Prepar3D v4\"
       93 ---------------------- Joystick Device Scan -----------------------
      109 Product= T.Flight Hotas X
      109    Manufacturer= Thrustmaster
      109    Vendor=044F, Product=B108 (Version 1.0)
      109    GUIDs returned for product: VID_044F&PID_B108:
      109       GUID= {E85E7700-08B1-11EA-8004-444553540000}
      109       Details: Btns=12, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V0,X1023,Y1023,Z255
      109 -------------------------------------------------------------------
      140 Device acquired for use:
      140    Joystick ID = 0 (Registry okay)
      140    0=T.Flight Hotas X
      140    0.GUID={E85E7700-08B1-11EA-8004-444553540000}
      140 -------------------------------------------------------------------
      156 LogOptions=00000000 00000001
      156 SimConnect_Open succeeded: waiting to check version okay
      156 Opened separate AI Traffic client okay
     3640 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.14.34698 (SimConnect: 4.5.0.0)
     3640 Initialising SimConnect data requests now
     3640 FSUIPC Menu entry added
     3703 C:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
    51921 C:\Users\Rado\Documents\Prepar3D v4 Add-ons\FSLabs\SimObjects/Airplanes\FSLabs A320 IAE\A320.air
    99359 Aircraft loaded: running normally now ...
    99359 User Aircraft ID 2 supplied, now being used
   102437 System time = 30/04/2021 13:51:50, Simulator time = 13:50:36 (11:50Z)
   102437 Aircraft="FSLabs A320X IAE - FSLabs - British Airways (G-EUYE)"
   109000 Starting everything now ...
   109000 *** LUA Error: error loading module 'socket' from file 'socket':
	socket: bad header in precompiled chunk
   109062 ASN active function link set
   109062 Ready for ASN WX radar
   110171 Advanced Weather Interface Enabled
   116609 Weather Mode now = Theme
  1481718 Sim stopped: average frame rate for last 1384 secs = 38.1 fps
  1481718    Max AI traffic was 3 aircraft (Deleted 0)

 

Link to post
Steve Foster

Hi Nils,

I've checked a few things with regards to me not getting a FLEX SET call and have included a number of screenshots and my FSUIPC log as requested.

If you look at the attached pdf file you will see screenshots showing the throttle detent settings from the MCDU alongside the cockpits actual throttles and as far as I can tell all of the set positions line up properly with the actual throttle location and the Green Text at the top of the screen seems to confirm this to.

The final page of the pdf shows the actual flight to which the FSUIPC log relates and as you can see the FMA is showing MAN FLX +70 the N1 is greater than 80% and the THR POS in the MCDU shows that the throttle lever would be in the FLX MCT gate, however, no FLEX SET call was made, all other calls were heard as expected.

Now for the slightly weird bit, if I set the flight up in the same way but this time hold it on the brakes or chocks and advance a thrust lever into the FLX MCT gate, once the N1 has got just over 80% I do hear a FLEX SET call, as long as the aircraft is not moving it plays!

Hope this may be of some help but have to admit to being slightly stumped right now.

Thanks,

Steve.

FSUIPC6.log

Thrust Lever Positions.pdf

 

Link to post
NilsUnger

Yeah, will check again. I guess the script timing has problems with your very light aircraft (Vr of 119?) and it's acceleration. The 100 call kills the flex call. This is an edge case.

Link to post
NilsUnger

On top, we don't know exactly what the N1 is as the IAE shows EPR. The easy fix would be to lower the limit to 70 or 75 N1 for the trigger. Though, for most cases the call would come early then. The problem is, I can't read the target thrust to use it for comparison.

Link to post
Steve Foster

Hi Nils,

Just tried exactly the same flight as before but this time loaded the aircraft up a lot more had a ZFW of 62.1 and 5.0 fuel, that gave me a V1 & Vr of 140, unfortunately still no FLEX SET call.

I will try your suggestion tomorrow and see if it makes any difference, I'm sure it's related to the TCA throttle quadrant because when I used my Saitek throttle before it used to work.

Need to find someone with a TCA throttle set up who also uses your PMCO file and see if they have the same problem or if it is just my setup.

Link to post
NilsUnger
43 minutes ago, Steve Foster said:

I'm sure it's related to the TCA throttle quadrant because when I used my Saitek throttle before it used to work.

Yes, that's weird. But I don't think it's that. I can see in the log, that you were in takeoff phase. For that alone, the thrust lever needs to be either in FLX or TOGA detent. So that's working. Also you said, if you hold the brakes it's working. What was your FLX temp the last time you tried? I still think it's a timing issue reaching N1 80% late.

The logging of my code is not detailed enough to see the reason for the skipping. I will work on that.

Link to post
NilsUnger

I uploaded V2.2 of PMCO, if anyone is interested. Please see the changelog for more details. Thank you.

  • Like 1
  • Thanks 3
Link to post
  • 2 weeks later...
NilsUnger
7 minutes ago, Pat Brooks said:

PMCO v2.2 is not working for me using the new sharks.

Yes, I know. :)

I'm already testing a new version. Will try to upload tomorrow. Fix is easy but I want to test a little more.

  • Like 2
  • Thanks 2
Link to post
Alexander Luzajic
On 5/13/2021 at 6:20 PM, NilsUnger said:

You (and others) may try this, until I upload a new version.

Overwrite the existing file.

PMCO.lua 40.06 kB · 26 downloads

[Profile.FSL_A32X]
  1=FSLabs A320X
  2=FSLabs A319X
  3=FSLabs A321X

 

I assume this will works with SL even though not there....?

Link to post
António Abreu
On 5/13/2021 at 11:20 PM, NilsUnger said:

You (and others) may try this, until I upload a new version.

Overwrite the existing file.

PMCO.lua 40.06 kB · 38 downloads

Not working with me, the girl is too quite ...

[Edit] Was using V2.1, now with V2.3 and the temporary fix (PMCO.lua) above, will try it this afternoon and come back here. PS: am using a female voice I found somewhere in this forum.

Link to post
Stefan van Hierden
1 hour ago, António Abreu said:

Not working with me, the girl is too quite ...

[Edit] Was using V2.1, now with V2.3 and the temporary fix (PMCO.lua) above, will try it this afternoon and come back here. PS: am using a female voice I found somewhere in this forum.

I don’t think the fix above is needed with V2.3.

Link to post
NilsUnger
2 hours ago, António Abreu said:

Not working with me, the girl is too quite ...

[Edit] Was using V2.1, now with V2.3 and the temporary fix (PMCO.lua) above, will try it this afternoon and come back here. PS: am using a female voice I found somewhere in this forum.

If you can hear callouts it's working. If the callouts are too quiet you have to check the volume settings for that voice set. There is a cfg for that.

Link to post
António Abreu
2 hours ago, NilsUnger said:

If you can hear callouts it's working. If the callouts are too quiet you have to check the volume settings for that voice set. There is a cfg for that.

Hi Nils,

today I reinstalled the zip file V2.3 "by the book", tested and all worked fine. I think that somehow the FSUIPC.ini file got messed, I don't know if it was during the installation of the FSLabs A320 sharklets or because I had V2.1 before and installed on top of it. Anyway, all is good now and I thank you again for your work. These days I don't know how to fly without those callouts! :)

Have nice landings

Link to post
NilsUnger
1 hour ago, António Abreu said:

V2.3 "by the book"

If you installed it today 'by the book', that's probably the reason it's working again. I made the necessary changes in the readme.

I'm working on a way to simplify the install process. I want to get rid of this FSUIPC profile step. I get so many support questions because of that. It must end. :lol:

  • Thanks 1
Link to post
Marc Delaloy

Hello Nils, what did you mean by "ALL FSLABS products"? 

[Profile.FSL_A32X]
 1=FSLabs A3 ;this references ALL FSLabs Airbus products (all variants)

 

regards

Marc

 

I have that in my FSUIPC.ini

image.png.a0d5ebf945e631fbb0fa21bbd3062e23.png

Link to post
NilsUnger
3 minutes ago, Marc Delaloy said:

Hello Nils, what did you mean by "ALL FSLABS products"? 

[Profile.FSL_A32X]
 1=FSLabs A3 ;this references ALL FSLabs Airbus products (all variants)

 

regards

Marc

 

I have that in my FSUIPC.ini

image.png.a0d5ebf945e631fbb0fa21bbd3062e23.png

They renamed the whole aircraft range for some reason (commonality?). What you have in your ini will no longer work (or is it working for you?).

With all products I mean every Airbus model they released.

As said, I'm working on a solution without the need of profiles to make it simpler.

  • Thanks 1
Link to post
Marc Delaloy
14 minutes ago, NilsUnger said:

‎Ils ont rebaptisé toute la gamme d’avions pour une raison quelconque (point commun?). Ce que vous avez dans votre ini ne fonctionnera plus (ou est-ce que cela fonctionne pour vous?). ‎

‎ Avec tous les produits, je veux dire tous les modèles Airbus qu’ils ont libérés. ‎

‎ Comme dit, je travaille sur une solution sans avoir besoin de profils pour le rendre plus simple.‎

Currently nothing work in WTF & SL. I didn't show Displayed Status message despite option is set to 1.

Link to post
Dick Riddersma

For me it works fine. The only thing I needed to do ( after having updated the LUA file with the new one that Nils provided) was to add each individual livery to the profile in FSUIPC.

Link to post
NilsUnger
6 minutes ago, Dick Riddersma said:

For me it works fine. The only thing I needed to do ( after having updated the LUA file with the new one that Nils provided) was to add each individual livery to the profile in FSUIPC.

Yes, that was also my interim solution. But obviously it's a pain. Especially for user's without experience with FSUIPC. I'm uploading a new version that works completely without profiles. It will be available in a few minutes.

  • Thanks 1
Link to post
Dick Riddersma

Nils.. there is an easy shortcut that works for me.

Once in the livery that needs to be added open FSUIPC in the P3D top menu. Go to axis assignment ( I have axis assigned) and move one of the assigned axis and after that check the "profile specific" box. FSUIPC will add the livery in question to the ini file..

You will need to restart P3D for the change to take effect.

  • Thanks 1
Link to post
NilsUnger
2 minutes ago, Dick Riddersma said:

Nils.. there is an easy shortcut that works for me.

Once in the livery that needs to be added open FSUIPC in the P3D top menu. Go to axis assignment ( I have axis assigned) and move one of the assigned axis and after that check the "profile specific" box. FSUIPC will add the livery in question to the ini file..

Thanks Dick, I know this and this is what I also do. Still it's not optimal. I get MANY support requests via PM and they almost always are about profile setup of FSUIPC.

Link to post
NilsUnger

I just uploaded Version 2.4 of PMCO.

From now on, if you want the script to start automatically, there is no need for FSUIPC profiles anymore.

The [Auto] section of your FSUIPC5.ini or FSUIPC6.ini respectively, should contain the lua call of PMCO.

[Auto]
1=Lua PMCO

This is the "global" [Auto] section of FSUIPC. That means, PMCO always starts when you start a flight, even if it is with another aircraft than FSLabs Airbus. The script itself then looks for the active aircraft and terminates, if it's not a FSLabs addon.

If you have setup any profiles in your ini just for PMCO, you can now delete these entries.

Link to post
NilsUnger
55 minutes ago, Marc Delaloy said:

Currently nothing work in WTF & SL. I didn't show Displayed Status message despite option is set to 1.

Please try the new version 2.4 and follow the instructions. Thanks.

1 minute ago, NilsUnger said:

I just uploaded Version 2.4 of PMCO.

From now on, if you want the script to start automatically, there is no need for FSUIPC profiles anymore.

The [Auto] section of your FSUIPC5.ini or FSUIPC6.ini respectively, should contain the lua call of PMCO.


[Auto]
1=Lua PMCO

This is the "global" [Auto] section of FSUIPC. That means, PMCO always starts when you start a flight, even if it is with another aircraft than FSLabs Airbus. The script itself then looks for the active aircraft and terminates, if it's not a FSLabs addon.

If you have setup any profiles in your ini just for PMCO, you can now delete these entries.

 

  • Like 1
Link to post
Marc Delaloy

Working fine in my sim, I have also updated FSUIPC to the lastest version.

Thanks for your hard working

  • Thanks 1
Link to post
Søren Rasmussen

Just to make this clear.

I have the following 'AUTO' section in the FSUIPC6.ini:

[Auto.FSLabsA3XX]
1=Lua gsxautopilot
2=Lua PMCO
3=Lua PMCOMCDU
4=Lua brakes


Should I add another 'AUTO' section as follows:

[Auto]
1=Lua PMCO
 

and just remove that line from the first, or?

Link to post
NilsUnger
1 minute ago, Søren Rasmussen said:

Just to make this clear.

I have the following 'AUTO' section in the FSUIPC6.ini:

[Auto.FSLabsA3XX]
1=Lua gsxautopilot
2=Lua PMCO
3=Lua PMCOMCDU
4=Lua brakes


Should I add another 'AUTO' section as follows:

[Auto]
1=Lua PMCO
 

and just remove that line from the first, or?

Yes. Please remove line 2 AND 3 from your old profile and try that.

  • Thanks 1
Link to post
Safak Cayli

I have an issue, It was working with WTF version but I just update PMCO but with SL version it did not work for me

Link to post

×
×
  • Create New...