OHM Formosat-5

Hi Barry, if you just google for "windows 10 show file extensions" it should give you instructions how to set it up to show file extensions.

I opened the conf file went to the folder that said earth opened that
From the sound of it you have opened the Config/Earth/ folder. That's not the right place. If you open your Config/ folder, scroll down past all the sub-folders, you should see a whole list of files including "Earth.cfg" (or just "Earth" if you don't have file extensions showing)- that's the one you need to edit.

Just to confuse matters more - I don't see why editing The Earth.cfg would affect the performance of the Falcon9 - the edit just changes the LC39A pad to the appropriate mesh. There's something else going on.

If someone who has this "landing short" problem could post their orbiter.log file, that would be useful.

Thanks and regards,
Brian
 
Still having problems

Orbiter.Log

**** Orbiter.log
000000.000: Build Aug 28 2016 [v.160828]
000000.000: Timer precision: 4.46049e-007 sec
000000.000: Found 1 joystick(s)
000000.000: Module AtlantisConfig.dll .... [Build 160828, API 160828]
000000.000: Module AtmConfig.dll ......... [Build 160828, API 160828]
000000.000: Module DGConfigurator.dll .... [Build 160828, API 160828]
000000.000: Module D3D9Client.dll ........ [Build 160830, API 160828]
000000.000: Module DX9ExtMFD.dll ......... [Build 150812, API 100830]
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: oapiRegisterMFDMode
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------
000000.000: Module Interior_Navigator.dll [Build 150901, API 100830]
000000.000: Module Multistage2015_MFD.dll [Build 161006, API 160828]
000000.000: Module ReFuelMFD.dll ......... [Build ******, API 060425]
000000.000: Module SpaceNetwork.dll ...... [Build 130801, API 100830]
000000.000: Module ExtMFD.dll ............ [Build 160828, API 160828]
000000.000: Module ScnEditor.dll ......... [Build 160828, API 160828]
000000.000: Module OrbiterSound.dll ...... [Build 121120, API 100830]
000000.000:
000000.000: **** Creating simulation session
000000.000: D3D9: [DirectX 9 Initialized]
000000.000: D3D9: 3D-Adapter = AMD Radeon HD 7660G
000000.000: D3D9: MaxTextureWidth........: 16384
000000.000: D3D9: MaxTextureHeight.......: 16384
000000.000: D3D9: MaxTextureRepeat.......: 8192
000000.000: D3D9: VolTexAddressCaps......: 0x3F
000000.000: D3D9: NumSimultaneousRTs.....: 4
000000.000: D3D9: VertexDeclCaps.........: 0x3FF
000000.000: D3D9: XNA Math Support.......: Yes
000000.000: D3D9: Vertex Texture.........: Yes
000000.000: D3D9: Shadow Mapping.........: Yes
000000.000: D3D9: D3DFMT_A16B16G16R16F...: Yes
000000.000: D3D9: D3DFMT_A32B32G32R32F...: Yes
000000.000: D3D9: D3DFMT_D32F_LOCKABLE...: Yes
000000.000: D3D9: D3DFMT_A2R10G10B10.....: Yes
000000.000: D3D9: D3DDTCAPS_DEC3N........: Yes
000000.000: D3D9: D3DDTCAPS_FLOAT16_2....: Yes
000000.000: D3D9: D3DDTCAPS_FLOAT16_4....: Yes
000000.000: D3D9: Available Texture Memory = 4086 MB
000000.000: D3D9: [3DDevice Initialized]
000000.000: D3D9: [Loading Constellations]
000000.000: D3D9: [D3D9Client Initialized]
000000.000: Module Sun.dll ............... [Build 160828, API 160828]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
000000.000: Module Mercury.dll ........... [Build 160828, API 160828]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
000000.000: Module Venus.dll ............. [Build 160828, API 160828]
000000.000: Module VenusAtm2006.dll ...... [Build 160828, API 160828]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
000000.000: Module Earth.dll ............. [Build 160828, API 160828]
000000.000: Module EarthAtmJ71G.dll ...... [Build 160828, API 160828]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
000000.000: Module Moon.dll .............. [Build 160828, API 160828]
ELP82: Precision 1e-005, Terms 116/829
000000.000: Module Mars.dll .............. [Build 160828, API 160828]
000000.000: Module MarsAtm2006.dll ....... [Build 160828, API 160828]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
000000.000: Module Phobos.dll ............ [Build ******, API 060425]
000000.000: Module Deimos.dll ............ [Build ******, API 060425]
000000.000: Module Galsat.dll ............ [Build 160828, API 160828]
000000.000: Module Jupiter.dll ........... [Build 160828, API 160828]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
000000.000: Module Io.dll ................ [Build 160828, API 160828]
000000.000: Module Europa.dll ............ [Build 160828, API 160828]
000000.000: Module Ganymede.dll .......... [Build 160828, API 160828]
000000.000: Module Callisto.dll .......... [Build 160828, API 160828]
000000.000: Module Satsat.dll ............ [Build 160828, API 160828]
000000.000: Module Saturn.dll ............ [Build 160828, API 160828]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
000000.000: Module Mimas.dll ............. [Build 160828, API 160828]
SATSAT Mimas: Terms 113
000000.000: Module Enceladus.dll ......... [Build 160828, API 160828]
SATSAT Enceladus: Terms 33
000000.000: Module Tethys.dll ............ [Build 160828, API 160828]
SATSAT Tethys: Terms 101
000000.000: Module Dione.dll ............. [Build 160828, API 160828]
SATSAT Dione: Terms 59
000000.000: Module Rhea.dll .............. [Build 160828, API 160828]
SATSAT Rhea: Terms 68
000000.000: Module Titan.dll ............. [Build 160828, API 160828]
SATSAT Titan: Terms 100
000000.000: Module Iapetus.dll ........... [Build 160828, API 160828]
SATSAT Iapetus: Terms 605
000000.000: Module Uranus.dll ............ [Build 160828, API 160828]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
000000.000: Module Miranda.dll ........... [Build ******, API 060425]
000000.000: Module Ariel.dll ............. [Build ******, API 060425]
000000.000: Module Umbriel.dll ........... [Build ******, API 060425]
000000.000: Module Titania.dll ........... [Build ******, API 060425]
000000.000: Module Oberon.dll ............ [Build ******, API 060425]
000000.000: Module Neptune.dll ........... [Build 160828, API 160828]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
000000.000: Finished initialising world
000000.000: Module slc4er.dll ............ [Build 170623, API 160828]
000000.000: Module formosat5.dll ......... [Build 170824, API 160828]
000000.000: Module f9_v12.dll ............ [Build 170804, API 160828]
000000.000: Module barge.dll ............. [Build 170811, API 160828]
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
000000.000: D3D9: [Scene Initialized]
000000.000: Finished initialising panels
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: VESSEL::GetHorizonAirspeedVector
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------
000000.010: ---------------------------------------------------------------
000000.010: >>> WARNING: Obsolete API function used: VESSEL::GetShipAirspeedVector
000000.010: At least one active module is accessing an obsolete interface function.
000000.010: Addons which rely on obsolete functions may not be compatible with
000000.010: future versions of Orbiter.
000000.010: ---------------------------------------------------------------
000174.558: ---------------------------------------------------------------
000174.558: >>> WARNING: Obsolete API function used: VESSEL::CreateVariableDragElement
000174.558: At least one active module is accessing an obsolete interface function.
000174.558: Addons which rely on obsolete functions may not be compatible with
000174.558: future versions of Orbiter.
000174.558: ---------------------------------------------------------------
000443.469: D3D9: [Session Closed. Scene deleted.]
000443.469: D3D9: [Destroy Render Window Called]
000443.469: D3D9: ERROR: UnDeleted Surface(s) Detected
000443.469: D3D9: ERROR: Surface 0x16C944E8 (Falcon9R_V12\f9logo_char.dds) (256,512)
000443.469: D3D9: ERROR: Surface 0x16C95D48 (Falcon9R_V12\f9_hull_logo_char.dds) (256,1024)
000443.469: **** Closing simulation session

Quicksave after separation:

BEGIN_DESC
Orbiter saved state at T = 496
END_DESC

BEGIN_ENVIRONMENT
System Sol
Date MJD 57989.7765700756
Context SpaceX
Help CurrentState_img
END_ENVIRONMENT

BEGIN_FOCUS
Ship Falcon9_Stg1
END_FOCUS

BEGIN_CAMERA
TARGET Falcon9_Stg1
MODE Cockpit
FOV 40.00
END_CAMERA

BEGIN_HUD
TYPE Surface
END_HUD

BEGIN_MFD Left
TYPE Surface
SPDMODE 1
END_MFD

BEGIN_MFD Right
TYPE Map
REF Earth
ZOOM 32
END_MFD

BEGIN_SHIPS
SLC4E:Falcon9R_V12/slc4er
STATUS Landed Earth
POS -120.6102030 34.6324760
HEADING 190.00
ALT 3.174
AROT -115.819 25.717 -152.249
AFCMODE 7
PRPLEVEL 0:1.000000
NAVFREQ 0 0
PST 0.1079 0.1842 3
TOWER 1 1.0000 1.0000
END
Formosat5:formosat5/formosat5
STATUS Orbiting Earth
RPOS -3943611.834 1110292.806 5667477.857
RVEL -1678.5531 -3744.7368 1563.7092
AROT -91.199 0.973 -33.912
VROT -2.0000 2.0000 0.0000
ATTACHED 0:0,Falcon9
AFCMODE 7
PRPLEVEL 0:1.000000
NAVFREQ 0 0
SPR 0 0.0000
END
Falcon9:Falcon9R_V12\f9_v12
STATUS Orbiting Earth
RPOS -3943611.691 1110301.173 5667478.033
RVEL -1678.5531 -3744.7368 1563.7092
AROT -91.199 0.973 -33.912
VROT -2.0000 2.0000 0.0000
AFCMODE 7
PRPLEVEL 1:0.269661 2:0.987032
THLEVEL 12:0.000000 14:0.000000 25:0.700000
NAVFREQ 0 0
FAIRS 1
SOST 1 0 0 1 1 1 1
SOPR -1.7153 720000.0 720000.0 23000.0 240160.0 ASDS 0.8153
LOTM 0 0 0 0
END
ASDS:Falcon9R_V12/barge
STATUS Landed Earth
POS -122.1350000 29.4490000
HEADING 90.00
ALT 0.335
AROT 180.000 -57.865 -119.449
AFCMODE 7
NAVFREQ 0 0
END
Falcon9_Stg1:Falcon9R_V12/f9_v12_stg1
STATUS Orbiting Earth
RPOS -3637531.329 1350337.509 5255033.833
RVEL 184.6747 -1464.1487 -1004.0676
AROT 64.352 15.788 -60.811
VROT 0.0083 0.2183 0.0000
AFCMODE 7
PRPLEVEL 0:0.057312 1:0.771837
THLEVEL 0:0.003284 1:0.000493 6:0.003284 7:0.000493
NAVFREQ 0 0
LEGS 0 0.0000 0.0000 0.0000 0.0000
FINS 0 0.0000 0.5000 0.5000
APST 0 0 0 1 3 1 0 0.0000 0
LPRM ASDS
END
Falcon9_Fair1:Falcon9R_V12/f9_v12_fair_1
STATUS Orbiting Earth
RPOS -3667415.476 1335332.104 5299687.413
RVEL 80.1670 -1506.1780 -848.0235
AROT 154.486 -63.050 -167.734
VROT -0.0836 -11.4552 0.0000
AFCMODE 7
END
Falcon9_Fair2:Falcon9R_V12/f9_v12_fair_2
STATUS Orbiting Earth
RPOS -3669333.821 1335446.141 5298385.196
RVEL 73.9425 -1505.8054 -852.2324
AROT 165.581 -6.366 -173.136
VROT -0.0836 11.4631 0.0000
AFCMODE 7
END
END_SHIPS

BEGIN_DX9ExtMFD
END

BEGIN_ExtMFD
END
 

Attachments

  • off landing.jpg
    off landing.jpg
    53.9 KB · Views: 17
Voyager VI, thanks very much - I'll take a look.

---------- Post added at 02:17 PM ---------- Previous post was at 12:51 PM ----------

OK, I can see from your saved scenario that your 1st stage is already coming down short before the re-entry burn happens. Your 1st stage has an Apa. about 100m lower than "nominal", so looks like it has a lower velocity at separation. The question is "Why?".

I thought it might be a frame-rate issue but I can't reproduce it running the sim at fixed time steps of 0.01s up to 0.1s.

Sometimes plug-in modules can cause unexpected effects.
Can you try running the Formosat-5 launch with the following modules disabled in your Orbiter Modules tab?
DX9ExtMFD
Interior_Navigator
Multistage2015_MFD
ReFuelMFD
SpaceNetwork

Also, the stock "MapMFD" causes periodic lag for me when using the D3D9 client, so try turning off the MapMFD as well.

Any improvement?

If you have time, you could check to see if the scenario "10K to ISS(LC39A ASDS EDL only)" in the Falcon9 for Orbiter2106 folder, works for you.

The EDL-only flight profile is incredibly sensitive to ASDS position and 1st stage separation velocity, so unless everything is right on the money you won't get a nice landing!

Thanks,
Brian
 
Last edited:
Hey BrianJ are the crates,and containers on the sides of the ASDS missing from the new 2016 version,or is it sitting in the water lower now,and you can't see them? just curious,great work BTW.Thanks
 
Hey BrianJ are the crates,and containers on the sides of the ASDS missing from the new 2016 version,or is it sitting in the water lower now,and you can't see them? just curious,great work BTW.Thanks
Yeah, the ASDS deck has to be pretty much at sea-level so the 1st stage can land on it without sinking through it. In Orbiter2010-P1 you could see the rest of the ASDS below sea-level. In Orbiter2016 you can't see it, so I just removed the crates, containers, etc. from the mesh.

I guess it is possible to implement collision detection for landing above Orbiter sea-level(or terrain-level), but seems like a lot of work for not much gain.

Cheers.
 
Hey Brian

Thanks for the help. I did open that and see where to add lines if need be. I tried to turn off multistage 2015 and no change there. I guess i'll try to change that when time permits. I'm having to fly the storm hitting us right now. Big thanks to DaveS for his help with this. I don't understand why this would need to be changed and is this going to mess something else up for later add ons.

---------- Post added at 04:13 PM ---------- Previous post was at 04:11 PM ----------

any body have any ideas why the default Atlantis shuttle doesn't start on the pad but up in the air ?
 
Hey Voyager_VI,

just saw that your DX9ExtMFD is still a build linked against API 100830 (Orbiter 2010).
Attached you'll find one linked against API 160828 (Orbiter 2016):thumbup:

Not that I think it matters in your case, but seeing less warnings is always good :lol:

/Kuddel
 

Attachments

Still no go with all Modules turned off

Ran the 10K to ISS, pinpoint landing ASDS.

Ran Formosat5 in normal Orbiter and Orbiter_NG, all modules turned off. MapMFD turned off as well. Still landing just off side of ASDS.
 

Attachments

  • 10K.jpg
    10K.jpg
    113.1 KB · Views: 13
  • 10K Outside.jpg
    10K Outside.jpg
    60.4 KB · Views: 13
  • No Modules on - regular Orbiter.jpg
    No Modules on - regular Orbiter.jpg
    53.5 KB · Views: 11
  • No Modules turned on Orbiter_NG.jpg
    No Modules turned on Orbiter_NG.jpg
    56.4 KB · Views: 11
Last edited:
**** Orbiter.log
000000.000: Build Aug 28 2016 [v.160828]
000000.000: Timer precision: 4.46049e-007 sec
000000.000: Found 0 joystick(s)
000000.000: Devices enumerated: 6
000000.000: Devices accepted: 5
000000.000: [ ] RGB Emulation (SW)
000000.000: [ ] Direct3D HAL (HW)
000000.000: [x] Direct3D T&L HAL (HW)
000000.000: [ ] Direct3D HAL (AMD Radeon HD 7660G) (HW)
000000.000: [x] Direct3D T&L HAL (AMD Radeon HD 7660G) (HW)
000000.000: Module AtlantisConfig.dll .... [Build 160828, API 160828]
000000.000: Module AtmConfig.dll ......... [Build 160828, API 160828]
000000.000: Module DGConfigurator.dll .... [Build 160828, API 160828]
000000.000: Module OrbiterSound.dll ...... [Build 121120, API 100830]
000000.000: Module Multistage2015_MFD.dll [Build 161006, API 160828]
000000.000: Module SpaceNetwork.dll ...... [Build 130801, API 100830]
000000.000: Module ScnEditor.dll ......... [Build 160828, API 160828]
000000.000:
000000.000: **** Creating simulation session
000000.000: DirectDraw interface OK
000000.000: Direct3D interface OK
000000.000: Graphics: Viewport: Window 1274 x 995 x 32
000000.000: Graphics: Hardware T&L capability: Yes
000000.000: Graphics: Z-buffer depth: 32 bit
000000.000: Graphics: Active lights supported: 8
000000.000: Loading 15382 records from star database
000000.000: ---------------------------------------------------------------
000000.000: >>> ERROR: DDraw error DDERR_BLTFASTCANTCLIP
000000.000: >>> [OrbiterGraphics::clbkBlt | .\OGraphics.cpp | 1633]
000000.000: ---------------------------------------------------------------
000000.000: Module Sun.dll ............... [Build 160828, API 160828]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
000000.000: Module Mercury.dll ........... [Build 160828, API 160828]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
000000.000: Module Venus.dll ............. [Build 160828, API 160828]
000000.000: Module VenusAtm2006.dll ...... [Build 160828, API 160828]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
000000.000: Module Earth.dll ............. [Build 160828, API 160828]
000000.000: Module EarthAtmJ71G.dll ...... [Build 160828, API 160828]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
000000.000: Module Moon.dll .............. [Build 160828, API 160828]
ELP82: Precision 1e-005, Terms 116/829
000000.000: Module Mars.dll .............. [Build 160828, API 160828]
000000.000: Module MarsAtm2006.dll ....... [Build 160828, API 160828]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
000000.000: Module Phobos.dll ............ [Build ******, API 060425]
000000.000: Module Deimos.dll ............ [Build ******, API 060425]
000000.000: Module Galsat.dll ............ [Build 160828, API 160828]
000000.000: Module Jupiter.dll ........... [Build 160828, API 160828]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
000000.000: Module Io.dll ................ [Build 160828, API 160828]
000000.000: Module Europa.dll ............ [Build 160828, API 160828]
000000.000: Module Ganymede.dll .......... [Build 160828, API 160828]
000000.000: Module Callisto.dll .......... [Build 160828, API 160828]
000000.000: Module Satsat.dll ............ [Build 160828, API 160828]
000000.000: Module Saturn.dll ............ [Build 160828, API 160828]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
000000.000: Module Mimas.dll ............. [Build 160828, API 160828]
SATSAT Mimas: Terms 113
000000.000: Module Enceladus.dll ......... [Build 160828, API 160828]
SATSAT Enceladus: Terms 33
000000.000: Module Tethys.dll ............ [Build 160828, API 160828]
SATSAT Tethys: Terms 101
000000.000: Module Dione.dll ............. [Build 160828, API 160828]
SATSAT Dione: Terms 59
000000.000: Module Rhea.dll .............. [Build 160828, API 160828]
SATSAT Rhea: Terms 68
000000.000: Module Titan.dll ............. [Build 160828, API 160828]
SATSAT Titan: Terms 100
000000.000: Module Iapetus.dll ........... [Build 160828, API 160828]
SATSAT Iapetus: Terms 605
000000.000: Module Uranus.dll ............ [Build 160828, API 160828]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
000000.000: Module Miranda.dll ........... [Build ******, API 060425]
000000.000: Module Ariel.dll ............. [Build ******, API 060425]
000000.000: Module Umbriel.dll ........... [Build ******, API 060425]
000000.000: Module Titania.dll ........... [Build ******, API 060425]
000000.000: Module Oberon.dll ............ [Build ******, API 060425]
000000.000: Module Neptune.dll ........... [Build 160828, API 160828]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
000000.000: Finished initialising world
000000.000: Module slc4er.dll ............ [Build 170623, API 160828]
000000.000: gcAPI: [Graphics Client Not Found]
000000.000: Module formosat5.dll ......... [Build 170824, API 160828]
000000.000: Module f9_v12.dll ............ [Build 170804, API 160828]
000000.000: gcAPI: [Graphics Client Not Found]
000000.000: Module barge.dll ............. [Build 170811, API 160828]
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
000000.000: Finished initialising panels
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: VESSEL::GetHorizonAirspeedVector
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------
000000.010: ---------------------------------------------------------------
000000.010: >>> WARNING: Obsolete API function used: VESSEL::GetShipAirspeedVector
000000.010: At least one active module is accessing an obsolete interface function.
000000.010: Addons which rely on obsolete functions may not be compatible with
000000.010: future versions of Orbiter.
000000.010: ---------------------------------------------------------------
000240.915: ---------------------------------------------------------------
000240.915: >>> WARNING: Obsolete API function used: VESSEL::CreateVariableDragElement
000240.915: At least one active module is accessing an obsolete interface function.
000240.915: Addons which rely on obsolete functions may not be compatible with
000240.915: future versions of Orbiter.
000240.915: ---------------------------------------------------------------

---------- Post added at 05:11 PM ---------- Previous post was at 05:05 PM ----------

Going to retry with a totally clean 2016 install and just SpaceX addons.
 
Clean Install - Even farther away...

No addons, MapMFD turned off, only D3D9
 

Attachments

  • Clean Install.jpg
    Clean Install.jpg
    48.6 KB · Views: 12
Hmm, so now you have:
- Only D3D9Client as active Module
- Done the changes in Earth.cfg
and still miss the ASDS?
But "10K to ISS" runs fine, right?

What scenario exactly are you flying?
 
Voyager VI, many thanks for persisting with testing. I'm scratching my head over what's going on with this. Worth noting the Formosat-5 flight profile is steeper than all the others, so even less margin for error with ASDS location.

I tested the scenarios with Wind Effect on and off, but never tried turning off the Complex Flight Model or Non-spherical Gravity parameters - could that be the cause?
I'll check it out myself later.

Cheers.
 
My two cents about the issue: it happened to me once while developing something I don't even remember now that, since some update code was in clbkPostStep and not in clbkPreStep, Earth was spinning and moving just a little (the amount relevant to time of the step) so I was missing the ground point for just that amount (that looks more or less what I saw in the picture).

could that be it?

Brian I read that you may have issues for landing on level above sea level, why don't you just attach the rocket to the ASDS? if it's close enough with right attitude etc,rocket creates attachment to asds and attach itself to it. Then you can even sail it home!

Cheers
Fred
 
Last edited:
OK Brian, turning ON all Perturbations did the trick. Three tries, three perfect landings on ASDS.
 
Last edited:
Hi Fred,
thanks for the input - I can see why you think it might be a sim-step/rotation issue. I certainly had to deal with that issue in the "Boostback" burn calculations. But I don't think it is that, in this case. I think I've narrowed it down to Wind Effect and Non-Spherical Gravity.

Re: Landing on ASDS - I had thought of going with an "attachment" solution, but I wanted to really test how well the 1st stage was landing, so I figured an "instant attachment" would be "cheating". But if the right velocity/attitude/pos constraints are met, then it can work OK. I like the idea of "sailing the ASDS home" - I hadn't thought about that - I will reconsider the "attachment" idea! Thanks!


@Voyager VI
I managed to reproduce the "landing short" by disabling both the Non-Spherical Gravity and Wind Effect parameters.

Disabling either one gives me a rather nasty (and unsurvivable) late Re-entry burn, but lands on target.

Disabling both gives me the "landing short" result.

What settings are you using for Non-Spherical Gravity and Wind Effect?
Does the landing work for you if Non-Spherical Gravity and Wind are on?

Guess I never did check the Formosat-5 scenario for Wind Effect discrepancies.

I'm going to need either a better "ASDS Location" calculation or a cleverer Re-entry burn algorithm. More tinkering required :)

---------- Post added at 05:57 PM ---------- Previous post was at 12:42 PM ----------

Thanks, Voyager VI. I think we tracked down the "anomaly".

The 1st Stage Re-entry burn on the EDL-Only flight profile is so finely balanced.
If the ASDS is a few km too far downrange, you never hit it.
ASDS too close, and you have to make the burn too high up and too early, it doesn't use as much fuel, not as much deceleration, further to fall, heavier stage, etc.

At the moment the Re-entry burn algorithm can correct for some cross-range error, but not down-range error. I'll have to work on it.

Cheers,
Brian
 
Update 170913 on OH:
Changed location of ASDS in scenario.
 
To me, it looks like the Zip is corrupt.
Yes. I just tried downloading it and the .zip is totally empty. I better notify the OH admin.

---------- Post added at 10:01 PM ---------- Previous post was at 04:29 PM ----------

OH admin notified, I've just updated the file on OH, formosat5_170913.zip should contain the correct files.
 
Back
Top