Bjoern

MIT - Maintenance and Income Tool (Freeware; FSPaX, AirHauler, FSE alike)

Recommended Posts

Maintenance and Income Tool
 
Need a purpose for your flights?
Tired of people stealing your airplane in FSEconomy?
Tired of that annoying flight attendant in FSPassengersX?
Tired of wussy passengers who panic during the slightest bit of turbulence?
Tired of having to purchase airplane paints and repurchase the whole darn thing when you want to switch repaints?
Tired of hunting down payload configuration files?
Tired of being permanently, financially screwed after a particularly bad flight?
Tired of that first officer that chews you out for not switching off the landing lights at exactly 10000.0000 ft?
Tired of running separate tools for passengers and cargo?
Broke?
 
Then MIT is the perfect solution for you!

  • This tool is actually only two gauges(!) to add some purpose to your aircraft. They install as any other subpanel and gauge can be used with any aircraft* having one to four engines**, so you can use it with everything from an ultralight to an A380.
  • Payload is just that: Payload. It doesn't discriminate between cattle, humanoid cattle, weapons or boxes. If it possesses weight, it can be hauled.
  • No whiny passengers. Hit some turbulence? Enjoy the ride! Your payload won't care.
  • No annoying flight attendant to scare you out of your sleep while on a transcon.
  • You're in charge of payload distribution with FSX' or the aircraft's payload manager. No hunting down bloody payload configuration files.
  • The only thing that counts for making revenue is arriving at the destination set in the flight plan. So fly where you want and take as much time as you need (as long as you can pay for the fuel).
  • Not in the mood to buy your plane? Turn the purchase requirement off.
  • Buy a panel variation or an entire aircraft type. It's up to you.
  • Watch the condition of the engine(s), flaps, landing gear and airframe degrade over time. The worse you fly, the quicker this will happen.
  • Failures are probability based and dependant on the plane's condition.
  • If a system fails, the particular type of failure will be randomly chosen.
  • Your reputation influences the amount of payload you're allowed to carry. Treat your plane well, fly well and watch your reputation (and thus income) grow.
  • Earn funds to pay for mandatory aircraft checks. Miss a check and your reputation is going to suffer.
  • Not in the mood to haul stuff? Use "free fly" mode to simulate positioning flights, training flights or simply to screw around and watch your aircraft's condition degrade.
  • Money is tight and there's an expensive check coming up? Cheat. MIT won't judge you.
  • MIT is written in XML and configurable, so you can tailor it to your liking.
  • Persistence across sessions and aircraft and more kindly provided by XMLTools.

So much for the exciting stuff.
The more unexciting stuff:

  • You will have to be able to run XMLTools 2.0. If you can't run it, you can't use MIT. XMLTools works in FSX, FSX:SE and (apparently) P3D. Instructions regarding the download and installation of MIT are included in the documentation.
  • While MIT is tailored to be as flexible as possible regarding the aircraft it is used with, its failure modeling might not play well with add-ons simulating failures themselves (i.e. AccuSim, Damage Mod, RealEngine). In that case, however, failure modeling can be turned off.
  • The destination in revenue mode has to be defined as an airport/airfield/seaplane base and available in FSX' flight planner. Moving ships are therefor NOT supported as a valid destination. Returning from a moving ship to an airport/airfield/seaplane base, however, works just fine.
  • The installation requires intitial configuration for the airplane you've installed MIT in. This is described in the documentation.
  • The default values for revenue generation mode might not work well for the aircraft you might want to use MIT in. The documentation contains a guide on how to determine values that might work better.
  • I can't test each and every scenerio, so there might be bugs. But it's freeware, which is good, right?
  • If you have a particularly good set of values for the configuration options for a certain aircraft, feel free to share them in this thread.

 

The link to the documentation (and download):
https://docs.google.com/document/d/1-HUCYi9oLjpQQGUMv29CzjDirvzOlXjep6YluTYIPMk/edit?usp=sharing
 
Read the documentation, give MIT a whirl and post a few words of appreciation here if you like it.
 
 
 
*Helicopters are untested and the failure simulation is tailored to fixed wing aircraft.
**Four is the simulation limit in FSX. Don't be ridiculous, An-225/B-52/B-36 drivers.

  • Upvote 1

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Heads up!
Make sure that the last leg of your flight plan (the one to your destination) is activated before or after you've landed!
Otherwise, the GPS and thus MIT will never set your status to "arrived" and you won't be able to record the flight.

In case you refuse to fly with a GPS, you'll have to make sure that you've hit all the waypoints on your flight plan (check the nav log).
Or create your flight plan as "Direct To".

This is a MSFS limitatation that I can't work around.

 

 

 

Also, MIT is totally tolerant about any FMCs or ATC addons you use for flying as long as you have a flightplan to your destination loaded in FSX.

Share this post


Link to post
Share on other sites

New revision online.

- Payload calculation is frozen after takeoff. You're welcome, TacPack users, firefighters and parachute carriers.
- The vertical speed of the last landing is now displayed in the message window.
- The message window will show a reminder to leave the landing lights on when you are below the minimum height for lights + 500 ft.
- To facilitate flight plan monitoring, the message window now shows the next waypoint.


Hint for "round trip" flights: Define any airport as the departure airport and create a "direct to" flightplan to your departure/arrival airport or put as many waypoints as you need in between. MIT will only consider you "arrived" at your destination after you've actually flown.

Share this post


Link to post
Share on other sites

When revisions are released what files need to be changed out?

 

Will it mean having to edit the plane name and company name each time?

Share this post


Link to post
Share on other sites

Thanks, guys.

 

When revisions are released what files need to be changed out?
 
Will it mean having to edit the plane name and company name each time?

 
Usually, the two xml files need to be overwritten.
 
Yep. There's no way around that.

Share this post


Link to post
Share on other sites

Jim's comment got me thinking, so...

 

New revision.

Highlights:
- Changed file handling, now with a base module in FSX\Gauges and an aircraft-specific gauge in the "panel" folder
- Automatic installation script for the panel.cfg
- The MIT window will now automatically pop up and sound the "no smoking" chime when a failure occurs. Popup without any sound will occur when a flight is finished. Can be switched off.
- Custom hotkey (default: CTRL+Shift+m) for the MIT window, configurable on a per-aircraft basis.

Read the "Installation" and "Configuration" parts of the documentation, especially if you're lready running MIT!


Upgrade:
- Uninstall the previous version. Keep the save files!
- Install the current version
- Change the save file names in MI_Tool_Aircraft.xml to the ones of your present save files
OR
- Generate new save files with new names by purchasing the aircraft in FSX, then transfer the file names of the new save files to your old ones and reload the aircraft

Share this post


Link to post
Share on other sites

New revision. Save files are compatible. Mind the save file name in MI_Tool_Aircraft.xml when upgrading.


05/01/2016

Improved aircraft value calculation; changed used aircraft value generation; baseline for increased engine wear is now 92.5% throttle (used to be 85%); purged some legacy code from the system file; fixed semi-broken tire damage code; new bought aircraft will now adhere to the time-to-failure value for the engines that is specified in the configuration area

10/12/2015

Fixed display of large amounts of funds in the status window; fixed a bug with reading aircraft-specific component wear rates

Share this post


Link to post
Share on other sites

I'm going to try to get a "destination suggestion" feature into the next revision. The list of available tasks at a given airport is one of the reasons why FSE is so motivating. Let's see if I can replicate this in XML.

Share this post


Link to post
Share on other sites

Yup, I've managed to implement said Desination Finder.

 

Changes:

- Added destination finder

- Revised documentation a bit

- Fixed a bug in touchdown speed tracking

- Planes are much more expensive and price scales better with MTOW now, but you get more starting funds in turn

- Used aircraft generation method improved a bit further

- Failure generation is now simpler and more reliable

- Engine fires may now burn 60 seconds before damaging the airframe

- There's now a clickspot for advancing stuck flightplans to their last waypoint (no more GPS required to do this)

 

 

The download link is the usual one (see manual in post #1).

 

 

MI_Tool_Aircraft.xml has changed, so remember to carry over any custom settings before upgrading!

Share this post


Link to post
Share on other sites

Very small update. I hope that failure generation and random number handling is ever slightly more robust now.

Also changed the installation instructions for XMLTools.

 

Download, etc...see post #1.

 

 

Affected files: MI_Tool_System.xml.

 

Updating XMLTools to 2.01 isn't mandatory, but can't hurt. It's just a matter of overwriting the old with the new .dll anyway.

Share this post


Link to post
Share on other sites

Small update. The reputation penalty incurred during a revenue flight will now clear correctly after accepting or rejecting the flight results.

 

Download: See the linked documentation in the first post.

Share this post


Link to post
Share on other sites

Hi,

 

It does not seem to be working in P3D v3. With a default installation, no changes to the xml files and only the panel.cfg updated with the MIT entries, ingame MIT is showing zero funds (default value in global xml file is 500000. When clicking on 'Buy Used For', it only says (Wait), without anything happening.

 

XMLtools for P3D are installed.

Share this post


Link to post
Share on other sites

Might be this "bug" (well, more of a P3Dv3 feature) at work:

http://fsdeveloper.com/forum/threads/disabling-cab-files.437967/#post-751143

 

Try to move the "MI_Tool_Aircraft" folder into the main P3D Gauges folder and see if it works. Keep in mind that you won't be able to use any plane-specific configurations that way. If it doesn't work, I'm out of ideas.

 

 

(I'm really starting to dislike P3D v3. So many unnecessary bugs and compatibility issues.)

Share this post


Link to post
Share on other sites

New release.

Bug fixes:
- Fixed the unit of the purchase requirement variable
- Fixed display unit of best landing vertical speed
- Landing light reputation penalties should now clear correctly
- Fixed a fuel usage bug

Additions:
- Added MIT configuration overview page
- Added optional structural payload limit for aircraft
- Added gradual loss of power with increasing engine wear by limiting throttle

Changes:
- Best landing vertical speed now tracked per aircraft
- Purged some unused variables from the save files
- Overhauled failure generation system with realistic base probabilities


This update affects MI_Tool_Aircraft.xml, so keep in mind to carry over and review your settings.
Since there were changes to the save files, edit them as per the instructions below or start over!


Save file editing before running the updated MIT for the first time:
1.) Delete lines #38 to (and including) #44 from the aircraft save file. The resulting file should have 61 lines with numbers in it.
2.) CUT line #3 from company save file and PASTE to end of aircraft save file.

Documentation and download:
https://docs.google.com/document/d/1-HUCYi9oLjpQQGUMv29CzjDirvzOlXjep6YluTYIPMk/edit

Share this post


Link to post
Share on other sites

This may be the most comprehensive update to MIT in ages. I've also overhauled the documentation a bit to reflect the changes.


Bug fixes:
- Fixed a bug/exploit that made earning money by idling on the ground possible
- Landing vertical speed is now correctly treated as a negative value
- Aircraft value calculation now working as it should
- Reputation can not go above 100 anymore
- Flight comfort grading uses negative vertical speed instead of positive

Additions:
- Added a help overlay to every page that will highlight all available clickspots
- A basic contract system generates random payload demand and payload rates every flight based on company reputation. Contracts can be renegotiated at the cost of reputation
- Calculation of payload demand uses maximum structural payload as a baseline when a value for such a limit is defined in the aircraft settings file

Changes:
- Landing light altitude restrictions now depend on the departure and destination airport altitudes
- Rewrote the user interface gauge, cutting the lines of code by more than 50% and reducing file size almost by half
- Polished the UI gauge here and there, changing orders and terms in some places
- Proper double-headed arrow bitmap
- A/B/C-Check and repair cost now scales with aircraft empty weight
- Total aircraft time decreases aircraft value
- Flight time is only tracked when airborne
- Overhauled the entire documentation


This update affects MI_Tool_Aircraft.xml, so keep in mind to carry over and review your settings.


Documentation and download: See previous post.

  • Upvote 1

Share this post


Link to post
Share on other sites

Quick and small update:

 

Bug fixes:

- Fixed a bug that prevented tracking of the landing vertical speed

- Engine power limitation due to engine wear works correctly now

 

 

Only MI_Tool_System.xml is affected, so no need for aircraft and save file config mumbo jumbo.

 

 

Documentation and download: See previous post.

Share this post


Link to post
Share on other sites

Another small update:

Bug fixes:
- Landing vertical speed should finally be displayed and treated correctly
- Landing gear wear is only calculated when the aircraft is actually moving

Changes:
- Flight quality ratings are only computed when airborne
- Flight comfort now tracks g force instead of vertical speed

Additions:
- An offset parameter to adjust both min and max allowable flight g force in MI_Tool_Aircraft.xml


This update affects MI_Tool_Aircraft.xml, so keep in mind to carry over and review your settings!


Documentation and download:
See post #18.

  • Upvote 1

Share this post


Link to post
Share on other sites

hi björn

 

first: thank you very much for your great little software!! i'm new to it, coming from the other cargo-payware, which i don''t like anymore. slow & clunky interface with time pressure and excel-like micromanagement-grind. your tool is exactly what i was searching for! love it!!! :)

 

1. i have downloaded your latest files some minutes ago and have replaced all old files and folders with your new ones in default config. now it shows a landing value. but  at "best landig" it shows always "-9999 ft/min" . the value doesn't change (same plane, several landings). could you doublecheck?

 

2. feature request: would it be possible to add some kind of loogbook-file next to the other files in main folder, company based und loadable in excel? for a simple overview for the best or worst landings, and some numbers showing the growi of the company? would be a nice addition.

 

3. another feature request: if not too complex, could you make a panel version with manual engine on/off buttons, that could work with the majestic dash8? you know the unrecognised engine status problem with the majestic plane? that would be great, if a workaround would allow to fly the dash8 with your tool.

 

however, i hope you go on with your software!!! 

 

beste grüße,

elki

Share this post


Link to post
Share on other sites

hi björn

 

first: thank you very much for your great little software!! i'm new to it, coming from the other cargo-payware, which i don''t like anymore. slow & clunky interface with time pressure and excel-like micromanagement-grind. your tool is exactly what i was searching for! love it!!! :)

 

1. i have downloaded your latest files some minutes ago and have replaced all old files and folders with your new ones in default config. now it shows a landing value. but  at "best landig" it shows always "-9999 ft/min" . the value doesn't change (same plane, several landings). could you doublecheck?

 

2. feature request: would it be possible to add some kind of loogbook-file next to the other files in main folder, company based und loadable in excel? for a simple overview for the best or worst landings, and some numbers showing the growi of the company? would be a nice addition.

 

3. another feature request: if not too complex, could you make a panel version with manual engine on/off buttons, that could work with the majestic dash8? you know the unrecognised engine status problem with the majestic plane? that would be great, if a workaround would allow to fly the dash8 with your tool.

 

however, i hope you go on with your software!!! 

 

beste grüße,

elki

 

1. This shouldn't happen. I'll check it out.

 

2. Company related values can be pulled from the save file after every flight (a list of variables corresponding to the values is provided in the gauge's folder). Exporting the last flight's result can be implemented as an option as well, but further processing of the results (in a spreadsheet) would be entirely up to you.

 

3. Should be doable, I guess.

 

 

 

P.S: A+ username!

 

 

 

- Edit:

 

I think I found the source of the best landing VS bug. The fixed revision is uploaded, so redownload it (same link) and overwrite MI_Tool.xml.

Share this post


Link to post
Share on other sites

The logging funtion for the last flight and the engine status override were less work than anticipated. Both require activation in the aircraft-related config file and the former will export in CSV format to make it easier to import into a spreadsheet.

 

Still considering some other things, so I won't upload the new revision just yet.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now