Jump to content

Nick Cooper

Administrators
  • Posts

    47,032
  • Joined

  • Days Won

    53

Posts posted by Nick Cooper

  1. Hello Michael,

     

    I would agree and thanks for pointing out the function in the Lorby-SI tool.

     

    While I can keep all my non-Orbx addon scenery outside P3D and for that matter FSX

    and simply use the Scenery Config Editor to add them in or take them out, introducing a

    second and less user friendly method seems to me to be an unnecessary complication.

     

    The declared preference by Lockheed Martin is followed in both cases.

  2. Hello again,

     

    I am also new to P3D, however, the "approved" way of installing addons is to keep their files outside the P3D root folder

    and use the .xml files that will be stored in the documents folder to tell P3D where these files are.

     

    To date, I have installed only one scenery item using this method.

    I can see one disadvantage straight away, which is that they then all appear at the top of the in-game scenery library and

    cannot be moved.

    I see no way either of ordering them, though that may be my ignorance, rather than there not being a way. 

     

    I keep no addon scenery files in the root folder in any case, Orbx products excepted and add them to P3D using the time

    honoured method of adding them to the scenery library.

     

    Whether addon scenery is installed to P3D with an .xml file of not is entirely up to the scenery developer.

    If you have scenery that is no longer supported or does not have an installer, there is a small freeware utility that will "install" it

    for you. You can find it on this page

     

    I find it to be very time consuming and a very poor substitute for the Scenery Config Editor.

     

     

     

  3.  

    Hello.

     

    No addons are installed in the documents folder.

    The .xml files that are used to install them are stored there but

    they are typically a few bytes each.

    The scenery files are placed wherever you choose to place them,

    which is less likely to "mess up my whole system partition".

  4. You should download the file I attached to the first post.

    Unzip it and you will see that it is named dsd_p3d_xml_sound_x64.dll.

     

    Rename this file to RASDuke_Sound.dll

     

    Then go to your P3Dv4 gauges folder and delete

    RASDuke_Sound.dll and if it is there, RASDuke_Sound.gau.

     

    Finally copy your new  RASDuke_Sound.dll to the gauges folder.

  5. 42 minutes ago, Adam Banks said:

    Spectacular find, Nick!! Many thanks! Fixed my beloved MJ DC-3's cockpit sounds :D.

     

    Adam.

     

    Thanks Adam, it was no find, it's not what you know but who.:)

    Huge thanks are due to Doug Dawson who has done this again for us all and for free.

    • Upvote 1
  6. If running in the background, MSI Afterburner can prevent FTX Central from running.

    Please disable MSI Afterburner and do not set it to start with Windows.

    As it is a configuration utility, it can be used and then closed.

     

    This error does not affect everyone but should be ruled out before a support request

    is posted.

     

  7. Hello,

     

    The intended purpose of this topic is to inform only when commonly used third party software becomes P3D v4 compatible.

    Ideally, this topic could become reference for us all.

     

    Please do not post workarounds.

     

    Please do not post release announcements for new products.

     

    Please do post update announcements for existing products that have had a P3D v4 compatible version released.

     

    Please do post the name of the software and if possible a link to where the information can be found.

     

    Please do NOT post support requests in this topic or critiques of any products.

     

×
×
  • Create New...