Velcro Rockets

Fixerger

Member
Joined
May 24, 2009
Messages
163
Reaction score
1
Points
18
Anyone here experince problems with SPINTABLE string that is not working?
 

Fixerger

Member
Joined
May 24, 2009
Messages
163
Reaction score
1
Points
18
Code:
How can I rotate the main stage for 90 deg? Attachment points?

Figured that out, but can't delete my post (in advanced mode).
 
Last edited:

spudman2

Yarr!binaut
Joined
Jul 28, 2011
Messages
11
Reaction score
0
Points
0
Location
-137km/s above Brighton Beach.
Kinda new here, decided to download & install this, but I'm having a bit of a problem with the Titan series (and others, maybe). I launch the Titan IIL scenario, and the world loads fine, but when it tries to get the Titan's Vessel Config file, it crashes. Here's the last bit of the error log:
Code:
Finished initialising world
>>> ERROR: No vessel class configuration file found for:
---------------------------------------------------------------
>>> ERROR: CVELTitanII
>>> [Vessel::OpenConfigFile | .\Vessel.cpp | 252]
---------------------------------------------------------------
>>> TERMINATING <<<

And while I'm posting, would anybody have a link for a .cfg tutorial?
 

n0mad23

Addon Developer
Addon Developer
Joined
Feb 10, 2008
Messages
1,078
Reaction score
17
Points
0
Location
Montesano
Website
soundcloud.com
You probably need to install CVEL Titans first, as that scenario is calling up a CVEL cfg. Here's the link: [ame="http://www.orbithangar.com/searchid.php?ID=1031"]http://www.orbithangar.com/searchid.php?ID=1031[/ame]
 

sputnik

Addon Developer
Addon Developer
Donator
Joined
Apr 3, 2008
Messages
424
Reaction score
0
Points
31
Location
Palmdale
Website
www.worldof2001.com
Yes, I suppose I could have been a bit clearer there, but the .pdf does say you need CVEL Titans for the couple of scenarios that add things to them. There are no separate, standalone Titan launchers under Velcro. Yet, anyway.
 

DaveS

Addon Developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
9,429
Reaction score
680
Points
203
Could custom exhaust streams be added to a future version of Velcro Rockets? Also is there an example of how to set up a jettisonable LES?
 

MetalheadOC

New member
Joined
Oct 23, 2011
Messages
16
Reaction score
0
Points
0
Location
South Whidbey, WA
GETDOCKINGPORTS not workin'

Hi all, first time post here, hope this is the right thread to drop this one...

Was really hoping I could figure this out without the old "Post on a new forum & wait for someone smarter than myself to come along" routine, but so be it.

Having a bugger of a time getting the GETDOCKINGPORTS command to work in a scenario. Everything else seems to work fine, loads, flies, jettisons ok, docking ports work after jettison, but not while things are still attached to velcro stages.
Docking button is grayed out in the scenario editor, manual docking don't work either. Here's the (I think) relevant code:


Code:
Proton-Stg3a:Velcro/ProtonSTG3
  STATUS Landed Earth
  BASE Doberai:5
  HEADING 0.00
  TGT_HEADING 090.0
  FUEL 1.000
  CONFIGURATION 0
  Fairing 2 5.0 0.0 5.0 0.0
  PAYLOAD Module2 Module2 Module2 0 0 7.25 30000.0 0.0 1.0
  PAYLOAD Fair1 Velcro/Parts/Angara95_PLF2 Velcro/Parts/Angara95_PLF2 0 0 10 1420.0 0 0.0 1.0
  PAYLOAD Fair2 Velcro/Parts/Angara95_PLF1 Velcro/Parts/Angara95_PLF1 0 0 10 1420.0 0 0.0 1.0
  GETDOCKINGPORTS 1
  DELAYSTART 10
END

Code:
Proton-Stg2:Velcro/ProtonSTG2
  STATUS Landed Earth
  BASE Doberai:6
  HEADING 0.00
  TGT_HEADING 090.0
  FUEL 1.000
  CONFIGURATION 0
  GETDOCKINGPORTS 1
  Fairing 2 10.0 0.0 10.0 0.0
  PAYLOAD Transtage-test Velcro/ProtonSTG2 Transtage-test 0 0 17 11715 0.0 1.0
  PAYLOAD Fair1 Velcro/Parts/Angara95_PLF2 Velcro/Parts/Angara95_PLF2 0 0 20 1420.0 0 0.0 1.0
  PAYLOAD Fair2 Velcro/Parts/Angara95_PLF1 Velcro/Parts/Angara95_PLF1 0 0 20 1420.0 0 0.0 1.0
  CAMERA 0 0 90.0
  DELAYSTART 5
END

Anything obvious wrong? There are two different "stacks" in the same scnario, I didn't post what I *think* isn't relevant so as not to clutter the post up.
 

Axertan

Member
Joined
Jun 7, 2010
Messages
171
Reaction score
1
Points
18
Hi all, first time post here, hope this is the right thread to drop this one...

Was really hoping I could figure this out without the old "Post on a new forum & wait for someone smarter than myself to come along" routine, but so be it.

Having a bugger of a time getting the GETDOCKINGPORTS command to work in a scenario. Everything else seems to work fine, loads, flies, jettisons ok, docking ports work after jettison, but not while things are still attached to velcro stages.

Anything obvious wrong? There are two different "stacks" in the same scnario, I didn't post what I *think* isn't relevant so as not to clutter the post up.

Code:
Proton-Stg3a:Velcro/ProtonSTG3
  STATUS Landed Earth
  BASE Doberai:5
  HEADING 0.00
  TGT_HEADING 090.0
  FUEL 1.000
  CONFIGURATION 0
  Fairing 2 5.0 0.0 5.0 0.0
  PAYLOAD [COLOR="Red"]Module2[/COLOR] Module2 Module2 0 0 7.25 30000.0 0.0 1.0
  PAYLOAD Fair1 Velcro/Parts/Angara95_PLF2 Velcro/Parts/Angara95_PLF2 0 0 10 1420.0 0 0.0 1.0
  PAYLOAD Fair2 Velcro/Parts/Angara95_PLF1 Velcro/Parts/Angara95_PLF1 0 0 10 1420.0 0 0.0 1.0
  GETDOCKINGPORTS 1
  DELAYSTART 10
END
This scenario looks correct to me, however default "Module 2" has 6 docking ports. Maybe try with just 1 docking port?
:edit:
[edit]Coming to think of it, Velcro probably can recreate multiple docking ports. Sputnik surely knows, maybe PM him?
Why not try moving the GETDOCKINGPORTS string right below CONFIGURATION ?[/edit]

Code:
Proton-Stg2:Velcro/ProtonSTG2
  STATUS Landed Earth
  BASE Doberai:6
  HEADING 0.00
  TGT_HEADING 090.0
  FUEL 1.000
  CONFIGURATION 0
  GETDOCKINGPORTS 1
  Fairing 2 10.0 0.0 10.0 0.0
  PAYLOAD [COLOR="Red"]Transtage-test[/COLOR] Velcro/ProtonSTG2 Transtage-test 0 0 17 11715 0.0 1.0
  PAYLOAD Fair1 Velcro/Parts/Angara95_PLF2 Velcro/Parts/Angara95_PLF2 0 0 20 1420.0 0 0.0 1.0
  PAYLOAD Fair2 Velcro/Parts/Angara95_PLF1 Velcro/Parts/Angara95_PLF1 0 0 20 1420.0 0 0.0 1.0
  CAMERA 0 0 90.0
  DELAYSTART 5
END
I assume the vessel named "Transtage-test" in this scenario has a docking port (seeing you have a custom config). I see no reason for this not to work.

If you don't get the PAYLOAD string to work, you can try attaching a payload with SERIESBURN instead. This will make the attached object stay active (e.g. you can switch focus to it, if available), and theoretically it's docking ports should work fine. I have not yet tried docking to SERIESBURN attached object myself, however.

I hope this helps at least a bit :tiphat:
 
Last edited:

sputnik

Addon Developer
Addon Developer
Donator
Joined
Apr 3, 2008
Messages
424
Reaction score
0
Points
31
Location
Palmdale
Website
www.worldof2001.com
Hi MetalheadOC, sorry I missed your post the first time.

You are doing ALMOST everything right. Unfortunately, what you missed (because the docs could be a lot more clear on this point; I apologize) is that, per the docs, GETDOCKINGPORTS works on a "primary" payload. What I meant by that, is one that uses SERIESBURN, not one that uses a CVEL string, as you have there.
The reason GETDOCKINGPORTS can't work with a CVEL payload is that with CVEL, your desired payload is carried as a mesh and an additional penalty mass, but it doesn't really "exist" until the moment it's jettisoned. Thus, Velcro Rockets can not determine what its docking ports should be, because they simply don't exist yet.

So, instead of

PAYLOAD Transtage-test Velcro/ProtonSTG2 Transtage-test 0 0 17 11715 0.0 1.0

try:

SERIESBURN 0 Transtage-test 0.0 0.0 -3.0 0 1 0

...AND make sure that Transtage-test is created, within the scenario (with its own vessel block) just like any other vessel. Location is not important; Velcro Rockets will move it to where it needs to be.


You can do the same with module2, but now, since you're using it as a Velcro attached stage, you'll need to make sure it has the attach point definitions that Velcro Rockets is looking for:


; === Attachment specs ===
BEGIN_ATTACHMENT
C 0.0 0.0 2.03 0 0 1 0 1 0 VELCRO1
C 0.0 0.54 0 0 0 1 0 -1 0 VELCRO2
P 0.0 0.0 2.03 0 0 1 0 1 0 VELCRO3
P 0.0 0.54 0 0 0 1 0 -1 0 VELCRO4
END_ATTACHMENT

Or something like that. Where 2.03 is the back end of the module, and 0.54 is the radius of the module.

A bit contrived, but it has to be, unfortunately. But at least it should work.
 

Ark

New member
Joined
Jan 31, 2009
Messages
2,200
Reaction score
0
Points
0
Could custom exhaust streams be added to a future version of Velcro Rockets? Also is there an example of how to set up a jettisonable LES?

Dunno about exhaust streams, but the LES is pretty easy to set up. Have a look at the Saturn V AMSO scenario:

Code:
AS-506:AMSO\Apollo
  STATUS Orbiting Earth
  RPOS -4065931.00 591626.06 15607271.12
  RVEL -5641.258 120.015 4005.905
  AROT -178.28 -50.83 -44.56
  RCSMODE 1
  PRPLEVEL 0:1.000
  NAVFREQ 0 1 2 3
  XPDR 0
  STATE 8
  ABORTSTATUS 0
  MISSIONTIME 12234.866
  PWR 0.000
  INVULNERABLE 1
END
AS-506_LM_vessel:AMSO\LM_vessel
  STATUS Orbiting Earth
  RPOS -204213676.76 5829152.21 45763422.63
  RVEL -1545.130 -27.290 2.834
  AROT -83.88 -6.74 -55.23
  PRPLEVEL 0:1.000
  NAVFREQ 0 1 2 3
  XPDR 0
  STATE 1
  C1DEAD 0
  C2DEAD 0
END
S-IVb:Velcro/s4b
  STATUS Landed Earth
  BASE Cape Canaveral:6
  HEADING 0.00
  TGT_HEADING 095.0
  FUEL 1.000
  CONFIGURATION 0
  CAMERA 0 0 40.0
  SLA 4 -2.0 2.0 0.0
  PAYLOAD Ring Velcro/Parts/S4b_upr_transition Velcro/Parts/S4b_upr_transition 0 0 0.0 0.0 0 0.0 1.0
  PAYLOAD SLA1 Velcro/Parts/SLA01 Velcro/Parts/SLA01 0 0 -52.0 3500.0 0 0.0 1.0
  PAYLOAD SLA2 Velcro/Parts/SLA02 Velcro/Parts/SLA02 0 0 -52.0 3500.0 0 0.0 1.0
  PAYLOAD SLA3 Velcro/Parts/SLA03 Velcro/Parts/SLA03 0 0 -52.0 3500.0 0 0.0 1.0
  PAYLOAD SLA4 Velcro/Parts/SLA04 Velcro/Parts/SLA04 0 0 -52.0 3500.0 0 0.0 1.0
  SERIESBURN 0 AS-506 0.0 0.0 -8.2 0.0 1.0 0.0 
  PAYATCH AS-506_LM_vessel 0.0 -0.0 0.0  0.0 -1.0 0.0  1.0 0.0 0.0
END
S-II:Velcro/s2
  STATUS Landed Earth
  BASE Cape Canaveral:6
  HEADING 0.00
  TGT_HEADING 095.0
  FUEL 1.000
  CONFIGURATION 0
  CAMERA 0 0 60.0
  LES 12.0
  SERIESBURN 0 S-IVb 0.0 0.0 -9.0  0.0 1.0 0.0 
  PAYLOAD Int2 Velcro/Parts/s2_s4bint Velcro/Parts/s2_s4bint 0 0 0 8000.0 0 0.0 1.0
  PAYLOAD LES Velcro/Parts/Sat5BPC Velcro/Parts/ApolloLES 0 0.0 52.3 500 0 1
END
s1cinter:Velcro/s1cinter
  STATUS Landed Earth
  BASE Cape Canaveral:6
  HEADING 0.00
  TGT_HEADING 095.0
  FUEL 1.000
  CONFIGURATION 0
  CAMERA 0 0 90.0
  SERIESBURN 0 S-II 0.0 0.0 -9.25  0.0 1.0 0.0 
END
S-1C:Velcro/S1C
  STATUS Landed Earth
  BASE Cape Canaveral:6
  HEADING 0.00
  TGT_HEADING 095.0
  FUEL 1.000
  CONFIGURATION 0
  CAMERA 0 0 90.0
  SERIESBURN 0 s1cinter 0.0 0.0 18.25 0.0 1.0 0.0
END

Notice this line in the S-II section:

PAYLOAD LES Velcro/Parts/Sat5BPC Velcro/Parts/ApolloLES 0 0.0 52.3 500 0 1

This adds your LES as a payload to the second stage. Since you want it to jettison while the second stage is burning, that is the stage it should be a payload of. The first directory is for the mesh file, the second is for the config file, followed by the position and rotation data.

This line determines when the LES fires, in this case it's 12 seconds after first stage seperation:

LES 12.0

I've made a few of my own LES systems with simple copying and pasting. For instance, I copied the mesh location of the Jarvis LES and fairings into the config files of some Apollo parts and saved them separately. As far as payloads go, it's not difficult to create new ones.

Fairings work in a similar way, but I think they're dependent on ambient pressure instead of just running on a timer after stage separation.
 

MetalheadOC

New member
Joined
Oct 23, 2011
Messages
16
Reaction score
0
Points
0
Location
South Whidbey, WA
Hi MetalheadOC, sorry I missed your post the first time.

You are doing ALMOST everything right. Unfortunately, what you missed (because the docs could be a lot more clear on this point; I apologize) is that, per the docs, GETDOCKINGPORTS works on a "primary" payload. What I meant by that, is one that uses SERIESBURN, not one that uses a CVEL string, as you have there.
The reason GETDOCKINGPORTS can't work with a CVEL payload is that with CVEL, your desired payload is carried as a mesh and an additional penalty mass, but it doesn't really "exist" until the moment it's jettisoned. Thus, Velcro Rockets can not determine what its docking ports should be, because they simply don't exist yet.

So, instead of

PAYLOAD Transtage-test Velcro/ProtonSTG2 Transtage-test 0 0 17 11715 0.0 1.0

try:

SERIESBURN 0 Transtage-test 0.0 0.0 -3.0 0 1 0

...AND make sure that Transtage-test is created, within the scenario (with its own vessel block) just like any other vessel. Location is not important; Velcro Rockets will move it to where it needs to be.


You can do the same with module2, but now, since you're using it as a Velcro attached stage, you'll need to make sure it has the attach point definitions that Velcro Rockets is looking for:


; === Attachment specs ===
BEGIN_ATTACHMENT
C 0.0 0.0 2.03 0 0 1 0 1 0 VELCRO1
C 0.0 0.54 0 0 0 1 0 -1 0 VELCRO2
P 0.0 0.0 2.03 0 0 1 0 1 0 VELCRO3
P 0.0 0.54 0 0 0 1 0 -1 0 VELCRO4
END_ATTACHMENT

Or something like that. Where 2.03 is the back end of the module, and 0.54 is the radius of the module.

A bit contrived, but it has to be, unfortunately. But at least it should work.

Well I did a quick test with the Transstage stack, and the docking port works (more or less :blink:), but something's not right, cuz now it can't even get close to orbit, whereas before it got there with fuel to spate?
 

sputnik

Addon Developer
Addon Developer
Donator
Joined
Apr 3, 2008
Messages
424
Reaction score
0
Points
31
Location
Palmdale
Website
www.worldof2001.com
Did you delete the PAYLOAD Transtage-test Velcro/ProtonSTG2 Transtage-test 0 0 17 11715 0.0 1.0 line?

If not, you're carrying TWO Transtages to orbit.

If you did, it might still be double-counting somehow. Can you post the complete .scn?
 

MetalheadOC

New member
Joined
Oct 23, 2011
Messages
16
Reaction score
0
Points
0
Location
South Whidbey, WA
Did you delete the PAYLOAD Transtage-test Velcro/ProtonSTG2 Transtage-test 0 0 17 11715 0.0 1.0 line?

If not, you're carrying TWO Transtages to orbit.

If you did, it might still be double-counting somehow. Can you post the complete .scn?

Yup sure did. Just tried a couple more times, can't even get half way to orbital speed. Used to make it with fuel to spare.

The "transstage" is nothing but a Proton second stage with a docking port & bigger RCS thursters.

Code:
BEGIN_DESC

END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 56885.9427581035
END_ENVIRONMENT

BEGIN_FOCUS
  Ship Proton-Stg1
END_FOCUS

BEGIN_CAMERA
  TARGET Proton-Stg1
  MODE Extern
  POS 7.58 165.61 92.10
  TRACKMODE GlobalFrame
  FOV 50.00
END_CAMERA

BEGIN_HUD
  TYPE Surface
END_HUD

BEGIN_MFD Left
  TYPE Orbit
  PROJ Ship
  FRAME Ecliptic
  ALT
  REF Earth
END_MFD

BEGIN_MFD Right
  TYPE Map
  REF Earth
  ZOOM 4
  POS 0.28 -0.04
END_MFD

BEGIN_SHIPS
Proton-Stg2:Velcro/ProtonSTG2
  STATUS Landed Earth
  BASE Doberai:6
  HEADING 0.00
  TGT_HEADING 090.0
  FUEL 1.000
  CONFIGURATION 0
  GETDOCKINGPORTS 1
  Fairing 2 10.0 0.0 10.0 0.0
  SERIESBURN 0 TransStage-test 0.0 0.0 -3.0 0 1 0 
  PAYLOAD Fair1 Velcro/Parts/Angara95_PLF2 Velcro/Parts/Angara95_PLF2 0 0 20 1420.0 0 0.0 1.0
  PAYLOAD Fair2 Velcro/Parts/Angara95_PLF1 Velcro/Parts/Angara95_PLF1 0 0 20 1420.0 0 0.0 1.0
  CAMERA 0 0 90.0
  DELAYSTART 5
END
Proton-Stg1:Velcro/ProtonSTG1
  STATUS Landed Earth
  BASE Doberai:6
  HEADING 0.00
  TGT_HEADING 090.0
  FUEL 1.000
  CONFIGURATION 0
  CAMERA 0 0 90.0
  SERIESBURN 0 Proton-Stg2 0.0 0.0 -7.8  0.0 1.0 0.0 
END
Proton-Stg3a:Velcro/ProtonSTG3
  STATUS Landed Earth
  BASE Doberai:5
  HEADING 0.00
  TGT_HEADING 090.0
  FUEL 1.000
  CONFIGURATION 0
  Fairing 2 5.0 0.0 5.0 0.0
  PAYLOAD Module2 Module2 Module2 0 0 7.25 30000.0 0.0 1.0
  PAYLOAD Fair1 Velcro/Parts/Angara95_PLF2 Velcro/Parts/Angara95_PLF2 0 0 10 1420.0 0 0.0 1.0
  PAYLOAD Fair2 Velcro/Parts/Angara95_PLF1 Velcro/Parts/Angara95_PLF1 0 0 10 1420.0 0 0.0 1.0
  GETDOCKINGPORTS 1
  DELAYSTART 10
END
Proton-Stg2a:Velcro/ProtonSTG2
  STATUS Landed Earth
  BASE Doberai:5
  HEADING 0.00
  TGT_HEADING 090.0
  FUEL 1.000
  CONFIGURATION 0
  CAMERA 0 0 40.0
  SERIESBURN 0 Proton-Stg3a 0.0 0.0 -1.564  0.0 1.0 0.0 
  DELAYSTART 5
END
Proton-Stg1a:Velcro/ProtonSTG1
  STATUS Landed Earth
  BASE Doberai:5
  HEADING 0.00
  TGT_HEADING 090.0
  FUEL 1.000
  CONFIGURATION 0
  CAMERA 0 0 90.0
  SERIESBURN 0 Proton-Stg2a 0.0 0.0 -7.8  0.0 1.0 0.0 
END
R7-boost1a:Velcro/r7blockb
  STATUS Landed Earth
  BASE Doberai:5
  HEADING 0.00
  TGT_HEADING 090.0
  FUEL 1.000
  CONFIGURATION 0
  CAMERA 0 0 90.0
  PARALLELBURN 1 Proton-Stg1a 0.0 -2.25 0.0  0.0 -1.0 0.0 
END
R7-boost2a:Velcro/r7blockb
  STATUS Landed Earth
  BASE Doberai:5
  HEADING 0.00
  TGT_HEADING 090.0
  FUEL 1.000
  CONFIGURATION 0
  CAMERA 0 0 90.0
  PARALLELBURN 1 Proton-Stg1a 1.95 1.125 0.0  0.866 0.5 0.0 
END
R7-boost3a:Velcro/r7blockb
  STATUS Landed Earth
  BASE Doberai:5
  HEADING 0.00
  TGT_HEADING 090.0
  FUEL 1.000
  CONFIGURATION 0
  CAMERA 0 0 90.0
  PARALLELBURN 1 Proton-Stg1a -1.95 -1.125 0.0  -0.866 -0.5 0.0 
END
R7-boost4a:Velcro/r7blockb
  STATUS Landed Earth
  BASE Doberai:5
  HEADING 0.00
  TGT_HEADING 090.0
  FUEL 1.000
  CONFIGURATION 0
  CAMERA 0 0 90.0
  PARALLELBURN 1 Proton-Stg1a 0.0 2.25 0.0  0.0 1.0 0.0 
END
R7-boost5a:Velcro/r7blockb
  STATUS Landed Earth
  BASE Doberai:5
  HEADING 0.00
  TGT_HEADING 090.0
  FUEL 1.000
  CONFIGURATION 0
  CAMERA 0 0 90.0
  PARALLELBURN 1 Proton-Stg1a -1.95 1.125 0.0  -0.866 0.5 0.0 
END
R7-boost6a:Velcro/r7blockb
  STATUS Landed Earth
  BASE Doberai:5
  HEADING 0.00
  TGT_HEADING 090.0
  FUEL 1.000
  CONFIGURATION 0
  CAMERA 0 0 90.0
  PARALLELBURN 1 Proton-Stg1a 1.95 -1.125 0.0  0.866 -0.5 0.0 
END
TransStage-test:Transtage-test
  STATUS Orbiting Earth
  RPOS 5431089.46 -359.05 4425786.97
  RVEL -4770.025 -1.627 5843.632
  AROT -0.00 -4.26 0.00
  AFCMODE 7
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 1
  CENTERTHRUST 0
  PADBIAS 1.000000
  TGT_HEADING 66.560846
END
END_SHIPS

BEGIN_MeshLand
  VESSEL 0
  TERRAIN 1
  ROTATION 1
  FRICTION 1
  GRAVITY 1
END
 

sputnik

Addon Developer
Addon Developer
Donator
Joined
Apr 3, 2008
Messages
424
Reaction score
0
Points
31
Location
Palmdale
Website
www.worldof2001.com
Ah. Well, your problem is simpler than that: you cheated. It's easy to do, with CVEL, even by accident.

When you lofted the Transtage-Test using CVEL, you used the string:

PAYLOAD Transtage-test Velcro/ProtonSTG2 Transtage-test 0 0 17 11715 0.0 1.0

That number, 11715, is the total penalty mass CVEL adds to your launcher to carry the thing into orbit. (and the 1.0 on the end tells it to spawn fully fueled).

But when you attached a Transtage-test instead using SERIESBURN, you created an actual, current vessel, with an actual, current mass. Looking at ProtonSTG2.cfg, I see that 11715 is the empty mass, to which is added the fuel mass of 156113 kg. (And, when you set PRPLEVEL 0:1.000000 for the Transtage-Test, you're saying it's fully fueled).

Try setting PRPLEVEL 0:0.000000, and it should fly exactly as it did. Of course, your stage won't be full of fuel, but that's the price of switching from CVEL to SERIESBURN. CVEL will let you cheat in this way; it's up to you to make sure the payload masses match "reality". You can't do that with SERIESBURN.
 

MetalheadOC

New member
Joined
Oct 23, 2011
Messages
16
Reaction score
0
Points
0
Location
South Whidbey, WA
Ah. Well, your problem is simpler than that: you cheated. It's easy to do, with CVEL, even by accident.

When you lofted the Transtage-Test using CVEL, you used the string:

PAYLOAD Transtage-test Velcro/ProtonSTG2 Transtage-test 0 0 17 11715 0.0 1.0

That number, 11715, is the total penalty mass CVEL adds to your launcher to carry the thing into orbit. (and the 1.0 on the end tells it to spawn fully fueled).

But when you attached a Transtage-test instead using SERIESBURN, you created an actual, current vessel, with an actual, current mass. Looking at ProtonSTG2.cfg, I see that 11715 is the empty mass, to which is added the fuel mass of 156113 kg. (And, when you set PRPLEVEL 0:1.000000 for the Transtage-Test, you're saying it's fully fueled).

Try setting PRPLEVEL 0:0.000000, and it should fly exactly as it did. Of course, your stage won't be full of fuel, but that's the price of switching from CVEL to SERIESBURN. CVEL will let you cheat in this way; it's up to you to make sure the payload masses match "reality". You can't do that with SERIESBURN.

Ah so. I thot it was a little fishy that 2/3rds of a Proton could put a fully fueled 2nd stage in orbit. Like the man said, I think I'm gonna need a bigger rocket :rofl:

Which brings me to my next question :hail: Below is a short snippit of .scn I'm trying to figure out how to make a nice evenly spaced "ring" of strap-on boosters, but no matter where & what number I plug in, nothing makes sense. Either a booster "seems" to pop up in a completely random place, or the proportions are all wierd. Seems to fly ok, just doesn't look pretty. About all I've figured out is the height (z axis?) where they show up. Help me out here. Perhaps I'm missing that "long form" number you mentioned? I'm trying to really understand how the numbers work, not just "here fix this!" :)

Code:
BEGIN_SHIPS
Energia:Velcro/EnergiaCore
  STATUS Landed Earth
  BASE Cape Canaveral:6
  HEADING 0.00
  TGT_HEADING 095.0
  FUEL 1.000
  CONFIGURATION 0
  PAYLOAD Zvezda /ISSR/ISS_Zvezda /ISSR/Zvezda 0 6.5 0 118000.0 0 0.0 1.0
  PAYLOAD Zarya /ISSR/ISS_Zarya /ISSR/Zarya 0 -6.5 0 118000.0 0 0.0 1.0
END
Energia-M:Velcro/EnergiaMCore
  STATUS Landed Earth
  BASE Cape Canaveral:6
  HEADING 0.00
  TGT_HEADING 090.0
  FUEL 1.000
  CONFIGURATION 0
  SERIESBURN 0 Energia 0.0 0.0 -30  0.0 1.0 0.0 
END
Booster1:Velcro/EnergiaBooster
  STATUS Landed Earth
  BASE Cape Canaveral:6
  HEADING 0.00
  CONFIGURATION 0
  TGT_HEADING 90.0
  PRPLEVEL 0:1.0 1:1.0
  PRIMEBOOSTER 0
  CENTERTHRUST 1
  PARALLELBURN 1 Energia-M 3.89 0.93 1  0.97 0.23 0.0
  NAVFREQ 21 50
  XPDR 20
END
Booster2:Velcro/EnergiaBooster
  STATUS Landed Earth
  BASE Cape Canaveral:6
  HEADING 0.00
  CONFIGURATION 0
  TGT_HEADING 90.0
  PRPLEVEL 0:1.0 1:1.0
  PRIMEBOOSTER 0
  CENTERTHRUST 1
  PARALLELBURN 1 Energia-M -3.89 0.93 1  -0.97 0.23 0.0
  NAVFREQ 21 50
  XPDR 20
END
Booster3:Velcro/EnergiaBooster
  STATUS Landed Earth
  BASE Cape Canaveral:6
  HEADING 0.00
  CONFIGURATION 0
  TGT_HEADING 90.0
  PRPLEVEL 0:1.0 1:1.0
  PRIMEBOOSTER 0
  CENTERTHRUST 1
  PARALLELBURN 1 Energia-M 3.46 -2 1  0.87 -0.5 0.0
  NAVFREQ 21 50
  XPDR 20
END
Booster4:Velcro/EnergiaBooster
  STATUS Landed Earth
  BASE Cape Canaveral:6
  HEADING 0.00
  CONFIGURATION 0
  TGT_HEADING 90.0
  PRPLEVEL 0:1.0 1:1.0
  PRIMEBOOSTER 0
  CENTERTHRUST 1
  PARALLELBURN 1 Energia-M -3.46 -2 1  -0.87 -0.5 0.0
  NAVFREQ 21 50
  XPDR 20
END
Booster5:Velcro/EnergiaBooster
  STATUS Landed Earth
  BASE Cape Canaveral:7
  HEADING 0.00
  CONFIGURATION 0
  TGT_HEADING 90.0
  PRPLEVEL 0:1.0 1:1.0
  PRIMEBOOSTER 0
  CENTERTHRUST 1
  PARALLELBURN 1 Energia-M 4.0 2 1  0.87 -0.5 0.0
  NAVFREQ 21 50
  XPDR 20
END
Booster6:Velcro/EnergiaBooster
  STATUS Landed Earth
  BASE Cape Canaveral:7
  HEADING 0.00
  CONFIGURATION 0
  TGT_HEADING 90.0
  PRPLEVEL 0:1.0 1:1.0
  PRIMEBOOSTER 0
  CENTERTHRUST 1
  PARALLELBURN 1 Energia-M -4.0 -2 1  -0.87 -0.5 0.0
  NAVFREQ 21 50
  XPDR 20
END
Booster7:Velcro/EnergiaBooster
  STATUS Landed Earth
  BASE Cape Canaveral:7
  HEADING 0.00
  CONFIGURATION 0
  TGT_HEADING 90.0
  PRPLEVEL 0:1.0 1:1.0
  PRIMEBOOSTER 0
  CENTERTHRUST 1
  PARALLELBURN 1 Energia-M 4.0 2 1  0.87 -0.5 0.0
  NAVFREQ 21 50
  XPDR 20
END
Booster8:Velcro/EnergiaBooster
  STATUS Landed Earth
  BASE Cape Canaveral:7
  HEADING 0.00
  CONFIGURATION 0
  TGT_HEADING 90.0
  PRPLEVEL 0:1.0 1:1.0
  PRIMEBOOSTER 0
  CENTERTHRUST 1
  PARALLELBURN 1 Energia-M -4.0 -2 1  -0.87 -0.5 0.0
  NAVFREQ 21 50
  XPDR 20
END
END_SHIPS
 

sputnik

Addon Developer
Addon Developer
Donator
Joined
Apr 3, 2008
Messages
424
Reaction score
0
Points
31
Location
Palmdale
Website
www.worldof2001.com
The choice of Energia-M as lower core stage and Energia as upper stage is an odd one. They're nicely sized so it works the other way 'round!

Nah, you don't need to fool with the "long form". That changes whether they're pointed straight up (+Z), and you do want them to be; the only way you'd want something different is if you're sticking them to the side of a sloped cone, like the NovaSSTO.

As you've probably figured out, the location coordinates are the location ON THE CORE where you want to stick the booster's ATTACH POINTS. Thus, you can conveniently swap out to a different booster while keeping the same location. Usually.

The orientation is which way it points. Since it's pointed along the Z-axis, you're setting a point in the X-Y plane which determines which way that attachment is pointing toward. This point needs to be normalized, which just means that SQRT(X^2 + Y^2) = 1. Velcro Rockets does NOT do this for you, and non-normalized vectors give very very strange results.
So choosing 1 0 0 puts the thing along the X-axis; 0.877 0.5 0 is 30 degrees off from that; 0.5 0.877 0 is 60 degrees off, and so on. To put 8 boosters around, they'd be at 1 0 0, and .707 .707 0, and 0 1 0, and -.707 .707 0, and so on.
 

MetalheadOC

New member
Joined
Oct 23, 2011
Messages
16
Reaction score
0
Points
0
Location
South Whidbey, WA
The choice of Energia-M as lower core stage and Energia as upper stage is an odd one. They're nicely sized so it works the other way 'round!

Nah, you don't need to fool with the "long form". That changes whether they're pointed straight up (+Z), and you do want them to be; the only way you'd want something different is if you're sticking them to the side of a sloped cone, like the NovaSSTO.

As you've probably figured out, the location coordinates are the location ON THE CORE where you want to stick the booster's ATTACH POINTS. Thus, you can conveniently swap out to a different booster while keeping the same location. Usually.

The orientation is which way it points. Since it's pointed along the Z-axis, you're setting a point in the X-Y plane which determines which way that attachment is pointing toward. This point needs to be normalized, which just means that SQRT(X^2 + Y^2) = 1. Velcro Rockets does NOT do this for you, and non-normalized vectors give very very strange results.
So choosing 1 0 0 puts the thing along the X-axis; 0.877 0.5 0 is 30 degrees off from that; 0.5 0.877 0 is 60 degrees off, and so on. To put 8 boosters around, they'd be at 1 0 0, and .707 .707 0, and 0 1 0, and -.707 .707 0, and so on.

OK... making slow progress, bear with me here.. (no one told me there was algebra involved in this! I want my money back!)

So the first string of 3 digits is the position, and the second string of 3 in the same line is the rotation, yes? How does the rotation part of it work? I tried setting them all to zero's figuring I'll get the position right first, then worry about rotation... but the results were odd to say the least, and it doesn't look like the booster is rotating about it's own center axis... rotating around its attach point perhaps?
 
Top