-
Posts
8,142 -
Joined
-
Last visited
-
Days Won
16
Content Type
Profiles
Forums
Gallery
Downloads
Store
Everything posted by FastCargo
-
Depends on the aircraft and flight model. For instance, a T-38 is nearly impossible to put into a spin, you could do stupid stuff with the stick post stall and nothing would happen except the aircraft falling like a brick. A early F-4 on the other hand, was dangerous at high AOA if you put any aileron at all. Most flight models for the SF series are fairly docile handlers at the limit...in line with the sim-lite focus, that and 'at the limit' handling can be hard (though certainly not impossible) to model. However, reefing back on the stick at 400 knots, especially in a non hard limit aircraft, would in reality result in an over-G, and possible catastrophic failure/G-LOC. You do NOT ham-fist these aircraft. What you're doing is a quick way to end up as meat on the table, out of airspeed, altitude, and ideas. FastCargo
-
Usually that's because you're stalling the aircraft...fast jets act like that if you put too much AOA on them and hold it there. FastCargo
-
F-20 Tigershark
FastCargo replied to Hitory's topic in Thirdwire: Strike Fighters 1 Series - General Discussion
Nice!!! So everyone stop asking ME to make one! FastCargo -
F-20 Tigershark
FastCargo replied to Hitory's topic in Thirdwire: Strike Fighters 1 Series - General Discussion
Actually there sparky, a B-36 exists in Gmax (I have the model and was simple to convert to 3ds Max). Maybe you'd like to hone your newfound modeling skills on it? PM me for details... FastCargo -
Australia goes with Fullbacks?
FastCargo replied to Silverbolt's topic in Military and General Aviation
If nothing else, it would be nice to have a real advesary squadron using actual advesary equipment. Why guess at capabilities when you can buy and use! We've done it on a limited basis (Constant Peg) but a full up dedicated squadron would be better... FastCargo -
Taking a back seat?
FastCargo replied to FastCargo's topic in Thirdwire: Strike Fighters 1 Series - Mods/Skinning Discussion
Progress. As mentioned, for the F-5s, I plan to use the MF F-5 pits...makes sense, why duplicate effort. Surprisingly, they work pretty well. Even got the mirrors to work properly. Here are 2 shots of the MF F-5A cockpit in my F-5B: The canopy bow you see there is the external model. Note in the first picture you can actually see the backseater's canopy open. You'll be able to see the canopy open and close from inside the aircraft. Learning a lot here... FastCargo -
I like the exploriing you're doing with the TW engine there Lexx...like I said eariler, your cockpit experiments are why I built the T-38/F-5 family the way I did. I REALLY like those cirrus effects, but from what you're saying, that's not something that can be done in a campaign...is it...? FastCargo
-
Folks, quick clairification...the initial report doesn't say the engines failed...it says the engines failed to respond to a throttle up command. In other words, the engines were running, but not at enough thrust to maintain the specified approach speed. This was after autothrottles and manual throttles both failed to make the engines respond. This was not an engine flameout, this was something else. What bothers me is this sounds an awful lot like the first A320 accident. This is only at first glance though... FastCargo
-
Danish Drakens
FastCargo replied to hgbn's topic in Thirdwire: Strike Fighters 1 Series - Mods/Skinning Discussion
Hey guys, merged the topics since they were about the same thing and hgbn got in touch with a Column5 representative. FastCargo -
I took a look at what you're asking. Each airfield has it's own ini file pointed at by the TARGETS file. Example, in the stock and Gepard/JSF_Aggie combo GERMANYCE_TARGETS.INI file: [TargetArea261] Name=Fassberg Airbase Position=461000.000000,671000.000000 Radius=8485.281250 ActiveYear=0 Location=1 Alignment=FRIENDLY AirfieldDataFile=german_airbase1.ini NumSquadrons=6 Target[001].Type=Runway6 Target[001].Offset=0.00,0.00 etc, etc, etc... And in comrpnt's airfield light mod GERMANYCE_TARGETS.INI file: [TargetArea261] Name=Fassberg Airbase Position=461000.000000,671000.000000 Radius=8485.281250 ActiveYear=0 Location=1 Alignment=FRIENDLY AirfieldDataFile=GERMANYCE_AIRFIELD1_LAYOUT2.INI NumSquadrons=6 Target[001].Type=Runway6 Target[001].Offset=0.00,0.00 Note the difference in bold. So, how to do a combo? First, you WILL NOT be able to mod Gepards' 8 new airfields or JSF_Aggie's airfields with comrpnt's light mod. The airfield.inis use coordinates to place objects based off a centralized point. Gepards airfields now each have a unique look and coordinate layout. In other words, if the old airfield end of the runway was X,Y, the new airfield may have (X+x),(Y+y) as the end of the runway point....but comrpnt's light mod is based off the older X,Y...and so trying to fuse those files will have bad results (misaligned lights, etc). Fortunately, that shouldn't be hard to avoid. Okay, first, BACKUP the GERMANYCE_TARGETS.INI file you want to alter...yes, AGAIN. Second, open up that GERMANYCE_TARGETS.INI file you want to alter AND comrpnt's GERMANYCE_TARGETS.INI file with your text editor of choice. You will need to have both files open at the same time. Third, within the file you want to alter, start a search at the top of the file looking for this entry: AirfieldDataFile=german_airbaseX.ini where X is a 1,2,3 or 4. Fourth, as you come up to each entry the search function finds, note the [TargetAreaXXX] entry and find that coorsponding entry in comrpnt's GERMANYCE_TARGETS.INI file. Fifth, copy comrpnt's GERMANYCE_TARGETS.INI [TargetAreaXXX] entry (the whole entry) for that airfield and paste it OVER the cooresponding entry in the GERMANYCE_TARGETS.INI file that you are altering. This will make sure that things line up in case comrpnt made minor changes on the airfield to accomodate his lights. You will need to do this for every FRIENDLY airfield entry that cooresponds to your search. After all this, save your new GERMANYCE_TARGETS.INI file. In fact, I'd recommend saving after verifying every cut and paste. Make sure comrpnt's GERMANYCE_AIRFIELDX_LAYOUTX.INI and GERMANYCE_AIRFIELDX_LAYOUTX_QRA.INI files from his mod have been copyed to your Terrain/GermanyCE directory. That should be it...you should find that your other airfields besides Gepards and JSF_Aggies now all have comrpnt's lights. By the way, I figured this out with about 5 minutes of skull sweat, knowing very little about airfield.inis other than simply opening the ini files up and reading. It isn't hard...just tedious. FastCargo
-
Danish Drakens
FastCargo replied to hgbn's topic in Thirdwire: Strike Fighters 1 Series - Mods/Skinning Discussion
Normally pylons are part of the aircraft model and cannot be altered externally. FastCargo -
The aircraft even with autothrottles only flies at the speed you tell it to...not the other way around. Period. FastCargo
-
A short somewhere? Also, sometimes I've seen this happen on a motherboard with a loose power connector on the motherboard. The solder point is worn and only just makes contact... FastCargo
-
Actually, in most modern airliners, it's really better to have the auto throttles on. Autothrottles tend to do as good or better job with speed adjustments. Modern high bypass engines have long engine response times due to the rotating mass. In addition, autothrottles engaged will enable safety features (such as auto throttle up if a stall condition is encountered, etc). Also, unlike low bypass engines that have hard stops, modern high bypass engine limits are determined based on temp, PA, etc. Unless you want to be fiddling with the engine limits on a go-around, it's better to just hit the TOGA lever and let the engines wind up safely on their own. Otherwise a rash action (other than for something like windshear or GPWS alerts) will cause a overpressure, damage to the engine and possibly the pylon. Finally, Cat III approaches (zero visibility) require the use of the autothrottles. And at any time, you can override either with a button toggle and/or direct manipulation of the throttles. FastCargo
-
GermanyCE Terrain Mod Combo INI files View File Readme for combining Gepard's 8 New Airfields and JSF_Aggie's Highway Airfields mods. These files are simply replacements for your GERMANYCE_TARGETS.INI and GERMANYCE_TYPES.INI files. What you will need first: Wings Over Europe with the GermanyCE terrain (Duh!) Gepard's 8 New Airbases for WOE: http://forum.combatace.com/index.php?autom...p;showfile=5078 JSF_Aggie's Highway Airfield Mod: http://forum.combatace.com/index.php?autom...p;showfile=2950 Instructions: 1. Backup your GERMANYCE_TARGETS.INI and GERMANYCE_TYPES.INI files first (if they have been extracted)! 2. Install both mods...don't worry about overwrites, we'll be fixing those later. 3. Copy the GERMANYCE_TARGETS.INI and GERMANYCE_TYPES.INI files from this archive into the "WOE"/Terrain/GermanyCE directory. Allow the overwrites. 4. That's it! As a bonus, I've included several areas you can use to base carriers out of. These files should work with other mods of the WOE terrain (Deuces or JSF_Aggie's tree mods, etc). However, they will erase any mods that have already altered the GERMANYCE_TARGETS.INI and GERMANYCE_TYPES.INI files. Enjoy your new airfields. Big thanks to Gepard and JSF_Aggie for giving me permission to combine their airfield inis...all the work was theirs, I just wanted them both at the same time! FastCargo Submitter FastCargo Submitted 01/19/2008 Category Terrains
-
430 downloads
Readme for combining Gepard's 8 New Airfields and JSF_Aggie's Highway Airfields mods. These files are simply replacements for your GERMANYCE_TARGETS.INI and GERMANYCE_TYPES.INI files. What you will need first: Wings Over Europe with the GermanyCE terrain (Duh!) Gepard's 8 New Airbases for WOE: http://forum.combatace.com/index.php?autom...p;showfile=5078 JSF_Aggie's Highway Airfield Mod: http://forum.combatace.com/index.php?autom...p;showfile=2950 Instructions: 1. Backup your GERMANYCE_TARGETS.INI and GERMANYCE_TYPES.INI files first (if they have been extracted)! 2. Install both mods...don't worry about overwrites, we'll be fixing those later. 3. Copy the GERMANYCE_TARGETS.INI and GERMANYCE_TYPES.INI files from this archive into the "WOE"/Terrain/GermanyCE directory. Allow the overwrites. 4. That's it! As a bonus, I've included several areas you can use to base carriers out of. These files should work with other mods of the WOE terrain (Deuces or JSF_Aggie's tree mods, etc). However, they will erase any mods that have already altered the GERMANYCE_TARGETS.INI and GERMANYCE_TYPES.INI files. Enjoy your new airfields. Big thanks to Gepard and JSF_Aggie for giving me permission to combine their airfield inis...all the work was theirs, I just wanted them both at the same time! FastCargo -
The F-15 break down simulation...
FastCargo replied to Nesher's topic in Military and General Aviation
With the extreme forces and loss of hydraulics, doesn't surprise me. When a plane breaks up in mid flight, all bets are off. Any and all sorts of strange stuff happens post break up. FastCargo -
Amateurs! My first flight sim was Flight Simulator...for the Timex Sinclair ZX81 in 1982. Written in BASIC...loaded with a cassette tape. And just about every one since then I've at least tried...at least until there started being reviews and I started being picky.... FastCargo
-
HA! You MUST be joking! I am mister joe average...not the 'hot stick', but not 'that guy' either... Pass checkrides, usually get a 'commendable' in a few places, that kind of thing... Besides, it's my yearly airliner checkride I have next week...just had my recur Qual check last week. Only 3 more military checkrides to go... On to other things. I know the Saegheh version I did is somewhat fictional (there have been no pictures of a 2 seat version of that aircraft). However, if everyone has noticed, all the aircraft I've showed so far have been 2 seaters. And all are based on the initial T-38 model I completed sometime ago. In order of progression: T-38A - Original model AT-38B - (From T-38A) Added centerline pylon, expanded 'Drag Chute housing slightly', added HUD, ini edits for centerline pylon. Time = 1 hour T-38C - (From T-38A) Modifed intakes, remapped same area, added HUD, shrank nozzle connectors, added and moved antennas. Time = 2 hours F-5B - (From AT-38B) Modifed intakes, added LERXs, leading edge slats, expanded center pylon, added wingtip rails, 4 underwing pylons, tailhook. Expanded Drag Chute housing and deleted nozzle connector. Thickened wheels. Remapped all changed areas, especially intakes. Added ini edits to incorperate new pylons. Time = 6 hours F-5F - (From F-5B) - Stretched and recontoured nose and spine. Stretched and widened engine 'box'. 'Squeezed' cockpit area. New gear doors, speedbrakes. Thickened landing gear and wings. Modified vertical stab. Nose cannon installed. Extensive changes requiring redo of entire texture mapping. Time = 12 hours. Saegheh - (From F-5F) - Duplicated and moved vertical fins. Recontoured intakes. Time = 2 hours. As the models have progressed away from the T-38 original, the time invested has gone up geometrically. And notice that the changes just haven't been that extensive. However, some of the most complex parts are the cockpit areas. Trying to do a single seat Saegheh would pretty much require a whole new nose section to build the canopy/cockpit from. And building the F-20 would pretty much require a whole new engine 'box' area plus the new nose/cockpit derived from the single seat Saegheh. An easier task would be to start with the MF F-5E model and go from there instead. You can see the task I would be up against. No wonder guys tend to want to have their own models instead...it's actually a bit difficult sometimes to try to modify an existing model, especially if you aren't the one that built it... So just givin some feedback there folks. Speaking of which...I've made a decision on the cockpits. All of the aircraft in the release that can either drop bombs/shoot missiles/guns or have a HUD will default flying from the front seat. For the F-5B,F-5F and Saegheh (which will be Iranian), because cockpits exist from their single seater stablemates, the user will have to have the MF F-5A/C/E to have cockpits. I will include inis for the F-5s/Saegheh to allow the MF cockpits to be used but I WILL NOT be supplying cockpits. This is predicated on the MF not having a problem with me doing this. The T-38s on the other hand will have cockpits built by me. The B and C model will be front seat...but the A model will be rear seat. There will be alternate inis provided to allow flying from the other seat, but it won't be quite so 'neat and tidy'. Hopefully, this will cut my workload down a bit. FastCargo
