busychild

FS Labs A320 for P3D v4

Recommended Posts

Hi,

today i installed the Update for the A320X (P3D v4.1) and unfortunately Linda doesn't seem to work with the new version. I installed the latest profile and Linda seems to find it (Its preselected in the dropdown near the sync button) but the connection to the aircraft doesn't seem to work (Linda recognizes my buttons and switches but nothing happens in the aircraft). I also recognized that my VRInsight Combo says "Linda Init... FSX Default" instead of the actual name of the aircraft. 

 

I'm using the Hotas Warthog + Throttle and the VRInsight Boeing Combo II (None of the devices are working). FSUIPC is updated. It worked perfectly in P3D v3 and it also works with the PMDG 737 in 4.1.

Are you aware of the issue or have an idea?

Thanks in advance and best regards

 

Florian

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Guys

I have been without internet today and have yet to download and test the new release. It will be a couple of days before I can answer your questions. Like you I have been awaiting the latest release. We did not receive an advanced beta release so we have to start with everyone else.

  • Upvote 3

Share this post


Link to post
Share on other sites

Fellow bus drivers,

 

do you all get the same error as I get?

(open the LINDA console F1)

[E] *** LUA Error: F:\Prepar3D v4\modules\linda/system/common.lua:179: attempt to call global 'InitDsp' (a nil value)
 

 

???

Share this post


Link to post
Share on other sites
15 minutes ago, guenseli said:

Fellow bus drivers,

 

do you all get the same error as I get?

(open the LINDA console F1)

[E] *** LUA Error: F:\Prepar3D v4\modules\linda/system/common.lua:179: attempt to call global 'InitDsp' (a nil value)
 

 

???

Exactly!

Share this post


Link to post
Share on other sites

Yes, i'm having the same message...

 

[E] *** LUA Error: D:\Prepar3D v4\modules\linda/system/common.lua:61: attempt to call global 'InitDsp' (a nil value)

Share this post


Link to post
Share on other sites

Hi Guenseli

I have now downloaded and installed v2. I am getting that error but there are other issues due to the new locations for installing add-ons in P3Dv4.1. It is similar to A2A but I need to do further investigation and testing. 

I will have a working solution as soon as practical. 

  • Upvote 2

Share this post


Link to post
Share on other sites
1 minute ago, ScotFlieger said:

Hi Guenseli

I have now downloaded and installed v2. I am getting that error but there are other issues due to the new locations for installing add-ons in P3Dv4.1. It is similar to A2A but I need to do further investigation and testing. 

I will have a working solution as soon as practical. 

Yes - i thought it might be because of the new location of the files! Thank you for your support!

Share this post


Link to post
Share on other sites
50 minutes ago, ScotFlieger said:

I will have a working solution as soon as practical.

 

Great!

thanks!

  • Upvote 1

Share this post


Link to post
Share on other sites

I actually saw the same error but was able to get it to work if you start the flight with any other plane but the FSLabs A320 then switch it.  It is the only bird acting this way with Linda so I'm sure they will come up with a fix but you can do this in the short term.

 

Tony

Share this post


Link to post
Share on other sites

Update: There is an issue with scanning the available LINDA aircraft modules with P3D4v4.1/FSUIPC 5.121c which is producing the InitDsp() error message. LINDA is remaining on FSX Default and not loading the A320X module which contains the called function. I have looked at possible workarounds and none work. This requires deeper analysis which will not be quick. Please be patient.

As FSLabs kept saying, quoting Captain Oakes "I may be some time." [from Scott's failed expedition to the South Pole].

  • Upvote 1

Share this post


Link to post
Share on other sites
59 minutes ago, Tony P said:

I actually saw the same error but was able to get it to work if you start the flight with any other plane but the FSLabs A320 then switch it.  It is the only bird acting this way with Linda so I'm sure they will come up with a fix but you can do this in the short term.

 

Tony

This works perfectly (i've selected the Piper Cub first and then switched to the A320X). Strange...

Share this post


Link to post
Share on other sites

Yes, it is right. Loading another (standard) plane before is working.

Having indeed loaded the A320 directly till now.

Share this post


Link to post
Share on other sites

There was a problem with LINDA scanning the available aircraft modules to find a match for the FSLabs A320 when the aircraft changed. I found an anomaly with the aircraft file path returned by FSUIPC 5.121c (offset 3C00) for the A320X which includes a single forward slash in the P3Dv4 Add-ons directory path. This does not occur for the similarly located A2A aircraft.

I have a beta version (build 728a) which works for me. Please try it and report back. If you have any issues, please follow the Fault Diagnosis thread above and send me the resulting fsuipc5.log file.

Edited by ScotFlieger
Correct for missing file

Share this post


Link to post
Share on other sites

Thanks for the beta! Unfortunately it doesn't work for me (just loaded up the A320X directly).

  • Linda 3.0.4.728
  • Module: FS Labs A320 (Version 0.7b)
  • Prepar3D 4.1.7.22841
  • FS Labs A320X
  • FSUIPC 5.121b

Here is the link to the FSUIPC5.log: https://www.dropbox.com/s/4qrud7agpgisek0/FSUIPC5.log?dl=0

I noticed that you're talking about FSUIPC 5.121c but i've 5.121b installed (the latest version from http://www.schiratti.com/dowson.html).

 

Share this post


Link to post
Share on other sites

Thank you for the report busychild and sorry to hear it does work for you. Unfortunately, for me, you have not followed the fault diagnosis thread procedure and turned on VERBOSE logging. Your fsuipc5.log does not contain any useful data.

You need to check the FSUIPC support forum and the download links for 5.121c beta (manual installation).  

Share this post


Link to post
Share on other sites
1 hour ago, ScotFlieger said:

Sorry. There was a key file missing from the above link. Try beta 728a.

I installed the files you provided in this thread and the latest FSUIPC version 5.121c, but unfortunately it isn't working for me. How can I help?

PS: Haven't tried loading a standard aircraft first, yet.

Share this post


Link to post
Share on other sites
Just now, danira said:

I installed the files you provided in this thread and the latest FSUIPC version 5.121c, but unfortunately it isn't working for me. How can I help?

PS: Haven't tried loading a standard aircraft first, yet.

Hi danira

As I mentioned, please follow the fault diagnosis thread and send me your logs so I can see what is going wrong. Do the test in your current configuration, copy the logs and then try again with a default aircraft and copy the new logs.

  • Upvote 1

Share this post


Link to post
Share on other sites

I tried the new FSUIPC and the latest LINDA beta you rpovided.

No success.

 

There is no error in the log now, but I can see with my MCP combo that FSX default is loaded.

Note, that  do not have installed the bus in the default place from the FSLabs installer.

 

Here is what my add-on.xml reads:

<SimBase.Document Type="AddOnXml" version="4,0" id="add-on">
  <AddOn.Name>Flight Sim Labs Products</AddOn.Name>
  <AddOn.Description>FSLabs Product Family. Publisher: Flight Sim Labs, Ltd.</AddOn.Description>
  <!-->Libraries Components</-->
  <AddOn.Component>
    <Name>FSLabs Sounds Module</Name>
    <Category>DLL</Category>
    <Path>Libraries\FSLSounds.dll</Path>
  </AddOn.Component>
  <AddOn.Component>
    <Name>FSLabs Events Module</Name>
    <Category>DLL</Category>
    <Path>Libraries\FSLEvents.dll</Path>
  </AddOn.Component>
  <AddOn.Component>
    <Name>FSLabs Options Module</Name>
    <Category>DLL</Category>
    <Path>Libraries\FSLOptions.dll</Path>
    <DLLType>PDK</DLLType>
    <DLLStartName>PDKDLLStart</DLLStartName>
  </AddOn.Component>
  <AddOn.Component>
    <Category>SimObjects</Category>
    <Path>SimObjects/Airplanes</Path>
  </AddOn.Component>
  <AddOn.Component>
    <Category>Effects</Category>
    <Path>Effects</Path>
  </AddOn.Component>
  <AddOn.Component>
    <Category>EXE</Category>
    <Path>Libraries\FSL_Configurator.exe</Path>
    <CommandLine>..\SimObjects\Airplanes</CommandLine>
  </AddOn.Component>
</SimBase.Document>

 

located in F:\0_P3D_Externe Szenerien\FsLabs A320\FSLabs

Share this post


Link to post
Share on other sites
4 minutes ago, guenseli said:

Loading the bus after a default aircraft still works

This is the way I always operate due to issues of swapping between aircraft like PMDG and FSLabs.

Can you send me the fsuipc5.log and linda2.log for loading the A320X first and also separately for when you load a default first and then the A320X? I will need to do some more work to parse the add-ons.xml fully.

Share this post


Link to post
Share on other sites
8 hours ago, ScotFlieger said:

Hi danira

As I mentioned, please follow the fault diagnosis thread and send me your logs so I can see what is going wrong. Do the test in your current configuration, copy the logs and then try again with a default aircraft and copy the new logs.

I mailed you the logs to the adress you provided in the fault diagnosis thread. If you need anything else, just say so ;)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now