OHM Quasar Super Heavy Launch Vehicle 2.55

[fausto]

K-Jameson, the project leader, is working on final release details, but real life steals time and energies.. please be patience, new Quasar is coming! :thumbup:

 

[K_Jameson]

I'm sorry for the delay (real life and another projects). Some features as an operative payload - like in the Jarvis package - will be postponed, but this weekend the package will be uploaded. :thumbup:

 

[Cosmic Penguin]

The new version has been released! :thumbup:

 

[Cosmic Penguin]

One problem with the new version: for some reason the Eridanus-related materials are not included in the add-on, so the Eridanus add-on can easily crash if the user has deleted the old Quasar folders before updating. Can you guys look at it? Thanks! :tiphat:

 

[K_Jameson]

:facepalm: you're right: with the deletion of the old Quasar folders, even some Eridanus material will be deleted, so the Eridanus addon can crash.

The problem can be solved, i think, with a reinstallation of the Eridanus package after the installation of the new Quasar (but some features of the new rockets can be lost, as the new shorter boosters).

I will check the thing to provide a solution. Sorry for the inconvenience.

---------- Post added at 11:55 AM ---------- Previous post was at 07:28 AM ----------

P.S.
can you post a log?

 

[Cosmic Penguin]

:facepalm: you're right: with the deletion of the old Quasar folders, even some Eridanus material will be deleted, so the Eridanus addon can crash.

The problem can be solved, i think, with a reinstallation of the Eridanus package after the installation of the new Quasar (but some features of the new rockets can be lost, as the new shorter boosters).

I will check the thing to provide a solution. Sorry for the inconvenience.

---------- Post added at 11:55 AM ---------- Previous post was at 07:28 AM ----------

P.S.
can you post a log?

I don't have a log here, because after CTD-ing once, I figured out what happened and manually moved some of the Eridanus-related configuration files, meshes and textures back into the new file, and it now works.

 

[K_Jameson]

I can confirm that with the reinstallation of the Eridanus package (AFTER the installation of Quasar 2.5), all problems are solved without other drawbacks.

After all, for the future, it's better to NOT delete all the old installation, but, if necessary, only the folder Scenarios (to keep it clean).

 

[boogabooga]

I was noticing that the payload simulator ballast cargoes for all FOI rockets tumble wildly and de-orbit themselves from LEO. The problem is that they all have masses of 1kg, so tiny aerodynamic forces can lead to huge accelerations.

The solution is to go to the folder Config/spacecraft and find the .ini files for the various ballast payloads.

Examples:
ballast220.ini
ballast440-452.ini
cargo_jarvis.ini

and so on for all FOI launchers (Quasar, Neptune, Trident, Jarvis)

Find the line

EMPTY_MASS=1

and change to a larger number.

This only effects the ballast type cargoes. Real payloads are O.K.

 

[K_Jameson]

The only task of the ballast is to give a demonstrative payload for the ascent to orbit; the fate of the ballast after the orbit insertion has never been considered important. This is the reason why the .ini file for these payloads was never configured carefully. :thumbup:

 

[boogabooga]

I figured It's O.K.

But if you like to follow it for a few minutes, then this is how to fix it.

 

[Cras]

What you have done to make it "D3D9" compatible is actually wholly unnecessary. D3D9 client is fully multistage and spacecraft3 compatible already, once the user creates the symbolic links required, a function that both the client can do automatically, and also something that the client will warn the user about if they do not exist.

So having that extra config folder probably presents more problems than it solves.

 

[Ripley]

Cras, it was me (without being a developer myself) who actually suggested to FOI developers to adopt this "compatibility workaround".

I've always read that one can create EITHER symbolic links, OR manually copying these folders, understanding that both are good solutions.

In the second case, though, keeping the folder updated can be tedious (at best) since it must be done manually every time we download an updated add-on.

Otherwise, if this leads to errors or can "present more problems than it solves", :facepalm: we'll change attitude.

I apologize for the inconvenience.

 

[K_Jameson]

Apart from the D3D9 discussion, do you like the new rocket?

 

[Cras]

Oh yes of course!

 

[K_Jameson]

Thanks!
Here, a brief look at the various configurations contemplated in the process of redesign.



From right to left:
- four boosters, 6x RS-25E
- two boosters, 6x RS-68
- all hydrolox: two Quasar220-derived boosters, total 12x RS-25E
- Quasar 471 "in-line": four boosters, 7x RS-68
- "Modern Saturn V" concept: no boosters, large kerolox first stage
- Quasar 452 with large second stage and narrow fairing
- Quasar 452 with large two-pieces fairing and long boosters
- Qusaar 452 final: shortened boosters and four-pieces fairing

 

[K_Jameson]

Soon, a new update: the controversial modules\server\config folder will be removed, and an operative payload will be added: the Pegasus B Test Satellite. The concept of this big satellite is the same as the Pegasus Satellite launched in the Saturn I test missions SA-8, SA-9 and SA-10 in 1965.

The satellite is equipped with four big panels (914 square meters) fitted with sensors to detect punctures by micrometeoroids and especially space debris, and in order to capture as much as possible. A big fuel reserve allows the Pegasus B to depart from LEO autonomsly and reach GEO to accomplish the same mission even in this orbit.











The test launch will be broadcast October 18, 2012 on Orbiter Live Missions.

 

[Cosmic Penguin]

Soon, a new update: the controversial modules\server\config folder will be removed, and an operative payload will be added: the Pegasus B Test Satellite. The concept of this big satellite is the same as the Pegasus Satellite launched in the Saturn I test missions SA-8, SA-9 and SA-10 in 1965.

The satellite is equipped with four big panels (914 square meters) fitted with sensors to detect punctures by micrometeoroids and especially space debris, and in order to capture as much as possible. A big fuel reserve allows the Pegasus B to depart from LEO autonomsly and reach GEO to accomplish the same mission even in this orbit.











The test launch will be broadcast October 18, 2012 on Orbiter Live Missions.

It also reminds me of the first ever payloads of the veteran Proton rocket: the Protons (of course! :lol. These were some of the largest scientific satellites ever launched: Proton 4 weights 17 tonnes!

http://space.skyrocket.de/doc_sdat/proton-1.htm

http://space.skyrocket.de/doc_sdat/proton-4.htm

 

[Pipcard]

That is one beautiful-looking satellite right there.

 

[Cras]

That looks brilliant!

 

[K_Jameson]

In red, the QTA (Quasar Test Article), an instrument unit for the test flight, mated with eight concrete blocks for 35 tonnes of ballast. This ballast increases the overall payload weight to 190,000 kg, making a more severe test for the rocket.