-
Posts
47,093 -
Joined
-
Days Won
53
Posts posted by Nick Cooper
-
-
Hello.
To clear up any confusion as to which setting to select:
Explanation.
Open LC NA includes the Orbx night lighting.
The NA regions also include Orbx night lighting.
Therefore, if you are in a region and you also have OpenLC NA
installed, you will have TWO sets of night lighting.
The control panel.
You will only see it if you have a region and OpenLC installed.
This is what it does.
BOX NOT CHECKED
BOX CHECKED
Apologies, the images were lost when Postimage unexpectedly moved.
Please read on in any case.
-
2
-
-
You might wish to post that again in the topic on that subject.
-
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.
-
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.
-
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".
-
Yes I believe so, if you look back you will see some references to the Legacy.
-
Hello,
I have tidied it up for you.
Thanks, this should help those who have them in both.
-
That seems to be part of a default aircraft, I would leave it alone
if your Constellation's brakes squeak.
-
Yes, it works perfectly, except for the sounds.
Now they are fixed too.
-
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.
-
Hello,
I have only the Real Air Duke v2 piston engine.
The file name for another version might not be the same,
if you have another version, you should check.
-
No problem, the thanks are due to Doug Dawson, I am only the messenger.
-
It must be RASduke_Sound.dll and P3Dv4, then it should work.
If you have RASduke_Sound.gau in your gauges folder, you should delete it.
-
42 minutes ago, Adam Banks said:
Spectacular find, Nick!! Many thanks! Fixed my beloved MJ DC-3's cockpit sounds
.
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.
-
1
-
-
- Popular Post
- Popular Post
The Doug Dawson sound gauge has been released for P3Dv4.
I have a copy and it is attached for you.
This is the new Doug Dawson 64 bit sound gauge for P3Dv4 ONLY.
If your aircraft is installed into FSX, FSX-SE or P3D v1, v2 or v3,
you should NOT use this gauge.It works as a direct replacement for the 32 bit gauge, so just rename it to
whatever the developer used, but do not change the .dll extension.
Replace the existing 32 bit version and you will have all your sounds back.
For example, the freeware Manfred Jahn C47 uses C47_dsd_fsx_xml_sound.gau.
Rename the new gauge to C47_dsd_fsx_xml_sound.dll
Once renamed, copy it into the panel folder and delete C47_dsd_fsx_xml_sound.gau
If you don't have the aircraft, you should, it is pretty much the definitive
version of this iconic aircraft and has features seen only at the very top
end of payware models.
You can fix the Real Air Duke the same way, rename the gauge to
RASduke_Sound.dll and put it in the P3D gauges folder.
If it is there, delete RASduke_Sound.gau
Anything you might have that uses the DSD_FSX_XML_Sound.gau,
rename the new 64 bit version to DSD_FSX_XML_Sound.dll, delete the original gauge and
put it in your gauges folder.
There are many many aircraft, freeware and payware that use this gauge for sounds and this
method will work for all of them that are compatible with P3Dv4.
Please note: This has nothing to do with the engine sounds but everything to do with switches that click and
other sound effects that developers may have added to their aircraft models.
Here is Doug's own comment, please respect it.
QuoteI would only ask that if you distribute the file, you do not include the letters 'fsx' in the name and that you not remove the letters '_x64' from the name.
I don't want anyone getting the idea that this version of the gauge will work in previous versions of FS - it's 64 bit and so of course it will not. It probably won't work in FSW either.
-
3
-
17
-
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.
-
-
-
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.
-
Apparently this file does not work with FTX Central v3.2.0.3.
Thanks to fellow customer Psin.
Attached is an alternative version.
-
1
-
-
Hello Simon.
On behalf of Kaspersky owners everywhere, thank you very much for going to the trouble of making this excellent guide.
I have pinned it and it will make a very useful reference.
I have also locked it to prevent it becoming a long support topic.
To anyone requiring further advice, please open another topic in this forum.
-
1
-
-
Good news Jack.
If I ever get P3D v4, I'll come to you for advice.
-
2
-
-
Hello Jack,
Two people have asked that question now.
Best visit the P3D forums for your answer.
You can of course find Elaine there too.
-
1
-
-
Hello,
Each P3D version has its own file structure and can be installed with any or all of the other versions.
I believe that you are not right, this is a version change and you will indeed have to pay if you want it.
I gather that you must be an optimist.
Orbx regions, night lighting control panel
in FSX Support Forum
Posted
Hello Jack,
If you don't tick the box, you have the regions' lighting and the OpenLC lighting at the same time.
Roughly twice as many lights in total.
The tick box is there to prevent this happening.