• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSX DLL.XML Problem

Messages
40
Country
canada
I purchased and installed two files from FSDeveloper - GLV2000 GPS and the Bendix Radios Gauges. I had a lot of issues with them, I have requested a refund and done the uninstall as instructed.

I was then left with a huge problem which was caused by the dll.xml file. It took me many hours to repair by finding a previous backed up file and copying it into my FSX folder. Finally everything is back to normal except for the one FSDevelopers aircraft which I used to change out the gauges with - the Beechcraft V35B Bonanza. I am left with an aircraft that launches but the avionics are totally messed up and do not work. I have completely uninstalled the Bonanza and reinstalled it but there is always an error message during the install pertaining to the dll.xml file.

If anyone can help me with this that would be great if not I will just have to ditch this aircraft from my hangar and purchase another producers Bonanza V35 as I do like this aircraft.
 
We do not offer payware add-ons here. Take any support inquiries to the actual developer.
 
Thanks Gary...

You're welcome, Dane.

BTW
: In addition to the links I posted above, I am suggesting that if you have not done so already, be sure to view these pages:

http://www.fsd-international.com/Hangar/V35B/

http://www.fsd-international.com/support/guarantee.htm


NOTE: In the latter link, you may wish to review certain statements in particular (quoted for purposes of review):


BlueDot.png
Refund requests must be made within 10 days of date of purchase.

BlueDot.png
The version of Flight Simulator for which the software is compatible is clearly specified for every title. Returns due to version incompatibility will be subject to a $4.00 non-recoverable license fee.

BlueDot.png
Refunds due to duplicate orders or orders by mistake are also subject to a $4.00 non-recoverable license fee.

BlueDot.png
The software must be completely uninstalled on each computer on which it was installed prior to receiving a refund. An uninstall tool will be provided for this purpose. If the purchase was by CD-ROM, the CD must be returned as well.

BlueDot.png
Shipping charges from the original purchase, and for return of the disk, are not refundable.

BlueDot.png
If a refund is requested due to technical issues we request that a good faith effort be made to follow the suggestions from our technical support staff first. For example, like a lot of Windows software, restrictive Windows access are permissions issues can result in installations problems. Software (not just ours) often requires no permissions restrictions, and sometimes, temporarily disabling security software. We have a publication that details this issue here. We cannot honor a refund request if you do not follow these procedures.

BlueDot.png
Unconventional hardware setups can create difficulties within the complex security environment in todays operating systems. For example, running programs like Flight Simulator or Prepar3D on external drives, SSD drives, etc. Windows is hostile to these locations on your computer in terms of access/permissions issues. We will work with you to try and resolve these Windows security related issues, but cannot guarantee that these unconventional setups will work. Refunds due to such Windows security issues or unconventional hardware setups will be subject to a $4.00 non-recoverable license fee.


CAVEAT: It is apparent that you have at some point 'customized' the panel configuration for a FSD payware aircraft.

Be aware that FSD gauges are very sophisticated, and have interconnections with various locations on your hard drive as well as in the Windows registry, and altering any of that out-of-the box default functionality as intended by FSD may at the least cause malfunction, and perhaps even void their terms and conditions for support or refund eligibility.

Also, since it would not be a default configuration when one has tinkered with their panel and/or gauge file configuration, it is not an impossibility that FSD will refuse to support your re-installation or removal of that aircraft and/or any of their add-on gauges.


Additionally, be aware that public discussions on various FS web forums contain numerous reports that FSD, in spite of the technical brilliance of their original in-house and sub-contracted design team(s) with nearly all products over the years, have a IMHO, appalling history for how they treat their customers even when all their instructions and install / un-install utility procedures have been followed precisely. :alert:


Personally, as a former customer of theirs, I decided not to give them further business because of their, IMHO, bad behavior by initially accusing me of piracy because purportedly their < not-so-foolproof ? > software "should" have otherwise worked properly. :yikes:

It turned out that they had failed to disclose "Shockwave Flash" had to be enabled throughout my Windows and web browser configurations in order for their store / download / install / configuration / un-install software to all work properly, and at that time I had inadvertently disabled "Flash" everywhere on my computer via a particularly 'over-zealous' plugin extension to FireFox. o_O


In your OP for this thread, you have indicated you would like to customize the panel and gauge configuration for the FSD Beechcraft V-Tail Bonanza to utilize non-FSD panel and gauge components.

I am doubtful that anyone here at fsdeveloper forums would be willing to assist with circumventing the intended design and security measures built into a payware aircraft, especially one from FSD. :pushpin:

And I doubt am confident that FSD would NOT support that process either.


AFAIK, there are other Beechcraft V-Tail Bonanza aircraft available as both payware and freeware; I suggest that you consider those options.

I would also suggest that you re-consider how your present dilemma with the DLL.XML file and the panel and gauge configuration for the FSD Beechcraft V-Tail Bonanza ...may have originally occurred.

It also seems possible that the FSD install / un-install may have failed due to your having some configuration issues in Windows with security and/or file / folder permissions that the FSD software may not be able to deal with successfully.

Alternatively, you may have had unexpected issues with the panel and/or gauge configuration of the aircraft at the time you attempted to un-install it ...that the FSD software may not be able to deal with successfully.


As for me, I continue to await the Aerosoft Pilatus PC-6 Porter ..to replace my FSD version of that aircraft (the FSX version was re-port-edly a "port" of the FS9 Porter model ...despite the 'upgrade' fee). ;)


Good luck with your endeavors. :cool:

GaryGB
 
Last edited:
I just wanted to add my two bits as I didn't know where else to have it circulating and found if someone else is Googling the web for this.
I just uninstalled my GLV2000 (from FSD International) as I couldn't get it to work after a LOT of time put in to sort out the bugs.
It was supposed to be a simple straight forward install on a clean FSX, (Win 10) to be used in the stock Cessna 172 and the RealAir Turbine Duke v2.
The GPS had several issues including not able to "lock" (get a green annunciator result) and have the VNAV kick in. It is very confusing setting up the VNAV as well.
The altitude setting system is very limited in that you have to click, yes click, one 100ft step at a time with a significant delay between each click. Not mouse wheel or keyboard option. So you can imagine how long that would take to up your altitude by, say, 5k ft. That's just one example of the un-intuitive nature of the design.

I went back and for several times with very pleasant tech support who provided limited canned responses along the line of "we have never had this problem before"...made me feel special for sure.

The GPS didn't install in the VC panel, only the popup. She said it was because the size was wrong and it couldn't be modified to fit. Again, I was trying to get in the FSX stock Cessna 172 and RA Duke. Not exactly out side of the standard of what you thing they would design it for.

Anyways, if anyone else is reading this, AVOID the product! I doesn't work well if at all and it is not cheap. Apparently the "money back guarantee" is not all that easy to get also with lots of conditions attached. Hoops to jump through including "proof" that you have done everything you can to install it properly.
So, hope that aid someone in there decision about the product and the company.
 
Robert, the gauge is designed to be an exact fit for the default G500 GPS, so it should be an easy drop in replacement for any aircraft that has the G500 installed in the VC.
 
That makes sense. However, their config/control tool couldn't make it happen and they couldn't/wouldn't(?) provide any help in editing the panel.cfg file.
Actually, I could almost have lived with that if it wasn't for the other issues I mentioned with the GLV2000 such as the LNAV/VNAV never engaging the VNAV was the main reason I purchased the unit in the first place.
Thanks for the reply though Bill.
 
Back
Top