Does that happen in 2010P1?
Project Multistage2015 - Development Thread
- Thread starter fred18
- Start date
Does that happen in 2010P1?
boogabooga
Bug Crusher
- Joined
- Apr 16, 2011
- Messages
- 2,999
- Reaction score
- 1
- Points
- 0
I've never had a problem with the engine not throttling up all the way. However, since I posted that, I have seen this:
http://www.ulalaunch.com/uploads/docs/Mission_Booklets/AV/av_oa4_mob.pdf
Actually, the throttle starts at -2.7 but should take 3.8 seconds, not 2.7. Perhaps that would be a more realistic fix?
BTW, did you like the way I set up the growing particle streams? I spent a lot of time on those to try to replicate what I saw in photos. I noticed that you made some very specific changes and was wondering what you had in mind when creating them yourself?
No, it's in r.43 Orbiter BETA.
that is simply because the launch pad is not leveled. When I'll release the beta version officially I'll change the ramp of the sls to the shuttle one. Try it yourself if you want. I think that Pad's not leveled can be an issue of orbiter beta itself, but I haven't had the chance to dig about this yet, since I'm too busy with ms2015 finishing
boogabooga
Bug Crusher
- Joined
- Apr 16, 2011
- Messages
- 2,999
- Reaction score
- 1
- Points
- 0
Go to the particle stream in the ini file and change "diffusive" to "emissive".
I'm getting crashes with the PTK NP addon by scorpius. I am starting the PTK NP with DGO launch scenario and the simulator crashes without warning. I have attached the log file but I don't see a problem. All the other versions of the Angara rocket load without problems I was thinking that it's maybe due to the fact that there is only a single stage defined but I'm just speculating.
[ame="http://www.orbithangar.com/searchid.php?ID=6294"]PTK NP Spacecraft[/ame]
[ame="http://www.orbithangar.com/searchid.php?ID=6294"]PTK NP Spacecraft[/ame]
HTML:
**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.01175e-007 sec
Found 1 joystick(s)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module EnergyConfigurator.dll [Build ******, API 060425]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module D3D9Client.dll ........ [Build 150111, API 100830]
Module BaseSyncMFD.dll ....... [Build 100616, API 100603]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiRegisterMFDMode
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module BurnTimeMFD.dll ....... [Build 140205, API 100830]
Module DVToolsMFD.dll ........ [Build 120331, API 100830]
Module GS2.dll ............... [Build 131201, API 100830]
Module IEATMFD.dll ........... [Build ******, API 060425]
Module InterMFD55.dll ........ [Build 100826, API 100704]
Module Multistage2015_MFD.dll [Build 151027, API 100830]
Module PursuitMFD.dll ........ [Build 121104, API 100830]
Module RendezvousMFD.dll ..... [Build ******, API 050206]
Module LaunchMFD.dll ......... [Build 150104, API 100830]
Module TransX2.dll ........... [Build 150926, API 100830]
Module OrbiterSound.dll ...... [Build 121120, API 100830]
**** Creating simulation session
D3D9Client: [DirectX 9 Initialized]
D3D9Client: Sytem has XNA math support
D3D9Client: [3DDevice Initialized]
D3D9Client: [Loading Stars]
D3D9Client: [Loading Constellations]
D3D9Client: [D3D9Client Initialized]
Joystick throttle: SLIDER 0
Joystick throttle control detected
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 EarthAtmNRLMSISE00.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]
MarsCristiapiAtm: correctly loaded and initialized.
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 Spacecraft3.dll ....... [Build ******, API 060425]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: VESSEL::SetBankMomentScale
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module multistage2.dll ....... [Build 151027, API 100830]
Load State Started
Angara 5P: Guidance File present: Config\AngaraLV\angara5p_leo.txt
Angara 5P: Config File: C:\Games\Orbiter\Config\AngaraLV\Angara5P.ini
Angara 5P: Number of stages in the ini file: 1
Angara 5P: Number of boosters group in the ini file: 2
Angara 5P: Number of Payloads in the ini file: 1
Angara 5P: This Rocket Has Fairing
Angara 5P: Texture n.1 Loaded Exhaust2
Angara 5P: Texture n.2 Loaded Contrail3
Angara 5P: WARINING PARTICLE TEXTURE NOT DEFINED, USED CONTRAIL3
Angara 5P: booster n. 1 Tank Added: 1.000 kg
Angara 5P: booster n. 2 Tank Added: 530000.000 kg
Angara 5P: Stage n. 1 Tank Added: 132500.000 kg
Angara 5P: Stage n. 1 Engines Exhaust Added--> number of engines: 1 , diameter: 1.000, position x: 0.000 y: 0.000 z: -15.700
Angara 5P: Booster Engines Exhaust Added--> Booster Group: 1 number of engines: 0 , diameter: 0.010, position x: 0.000 y: 0.000 z: 20.700
Angara 5P: Booster Engines Exhaust Added--> Booster Group: 2 number of engines: 1 , diameter: 1.000, position x: -2.086 y: 2.086 z: -15.700
Angara 5P: Booster Engines Exhaust Added--> Booster Group: 2 number of engines: 1 , diameter: 1.000, position x: -2.086 y: -2.086 z: -15.700
Angara 5P: Booster Engines Exhaust Added--> Booster Group: 2 number of engines: 1 , diameter: 1.000, position x: 2.086 y: -2.086 z: -15.700
Angara 5P: Booster Engines Exhaust Added--> Booster Group: 2 number of engines: 1 , diameter: 1.000, position x: 2.086 y: 2.086 z: -15.700
Angara 5P: Stage n.1 Mesh Preloaded: AngaraLV\manned\angara1p
Angara 5P: Stage n.1 Mesh Added Mesh: AngaraLV\manned\angara1p @ x:0.000 y:0.000 z:0.000
Angara 5P Payload Mesh Preloaded 1
Angara 5P: Payload n.1 Mesh Added: PTK_NP\ptknpos_p @ x:0.000 y:0.000 z:22.150
Angara 5P: Booster Mesh Preloaded: AngaraLV\manned\sas_1
Angara 5P: Booster Mesh Added Mesh: AngaraLV\manned\sas_1 @ x:0.000 y:0.000 z:25.700
Angara 5P: Booster Mesh Preloaded: AngaraLV\angara5boost_1
Angara 5P: Booster Mesh Added Mesh: AngaraLV\angara5boost_1 @ x:0.000 y:0.000 z:0.000
Angara 5P: Booster Mesh Preloaded: AngaraLV\angara5boost_2
Angara 5P: Booster Mesh Added Mesh: AngaraLV\angara5boost_2 @ x:-0.000 y:0.000 z:0.000
Angara 5P: Booster Mesh Preloaded: AngaraLV\angara5boost_3
Angara 5P: Booster Mesh Added Mesh: AngaraLV\angara5boost_3 @ x:0.000 y:-0.000 z:0.000
Angara 5P: Booster Mesh Preloaded: AngaraLV\angara5boost_4
Angara 5P: Booster Mesh Added Mesh: AngaraLV\angara5boost_4 @ x:0.000 y:0.000 z:0.000
Angara 5P: Fairing Mesh Preloaded: AngaraLV\manned\fairingpl_1
Angara 5P: Fairing Mesh Added Mesh: AngaraLV\manned\fairingpl_1 @ x:0.000 y:0.000 z:13.500
Angara 5P: Fairing Mesh Preloaded: AngaraLV\manned\fairingpl_2
Angara 5P: Fairing Mesh Added Mesh: AngaraLV\manned\fairingpl_2 @ x:-0.000 y:0.000 z:13.500
Load State Terminated
Post Creation Started
status:0 hdg:0.000 lng:0.000 lat:0.000
Angara 5P: Gravity Turn Initial Pitch by user: 89.500 Calculated:83.350
RESET PEG
Angara 5P: Planet Reference Pressure = 101325.0 Pa Atmosphere Altitude Limit:2500.0 km
Post Creation Terminated
Finished initialising status
Finished initialising camera
Finished initialising panelsAre you using this small patch? if no pls try it, it can contain the solution for that, if you are already using that or it doesn't fix the issue I'll investigate this.
http://www.orbiter-forum.com/showthread.php?p=518995&postcount=28
The improvement of the patch will be included in the definitive release that will come as soon as the developer mode will be finished.
Maybe Marg is referring to local light sources. If that is the case, yep for the time being light points are not yet implemented. I did them for the jarvis dll but the code was bad and I wasn't happy about that. So I'll restudy light sources documentation but I don't know if I will be able to make a "general" case of the parameters.
Yeah that works, sorry I didn't go through all the comments, didn't realise there was an update already :tiphat:
BrianJ
Addon Developer
Hi,
thanks for digging up the launch info .pdf and posting those .ini and guidance.txt's. The 3.8s throttle-up might help a bit, I think it's an interpolation/framerate issue, like fred18 has noted. I tweaked the particle streams from your .ini just for personal taste - but I'm not seeing any kind of expanding plume (just the usual exhaust plume plus MaxQ contrail) - can you post a screenie of what you get with your growing particle streams? Thanks!
Brian
two quick notes:
1) please use the small patch in the link above when you want to tweak the effect because I made an error in the official version (sorry about that) and I corrected it in the patch. It will be of course corrected also in the official version but in the meantime if you have to setup that kind of effect use the patch since it will be final that way.
2) remember to include also the scenario line that activates the effect, otherwise they will not be seen. This is intended to save low end computers from unwanted performance issues.
BrianJ
Addon Developer
Many thanks, Fred.
1) Already got it.
2) I am missing the scenario line! I'll give it a try.....
Cheers,
Brian
BrianJ
Addon Developer
OK, that kind of works! Using boogabooga's .ini I'm getting a LARGE exhaust plume straight after liftoff...
Is that as intended? Maybe the plume expansion should happen gradually with altitude?
I tried changing the numbers for GROWFACTOR_RATE and GROWFACTOR_SIZE, but I couldn't really figure out if it was having much effect.
EDIT:--------
AAAArgh!! Ignore this post! I failed to install the right Multistage2015 .dll
Expanding exhaust plume now works very well. Very interesting effect! Thanks!
Is that as intended? Maybe the plume expansion should happen gradually with altitude?
I tried changing the numbers for GROWFACTOR_RATE and GROWFACTOR_SIZE, but I couldn't really figure out if it was having much effect.
EDIT:--------
AAAArgh!! Ignore this post! I failed to install the right Multistage2015 .dll
Expanding exhaust plume now works very well. Very interesting effect! Thanks!
Last edited:
boogabooga
Bug Crusher
- Joined
- Apr 16, 2011
- Messages
- 2,999
- Reaction score
- 1
- Points
- 0
Yeah, I use the latest patch for multistage2015. The flame expands with altitude. I also intentionally made the flame longer and more slender to start with. The goal was to emulate what I saw in these photos:
http://www.orbiter-forum.com/showthread.php?p=518833&postcount=326
I spent quite a bit of time on those particle effects and am very interested in feedback. What sort of effect were you trying to capture with your changes?
I am interested in creating a repository of standard particle effects for different engine types (kero/LOX, hypergolic, etc.). This might helpful for launch vehicle developers.
http://www.orbiter-forum.com/showthread.php?p=518833&postcount=326
I spent quite a bit of time on those particle effects and am very interested in feedback. What sort of effect were you trying to capture with your changes?
I am interested in creating a repository of standard particle effects for different engine types (kero/LOX, hypergolic, etc.). This might helpful for launch vehicle developers.
BrianJ
Addon Developer
Well, I'm pretty much back to your original .ini particle stream settings. I was just going for a slightly larger, chunkier exhaust plume at liftoff. Only real change I'm thinking of keeping is using an EMISSIVE contrail for the Mach1/MaxQ contrail - so it's pure white. Also, I think a higher particle generation rate, velocity and atmos.slowdown rate, with a shorter particle lifetime, gives a more "energetic" feel to the contrail, which I like.
I like the "expanding plume" concept, but I'm not sure just changing the particle stream size and growthrate will be enough to make it look realistic(for AtlasV anyway). With your current .ini for AtlasV, by the end of the burn the plume looks about the right size, but I think it kind of needs a DIFFUSE element(exhaust smoke) and maybe more transparent overall. I might try a few particle stream experiments later, will let you know if I come up with anything interesting.
Cheers,
Brian
I think that relevant to this point a real game changer would be an ad hoc particle texture. I am not good at textures, and definitely bad about particle textures (I did a couple of tests with poor results) but I think that for example a texture with a bit of transparency in the middle can be used to create something like this:
or like this:
or like this:
BrianJ
Addon Developer
Yes, maybe a custom texture would be the way to go....
In the meantime, I did some experiments with contrails and this is about the best I've come up with so far. Here's the .ini.....
Some cropped screenies from launch, MaxQ, 90s, 130s...
Note: the 1st particle stream(yellowish) does not "expand" and fades out with atmos.pressure soon after MaxQ. The 2nd particle stream(white) is sort of "hidden" by the 1st particle stream until it expands enough, becoming visible just before MaxQ. The particle streams are not "packed_to_engine", so one stream per engine I assume (seems OK for framerate on my PC).
Fun with particle streams Don't know if this is any improvement, just an idea.
Cheers,
Brian
In the meantime, I did some experiments with contrails and this is about the best I've come up with so far. Here's the .ini.....
Code:
[MISC]
cog=8
FOCUS=1
GNC_DEBUG=1
[TEXTURE_LIST]
TEX_1=Exhaust2
[PARTICLESTREAM_1]
NAME=AV7contrail2
SRCSIZE=4.5
SRCRATE=100
V0=125.0
SRCSPREAD=0.02
LIFETIME=0.25
GROWTHRATE=-3
ATMSLOWDOWN=1
LTYPE=EMISSIVE
LEVELMAP=LVL_PSQRT
LMIN=0
LMAX=1
ATMSMAP=ATM_PLIN
AMIN=0.1
AMAX=1
TEX=contrail3
[PARTICLESTREAM_2]
NAME=AV7contrail
SRCSIZE=4.0
SRCRATE=25
V0=100.0
SRCSPREAD=0.00001
LIFETIME=0.15
GROWTHRATE=-3
ATMSLOWDOWN=0.2
LTYPE=EMISSIVE
LEVELMAP=LVL_PLIN
LMIN=0
LMAX=10
ATMSMAP=ATM_PLOG
AMIN=0.0001
AMAX=1
TEX=contrail1
GROWFACTOR_RATE=30
GROWFACTOR_SIZE=5
[PARTICLESTREAM_3]
NAME=mach
SRCSIZE=4.5
SRCRATE=50
V0=1
SRCSPREAD=0.1
LIFETIME=0.125
GROWTHRATE=0
ATMSLOWDOWN=4
LTYPE=EMISSIVE
LEVELMAP=LVL_PSQRT
LMIN=0
LMAX=2
ATMSMAP=ATM_PLOG
AMIN=0.7e-7
AMAX=1
TEX= contrail1
[FX_MACH]
pstream=mach
mach_min=0.8
mach_max=1.1
off_1=(0,0,30)
dir=(0,0,-1)
[STAGE_1]
Height=32.46
Diameter=3.81
EmptyMass=22182.7
FuelMass=284089.0
Thrust=3990000.0
BurnTime=238
off=(0,0,0)
speed=(0.,0.,-3.75)
ENG_1=(0,0.857,-20.5)
ENG_2=(0,-0.857,-20.5)
ENG_DIAMETER=2
MeshName="LRO/av_core"
ENG_TEX=Exhaust2
ENG_PSTREAM1=AV7contrail
ENG_PSTREAM2=AV7contrail2
PITCHTHRUST=362000
YAWTHRUST=362000
ROLLTHRUST=36200
ROT_SPEED=0
reignitable=0
[STAGE_2]
Height=12.68
Diameter=3.05
EmptyMass=2243
FuelMass=20830
Thrust=99200
BurnTime=927.7
off=(0,0,22.85)
MeshName="LRO/av_centaur"
ENG_TEX=Exhaust2
ENG_1=(0,0,-7)
ENG_DIAMETER=1.53
IGNITE_DELAY=10
PITCHTHRUST=17291.7
YAWTHRUST=17291.7
ROLLTHRUST=17291.7
Battery=3.5
[FAIRING]
N=2
MeshName="AV061\av_fair"
Diameter=4.2
Height=12
angle=180
off=(0,0.0,31.85)
EMPTYMASS=2127
[PAYLOAD_1]
MeshName="Orbital\Cygnus"
MASS=5649
off=(0,0,31.5)
SPEED=(0,0,1)
ROT_SPEED=(0,0,0)
Module=Vessels\AV061\Cygnus
name=Cygnus
Diameter=3
Height=5
Live=1Note: the 1st particle stream(yellowish) does not "expand" and fades out with atmos.pressure soon after MaxQ. The 2nd particle stream(white) is sort of "hidden" by the 1st particle stream until it expands enough, becoming visible just before MaxQ. The particle streams are not "packed_to_engine", so one stream per engine I assume (seems OK for framerate on my PC).
Fun with particle streams
Don't know if this is any improvement, just an idea.Cheers,
Brian
I also wanted to add that anomalous start, when rocket heavily leans upon liftoff (but autopilot corrects it), happens when there is
STATUS Landed Earth
POS -80.5771995 28.5619578
entry in scenario. It does not happen, if there is default launch pad:
STATUS Landed Earth
BASE Cape Canaveral:1
I changed positions, because I moved SLS to LC40.
P.S. Falcon Heavy by BrianJ does not show any anomalies.
STATUS Landed Earth
POS -80.5771995 28.5619578
entry in scenario. It does not happen, if there is default launch pad:
STATUS Landed Earth
BASE Cape Canaveral:1
I changed positions, because I moved SLS to LC40.
P.S. Falcon Heavy by BrianJ does not show any anomalies.
Thanks.
Orbiter Beta version of Multistage2015 has not been released yet, are you using the pre-release that I posted here sometimes ago? I posted this issue also to Martin. The issue happens when ground is not levelled. There is something relevant to the new touchdown points that still doesn't work perfectly in my opinion. In the version that I'm working on this is mostly solved. But anyway there is the need of a levelled ground.
Cizurator
Whooooosh!
I tried to reproduce the high-alt high-speed effects as shown in those pictures above. I used two simultaneous growing particle streams. One represents the burnt smoke shortly after liftoff, but gradually transforms into a large contrail. The second starts quite conspiciously, but grows into that orange semi-transparent "ball" of hot expanding exhaust gas. Using my own custom textures, this is the result with Firebird I:
Similar threads
