Blackbird Sims / Milviz Forum Archive

The Beaver might be a good plane if it worked. I tried to do what was suggested in the other threads but no luck. I don't have time to be trouble shoot a product that I paid good money for. How about sending me whatever files I need and some good instructions. Better yet put out a product that works right out of the box. If you can't do these things then tell how to get a refund.

Telling us what exactly is wrong would help... along with all relevant system info including OS sim version and type...

Windows 10. FSX SE. I had the boxed version of FSX installed as well so I uninstalled it and reinstalled the Beaver. Manifold Pressure inop. Gauge with Fuel Pressure, Oil Pressure and Oil Temp inop. Cylinder Head temp inop. This is the case whether it's started on launch or if it's open ready to start. The starter switch also doesn't seem to work but maybe there's something in the manual for that.

Almost forgot. FS crashes with the Beaver after ending the flight.

Hi,

Please follow the instructions on this thread:

viewtopic.php?f=137&t=7628

I believe most of your problems (if not all) should be solved then.

Tom

Tried this already. I get "FSX not found on this machine!!" -FSX must be installed on this machine previous to install XML Tools 2.01

Now what

Ok, so then go to this message:

http://www.milviz.com/forum/viewtopic.p ... 271#p71505

Download the dll and install it manually following the instructions on how to add it to DLL.XML

Tom

FYI, your registry is likely messed up due the twin installs... (you may still be able to fix it but... just saying)

Many folks don't realize that uninstalling FSX:boxed version does not remove the Registry entry. Unless they manually remove the original FSX Registry entry, FSX:SE will "see" the old Registry value and think that FSX:boxed is still installed and therefore install the Steam version as side-by-side.

This of course confuses installers that depend on the proper Registry keys...

Still no luck. I followed the vague instructions and nothing worked. I found several dll.xml files so I took a guess at the right one and did my best to edit the file. I'm not sure if it's correct because I'm not a developer or a beta tester. I'm an end user who purchased a product that I expect to work. So far 2 out of the three Milviz products I've purchased have required fixing before they could be used. With the F4 you said having both FSX and FSX-SE installed shouldn't be a problem. I've uninstalled FSX but if it requires editing the registry I'm not sure how to do that. I shouldn't have to do any of this anyway. I've purchased products from other developers and they work without a problem. I like your products after the bugs finally get ironed out but I shouldn't have to be the one doing it. I'll try it one more time. I need step by step instructions on how to make your product work. If not refund my money, I'll happily uninstall it and put the money toward the F105 when it comes out.

The F-105 will be just as “difficult” as this one.

Tomas, help this guy out please.

Ok let's do it step by step.

Please check in your FSX:SE main folder that XMLtools.dll is present.
If not, download the zip I posted in this thread and decompress it in that folder.

Then, do a search for DLL.XML and find all of those that are related to any "FSX:SE" or similar name.
Those are the files you need to update.

Let me know of your results and we will continue.

Tom

The XMLtools file is still looking for FSX. I uninstalled FSX and the Beaver. Then reinstalled the Beaver and XMLtools won't load. Is there another installer? Is there an installer specific to FSX-SE? How about some help?

Hang on i didn't see the last post.

I've got several that are possibilities. Is it ..FSX\ConfigData\AppData?