• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

MIT - Maintenance and Income Tool

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.


Also, I finally managed to get my reputation up on my second flight by a whopping 9 points. More payload, here I come!


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.
 
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
 
Bjoern said:
And thus does away with three of the biggest grievances I've had with FSE. Fly where you want, fly what you want, fly as much as you can haul.
Click to expand...

So it's FSE with hax on...


Nice idea, but as a long time user of FSE, it feels a bit lonely to have the same thing with nobody else around...

And you can fly where you want with what you want in FSE :p



I respect the work you put in, and the project is pretty cool, but doing it all alone seems a little bit like why I left airhauler and joined FSE... for the community.
 
Firekitten said:
So it's FSE with hax on...


Nice idea, but as a long time user of FSE, it feels a bit lonely to have the same thing with nobody else around...

And you can fly where you want with what you want in FSE :p
Click to expand...

Not really. Never found much of a good haul for a Metro 3 or Fokker 27 because those that were not used regularly were parked at some godforsaken airfield with awfully unprofitable flights to slightly less awful airfields. Once you've arrived at a bigger airport where the grass is green, the girls are pretty and there's $$$ to be made and logged off for a few days, some eejit would steal the plane and you'd have to start over. I'm pretty sure that my last recorded FSE state has me perilously close to bankruptcy and I frankly don't see any reason to go back to a Cessna 172 to farm enough money for bigger aircraft.

Group shared aircraft require a certain amount of time to invest and coordination with other members and purchasing an aircraft for yourself...yeah, have fun flying for the next few years.

Aircraft repaints(!!!) need admin approval and will delay your flight by a few hours until it's added to the database. I'm not too inclined to mess with [fltsim.x] titles for a single flight or fly with a paint that I don't fly with.
Adding other aircraft takes months because the admins are (understandably) very concerned with getting the right performance data in. I've tried to get the Hs125 into the database and even did most, if not all performance data research work for them, but it never came to anything.

I respect the work you put in, and the project is pretty cool, but doing it all alone seems a little bit like why I left airhauler and joined FSE... for the community.
Click to expand...

The community is another drawback. I'm pretty sure that FSE is long-term fun if you're willing to invest the time, but if you only pop in irregularly you simply don't catch as much of what's going on.
Also, the membership seemed, to a considerable extent, not really on the skill level regarding FSX that I'd feel comfortable around.


MIT was created to do away with the limitations of FSE as I've perceived them. With a bit of pen-and-papering or a tool that syncs aircraft and company status over the internet, you can even have it as a basis for VA or other community stuff.


For what it's worth, you can use both tools alongside of each other. Either keep your FSE payload below MIT's payload limit or don't fly in revenue mode.
 
Bjoern:

Try "pixel_size" for constant panel dimensions across all types of display screens.

Thus:

Code: 
[WindowXX]
background_color=0,0,0
position=8
[COLOR=#ff0000]size_mm=200,600
pixel_size=200,600[/COLOR]
alpha_blend=0.8
visible=0

gauge00=MI_Tool!MI_Tool, 0,0,200,600
 
The most current revision should already have that in its .cfg. Or at least it already scales well with the parent panel.


- Edit:
Oooooh, I see what you mean! Well, I'll keep it in mind and change it later.
 
People who only got their MIT news fix through SOH should check the document linked in the first post here as it will reveal whole bunch of fixes and some additions made to the tool in the past year.

Today's update only deals with a small bug regarding failures and reputation penalties.
 
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
 
It's done. 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:
https://docs.google.com/document/d/1-HUCYi9oLjpQQGUMv29CzjDirvzOlXjep6YluTYIPMk/edit
 
I'm taking my yearly break from fsx, been about 9 weeks since I last bothered firing it up but thanks for this, when I get back again this will come in handy to getme going, can see me setting up a buisness in my corner of West Aussie and seehow I go
 
I haven't used MIT on a small scale yet, but since you can tweak it, it might just work for a "rags to riches" scenario. If not, it's at east very easy to cheat (in between flights). :)
 
Way I see it, got a lot of rich folk who have fancy holiday houses down here and show up couple of times a year so I can be ferrying them and the stuff they need around, in the mean time with all the different projects on the go I can use it to be bringing in and out all the managers plus a DC3 would be cool to haul different goods that are needed urgent, and yeah I can always pad the figures as needed
 
Can you have more than 1 aircraft in the same company, or is it a per aircraft type of thing? Just wondering since you set the company name in the MI_Tool_Aircraft.xml for each aircraft?
 
Astoroth said:
Can you have more than 1 aircraft in the same company, or is it a per aircraft type of thing? Just wondering since you set the company name in the MI_Tool_Aircraft.xml for each aircraft?
Click to expand...

You can have 1, 20 or 3428932534589345425 aircraft per company. Same company save file name = same company.
 
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:
https://docs.google.com/document/d/1-HUCYi9oLjpQQGUMv29CzjDirvzOlXjep6YluTYIPMk/edit
 
This update is of particular interest for Majestic Dash 8 users and bookworms keeping track of their exploits in spreadsheets.


Bug fixes:
- Fixed missing indication for total landing gear failure in message window


Changes:



Additions:
- An optional "force engine running" function for users of Majestic's Dash 8 (see debug settings in MI_Tool_Aircraft.xml).
- The flight result may optionally be exported in .csv formatting as "ZZZ_MIT_LastFlight.txt", located in the FSX main folder. The feature is off by default and has to be enabled 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:
https://docs.google.com/document/d/1-HUCYi9oLjpQQGUMv29CzjDirvzOlXjep6YluTYIPMk/edit
 
Another week, another update

Changes:
- Contract revenue is calulated before takeoff based on estimated instead of actual flight time now
- Actual flight time is tracked from engine startup to shutdown again, as it was a few revisions before
- Rearranged some parameters in MI_Tool_Aircraft into a "Basic Settings" category
- The net result will only be displayed at the end of a flight


Additions:
- Flight plan analysis to estimate flight duration based on true cruise speed in aircraft.cfg or indicated cruise speed and flight plan cruise altitude in MI_Tool_Aircraft.xml
- Broadened the range for payload scale values a bit to make things more interesting
- Estimated flight time is exported to the flight log file
- Last flight's net result will be exported to the flight log file

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

Documentation and download:
https://docs.google.com/document/d/1-HUCYi9oLjpQQGUMv29CzjDirvzOlXjep6YluTYIPMk/edit
 
You must log in or register to reply here.
Back
Top