Knoblet

OK earlier this morning but now no connection to RT server

Checking through PSXT logs have been seeing references to end of licence such as;

License ends in 33 days

What licence is this? My RT licence ends in October.

Norm

P3Dv5.3 for the last 5 days or so

Very relieved to see I am not yhe only one with these issues

😄 I just knew you would say that! 😄

OK Nico thanks

I much prefer to see RT 'radar' screen on another computer because I fly many flights following real world flights using OFP's from my commercial pilot friends but if your new setup makes your life easier then so be it.

Everything is working ok networked but ai seems to be a little more 'jerky'. Any suggestions?

Had no choice but to update to latest version today and now no connection to RT.

I have always run RT on a laptop over my private network with no problems with previous versions.

Do I still need to add     <parameter name="PSXT_RT_SAME_COMPUTER" value="false" /> to parameter file?

I did try it and still no connection. Something is very broken

Fixed with many thanks..........yet again 😂

OPIS is installed in my third party folder yet PSXT does not recognise it and gives a message of:

"User aircraft on the ground with a lat long (which by checking the airport bgl with ADE is correct)  and no airport in sight"

Is this because as a relatively new aiport it is not included in default scenery but the old one OPRN is?

Of course 🙂 I did not think to look there. I will change myself and wait for the udate.

Many thanks for the superb support.

Norm

As requested:

[General]
atc_type=AIRBUS
atc_model=A359
editable=0
performance=VERY GOOD
Category=AIRPLANE

[fltsim.26]
title=AIGAIM_Lufthansa Airbus A350-900 - IC
sim=utt_a350_900
model=OW
texture=DLH-Lufthansa_IC
atc_airline=LUFTHANSA
atc_heavy=1
atc_parking_types=GATE
atc_parking_codes=DLH
ui_manufacturer="United Traffic Team (UTT)"
ui_type=Airbus A350-900
ui_variation=Deutsche Lufthansa AG
ui_createdby=Provided by: JB Filename: UTT A359 Lufthansa FSX.zip
description=UTT_A350-900(p3dv5)

[fltsim.27]
title=AIGAIM_Lufthansa Airbus A350-900 - OC
sim=utt_a350_900
model=OW
texture=DLH-Lufthansa_OC
atc_airline=LUFTHANSA
atc_heavy=1
atc_parking_types=GATE
atc_parking_codes=DLH
ui_manufacturer="United Traffic Team (UTT)"
ui_type=Airbus A350-900
ui_variation=Deutsche Lufthansa AG
ui_createdby=Provided by: JB Filename: UTT A359 Lufthansa FSX.zip
description=UTT_A350-900(p3dv5)

FYI no problems with other paints

Norm

Hi Nico

I have checked the a/c config and there is no atc_id in either of the paints I have

From the latest version 31.17,6  log:

4578 liveries read from \liveries\AI_liveries.xml
string12 size 43
s D-AIHIAIGAIM_Lufthansa Airbus A350-900 - IC
s D-AIHIAIGAIM_Lufthansa Airbus A350-900 - IC
string12 size 43
s D-AIHIAIGAIM_Lufthansa Airbus A350-900 - IC
s D-AIHIAIGAIM_Lufthansa Airbus A350-900 - IC
string12 size 43
s D-AIHIAIGAIM_Lufthansa Airbus A350-900 - IC
s D-AIHIAIGAIM_Lufthansa Airbus A350-900 - IC

Lufthansa.txt has no errors for the A359 except for no registrations which on checking the aircraft.cfg is correct.

Norm

I have been using the latest 31.15.3 P3D and checking the log after my last flight this error occurs several times which is not mentioned in the error table in the docs.

e.g. processLine: sys error 46: lalo 45.304270,0.000000

Norm

Good to see you back Steve.

A minor..ish point. TUI Germany i.e. TUIFly ditched the banana colors a long time ago 😉

Norm, from you know where.

I am seeing similar. I suspect it is because an airport afcad assigns a parking spot as cargo and any pax aircraft that park there  will be missed.

1 hour ago, Rob_Ainscough said:

Interesting, I don't have GFConfig installed because it's not required when using GIT ... in fact it can actually cause issues.  Why is GFConfig (GoFlights not GIT) required for iFly?  To be clear GFConfig is GoFlight's tool and GIT is Steve's tool.

Cheers, Rob.

Some confusion here Rob.

I don't know whether you saw my later post regarding my xmas excesses but to clarify things:

GFConfig has built in support for all Ifly aircraft, FS default aircraft, LevelD and Project Magenta, all selected from the dropdown list.  The remaining choice is Compatible Addon which is only used along with GIT.

So, with say PMDG aircraft GFConfig is set to Compatible Addon and GIT will run perfectly. Any GIT profiles the user has made also requires GFConfig to be set to Compatible Addon to operate correctly as per your GIT tutorials.

To summarise. As an iFly beta tester for many years all iFly needs is GFConfig to be configured to iFly.

All the best

Norm

Rob,

Too much early xmas cheer........🥵 GIT is not needed! Just the GFConfig software correctly configured.

Norm 

Rob,

No issues here with GIT everything working perfectly. Check if GFConfig software is set to Ifly

Norm

5 hours ago, Ray Proudfoot said:

It's a requirement for all 737 functionality to work on the PMDG such as LNAV, VNAV etc. The basic GoFlight driver will only give you Hdg, V/Spd and the other standard P3D autopilot commands. I imagine it will be the same for the iFly.

If the GoFlight driver worked on specialist aircraft why would Steve write GIT? It works giving limited functionality.

I think GIT  was originally written to enable the GoFlight hardware to interface with PMDG but has changed beyond all recognition now and is an extremely powerful tool. So much so that I now use it to interface my MCPPro and EFIS with CaptainSim and Quality Wings aircraft, after a lot of programming and head scratching of course 😎

Norm

GIT is not needed.

The Goflight software can be enabled to use all iFly types i.e. 737's, 747/8 from the dropdowns for MCPPro and EFIS.

Norm

All done and up and running.

Excellent support. Thank you

Norm

Hi,

Getting the same error here after uninstalling  1.13.5.0  and re-installing with a consequent update. All with Defender disabled.

Sent a message to support as above

Norm

Ok Nico understood and thanks for your response. And yes you are right a great majority of the models deploy the reversers and speed brakes also.

Norm

Quote

Quote

 

I use a mixture of AIsounds and 3DSounds for my AI models which work very well except for reverse thrust on touchdown. Just before the aircraft touches down the engine sound cuts and then reverts to a taxy sound. This happens when PSXT is controlling the aircraft.

If I use a traffic bgl with the same aircraft models and not PSXT all aircraft sounds and especially reverse thrust are perfect.

Is this because of the way PSXT interacts and controls the aircraft model at touchdown?

Not supremely important but would be nice when spotting and collecting data for a particular airport.

Norm