Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by EvenFlow

  1. Mitsubishi F-4EJ Phantom II Towards the end of the 1960s the Japanese F-104 fleet started showing it’s age. Modern air-to-air combat shifted beyond the horizon and a modern, robust platform was needed to equip the JASDF for the new era. Soon after the deal was struck between Mitsubishi Heavy Industries and McDonnell Douglas the production of the F-4EJ begun - it was the first 3rd generation fighter manufactured on Japanese soil and apart from missing the avionics necessary for guiding ground ordnance (due to post-war Japanese military limitations) was just as capable as it’s US counterpart. The F-4EJ saw long service with the JASDF, both in the standard and it’s modernized F-4EJ Kai versions with the last Phantoms being phased out from service in 2020. 301 Hikōtai is currently the last squadron using the F-4EJ and will recieve new F-35 fighters before the end of the year. This is a complete rebuild of my older F-4E and I am very satisfied with the result. Flight performance is admirable and the plane is very stable and pilot friendly in most cases! I hope you enjoy flying it out as much as I enjoyed building it. ACTION GROUPS: AG1 - Toggle afterburner AG2 - Toggle flaps AG3 - Toggle airbrake CHANGELOG: v1.0 - Initial release v2.0 - Revamped the engine section - intake/engine transition made smoother, exhaust nozzles made wider and more detailed, airbrakes added, external stores added, intake ramps revamped. DOWNLOAD LINK: https://kerbalx.com/EvenFlow/Mitsubishi-F-4EJ-Phantom-II
  2. Not yet, but I could give it a try! Should be flyable with some tweaking i think c:
  3. HISTORY In mid-1960s airlines had to choose between the low-capacity narrow-body 707 or the massive 747 for transatlantic routes. Future of air travel clearly belonged to the spacious and cost-efficient wide-body jetliners and so a gap in the market appeared for a long-range, mid-capacity wide-body airliner. While Lockheed’s L-1011 may have paved the way for tri-engine jets it’s extremely complex S-duct made it hard to maintain and prone to failures. The odd shape also meant that upgraded, bigger engines could not be fitted. A technological wonder of it’s time was a dead end in the long run. McDonnell-Douglas also developed a trijet of their own and decided to learn from Lockheed’s shortcomings. The fruit of their project was the DC-10. With the engine number 2 integrated into it’s vertical stabilizer the DC-10 was far easier to maintain and could fit a multitude of engines. Three engines allowed it to conduct flights directly over the ocean (it was free of ETOPS restrictions) and it’s sleek silouhette meant that it was more fuel-efficient than it’s contemporaries. It gained some bad reputation after a series of accidents attributed to it’s cargo door locking mechanism. In retrospect the bad press was greatly exaggerated and the DC-10 proved to be as reliable and safe as other airliners of it’s generation over it’s service life. It was quick and fairly easy to maintain compared to 4-engine monsters like the 747 but after the ETOPS restrictions were lifted and aircraft like the B777 or the A330 started making direct flights over the oceans the trijet quickly lost it’s edge in terms of efficiency. Two engines were the future, and in the late 1990s the DC-10/MD-11s were slowly being phased out of service. Last passenger variants of the MD-11 were retired from service with KLM in 2011, but the powerful platform was quickly adapted for cargo-carrying duties by Fedex and UPS among others. Many DC-10-30Fs and MD-11Fs remain operational to this day in those companies. This replica of a cargo variant of the DC-10-30 is my biggest flyable craft to date, and perhaps also the most detailed and functional. It features custom landing gear, flaps, spoilers and a ton of detail which make flying it a great experience. It’s also relatively low partcount for a craft of this size which should make it quite playable! FLIGHT MANUAL 1. STARTUP AND TAKEOFF Since KSP slams your craft onto the runway REALLY hard when spawning, the gear may get a little wobbly and you may have to wait a few seconds until it settles down and straightens out (you may want to enable SAS and brakes). This happens only on loading so don’t worry about it too much when landing. Be sure to enable the APU with AG3 so you don’t run out of power while your engines aren’t running. After the DC-10 is sitting still on the runway you can start up the engines on idle throttle. You can extend the flaps with AG1 for takeoff. To take off apply gentle throttle (no more than 20-25%) until you are moving at approx 40-50m/s on the runway to prevent stalling the compressors and losing thrust. Optimal V2 is approx 80-90m/s. After takeoff you should be moving fast enough to prevent any compressor stalls at high throttle. Retract the flaps with AG1 and retract the landing gear with G. 2. FLIGHT There isn’t too much to it - the DC-10 is very stable and pilot friendly for the most part. Roll rate and pitch authority are both very good for an aircraft of this size. The cruising speed is approx 200m/s and top speed sits at somewhere around 270m/s at 5-6km. Be careful not to overstress the airframe if you are making hard maneuvers at higher speeds. This airframe is rated at no more than 4.5Gs. 3. APPROACH I recommend lining up with the runway in advance to give you time to set up a smooth glideslope. After you line up with the runway drop your speed to about 120m/s to allow for flaps to deploy safely. You can now deploy the landing gear (G), flaps (AG1) and spoilers (AG4). 4. LANDING The DC-10 will become really sluggish and stall-happy below 60m/s so land at approx 75-80m/s if possible. Be sure to flare and reduce your vertical speed to prevent damage to your landing gear. After touchdown, apply brakes and activate thrust reversers with AG2. Remember to reduce thrust when your speed drops to prevent compressor stalls. That’s it! Below are the main controls: AG1: Toggle flaps AG2: Toggle thrust reversers AG3: Toggle APU AG4: Toggle spoilers U: Toggle landing lights Enjoy and fly safe! v1.0 - Initial release DOWNLOAD: https://kerbalx.com/EvenFlow/McDonnell-Douglas-DC-10-30F
  4. The DC-10-30 is slowly nearing completion. I'm not sure whether I want to make the freighter or the passenger variant.
  5. You can use Elevons 2/3 to make that trapezoidal shape. It looks great!
  6. Large amounts of freedom are inbound to your location. ETA: a few hours or so.
  7. After finishing the Ki-87, I decided that it needed something to hunt for. Well, here's the Superfortress. It's got custom landing gear, working, spacious bomb bays and nice propeller engine replicas. I still need to do the cockpit which will probably take some time but it actually flies!
  8. The Phantom is up for grabs on KerbalX now. Also, if you prefer the oldtimers...
  9. Inspired by servo's brilliant replica, I have decided to give my old Phantom a little revamp and equip it with a new nosecone and intakes.
  10. Breaking Ground joints were super rigid in 1.7.2, but then 1.7.3 came and screwed things up. Pic of my Tomcat for reference: Btw, I love the Tomcat, great usage of stock parts!
  11. Yup, practically all means of delivery are allowed.
  12. Incredible job @Cela1! Great precision on that parachute drop as well! I will make sure to put the score on the leaderboard as soon as i can tomorrow since I'm preparing for a job interview right now. Congratulations on completing the challenge! I have to say i underestimated just how efficient those Making History rover wheels are since I don't own the DLC. That was great!
  13. In the picture you can see the exact same aircraft between two versions of KSP in a 5-6G turn at roughly the same speed. In 1.7.3 the rotatron supporting the wing is very wobbly regardless of autostrutting. This makes using these parts pretty frustrating as you cannot put struts between two rotating parts to make them more rigid. I really hope this gets fixed very soon.
  14. I have no idea how to properly replicate or document it, but did anyone else notice that connection nodes of robotic parts seem less rigid in the newest update? Variable sweep wings on my replicas have become extremely wobbly using the smallest rotatron while they worked absolutely fine in the previous updates. I didn't notice any mention of such changes in the patch notes. If other people are experiencing similar issues - is this intended behavior?
  15. Thank you so much! I really can't wait to see what people can come up with here. Will do my best to keep the challenge running for as long as possible c:
  16. FOREWORD After Reactor 4 of the Chernobyl NPP exploded, large amounts of rubble, graphite moderator and other radioactive material from the destroyed reactor were ejected onto the roofs of power plant facilities. Radiation on some parts of the roof was so severe that unprotected circuitry used in remote-controlled robots failed near-immediately. To continue cleanup works rubble needed to be removed from the rooftops. Since the radiation levels would give human workers lethal doses in a matter of minutes, robotic solutions were in high demand. One of such solutions was a repurposed lunar rover (named STR-1), a remnant of the Lunokhod program outfitted with dosimetry equipment and a bulldozer blade. It's circuitry was already hardened against cosmic radiation, and such it could be quickly modified and deployed into the containment zone. Even with this protection, it only managed to clean up a couple dozen square meters of the roof before succumbing to the extreme radiation. In this challenge, you will take on this exact task. You will develop a rover with limited operation time which will help remove graphite rubble from the power plant site along with a delivery method. THE CHALLENGE The cleanup operation will consist of four major phases. 1. Rover delivery Taking off the KSC airfield, you will need to deliver the rover to the disaster site. Time will be counted with the in-game clock from the mission start to the moment, where you come within 150m of the reactor (when the distance marker disappears). In this case, the quicker the better. Point assignment rules will be elaborated on in the next section. 2. Landing your rover on the roof Since the radiation levels near the core are extremely high, you will need to minimize your time in the proximity of the reactor. From the moment of your arrival within 150m of the reactor you will have two minutes in-game time to deploy the rover onto the roof and leave the 150m perimeter. 3. Retrieving the carrier craft This section will not be timed, albeit additional points will be awarded if you can return your carrier craft to the KSC unscathed. 4. Cleaning up the roof After your carrier vehicle has landed (or crashed horribly) you can begin your operation. This section is not timed - the only limit being your battery life (to simulate radiation exposure). Points will be awarded based on how many of the 10 graphite blocks (Oscar-B fuel tanks) situated on the roof you can remove before your battery dies. The blocks are supposed to be pushed off the edge of the roof into the destroyed reactor building where they will not pose a threat. The challenge ends after your rover battery dies. RULES As with all challenges, here are some rules: 1. Your carrier craft can be a VTOL aircraft, a helicopter or even a land-based vehicle. The choice is yours in that regard and creativity in the delivery method department is greatly encouraged! 2. Your rover's only power source can be a single Z-400 battery. All other power sources such as your control modules are prohibited and need to be emptied in the hangar. 3. You may not use any power producing parts such as solar panels, fuel cells and RTGs. 4. The rover has to be delivered onto the roof via the carrier craft, e.g. it may not be deployed outside of the 150m perimeter and flown or driven onto the roof. 5. Albeit the graphite blocks may explode after being dropped into the reactor, they may not be exploded directly on the roof as a mean of their removal. 6. Using kraken drives to propel your rover is prohibited, as the whole point of this challenge is dealing with the problems within time and resource constraints. 7. Please let me know if your submission is stock + DLC or uses some other mods for ease of organization 8. For obvious reasons, the rover must be unmanned. No Kerbals can come close to the reactor, they are already green enough as they are. The points for each section will be awarded according to these rules: Section 1 - Delivery Number of points is the value of the following function: ceil(max(300 - your_time [sec], 0) / 2) Section 2 - Landing the rover Number of points is the value of the following function ceil(max(120 - your_time [sec], 0) * 4) Section 3 - Returning the carrier craft Number of points awarded is 40 - if the carrier aircraft is landed undamaged at the KSC 0 - otherwise Section 4 - Clearing the roof Number of points is the value of the following function 100 * blocks_removed HOW TO SUBMIT YOUR ENTRY First, you should download the savefile containing the powerplant set up in the correct spot. It can be found here: https://filebin.net/h67zuoh36flmrfpz Afterwards, after creating your entry you should either film your run, or document it via screenshots. If you choose to go with the screenshot route, please provide the following: 1. Screenshot of your crafts on the KSC runway at the beginning of the mission 2. Screenshot of your arrival within the 150m perimeter with the HUD enabled 3. Screenshot of your carrier craft departure with HUD enabled (if you choose to retrieve it) with the rover on the roof visible in the shot, or just a picture of the rover on the roof if your delivery method is expendable 4. Screenshot of your carrier craft landed (if you choose to retrieve it) with HUD enabled 5. Screenshot of your rover on the roof with amount of electric charge remaining at the beginning of cleanup visible 6. Screenshot of the roof after your electric charge runs out with all remaining graphite blocks visible If you have any questions regarding this challenge, feel free to ask them via messages or here in the thread itself. Have fun and good luck on your journey. If you feel that any of the rules or point awarding mechanisms need tweaking please let me know! Be wary that the power plant building contains almost 1100 parts so you may experience quite a bit of lag. This is kind of offset by the fact that the model is static and the game does not seem to lag quite as much as with most mobile spawned high-partcount crafts. With a GTX1050 and 8GB of RAM I was able to keep the FPS at about 20-25 at all times and I could execute the mission without too many lag-related issues. I will prepare a proper badge for all participants and will post it here in a few hours. Cheers. c: STOCK LEADERBOARD 1. Cela1 - 1594 pts (134 + 420 + 40 + 1000) 2. jinnantonix - 1532 pts (140 + 352 + 40 + 1000) 3. ----------------------------------------------- 4. ----------------------------------------------- 5. ----------------------------------------------- 6. ----------------------------------------------- 7. ----------------------------------------------- MODDED LEADERBOARD 1. ----------------------------------------------- 2. ----------------------------------------------- 3. ----------------------------------------------- 4. ----------------------------------------------- 5. ----------------------------------------------- 6. ----------------------------------------------- 7. -----------------------------------------------
  17. Hit me up if any of you guys had problems with hostile submarines lurking around your space center lately.
  18. Not quite a F-111! The MiG-23M is now finished. Coming soon to a KerbalX near you. c:
  19. Hey there everyone, i've been taking a little break for the past few months, but now that my uni duties have ended I've bought myself the expansion and I am back to work. I'm making a really neat replica, I think you guys might like it if you liked the Tomcat. So far I've made the landing gear. It's custom. Any wild guesses on what it might be? :>
  20. Finally found the mod! It's RealPlume, it should be compatible with the latest update c:
  • Create New...