Editing "Effects" files

Printable View

September 12th, 2019, 03:57
gray eagle

Editing "Effects" files

There is an excellent tool available for editing any effect (fx) file - those from FSX and those from FS2004 also.
It is called FX Edit and is invoked from the Tools menu of FSX when in windowed mode.

I wonder if there is something like this in P3D?

https://www.flightsim.com/vbfs/showthread.php?213899-Editing-quot-Effects-quot-files
September 12th, 2019, 04:30
Postbaer61

Hello gray eagle,
This should do it with P3D all Versions

https://www.scenerydesign.org/development-releases/
scroll down and look for "FXEditor"
September 12th, 2019, 06:37
jeansy

Quote:

Originally Posted by Postbaer61

Hello gray eagle,
This should do it with P3D all Versions

https://www.scenerydesign.org/development-releases/
scroll down and look for "FXEditor"

thats very dated, theres a thing you have now called VisualFXTool in the sdk, it can be set up to run live during the sim and all changes are live
September 12th, 2019, 10:15
gray eagle

Quote:

Originally Posted by Postbaer61

Hello gray eagle,
This should do it with P3D all Versions

https://www.scenerydesign.org/development-releases/
scroll down and look for "FXEditor"

I found that one a day or so ago thank. It will load a FX file and it will play any anumation (if any)

Now, if I only knew how to tweak the fx file in question.
September 12th, 2019, 10:17
gray eagle

Quote:

Originally Posted by jeansy

thats very dated, theres a thing you have now called VisualFXTool in the sdk, it can be set up to run live during the sim and all changes are live

I found that, it is a dll file. What exe file runs it?

I found this

http://www.prepar3d.com/SDK/Environm...0Tool%20Dialog

However, it's not clear to me how to open this FS tool that is mentioned. They lost me there.
September 12th, 2019, 10:42
gray eagle

Quote:

Originally Posted by jeansy

thats very dated, theres a thing you have now called VisualFXTool in the sdk, it can be set up to run live during the sim and all changes are live

I'd like to know how it is set up.
September 12th, 2019, 11:35
Postbaer61

You must have installed the SDK to use this tool.

Build a folder called "Visual Effects Tool" in your Documents/Prepar3D v4 Add-ons folder .
Build a new texture file in the Prepar3D v4 Add-ons folder and
copy and paste the following entry in it and correct the path entry according to your installation location.
Then save the texture file as add-on.xml not add-on.xml.txt ;-)
thats it.
You will find the FX Tool in your sim menu bar under Tools.

<SimBase.Document Type="AddOnXml" version="4,0" id="add-on">
<AddOn.Name>Visual FX Tool</AddOn.Name>
<AddOn.Description>Design special effects in the Prepar3D *.fx format. Publisher: Lockheed Martin</AddOn.Description>
<AddOn.Component>
<Category>DLL</Category>
<Path>J:\Program Files (x86)\P3DV4 SDK\Modeling\Special Effects\Visual FX Tool\VisualFXTool.dll</Path>
</AddOn.Component>
<AddOn.Component>
<Category>Effects</Category>
<Path>J:\Program Files (x86)\P3DV4 SDK\Modeling\Special Effects\Visual FX Tool\Effects</Path>
</AddOn.Component>
<AddOn.Component>
<Name>Visual FX Tool Scenery</Name>
<Category>Scenery</Category>
<Path>J:\Program Files (x86)\P3DV4 SDK\Modeling\Special Effects\Visual FX Tool\Scenery</Path>
</AddOn.Component>
</SimBase.Document>
September 12th, 2019, 13:23
gray eagle

Quote:

Originally Posted by Postbaer61

You must have installed the SDK to use this tool.

Build a folder called "Visual Effects Tool" in your Documents/Prepar3D v4 Add-ons folder .
Build a new texture file in the Prepar3D v4 Add-ons folder and
copy and paste the following entry in it and correct the path entry according to your installation location.
Then save the texture file as add-on.xml not add-on.xml.txt ;-)
thats it.
You will find the FX Tool in your sim menu bar under Tools.

<SimBase.Document Type="AddOnXml" version="4,0" id="add-on">
<AddOn.Name>Visual FX Tool</AddOn.Name>
<AddOn.Description>Design special effects in the Prepar3D *.fx format. Publisher: Lockheed Martin</AddOn.Description>
<AddOn.Component>
<Category>DLL</Category>
<Path>J:\Program Files (x86)\P3DV4 SDK\Modeling\Special Effects\Visual FX Tool\VisualFXTool.dll</Path>
</AddOn.Component>
<AddOn.Component>
<Category>Effects</Category>
<Path>J:\Program Files (x86)\P3DV4 SDK\Modeling\Special Effects\Visual FX Tool\Effects</Path>
</AddOn.Component>
<AddOn.Component>
<Name>Visual FX Tool Scenery</Name>
<Category>Scenery</Category>
<Path>J:\Program Files (x86)\P3DV4 SDK\Modeling\Special Effects\Visual FX Tool\Scenery</Path>
</AddOn.Component>
</SimBase.Document>

Thanks for the info. I'll give it a try.

I made the addon.xml and the Visual Effects Tool folder. I use P3D V3.4 and it is on my P: drive.
So I made tweaked the entries to refles version and locationof my P3d. No FX tool bar yet.
When I run P3D V3 it asks me if I want to unload a scenery file. I said no.

<SimBase.Document Type="AddOnXml" version="4,0" id="add-on">
<AddOn.Name>Visual FX Tool</AddOn.Name>
<AddOn.Description>Design special effects in the Prepar3D *.fx format. Publisher: Lockheed Martin</AddOn.Description>
<AddOn.Component>
<Category>DLL</Category>
<Path>P:\Program Files (x86)\P3DV3 SDK\Modeling\Special Effects\Visual FX Tool\VisualFXTool.dll</Path>
</AddOn.Component>
<AddOn.Component>
<Category>Effects</Category>
<Path>P:\Program Files (x86)\P3DV3 SDK\Modeling\Special Effects\Visual FX Tool\Effects</Path>
</AddOn.Component>
<AddOn.Component>
<Name>Visual FX Tool Scenery</Name>
<Category>Scenery</Category>
<Path>P:\Program Files (x86)\P3DV3 SDK\Modeling\Special Effects\Visual FX Tool\Scenery</Path>
</AddOn.Component>
</SimBase.Document>
September 13th, 2019, 10:08
PhantomTweak

Ummmm...

Forgive my intrusion, don't you need the name of the DLL or EXE file on the end of the <Path> entry?
Something like J:\Program Files (x86)\P3DV4 SDK\Modeling\Special Effects\Visual FX Tool\Effects\EffectEditor.exe

Just an example, not the real thing.
Pat☺
September 13th, 2019, 10:36
Postbaer61

@gray eagle

Take a look at your addon.cfg which you can found at
C:\Users\Administrator\AppData\Roaming\Lockheed Martin\Prepar3D v3
and check if there is an entry like following

[Package.0] <== consecutive number
PATH=C:\Users\Administrator\Documents\Prepar3D v3 Add-ons\Visual Effects Tool
ACTIVE=true
REQUIRED=false

if not try to add it manually.

@ Pat
It's not necessary, because there is no exe or dll file in it.
Effect and scenery folders content only example files.
The first path linked to the VisualFXTool.dll.
September 14th, 2019, 03:10
jeansy

or you can copy the folder and place it directly in the p3d addons folders

thats how ive done it
September 14th, 2019, 08:47
gray eagle

Quote:

Originally Posted by jeansy

or you can copy the folder and place it directly in the p3d addons folders

thats how ive done it

But I've already made a visual Effects folder in my C:\Users\Documents folder
September 14th, 2019, 08:51
gray eagle

Quote:

Originally Posted by PhantomTweak

Ummmm...

Forgive my intrusion, don't you need the name of the DLL or EXE file on the end of the <Path> entry?
Something like J:\Program Files (x86)\P3DV4 SDK\Modeling\Special Effects\Visual FX Tool\Effects\EffectEditor.exe

Just an example, not the real thing.
Pat☺

Not sure I follow.....
September 14th, 2019, 08:53
gray eagle

Quote:

Originally Posted by Postbaer61

@gray eagle

Take a look at your addon.cfg which you can found at
C:\Users\Administrator\AppData\Roaming\Lockheed Martin\Prepar3D v3
and check if there is an entry like following

[Package.0] <== consecutive number
PATH=C:\Users\Administrator\Documents\Prepar3D v3 Add-ons\Visual Effects Tool
ACTIVE=true
REQUIRED=false

if not try to add it manually.

@ Pat
It's not necessary, because there is no exe or dll file in it.
Effect and scenery folders content only example files.
The first path linked to the VisualFXTool.dll.

I checked and there is no folder there like that. No folders after appdata are there.

I found one and its contents:

[Package.0]
PATH=C:\Users\XXXX\Documents\Prepar3D v3 Add-ons\FsDreamTeam KMEM
ACTIVE=true
REQUIRED=false

When I tried to get P3d to load it would ask me if I wanted to unload FsDreamTeam KMEM
and subsequently no tool bar either.....
September 14th, 2019, 09:25
gray eagle

Quote:

Originally Posted by Postbaer61

@gray eagle

Take a look at your addon.cfg which you can found at
C:\Users\Administrator\AppData\Roaming\Lockheed Martin\Prepar3D v3
and check if there is an entry like following

[Package.0] <== consecutive number
PATH=C:\Users\Administrator\Documents\Prepar3D v3 Add-ons\Visual Effects Tool
ACTIVE=true
REQUIRED=false

if not try to add it manually.

@ Pat
It's not necessary, because there is no exe or dll file in it.
Effect and scenery folders content only example files.
The first path linked to the VisualFXTool.dll.

It is located here:
C:\Users\XXXX\Lockheed Martin\Prepar3D v3

and this is the contents:

[Package.0]
PATH=C:\Users\XXXX\Documents\Prepar3D v3 Add-ons\FsDreamTeam KMEM
ACTIVE=true
REQUIRED=false

So now what do I do?
September 14th, 2019, 10:13
gray eagle

Quote:

Originally Posted by Postbaer61

@gray eagle

Take a look at your addon.cfg which you can found at
C:\Users\Administrator\AppData\Roaming\Lockheed Martin\Prepar3D v3
and check if there is an entry like following

[Package.0] <== consecutive number
PATH=C:\Users\Administrator\Documents\Prepar3D v3 Add-ons\Visual Effects Tool
ACTIVE=true
REQUIRED=false

if not try to add it manually.

@ Pat
It's not necessary, because there is no exe or dll file in it.
Effect and scenery folders content only example files.
The first path linked to the VisualFXTool.dll.

Okay, I've added that entry to contents of the addon.cfg

[Package.0]
PATH=C:\Users\xxxx\Documents\Prepar3D v3 Add-ons\FsDreamTeam KMEM
ACTIVE=true
REQUIRED=false

[Package.1]
PATH=C:\Users\xxxx\Prepar3D v3 Add-ons\Visual Effects Tool
ACTIVE=true
REQUIRED=false

I don't see the fx tool bar.

https://i.postimg.cc/1zB6P0vV/Untitled.jpg

https://i.postimg.cc/VLcCrLdF/Capture.jpg
September 14th, 2019, 12:39
Postbaer61

Okay, there must be something wrong with your path settings.
Then simply go to your P3DV3 \ SDK \ Modeling \ Special Effects folder
and copy the whole Visual FX Tool folder and paste it into your
C:\Users\Administrator\Documents\Prepar3D v4 Add-ons folder,
as like Jeansy and i have done.
September 14th, 2019, 13:42
gray eagle

Quote:

Originally Posted by Postbaer61

Okay, there must be something wrong with your path settings.
Then simply go to your P3DV3 \ SDK \ Modeling \ Special Effects folder
and copy the whole Visual FX Tool folder and paste it into your
C:\Users\Administrator\Documents\Prepar3D v4 Add-ons folder,
as like Jeansy and i have done.

Not working, think I will just try something else out.

Thanks anyway.
September 14th, 2019, 16:33
jeansy

Just start again and make sure you have the latest verson of the sdk

Just note, this is the p3d v4 forum so things maybe different for v3 and file structures may be different as well

To get this to work in v4 and quite possibly in v3 you will need to

1. by deleting what folders and files you have created in your documents folder for this

2 Copy the visual tools folder from the sdk into your p3d v3 addons folder in your documents folder

3 go to the p3d program data folder in c: drive and delete the file addons.xml

4. Go to the users app data p3d folder and delete the file addons.xml

5 restart the game and allow the addons.xml to rebuild

There should be no reason why this shouldn't work if you follow these steps, the tools foldsr has its own addon.xml entry contained with it so there is no need to to add or modify anything

The only thing that would prevent this, would be throwing incorrect files into the equation or your p3d is corrupted
September 15th, 2019, 13:07
gray eagle

For what it's worth, my SDK folder is located:

P:\Prepar3D v3 SDK 3.4.22.19868

which is outside my main P3D folder. Is that the normal location?
September 15th, 2019, 15:53
jeansy

Quote:

Originally Posted by gray eagle

For what it's worth, my SDK folder is located:

P:\Prepar3D v3 SDK 3.4.22.19868

which is outside my main P3D folder. Is that the normal location?

It has no relevance if you follow the above, we are not pointing anything to the sdk