Aces High Bulletin Board

Help and Support Forums => Technical Support => Topic started by: 8thJinx on April 19, 2022, 12:53:37 PM

Title: Film viewer won't excute
Post by: 8thJinx on April 19, 2022, 12:53:37 PM
I've reloaded the latest version twice, still can't get film viewer to work.  Get an error saying the film viewer can't find fmodstudio.dll, which is sitting there in the root directory.
Title: Re: Film viewer won't excute
Post by: 100Coogn on April 20, 2022, 12:44:36 PM
I've reloaded the latest version twice, still can't get film viewer to work.  Get an error saying the film viewer can't find fmodstudio.dll, which is sitting there in the root directory.

Just tried mine to see if it would work.  It started fine.  I'm using version 3.06 Patch 4 (DX-11)
That is odd that it won't start for you.  Hopefully Bizman will pop in on this one.

Coogan
Title: Re: Film viewer won't excute
Post by: Bizman on April 20, 2022, 01:08:07 PM
You called, sir?



Well, I've got no big ideas. Works for me as well, both from the Start Menu and by double clicking a film.

If the issue is Windows related, I'd start with my fav trick: Keep the Shift button pressed while clicking Shutdown for Windows.
If that doesn't work, I'd run "sfc /scannow" without quotes in either the Command Prompt or Power Shell, both as an administrator.
If that finds problems it can't fix, well, there's ways.

Also, did you reboot your computer after each reload?
Title: Re: Film viewer won't excute
Post by: 8thJinx on April 20, 2022, 02:34:59 PM
I figured it out.  For some reason the film viewer was getting installed in a subdirectory of the Aches High III folder tree.  Once I moved it over it worked.
Title: Re: Film viewer won't excute
Post by: Bizman on April 21, 2022, 12:59:41 AM
Glad you got it sorted.

In theory the Ahfilm.exe shouldn't install elsewhere than the main folder unless a) Hitech has accidentally moved it in which case it should affect more players, or b) you've accidentally moved it. In the former case an update should have fixed it, in the latter installing over the existing files may not return mislocated files of certain types. As an example of that my system "knows" that AH is on my E:\ drive instead of C:\.