• 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.

Flight Dynamics Workbook Error

Messages
683
Country
us-california
I decided to try this program last night. When I try to "write updates" or "update aircraft cfg" I get a Visual Basic run-time error 13. I'm using Excel 2007.
 
I just Googled 'Visual Basic run-time error 13' and got over 6 million hits. Putting the same line in quotes ("...") returned 29,100.

Looks like it might be a hard one to track down as it seems multiple things can cause the error.
 
I decided to try AirWrench. It looks a lot easier, and I am supporting a good source of info for us developer types. :)
 
Re FDWB:- are you allowing the macros in the spreadsheet to run? (Excel security settings)
 
I had them set to run. I seem to recall trying the program many years ago with the same issue being why I gave up back then.
 
I use the Workbook a lot because it lets you decide on the details of air file values. AirWrench is a super tool for checking how those details work out in the big picture, so I develop using Workbook and do a sanity check using AirWrench.

AirWrench makes various assumptions based on the type of aircraft you select on the "Tuning" page. As a result, I never save the edited data, because it changes the air file I have spent hours on using Workbook.

Workbook is very complicated, but I have found it well worth the effort, having used it for about 12 years.

If you get an error with the Workbook, when writing Updates.txt, it is usually due to an input you made in the Data sheet that resulted in an error in one of the other sheets. The Write Updates.text associated macro will stop when it hits an error. You can try to debug the problem in Visual Basic, but usually Workbook highlights a problem entry by coloring it red.

Roy
 
Back
Top