So I've had a run of either bad luck or stupidity, or maybe a little combination of the two. I was working on getting a turret in game, which apparently can't be done properly with MshEx (the model doesn't move with you and looks like THIS), so I decided to try out the Foundation demos. 4.2 had the weird problem of opening once, crashing a bit in, then not rendering the work area the second time I opened it. So I moved on to 5.0, which is what I want to concentrate on in terms of my problems.

I have the odd problem of not being able to create primitives without a work around, but since I've found a way around that, it's not my real concern. For some reason, I can't get the Pandemic addon to work properly with 5.0. The cloth options window pops up fine, the edit flags just doesn't do anything, and the exporter comes up with THIS error. It should be noted that this is the same exact thing that happens if I try to run the addon with Mod Tool 6.

I guess what I'm asking is if anyone else has had this problem, or am I just missing something obvious?

For the edit flags you have to be in polygon selection mode, just having the object selected won't do anything.

That makes sense (and obviously works), but regardless, my real problem is with the exporting.

If you're using Vista then it sounds a lot like the same problem MandeRek had, try this:

MandeRek wrote:How to solve this problem: (a Vista problem)

Run RunMeOnce.bat from:

• c:\users\<your_user_name>\Softimage\XSI_5.11_Foundation\Addons\PandemicBF2

If windows shuts it down, press Start and type cmd.
Now in the search results it shows cmd.exe
RIGHT click on it and from the context menu select 'run as administrator'.
It'll open the command prompt, type this:

Code: Select all

Regsvr32 c:\users\<your_user_name>\Softimage\XSI_5.11_Foundation\Addons\PandemicBF2\Application\bin\nt-x86\PandemicExporter.dll

Then, it will say it is succesfully loaded.

Source*:
http://www.gametoast.com/forums/viewtop ... 30#p240830

You'll need to edit the path to reflect the 5.0 version where it says <version> and you'll also need to enter your user name where it says <username>

*Changed regsvr to regsvr32 to fix that typo in MandeRek's post.

Well, I guess it was more on the stupidity side then; I remember that topic and should have found it through search.

I ran the RunMeOnce.bat file and it shut down, but when I ran it as Admin, it was fine. When I went to check, it still didn't work, however. I used the code provided by MandeRek and it worked fine with the exception of "regsvr" which for both my 32-bit and 64-bit is "regsvr32" (this could be because my 32-bit is Windows 7, though).

With some testing, I can note that the reason RunMeOnce.bat doesn't work is because the command line won't accept that path as the proper path. I just finished the beginning of the path to the c:\ drive and the batch file worked fine.