Project G42-200 StarLiner

[Scruce]

use tab to switch seats

You can also 'click' on the pilot you want the camera to snap too.

E.g: Sitting on the Pilot's side and clicking on the Engineer in the VC will snap the camera to him.

 

[distructor20]

srry wrong thread

---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------

i've two questions:
- Do the RAMCASTER engines already work in the current version? If yes, how do you start them?
- Will all the switches and instruments eventually work in the cockpit? Understandable if they won't. That's a hell of a job!

I really love the design! :thumbup:

 

[Scruce]

- Do the RAMCASTER engines already work in the current version? If yes, how do you start them?

See post #852

 

[Moach]

srry wrong thread

---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------

i've two questions:
- Do the RAMCASTER engines already work in the current version? If yes, how do you start them?
- Will all the switches and instruments eventually work in the cockpit? Understandable if they won't. That's a hell of a job!

I really love the design! :thumbup:

- the ramcasters will only engage under the proper flight conditions (see T1 and T2 marks on the eicas screen)

other than that, you still need to have the RAMX feed pumps running and the inlets open, then open up the throttle to about 70% before turning the switch, lest it'll not engage....

when it does engage, you should hear a "boom"-like sound - check the ramcaster eicas screen showing "mode: LO" - then turn down the main engines, shut them off and set them to "int" (that closes the inlets)



- as for the switches, if i can pull it off - then yes, all of the should be at least flickable (i have ways to automate most of the toil in doing so).... they actually doing anything meaningful is another whole deal (some don't really matter at all, as far as Orbiter can properly simulate)

 

[MaverickSawyer]

Another JATO .scn, but a little overpowered.
Comments and criticisms are welcomed.

BEGIN_DESC
Testing a G42-200 with 4 JATO packs.
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 51982.6869147187
END_ENVIRONMENT

BEGIN_FOCUS
  Ship G422
END_FOCUS

BEGIN_CAMERA
  TARGET G422
  MODE Extern
  POS 3.21 5.81 -0.52
  TRACKMODE TargetRelative
  FOV 40.00
  BEGIN_PRESET
    Track:Earth:50.00:RELATIVE 1.299 0.556 0.107
    Cockpit:G422:50.00
    Cockpit:G422:50.00
    Track:Earth:20.00:RELATIVE 1.553 -0.395 -0.680
    Track:Earth:20.00:RELATIVE 1.434 0.192 -0.403
    Cockpit:G422:50.00
    Track:Earth:20.00:RELATIVE 1.434 2.433 -0.488
    Cockpit:G422:50.00
  END_PRESET
END_CAMERA

BEGIN_HUD
  TYPE Surface
END_HUD

BEGIN_MFD Left
  TYPE HSI
  NAV 0 0
  OBS 0.02 0.00
END_MFD

BEGIN_MFD Right
  TYPE Orbit
  PROJ Frame
  FRAME Ecliptic
  REF Earth
END_MFD

BEGIN_MFD 3
  TYPE Surface
  SPDMODE 3
END_MFD

BEGIN_MFD 4
  TYPE COM/NAV
END_MFD

BEGIN_VC
END_VC

BEGIN_SHIPS
ISS:ProjectAlpha_ISS
  STATUS Orbiting Earth
  RPOS 4435429.28 -5153255.38 592586.81
  RVEL -5587.869 -4563.839 2370.730
  AROT 110.66 -13.54 79.81
  AFCMODE 7
  PRPLEVEL 0:1.000000
  IDS 0:588 100 1:586 100 2:584 100 3:582 100 4:580 100
  NAVFREQ 0 0
  XPDR 466
END
Mir:Mir
  STATUS Orbiting Earth
  RPOS 4696959.22 -290486.26 -4845263.68
  RVEL 5486.213 326.274 5296.510
  AROT 0.56 -43.92 89.64
  AFCMODE 7
  IDS 0:540 100 1:542 100 2:544 100
  XPDR 482
END
Luna-OB1:Wheel
  STATUS Orbiting Moon
  RPOS -1817205.24 -1342820.45 129.87
  RVEL 861.972 -1186.419 0.189
  AROT -0.00 -0.00 171.36
  VROT 0.00 0.00 10.00
  AFCMODE 7
  IDS 0:560 100 1:564 100
  XPDR 494
END
G422:G42-200 Starliner
  STATUS Landed Earth
  POS -80.7056984 28.6322184
  HEADING 149.82
  AFCMODE 7
  PRPLEVEL 0:1.000000 1:1.000000 2:1.000000 3:1.000000 4:1.000000 5:1.000000
  NAVFREQ 0 0
  XPDR 452
  GEARS 2
  CNRDS 2
  VISOR 1
  RCSDOORS 1
  INLET_MAIN 1
  INLET_RAMX 1
  WING_WVRD 1
  WING_FTHR 1
  CGO_BAY 1
  MAIN_ENG_MD 0
  BURNER_TGGL 1
  RAMX_ENG_MD 0
  THR_AUTH_MD 0
  ENG_MAIN_L 1 3 0.0000 0.0000 0.0000 1.0000 0.0000
  ENG_MAIN_R 1 3 0.0000 0.0000 0.0000 1.0000 0.0000
  ENG_RAMX 6 3 0.0000 0.0000 1.0000
  ENG_APU 0 1 0.0000 0.0000 0.0000
  VC_SWS ====-=^=vvvvvvvvvvvvvv=-==vvv^^^^^^^^v===-=====---
END
JATO 1:Velcro\JATO
  STATUS Orbiting Earth
  RPOS 5207044.91 3611746.09 -657148.75
  RVEL 147.607 -149.386 348.357
  AROT -90.65 -33.83 -173.71
  AFCMODE 7
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 0
  CENTERTHRUST 0
  DELAYSTART 5.00
  PADBIAS 1.00
  TGT_HEADING 66.56
  PARALLELBURN 1 G422 -1.5000 2.0000 -25.0000 0.0000 0.0000 -1.0000 -1.0000 0.0000 0.0000
END
JATO 3:Velcro\JATO
  STATUS Orbiting Earth
  RPOS 5207044.91 3611746.09 -657148.75
  RVEL 147.607 -149.386 348.357
  AROT -90.65 -33.83 -173.71
  AFCMODE 7
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 0
  CENTERTHRUST 0
  DELAYSTART 5.00
  PADBIAS 1.00
  TGT_HEADING 66.56
  PARALLELBURN 1 G422 -1.5000 0.3000 -25.0000 0.0000 0.0000 -1.0000 -1.0000 0.0000 0.0000
END
JATO 4:Velcro\JATO
  STATUS Orbiting Earth
  RPOS 5207044.50 3611745.87 -657153.23
  RVEL 147.606 -149.388 348.357
  AROT -90.65 -33.83 6.29
  AFCMODE 7
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 0
  CENTERTHRUST 0
  DELAYSTART 5.00
  PADBIAS 1.00
  TGT_HEADING 66.56
  PARALLELBURN 1 G422 1.5000 0.3000 -25.0000 0.0000 0.0000 -1.0000 1.0000 0.0000 0.0000
END
JATO 2:Velcro\JATO
  STATUS Orbiting Earth
  RPOS 5207044.50 3611745.87 -657153.23
  RVEL 147.606 -149.388 348.357
  AROT -90.65 -33.83 6.29
  AFCMODE 7
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 0
  CENTERTHRUST 0
  DELAYSTART 5.00
  PADBIAS 1.00
  TGT_HEADING 66.56
  PARALLELBURN 1 G422 1.5000 2.0000 -25.0000 0.0000 0.0000 -1.0000 1.0000 0.0000 0.0000
END
END_SHIPS

I had a little trouble getting the plane to unstick until after JATO sep, and I was doing about M 0.82! Let's see if it was just me, or if it's a problem with where I placed the JATOs...

 

[MaverickSawyer]

OK, problem solved. Attaching a scenario and customized JATO packs for the G42.
Rotate the ship at about Mach 0.35.

 

[distructor20]

- the ramcasters will only engage under the proper flight conditions (see T1 and T2 marks on the eicas screen)

other than that, you still need to have the RAMX feed pumps running and the inlets open, then open up the throttle to about 70% before turning the switch, lest it'll not engage....

when it does engage, you should hear a "boom"-like sound - check the ramcaster eicas screen showing "mode: LO" - then turn down the main engines, shut them off and set them to "int" (that closes the inlets)



- as for the switches, if i can pull it off - then yes, all of the should be at least flickable (i have ways to automate most of the toil in doing so).... they actually doing anything meaningful is another whole deal (some don't really matter at all, as far as Orbiter can properly simulate)

OK, Thanks!
(dude, really can't wait untill it's done! I absolutly love it!)

 

[Moach]

well, just a quick note to say - i've fixed a long-standing problem with the wings code for "feathered position" (folded upwards)

this setup would allow the '42 to "bleed off" some of it's lift power in exchange for an increase in stability, making reentries a little easier on the ship and everyone aboard...

anyways, that whole feature wasn't working due to some pretty embarrasing problems in the position check code (had a '-' sign where thhere shouldn't be one)

so now, it is possible to feather the wings and get some lift dumping out of it :thumbup:

i'll still plan on implementing an important shift in the center of lift with this mode - the feathered wings to the rear should put the center of pressure a meter or two to the front, causing a pitch-up force that is much needed on high-energy reentries (and unlikely to come from fuel-transfer CoG shifting, since most of the fuel is gone by then)



anyways, i'll get that sorted out, repack the new VC models (yep, it now features ALL switches - albeit most are just for show ATM) - then i'll update to WIP-303, which should contain a more comprehensive flight manual, covering at least the basic nominal ascent procedure and an overview of the ship's features



and now... back to work

 

[Proximus]

Excellent :stirpot:

 

[Wonderer]

Awesome job so far, one of the most awaited addons for me! Just one question, any plans for an attitude hold autopilot? :hmm: Without one my re-entries tend to be "less than optimal" :lol:

 

[sphinxbot]

This is great, I can't wait:thumbup:

 

[Moach]

minor progress report.....


well, this wednesday was a national holliday, so i got myself a couple of rather insufficient hours of able time on the '42 project....

it was enough to pull off a thing or two tho.... but unfortunately most of it was just intangible research work - with the exception of the now-animated tiller handle for the nosewheel steering (only when on ground) plus a couple of tuneups for the flight model....


but more impotantly, i've learned a few new things about ram/scramjet design - and might be worth it to redo some code for a much more realistic representation of how a thing like that would work... (and here we go on the "how to build the thing for real" discussion again)


the first key concept - the need for a mighty turbopump

an engine like that doesn't light itself up - fuel must be pumped to something like 100bar for injection.... that requires a big beefy pump, a heavy pump....

but - having more engines aboard, two additional options came to mind to remove that extra weight

* we can use a crossfeed system and use the two main engines to pump fuel for the ramcaster - would require oxidizer flow, tho.... could be less than optimal in terms of efficiency

or.....

* we can rev up the APU and use that to drive this pump - it already runs on monopropellant, so no oxidizer would be needed (it would need to burn from the RCS//OMS supply during ramcaster ascent, tho)

i find the second solution to be generally more agreeable (and less heavy on redesign work than the first one...) - so i just might go with that...


now, the second thing.... this is more complex stuff

the constant dynamic pressure flightpath

up to now, the optmal ascent path was defined somewhat arbitrarily through a lookup bitmap reference interpolation process....
but having a better understanding of how real scramjets perform, i feel there could be a LOT of room for improvement on that whole area

i don't plan on removing the lookup table scheme altogether - but i just might have it redone over different parameters... so instead of a mach x altitude table as it's been so far, we'd have a dynamic pressure x mach reference lookup, providing a far more accurate representation of what a ramcaster ascent would be like if it were for real


needless to say, this is kinda bad news for that flight manual.... for if i'm gonna change stuff around, writing about it is just south of conterproductive, i suppose :hmm:

so please be patient.... there shall be a manual, as soon as there's something less, ehmm... "variable" to write about :lol: - in the meantime, help eachother out as you can, and don't hesitate to ask me about anything (even if it seems too obvious)


i guess i shall update to WIP-303 with the current state as is.... these new changes are meaningful enough to qualify as WIP-4



well.... back to work

 

[Cras]

I think having the APU run during the entire ascent is a good safety measure anyway, so you loose nothing and gain a bunch letting it drive the pumps.

I always figure on like the XR2 to have the APU run all the way up because if there is a need to bail on the ascent and return to an alternate landing site, in which case I need the APU. I know that in the XR2 the APU startup is fool proof, I still treat it as though it could fail on a second or third start up, so instead of constantly fired it up and shutting it down, when it goes up for ascent, it stays on. If that makes sense.

But I have enjoyed following the development of this add-on. Impressive may not be adequate a word for this. It certainly is a must have add-on in the making.

 

[Moach]

ok, i'm now uploading the updated WIP-303 revision....

not too much news there, a few improvements on the VC model, flight dynamics and some other minor stuff... still worth getting, nonetheless :thumbup:

almost done... i'm updating the link on the hangar, btw - so its the same entry, but a different file


and now, onto business (the things i mentioned earlier today)

next release will be WIP-401... if all goes well, that is



edit: there it is: [ame="http://www.orbithangar.com/searchid.php?ID=5456"]G42-200 StarLiner WIP-302[/ame] (never mind the 302 page title, the zip shows it's 303 now)

 

[GuiConteDGIV2X]

Hi moach,you project is better at ever release.Keep going.

Suggestion:What about in the later versions you upload 2 G42-200s in 1 zip?
One for standart Orbiter (Directx 7 graphics engine) and the another one to D3D9 version(Directx 9 graphic engine).
Because in D3D9 Graphic engine there is a CTD at you G42-200.And the D3D9 can offer high FPS rates if you are playing in Windows Vista and Windows 7.

 

[RaR76]

Each time I see Moach put a clickable link, it feels like Christmas

 

[Goth]

You should put the "how to fly" thing into the readme as in the WIP1, otherwise a guy has to download also the WIP1 just to know how to fly it.

 

[Moach]

Hi moach,you project is better at ever release.Keep going.

Suggestion:What about in the later versions you upload 2 G42-200s in 1 zip?
One for standart Orbiter (Directx 7 graphics engine) and the another one to D3D9 version(Directx 9 graphic engine).
Because in D3D9 Graphic engine there is a CTD at you G42-200.And the D3D9 can offer high FPS rates if you are playing in Windows Vista and Windows 7.

the current WIP-3 version should be already fully D3D9 compatible (and inline graphics too).... not sure why you're getting a CTD with it - could you post your log so we can see what might be going on there?




and as for the "how to fly" on the past versions, that thing is so badly outdated i figure it does more harm than good... not only a lot of stuff now works differently, some switches have been rearranged or are not even there anymore

please be patient - a proper manual is in the high-priorities list

 

[GuiConteDGIV2X]

Here is it.

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1434 x 874 x 32
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: 8
Loading 15382 records from star database
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll ............ [Build ******, API 060425]
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Satsat.dll ............ [Build 100215, API 100212]
Module Saturn.dll ............ [Build 100830, API 100830]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll ............. [Build 100215, API 100212]
SATSAT Mimas: Terms 113
Module Enceladus.dll ......... [Build 100215, API 100212]
SATSAT Enceladus: Terms 33
Module Tethys.dll ............ [Build 100215, API 100212]
SATSAT Tethys: Terms 101
Module Dione.dll ............. [Build 100215, API 100212]
SATSAT Dione: Terms 59
Module Rhea.dll .............. [Build 100215, API 100212]
SATSAT Rhea: Terms 68
Module Titan.dll ............. [Build 100215, API 100212]
SATSAT Titan: Terms 100
Module Iapetus.dll ........... [Build 100215, API 100212]
SATSAT Iapetus: Terms 605
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll ........... [Build ******, API 060425]
Module Ariel.dll ............. [Build ******, API 060425]
Module Umbriel.dll ........... [Build ******, API 060425]
Module Titania.dll ........... [Build ******, API 060425]
Module Oberon.dll ............ [Build ******, API 060425]
Module Neptune.dll ........... [Build 100830, API 100830]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Finished initialising world
Module DeltaGliderXR1.dll .... [Build 110306, API 100830]
Module ShuttleA.dll .......... [Build 100830, API 100830]
Module ShuttlePB.dll ......... [Build 100830, API 100830]
Module DeltaGlider.dll ....... [Build 100830, API 100830]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
ERROR: DDraw object is still referenced: 4
---------------------------------------------------------------
>>> ERROR: Destroy framework objects failed
>>> [OrbiterGraphics::Exit3DEnvironment | .\OGraphics.cpp | 1034]
---------------------------------------------------------------
**** Closing simulation session

Thanks for the tip Grover

EDIT:finnaly made it

 

[Grover]

remember to put it in (code) (/code) next time

and thats a graphics problem:

---------------------------------------------------------------
>>> ERROR: Destroy framework objects failed
>>> [OrbiterGraphics::Exit3DEnvironment | .\OGraphics.cpp | 1034]
---------------------------------------------------------------

not sure if thats Orbiter or the G42...