Where Flight Simulation Enthusiasts Gather from Around the World!
AVSIM Library - Search Results
| Category: Flight Simulator X - Aircraft Repaints, Textures and Modifications | |
| Boeing B-17G Flying Fortress #43-97976 "A Bit o' Lace" |
|
Images related to this file:
File Description:
This folder contains a repaint for the accu-sim version of the A2A B-17G Flying Fortress. It represents #42-97976 "A Bit o' Lace", which was assigned to the 709th BS /447th BG. The nose art consisted of a cartoon by Milton Caniff. The co-pilot was Lt. John Bauman, a fraternity brother of Milton Caniff. He sent Caniff a detailed idea of the proposed artwork and the sketch was returned with Caniff's annotation: "A Bit-O-Lace for Lt. John H. Bauman, and the rest of the gang, with my best wishes - Milton Caniff NY, Oct. 1944". Nicholas Fingelly, an artist attached to the 709th BS, carried out the work and completed the painting in about six hours and gave Milton Caniff full credit for his his character. Her first crew flew 35 missions over Europe with no injuries, although returning with a good many holes, at times. The closest call was when a piece of shrapnel came up through Navigator's table and "Ike" Eisenhart's arms, but missed him. A surprise souvenir for Ike, which he still has. She flew more missions with different crews, until the april 4, 1945 flight. From the navigator, John Kirkwood: "Right over Kiel, and seconds before the bomb release, I heard the co-pilot say that "This airplane feels funny." Seconds later the tail gunner, who had regained his power of speech, blurted out something to the effect that part of "The tail was gone." A flak shell had gone right through the left horizontal tail, leaving only a partial surface, and completely removing the left elevator.
We dropped out of the formation, and tried to drop the bombs, but the electrical system failed. We flew north a minute or so, the plane now in the hands of the pilot. The pilot did not want to drop over Denmark, so we turned out over sea, and dropped via screwdriver. Actually, we were over Schleswig-Holstein, according to my position, but it was close, and Tom did not want to chance killing danes.
We flew on, at a reduced speed, far out to sea on a west-south-west course with occasional ETA's to the pilot. Several fighters joined us, and finally we got back to the base, and the runway was cleared for us. A decision had to be made by the pilot: To jump or ride her in.. Tom decided that he could land the plane, so we all congregated to the radio room, and that was that.
I might add that none of us had any desire to jump. Most of the photos of 976 were taken after repairs, hence the dark colored rudder and left elevator. As you know, the color prior to the damage was silver. 976 flew one or two missions after that, but I never saw her again, other than in a color photo of the moth-balled fleet in Arizona."
Repaint by Jan Kees Blom, based on the repaint kit by A2A.
| Filename: | Boeing_B17G_Flying_Fortress_4397976_A_Bit_o_Lace.zip |
| License: | Freeware |
| Added: | 20th August 2010, 22:14:46 |
| Downloads: | 723 |
| Author: | Jan Kees Blom |
| Size: | 19.95 MB |
| Category: X-Plane - Utilities | |
| X-Camera 2.2.1 |
|
Images related to this file:
File Description:
The X-Camera 2.1.1 plugin for X-Plane 9 and 10 is a replacement camera system that lets you define multiple view categories and multiple views within those categories that are associated with specific aircraft. X-Camera is similar to EzDok for FSX only for X-Plane. Watch this short X-Camera demo on YouTube: https://www.youtube.com/watch?v=PgOxG8ejq9A
Each view can have options:
- TrackIR:
Each view can enable or disable the TrackIR input. If the view is out the cockpit window having TrackIR enabled is desirable. However, if the view is a close-up of an instrument panel then having TrackIR disabled is probably the better choice since the view will be stable making it easy to click on cockpit controls with the mouse. We also support LinuxTrack on Linux and Mac systems.
- HeadShake:
If the HeadShake plugin from SimCoders is installed then the view can accept input from HeadShake. Similar to the TrackIR feature you will likely want this enabled for certain views but disabled for views on instrument panel close-ups where a stable camera makes it easier to use a mouse to control cockpit knobs and switches. The HeadShake plugin must be at version 1.3 or higher for the integration to work.
- Scenic Flyer:
If the Scenic Flyer plugin from Digital Avionics is installed then the view can choose to display either the Scenic Flyer Glass panel or GA panel.
- Smooth Transition:
When this option is enabled the camera with smoothly transition from one view to another over approximately half a second. When the option is off the view will transition immediately.
- Views can be controlled in a number of ways:
> Each view can be positioned by using keyboard keys or a control panel
> The camera'™s X, Y, Z, Heading, and Pitch can all be adjusted for each view
> Views can be assigned to a HotKey or JoyStick button for easy selection
> HotKey or JoyStick button can be used to navigate to next or previous views
> The views for a specific aircraft can be saved to a CSV file for easy editing
- Walk Mode:
Any view'™s camera can be placed in Walk Mode. While in this mode the camera can be walked or floated around using keyboard input. If you ever played the video game asteroid that is what walk mode is like. The mode is particularly useful for pre-flight inspections of your aircraft. You can create a external view and after selecting that view you can "Walk" the camera around checking out your landing gear, props, etc.
- Linear Transitions and Auto Advance:
Linear transitions allows you to define a transition between two adjacent cameras in category. This capability, in conjunction with the auto advance feature, allows you define fairly sophisticated animations that can be used for automated Pre-flight inspections, scenery viewing, and cool transitions affects that can be used when creating flight videos. All the transitions in our YouTube video were done with X-Camera.
- Bezier Curve Transitions:
Bezier curve transitions allows you to define a transition between three or more adjacent cameras in a category. This capability, in conjunction with the auto advance feature, allows you define fairly sophisticated animations that have an ultra smooth movement between the curve control points.
- Many Unique Camera Attributes:
Tracking Cameras - Camera Leveling - Smooth Camera Joining - Auto Advance to the Next Camera - Individual Zoom and Field of View Setting - External Cameras - Free Cameras - Target Following Cameras - Cineflex Cameras - Automatically Generate Unique Orbit and Fly-By Animations
X-Camera can create unique orbit and fly-by camera sequences by providing a few key parameters
- Airport Cameras:
You can define a set of free cameras associated with an airport. You can create up to 2,000 cameras per airport. X-Camera can also automatically populate airport cameras by reading the airport scenery files and creating cameras at runways, starting locations, taxiway signs, and airport viewpoints. You can map a joystick button to quickly switch between your aircraft camera set and the nearest camera at the nearest airport.
- Target Following Cameras:
Targets are locations defined by a latitude, longitude, and elevation in meters. Target following cameras are a special type of external camera that is attached to your plane and it has the ability to track a selected target. You can also view the target reciprocal which as a view from the target back to you plane.
X-Camera Tutorial Videos: There is also a four part series of tutorial videos that will help you get started with X-Camera. You can access them from the X-Camera Tutorial Page: https://www.stickandrudderstudios.com/x-camera-tutorial-videos/
The full manual is included in the zip file you can also view it here: https://www.stickandrudderstudios.com/downloads/User_Guide.pdf
| Filename: | XCamera_221.zip |
| License: | Shareware, limited functionality |
| Added: | 27th January 2017, 15:14:21 |
| Downloads: | 478 |
| Author: | Mark Ellis |
| Size: | 4.61 MB |
| Category: Microsoft Flight Simulator (2020) - Utilities | |
| Flightplan Visualizer 1.19 |
|
Images related to this file:
File Description:
Flightplan Visualizer (FV) version 1.19.0. Copyright 2018-2021 by Pelle F. S. Liljendal ([email protected]), all rights reserved.
FV comes with 1164 pre-imported AI flightplans (of which +380 are BizJet flightplans, the rest are commercial). However you are able to import additional (AI) flightplans yourself. Once imported these (AI) flightplans can be visualized on a map-view, and the user will be able to search accross all these. Hence you can use the program as inspiration as to which routes to fly. E.g. you can search across all imported flightplans to find all flights in an A321 flying into/out from LDDU, or simply to look for all flights in a Boeing 747-8F.
Simply run the included installer to install the software. The program will be installed into "C:\Program Files (x86)\Flightplan Visualizer" and all datafiles will be installed into: "C:\Users\[UserName]\AppData\Roaming\FlightplanVisualizer". The program comes with a full manual explaining everything, and a 3 page quick manual to get you started. The first 3 times you run the program the quick manual will automatically open. The forum is hosted here: https://forum.aerosoft.com/index.php?/forum/919-flightplan-visualizer/
Version 1.19 Contains the following changes:
- The release-version of the application is now aimed at 64-bit (granting access to more memory if needed). Enabling 64-bit adds a memory overhead of approx 50% compared to 32-bit, but its the "price to pay" to have access to more memory (for those of you with many active flightplans loaded into memory at the same time).
- FV can now connect to your simulator using FSUIPC (tested both with P3D and MSFS). By default you will have to manually connect/disconnect (using new menu-items in the File-menu). However in settings you can choose to do it automatic. When automatic-connection is selected the connect/disconnect menu-items becomes inactive.
- When connected to a sim, the location/heading of your aircraft can be displayed on the map, using an orange aircraft-marker, and hoovering the mouse over this marker will display some key data (GPS-location, altitude, heading, speed and so on).
- Added abillity to playback audio-files. In settings you can choose which audio-device to use, and set the volume at which these files are played (defaults to 50%). If volume>0 these files will automatically be played back whenever FV connects to/disconnects from the Sim.
- Added additional icons that are automatically selected to indicate when the program is connected to the simulator. Hence the icon in the main-form will indicate if FV is connected to a simulator or not.
- In the form for editing (user)-airlines and in the form for searching airlines the context menu now have a menu-item called "Show usage". When selected, it will generate a report showing all the (active) flightplans in which the airline is used.
- Added a new "Manual" check-box next to the load-factor when editing user-airlines. This check-box needs to be checked if you want to manually enter a load-factor. When not checked (default) the load-factor will automatically be set to the default value of the selected country.
- When editing user-airlines, the airline just added/edited will be visible and selected in the list-view. Likewise when deleting an airline, the previous item will be be visible/selected (in stead of always scrolling to the top afterwards, as in previous versions).
- The Insert/Delete keyboard-keys can now be used as shortcuts adding/deleting user-airlines and user-aircraft (both owned and types).
- The gate-map context-menu (Airport Info), now allows you to re-center the map (in case your have been panning the map, and can't locate the airport again).
- Added a new menu-item/form to calculate head/cross-wind from manually entered flight/runway-heading and wind-direction/speed. Don't forget the runways tab-page in the Airport-info form already calculates this for each runway (and wind-direction/speed is automatically obtained from METAR).
- Added a new menu-item/form to convert plain-text into morse-code. There is also a button that lets you listen to the generated morse-code, so you can practice your morse-code listening skills (e.g. entering an ILS/VOR-ident, to know which morse-code to listen for in the aircraft, to verify the correct ident is reqeived).
- The "Cruise speed" column have been removed from the aircraft tab-page of the Edit Flightplan form to make more room for the Carrier/Operator-columns. In the past these simply contained the ICAO for the airlines. Now it both contains: ICAO, IATA (if not blank) and Name.
- The criteria in the leg-search window now allows you to filter on departure/arrival week-days (e.g. only include flights departing a particular airport on a Saturday or Sunday).
- When using the flightplan-filter on the main-form, it will favour the current active flightplan (as in previous versions), however if not able to, it will select the first flightplan included in the filtered list (in stead of choosing "[None]").
- Improved import of AIGFP-flightplans where the airport is not contained within the embedded airport.txt file and is using a different ICAO-code in route-files (observed for "AIG_UTair_Summer2018v6" and "AIG_S7Airlines_Winter2019-2020v3").
- Added runway-info (for both Departure/Destination-airports) to the flightplan leg-report. For ILS-eqiupped runways its lists the ID (both as text, as morse-code), frequency and ils-slope.
- Morse-code also added to ILS-ID column on the "Runways" tab-page of the airport-info form. Above the list-view there is also a label showing the morse-code (using a larger font), and next to it there is a button that lets you listen to the morse-code.
- Traffic-pattern direction (for take-off and landing) are now displayed for each runway. These data are extracted from the scenery by MakeRunways, hence the info can't be "better" than the info in the scenery (hence most default airports simly shows 'Left').
- Current/peak- memory usage is now logged at various stages while running, and when closing the program. These values can also be observed opening the about-box, which will also forcefully append these values to the log.
- When using MkRwy with MSFS it can't obtain the country-name, hence these are taken from the airport-database embedded with FV. However the name for USA ("United States of America") is too long to be shown together with state-name, hence code have beed added it to shorten it to "United States" (which was the default country-name used in FSX/P3D).
- Changed font in Comments-box for user-aircraft to a fixed font, in case some users what to enter text "in columns" (e.g. if you make "tables" with speed-restrictions).
- Changed the color of the splitter-bars in the Airport-info and leg-search forms to a draker color, to better indicate where it is.
- The build-part of the version-number can now be ignored when performing the automatic version-check at start-up. This new setting is by default disabled. If enabled it will ignore changes from version 1.x.0 to 1.x.1 (e.g. an update from 1.19.0 to 1.19.1). However major/minor versions-updates (e.g. from 1.19.x to 1.20.x) will not be ignored.
- Fixed: Excessive logging while importing AIGFP flightplans removed (leftover from fixing a bug before the release of version 1.18).
- Fixed: When using kg in the leg-info report, the weight of Luggage incl. pax weight (shown in parentees) was wrong.
- Fixed: Button to open filter-manual on Gate-page of the Airport-info form was not visible/position was not fixed.
- Fixed: The wind-speed obtained from the METAR and used to calc head/tail-wind on the Runway tab-page of the Airport-info form, did not considder the unit (e.g. Khp or meters-per-second).
- Data: A VERY BIG THANK YOU to Bruce Nicholson for assistance updating the Airline-database, both with new/missing entries and marking defunct airlines as such.
- Data: A lot of "fictios airlines" was added as well. These are used for companies without official ICAO/IATA codes. To indicate they are fictios the ICAO-code is set to "---" and the IATA-code is used to indicate the kind of traffic (e.g. the combination "---/BZ" is used for biz-jet flights).
- Data: Also thanks to Bruce for pointing out that a few aircraft were not being detected as they should. So this version should do a better job with Cessna T206H, Cessna Citation SII/S550 and Global 7500.
- Flightplans: The bundled AIG flightplans have been updated to the latests versions/revisions available from AIG (there were a few defunct that was removed, a few new versions that was added, and a lot of new revisions being updated).
- Flightplans: Eric Steinmetz's Bizjet (AI) flightplans that have previously been available as a separate download are once again bundled with the installer (they are only installed if you choose the option during installation). These have all been updated to use the new "---/BZ" airlines (for companies without official ICAO/IATA-codes), and the Author/Provider have been set to "Eric Steinmetz"/"ESAI" (the previous/separate download was created before adding author/provider to the software).
Pelle
| Filename: | Flightplan_Visualizer_119.zip |
| License: | Freeware, limited distribution |
| Added: | 2nd May 2021, 00:02:01 |
| Downloads: | 280 |
| Author: | Pelle Liljendal |
| Size: | 35.71 MB |
© 2001-2026 AVSIM Online
All Rights Reserved
Privacy Policy |