Jump to content
The simFlight Network Forums

FSUIPC 6.0.12 Lua Script Sound.path


Recommended Posts

I have a problem with FSUIPC 6.0.12 registered and the Lua Script ThrottleManager. The previous versions were still installed in the Modules folder in the main directory of P3D. There the Throttlemanger worked with my different aircrafts from PMDG and FSLabs without any problem.
After installing FSUIPC 6 outside the directory of P3d, the throttle manager only works to a limited extent. The thrust reverser still works, but the sound that normally sounds when switching the thrust reverser on and off is no longer audible.
My installation locations are as follows
FSUIPC in the folder "C:\Users\Myname\Documents\Prepar3D v5 Add-ons\FSUIPC6".
P3Dv5 in the folder "D:\Program Files\Lockheed Martin\Prepar3D v5".

The Lua script ThrottleManager.lua and the sound files are in the folder FSUIPC6.
In the Lua script I noticed a line that is the possible reason for this.
It is the line: sound.path("..\\Modules\\"). It points to the old folder where FSUIPC was installed before.

I have tried the following changes without success:
1. I created a folder "Modules" in the main directory of P3D v5 and copied the sound files into this folder.
2. I copied the sound files into the folder "Sound" which is in the main directory of P3D v5 and deleted the line sound.path("..\\Modules\\").
3. I changed the line to
sound.path("C:\Users\Myname\Documents\Prepar3D v5 Add-ons\FSUIPC6")
Now I am at the end with my non-existent Lua knowledge.
Can anyone help me with this?
Thanks Stefan

enclosed log files of the last two sessions

FSUIPC6.log FSUIPC6_prev.log

Link to post
Share on other sites
33 minutes ago, Stefan01 said:

The Lua script ThrottleManager.lua and the sound files are in the folder FSUIPC6.

Which FSUIPC6 folder - did you move the sound files to your new installation folder (C:\Users\Myname\Documents\Prepar3D v5 Add-ons\FSUIPC6)?
If so, then your 3rd attempt would have worked if you had escaped the backslash, i.e. try
     sound.path("C:\\Users\\Myname\\Documents\\Prepar3D v5 Add-ons\\FSUIPC6")

or simply
     sound.path(".\\")
(i.e. the current folder)
 

33 minutes ago, Stefan01 said:

2. I copied the sound files into the folder "Sound" which is in the main directory of P3D v5 and deleted the line sound.path("..\\Modules\\").

Then you can just use that path, i.e.
    sound.path("D:\\Program Files\\Lockheed Martin\\Prepar3D v5\\Sound")

Link to post
Share on other sites
30 minutes ago, Stefan01 said:

The Lua script ThrottleManager.lua and the sound files are in the folder FSUIPC6.
In the Lua script I noticed a line that is the possible reason for this.
It is the line: sound.path("..\\Modules\\"). It points to the old folder where FSUIPC was installed before.

Does the ThrottleManager play sounds? Seems rather odd to me.

However, the line

sound.path("C:\Users\Myname\Documents\Prepar3D v5 Add-ons\FSUIPC6")

needs to be

sound.path("C:\\Users\\Myname\\Documents\\Prepar3D v5 Add-ons\\FSUIPC6")

because the \ character is what is called an "escape", used to say the next character has special meaning (eg \n means "new line"). "\\" means 'yes really a \'. Quaint, eh? That's programming for you! 😉

That, mind, is assuming that the sound files (".wav"s) are in the FSUIPC6 folder. It's generally better to create a Sound folder there and put them into it, making the line

sound.path("C:\\Users\\Myname\\Documents\\Prepar3D v5 Add-ons\\FSUIPC6\\Sound")

Note that it would have been rather tidier, and simpler for paths, if you had installed FSUIPC6 into a folder such as D:\FSUIPC6. But now you are set-up there I'd leave it. However, best to clean up and remove your added Modules folder in P3D, unless some other add-on is also using it.

I see you are also using LINDA. Is that okay since you moved things or did you uninstall it then re-install?

Pete

Ooops. I see John posted simultaneously!

 

 

 

 

 

Link to post
Share on other sites

Dear Pete and John,
Thank you very much for the quick reply and advice.
I have implemented the last suggestion and it works.
I have created a new folder Sound in the FSUIPC6 folder and copied the sound files there. I changed the line for the sound.path to sound.path("C:\\Users\\Myname\\Documents\\Prepar3D v5 Add-ons\\FSUIPC6\\Sound") as suggested.
After starting, the sound was heard again when switching the thrust reverser on and off.

If I remember correctly I installed FSUIPC6 into the folder "C:\Users\Myname\Documents\Prepar3D v5 Add-ons\FSUIPC6" as suggested by the installer. After that I copied all the Linda files and folders into the new FSUIPC6 directory. FSUIPC and Linda are running without any problems.
Thanks again

Stefan Liebe

Link to post
Share on other sites
12 minutes ago, Stefan01 said:

If I remember correctly I installed FSUIPC6 into the folder "C:\Users\Myname\Documents\Prepar3D v5 Add-ons\FSUIPC6" as suggested by the installer.

That was the default installation path in earlier versions of the installer - this has now changed. However, when you re-install, the default location will be the previous installation location.
Event though that location was the default, the Installation and Registration guide advices that you should change this. It is the folder where the add-on.xml file goes for auto-discovery by P3D. It is better to have the actual installation folder in a different location.

But if its all working now, you can just leave things as they are.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.