Read below for general information on the tools found in PD Particles. Or head right over to the PD Help pages
for PD Howler, PD Artist and PD Particles altogether. Simply ignore the
parts that are specific to the big sister or big brother, i.e. the
parts on 3D and animation/video tools and many filters only found in the
Thank you so very much for using
PD Particles, such as the all new PD Particles v9, aka Particle 9.
likely, you will find that installing and using PD Particles
natural and is straight-forward and easy.
Still, and over time, we're going to have some feedback
and their solutions that a few users may have encountered.
this page and
come back soon.
Here is a problem that you may see on rare occasion when running or
installing several copies of the same or different editions of Project
For now, since much of PD Particles is based on the
Optipustics particle brushes and powered by Project Dogwaffle, here
links to information that may help too, coming from general Project
Here are some chapters of particular interest to users of PD
(even if some parts of the material presented are not
applicable to PD
Particles, or if some user interfaces are different) simply
ignore references to animation, video and 3D or the filters that are not
found in your version:
Some versions of Photoshop have reported trouble loading the
saved from PD Particles in some cases. We recommend that you
'Default Targa' or 'Tiff' or other formats if you experience
problems, until we have a fix for this.
Crash in 'Nova' style - fixed in the 1.0a patch
The Nova style of the particles brushes doesn't work in v1.0
PD Particles to exit. We're looking into fixing it with an
patch. (it works fine in PD Pro and Project Dogwaffle)
no undo for large images?
There is a fixed amount of memory allocated for undo, when
Particles. That amount is not very high in v1.0, so if
on very large images it may not be possible to use many
levels of undo,
in some cases even none at all. This will hopefully be
remedied in a
future patch, with more memory allocated or a choice given
to the user
to choose how much memory to pre-allocated. In the meantime,
a few alternatives: The Pro version (PD
Pro) offers more control, a slider in the
to allocate more memory than the default. You can also use
entries for the pre-allocation to set it higher than the max
value if desired. Another option is to use the
Clipboard menu to often save a snapshot of the current image
Clipboard. That way you can return to it quickly if needed.
::: Frequently Asked
Problems - Not the right software?!?
We have seen a few rare instances where the downloaded file
purchase & download appeared to be from a different
typically something that already was on the client's
computer, such as
a printer driver or imaging tool. This is just an
appearance, it is not a
faulty installer, it is due
to a pre-existing misconfiguration on your PC. In most cases
easily corrected by a standard disk cleanup.
When such problem occurs, what happens is that during the
of the installation process, our installer starts by
number of files which will eventually be placed into the
destination folder for PD Particles. These files are
self-extracted into a temporary (Temp) folder, usually
where 'username' would be your login username, such as
'John' or 'mom'
or 'superkid' or whatever.
After the first phase, i.e. after the self-extraction, our
be there in the Temp folder, and one of these files is named
proceeds with the second phase, which is to run that
(which is expected to be our
Unfortunately, in some rare cases, it has been found
another setup.exe file to either be executed instead,
perhaps from a
different folder, if your system's Path variable was
up by installation of other software, or, and more likely, a
setup.exe file was there in the Temp folder and is being
kept in a
locked state, and thus could not be updated or replaced with
installer's setup.exe file. The file may be in a locked
another program is 'using' it. Or it was saved as a
'read-only' file by
such, making it write-protected.. Thus, when our
proceeds to run 'its' setup.exe file, your old printer
imaging utility or whatever that old setup.exe file was
about could be
re-run, making it appear like our installer is not PD
To remedy this, you can try a few things. One first
recommended task is
to clean up the Temp folder. It's supposed to be for
and files in there. Windows offers a 'Disk Cleanup' utility
1) open 'My Computer'
2) right-click on the "C:" drive
3) select 'Properties'
4) click "Disk Cleanup"
There are various options for different things to be cleaned
up. If you
have never done a disk cleanup in years, you might want to
all, you'll be surprised how much disk space you may regain
way. But at least make sure that the 'Temp' folder option is
so that Windows can try to cleanup the files found in there.
'try', because if a file is locked it will continue to stay
and you may need to manually go into the Temp folder to
remove or at
least rename the file so that it won't interfere with our
After the disk cleanup is done, open the Temp folder to see
files are gone. Ypu should probably also do a re-boot.
Then run our installer again. If it still fails, then
scenario is probably happening: the setup.exe from a
folder is used. This is tricker to fix but can be
done. Check the
general FAQ for assistance. If you can't find the answer,
culprit setup.exe file
You can use the Windows Search facility to find all files
setup.exe found on your system. One of them is probably the
erroneousy executed. If you can locate it (look for the name
folder that contains it), you may want to rename it to
setup_bad.exe, at least temporarily, and see if you
properly run the PD Particles installer.
Unfortunatey, it is likely that if your system's path was
messed up by
prior installation of that other sftware, it could still
pick another (the 'next) setup.exe file.
workaround - run setup directly
Here's another workaround that might help, if after the
(self-extraction phase) all files including our setup.exe
properly copied into the Temp folder. When the 'wrong'
over, simply move it aside and ignore it for the time being
click 'Cancel', as that will remove the extracted files.)
Open the Temp folder where you will find the files that were
extracted. It should be something like
Find the file named setup.exe
and run it. If it is our
this should allow the second phase, i.e. the installation of
Particles, to properly complete. If not, just cancel to
you only see 'setup', without the '.exe' file type
You can configure Windows Explorer to hide the file
extensions, such as
.exe, .jpg, .txt, etc... for known file types. That is in
default. We strongly recommend not to leave it this way,
leaves you in the dark as to which files you're actually
For example, if you have several files in a folder, and the
the same base name, such as
then you would only see them as
and you have no immediate clue as to which file is which.
This is dangerous and can lead to accidentally running the
Even worst, if the file were a virus in hiding, such as
in email attachments, you may be putting your PC at risk.
if you have a file named
which is an executable, and potentially a virus, you would
if Windows Explorer is configured to hide the file, the type
at the end (in this case the .exe part)
Thus, we recommend and strongly advise you not to stay in
the dark, by
preventing Windows from hiding the extension of known
Here's how to do that:
1) Right-click on 'My
2) select 'Explore'
3) select Tools>Folder options...
4) click the 'View' tab
the option "Hide
Extensions for known file types". This will
ensure that instead
of hiding them, the system will show the extension on all
regardless of whether Windows recognizes the file type.
Instead of my-image
might see my-image.jpg
if it is a Jpeg format image, or perhaps my-image.bmp
if it's in Btmap format. RThis will help, since you'll
be able to know
which format it is just by looking at the filetype.
Instead of Setup
you might see it
Instead of My-report
you might see it as My-report.doc
6) You might also want to select 'Show
hidden files and
folders' if you're unable to see the 'Local
Settings' or Temp
There are various things that can occur which could make a
Basic) runtime error occur. Perhaps the VB runtime files
by a system failure (such as a bad block on the disk hard
Perhaps a virus has messed with or deleted some of the VB
DLL's. Perhaps the registry entries used by PD Particles got
and contain insanely large values for panel width and
out of memory errors when VB tries to oblige.
If you suspect you may have bad data in the registries used
Particles, try this to clear those entries used by PD
have the program start fresh with internal default settings:
Click Start --> Run ...
to launch the Registry Editor
In the left pane, open the category named HKEY_CURRENT_USER
...then into the category named Software
...then into subcategory: VB
and VBA Program
...then into subsubcategory: Optipuss
Within the Optipuss category: right-click
WindowData, and select Delete
Move the registry editor to the side or minimize it
close it, you might need it some more). Try launching PD
again. If that didn't fix the problem, try deleting both
the WindowData and
If that didn't fix it either, try deleting the OptiPuss group
If that didn't fix it, then it's not likely a registry
Installing the VB Runtimes If you suspect you may
old or incomplete/corrupted VB runtime files, you may want
and reinstall the VB runtimes from Microsoft.
Several versions ill show listed. Make your you pick
latest or most recent version for your version of
Windows. Version 6 or
higher should be fine. If you're on Windows Vista make
you you get a
version that's made for Vista too.
Download it, (save to disk, e.g. desktop or My
then double-click the saved installer to install the VB
PD Particles and Project Dogwaffle are
trademarks of Dan Ritchie. All other names, trademarks or
trademarks mentioned here are the sole property of their
owners and only used for identification purposes. No
other support is intended or implied. Use at your own
risk.This software is provided as is with no warranties expressed nor