gilflo

Adventure begins, we are flying the Explorer to test its range and discover this big island: Birds island Start and take off Climbing quickly to 20000m to test the range Using Fly by wire with atmospheric autopilot, atmosphere is thin here, wings are short and Explorer can stall quickly, but we have an overpowered engine which help a lot. 19000m and mach>2, trying with 1/3 thrust Not satisfactory, we climb again Mach>3 around 28000m, 1/3 thrust it's much better Jool rising at 29000m 31000m and Mach 4 Thrust less than 1/3, it's the best range. We see well the roundness of the planet Flying back to our landing site, we have burn a lot of fuel and it's really mandatory to climb as quick as possible to 310000m which is the best range altitude!! in descent, Jool rising higher 20000m and 54 kms from landing Final 19 kms, vertical speed 100m/s 2500m, gear down at 6 kms from landing, high angle of descent Still high rate of descent, speed is stabilized, pitch and engine gimball are very effective for quick correction of descent rate Flare Landed Back to the "Tanker", the pilot is bringing the line for refuel Pluging the line on Explorer And filling the tanks Then we unplug and the line retracts itself to the Eaglestar And a small vid of the flight https://www.youtube.com/channel/UCD4Xqb ... sHi3bLTQRQ And a small vid of the flight

My game quit if i do this or if i use Wizard installation, even when i suppress the plugin folder.........Maybe some incompability with another mod?

Thank's

Hello Boris Thank's for update. I just wanted to keep my settings for many planes from 1.2.2 through 1.3 and i thought i had only to transfer the designs folder from AA in KSP 1.2.2 in the AA folder in KSP 1.3, but it does not seem to work when i open atmospheric Autopilot. Is there something i am missing?

So far, the bulb engine i use on a reckon satellite in 1.2.2 with the "AtomicAgePatches" is working fine on 1.3, no problem with gimball

I was just wondering why they let to download a non working version (01622) as the version 01604 works perfectly ! At least they could leave the 1604 for download!

Hello Is OPT mod working on 1.3? Maybe same small problem? As i have a lot of OPT planes in my game, i don't want to go to 1.3 if i am not sure it will work....

Explorer launch from SSTO deck during sea run and flight to the mining site 4 StarEagle engines are at reduce thrust 50% Flight controls free and liquid fuel tanks open Around125 m/s, decouplers free both docking ports, 4 main engines are stopped, Explorer engine is at full thrust, SSTO speed brakes are out, if the run has been done speed brakes in. The run can also be done speed brakes out. If the pitch control is pulled, while the Explorer is being decoupled, it takes off immediately from the deck, but it can roll a while without problem before taking off. Pitch action is limited to 70% to avoid tail strike. Taking off from the deck Pass over StarEagle, before heading to the mining site Landing The SSTO being very light (around 400T) , its gears supporting its take off weight (1031T) it can easily land on ground near the mining site. Taking off at reduce thrust, 50% Approach Final Landing You will see on the vid that we made a barrel for the fun with this big bird……launch more interesting than on the screens!!

Ok, so why is it still in download section in the store?

Hello I just downloaded the last 1.2.2 version for mac OS X. Build id is 01622. It does not work, staying blocked at "loading bundle asset definition". My mac is updated at the last version of OS X Sierra. What's happening? The build id 01604 is working.

My trip to Laythe in one go with starEagle, an OPT SSTO Seaplane of 1031T . After the Reckon Sat launch and scan of Lathe, we entered the atmosphere and ditch safely near an oOe mining site, with our explorer aircraft stowed on the deck. Explorer aircraft will be soon launched from theStarEagle deck while on sea and then both aircrafts will land on the mining site. Screens and vids

Vid of atmospheric entry and ditching To follow: launch of the explorer plane stowed on deck and landing of both aircrafts on the ore mining site

ATMOSPHERIC ENTRY AND DITCHING IN LAYTHE SEA I eventually get a good scan for Ore mining and now we are preparing for Entry and ditching after some aerobraking passes. I determine 2 waypoints, one for mining, one for ditching. Eaglestar being south of those points, i let mechjeb calculate and begin nukes braking for Entry Once we are nearly aligned, i take over and brakes in retrograde myself. we can see the waypoints behind us. Eaglestar had difficulties to maintain retrograde, I realized I forgot to use SAS!! We will be too long, no matter! Heating is really not a factor I should really have selected prograde...I switched through Radial + to help braking, no a good idea!! Ramjet engines are lighted to begin a 180° turn to island We are so light that we need only 1/5 thrust to fly Turning left on final to ditch along shoreline Still nearly poor thrust Final at 940m, explorer standing on deck. Flying manually by wire with atmospheric autopilot 245m, Trust 1/10, 95m/s, it flies very well Altitude 88m, null thrust ditching in a few seconds, speed 95, vertical speed 3.5 is perfect, no thrust In water! it slows very quickly, but to reach 0, you need to extend gears We did it! We join Laythe in one go and now we are ready to launch the Explorer plane..

Thank's That's what i have been hopping for, but it i did not happen, whatever is the number of passes done by the scanner. It looks like there's a bug, even with the last version of scansat mod i downloaded for ksp 1.2.2. But i manage to dicover some places in the strips with enough Ore to mine and convert. so i should be able to go on...

Ok thank you, i'll try that

Hello i have a problem on KSP 1.2.2 with Ore scanning on Laythe. Biome scanning was perfect but for Ore here is the screen impossible to have more detection, orbit is polar, color management is the following: green is ore, white is no ore, i just need to set the scaling better because it's too green. But the problem is that the satellite can make as may orbit as i want, there's no more detection. Electricity is ok and the biome scan was perfect...I use M 700 scanner, M4335 scanner and all the scans scanners.... What am i missing ? here is the biome, full detected....

Reckon Sat launched Opening the cargo doors near the periapsis at 750 kms. the goal is to be far enough for inclination change from equatorial to polar, it will be less expensive The satellite is out. I unlock fuel tanks and thrust is set to 100% Engine started to establish a 250 kms periapsis, better for scanning EagleStar aerobraking periapsis has been set to 60 kms to let him orbit while i scan...Starting inclination change Nearly completed Scanners out, solar panels deployed Biome scan completed, Perfect planetary overlay And now here is a problem with ore scan: while is it half done??? I don't understand this planetary overlay, green being great Ore concentration, white being no Ore. I tried all Scansat settings without success..... Can somebody help?? Thank's

NAVIGATION TO JOOL AND LAYTHE The burn to Cool will be long, around 25mn, so i will have begin the burn 12 to 13 mn before the node and that means my circular orbit will be not long circular and when we will not really pass over the node but somewhere around. I use Protractor to determine the day of the burn, then Mechjeb node editor to help to get the best time to burn We start with 75% fuel left and I know that we will be so fast that aerobraking on Jool would be a disaster, as a direct navigation to aerobrake to lathe would be too! We will burn to intercept Jool and set Apoapsis to 22700 kms, Laythe being at 21700. Beginning Burn to Jool As stated, this long burn deviate us At the end I change from Node to Target, hoping it will help...I choose a 250 periapsis on Jool arrival. Cost of 22700 Apoapsis will be another 1042 DV for fuel Jool retroburn One tour around Jool and i can see that the speed at apoapsisi is around 1550 m/s, perfect for Laythe interception. I use again node editor to find the best way to intercept Now that we are on our way to the periapsis i choose a 43.5km periapsis, not to low in atmosphere as we are going to accelerate all the way down.. Ready for lathe aerobraking At 45.5 kms, it's very hot and speed is still Mach 10!! Close up approching 43.5, still very hot, but the orbit is going to close, that's good! Woow..........Eaglestar is flipping .....we turn and turn, but it's ok , no burn, no braking Now we are establish on our orbit. We still need to burn to set apoapsis at 750 kms, point were we will release ou reckon satellite, then plan is to stabilize to a circular 70 kms orbit by aerobraking and burning. Fuel left is 20%, i thing it's enough for atmospheric entry, flight near an Ore place and ditching.. See you soon!

My OPT seaplane, after a lot of work, is airborne to Laythe

My OPT seaplane, after a lot of work, is airborne to Laythe

I agree but i don't know why, the sound was not recorded., it's my mistake!

HD Vid of the flight

Check List done and take off was successful Rotation 152m/s increasing pitch to 35° We are airborne to orbit: 4 pilots, 3 scientists and 1 engineer 4300m, nearly Mach 1 Pitch 15° for acceleration It begins to be hot, slowly 25000m,, pitch is at 15°, Nuke engines have just been switched on, we are at Mach 6 38700m, main engines just shut off and air intakes closed, just a small trouble without consequences, Thrust is not at maximum for a short while 45kms, apoapsis at 82 View from the rear at 65700m Starting Circularization Establish at 610 kms, DV left are not representative I do not know why, but in fact there's far much more for the nuke engines..

After a few weeks of research, i desgined an OPT SSTO Sea plane able to join Laythe and ditch in the sea. StarEagle will be carrying science stuff ad an OPT Lab, a reckon satellite to scan Laythe and draw maps, 6 big drills and a big Converter to mine for the return fuel, a Laythe explorer aircraft which will fly back to Kerbin with the SSTO Seaplane Here is the monster As you can see, the Laythe explorer Aircraft is stowed on the flight deck, while the Recon Satellite is in the cargo hold, with the science stuff, the converter and the drills.This aircraft will be launch from the flight deck on a sea run with StarEagle 2 decouplers, 1 on each docking port will free the aircraft when the speed reach 120m/s, lighting on its main engine and switching off EagleStar main engines. For the return flight, the Explorer aircraft will climb to orbit and dock on the Eaglestar deck. 4 J61 Ramjet Starwaster engines (2 at the front and 2 at the rear), running on LiquidFuel only, will thrust the 1031T EagleStar to orbit with the help of 4 MRS QuadNuke engines. Here is the check list before take off that allowed me to discover a lot of small troubles before the real launch Before take off check list Laythe EagleStar +4 J61 main engines ON +Thrust set 100% +Air intakes OPEN +4 Quad MRS nuke engines OFF +Thrust set 100% +All fuel tanks open and balanced Batteries and generators ON Cockpit Vernors engines ON Flight control 150% Speedbrakes active Cargo hold closed Drills and Converter OFF Ladders UP Pilot assistant preset -Heading 090° -Pitch 35° Mechjeb set for a climb to 619 kms RCS for rotation ON SAS ON Laythe explorer Deck stowed CHECK RCS OFF Main and Nuke engines OFF Air intakes OPEN Flight Controls locked and de-activated Speedbrakes activel All fuel tanks LOCKED Ladders UP Gear DOWN Decouplers OFF Reckon Satellite Cargo Stow checked RCS manually de activated All fuel tanks LOCKED Main engine OFF In the hold Take off and ditching will be manually flown. Climb to orbit with the help of Pilot Assistant and Mechjeb. no interest to keep a 090° heading with some pitch changes. Laythe EagleStar is balanced in the whole flight enveloppe from ground to orbit. atmospheric entry in cobra position.

Well i did the following: suppress the module about custom flag in each part.cfg and add my own flag in the Squad/flag folder. Then i add them in each part.cfg in the FStextureSwitch2 Module in textureNames and textureDisplayNames and it works.