[Closed] beta3 of CTV-ATV

[no matter]

_______________________________________________________________________
Only for members of CTV beta team list - Do not post if you're not members - Thanks
_______________________________________________________________________

Beta 3 of CTV v2.1

Download:
You must have received a PM with the link to the beta archive, please do NOT publish this link.

BUG REPORT:
Please use the text form in the link below to report a bug: It's important !
http://perso.orange.fr/nomat/public/CTV_beta_form.txt (CTV and anything else but ATV)
http://perso.orange.fr/nomat/public/ATV_beta_form.txt (dedicated to ATV)

GETTING STARTED:
Unrar archive in Orbiter keeping directory structure.
You must have Orbiter 2006 P1

CHANGES:
- autopilots spins fixed, autopilots modified by Momo
- target name fixed on Map MFD in launches to ISS scenarios
- hatour mesh modified
- [bug fixed], port hatch state displaying eva hatch state
- airlocks gestion slightly enhanced (port1 airlock remains closed when dock is not engaged)
- [new feature]separation lock (status is displayed on the HUD) forbid the capsule separation if enabled
- documentation CTV-Doc-eng updated, .chm help updated.

Meshes problems, like the capsule's windows and EVA door, will be fixed soon, I have been disturbed this afternoon
by a problem with acrobat and I did not have time to finish that.

Happy testing!



Message modifié ( 20-09-2007 20:38 )

[DoyleChris]

I haven't run into any serious problems with the beta.

[siriusfett]

Bon je la fais en anglais, si tu ne comprend pas, j'ai le double en français

ATV2 BUG

description:

Not thorough automatic by using IMFD 4.6

Severity:

serious

complete description:

After a projection towards the moon with the last stage, impossible to make corrections with put parcour with the ATV2, only
the RCS function. The thorough one is only possible manually.

Reproduce bug:

No change after having reloaded the scn...



Message modifié ( 21-09-2007 00:01 )

[picto]

Outch ...
Je suis tombé sur un méchant bug.

Sur un scenario docké à ISS, je me détache, puis retrograde pour retour sur Terre.
Mais j'avais envie de rigoler un peu donc je me met sur une trajectoire plutôt plongeante
Puis prograde et j'essaye de dédocker ( la sécurité fonctionne) mais trop.
Impossible de dédocker. Donc est ce une feature parce que ma trajectoire était débile ou un bug ?
Je n'en sais rien.

Par contre plus grave, au moment ou ça commençait à chauffer ( toujours docké donc)
tous les vaisseaux ont disparu y compris de la fenêtre F3. J'essaye de reproduire le truc.

[no matter]

Which model picto, LEO4 LEO6 or LUNAR (stream or tex?)

I am testing right now!

[no matter]

Siriusfett, i put a resolved color on your report. This is a thing I have to add on the documentation, glad that you
reported it!

IMFD 4.6 &4.7 are not compatible with any spacecraft that use more than 2 thrusters by ATTITUDE_GROUP. So
ATV and CTV can't use IMFD 4.6 or 4.7.

It works with the new one, IMFD 5.0 as jarmonik has solved this problem in August. It works with IMFD 4.2.1 too.

[picto]

It was LEO4_docked_ISS
But I can't reproduce it ...
I 'am trying again ... BTW ... it's fun to test !  

[siriusfett]

ok I will carry out a test

[no matter]

A lil' translation of the previous post in french:
Picto reported a bug about being unable to separate and had deorbited hanged to tha service module, report the
vessel was deleted too while the rentry!

Picto for the disparition, the SSA burns and disappear when reentering the atmosphere. If not jettisoned, the capsule
will disappear too.  This part is normal, I am trying to reproduce the unability to separate.

[no matter]

It was LEO4_docked_ISS
But I can't reproduce it ...

Can't reproduce here too. I am going to make 2 or 3 more tests,
Do you remember at which altitude did you try to separate?



Message modifié ( 21-09-2007 00:28 )

[picto]

No it is my fault, ...
May be I thought I was separating and I missed the good keybord entry.
All is working fine. Sorry for the stress.

If I separate in retrograde just before heat increase I can even see
the "roll" of the capsule because of drag....
Reentry procedure made this way is really a chaos but it's fun.



Message modifié ( 21-09-2007 00:32 )

[no matter]

I tried a really hard reentry, lift was set to 1.0, separation at 130 km without problem.
The Gmeter hit 20G and for the first time I saw the display becoming orange then red.

I should add a line or too in the code to kill the crew if the G-meter exceed 10G.

[EDIT:]

No it is my fault, ...
May be I thought I was separating and I missed the good keybord entry.
All is working fine. Sorry for the stress.

If I separate in retrograde just before heat increase I can even see
the "roll" of the capsule because of drag....
Reentry procedure made this way is really a chaos but it's fun.

Ok, I am breathing again



Message modifié ( 21-09-2007 00:39 )

[picto]

Gmeter hit 20G

That's an idea ... to try the best score.

It would be nice for crew Killing ...
And why not a little destruction of the capsule.
I think this sort of features is really cool as it makes the mission more interesting to do.
And it's really simple to code ... A big wow effect for not much efforts of coding.

[no matter]

I get a nice value to delete the vessel, the same that "light" the shield. But I don't have activated it yet.
But with the G, I can kill the crew or they can faint even if the capsule is not deleted.

The only value that kill the crew actually is when the O2 tank is empty. I only use DeletePropellantRessource or
something like that and display "a crew is dead" message. It is a feature at its early stage

[picto]

It is a feature at its early stage ...

I can believe that.
It will be really cool and increase the interest for your addon.

En attendant ! Battu !
It climbed to 25 but no time to take the screenshot

[no matter]

Nice HeatQ too

Ok, I will develop the crew killing



Message modifié ( 21-09-2007 01:09 )

[no matter]

It climbed to 25 but no time to take the screenshot

Ahh, no more than 23 here, you win

[Pagir]

I should add a line or too in the code to kill the crew if the G-meter exceed 10G.

Humans can sustain 10G for a while... even 40G for a brief moment...
http://www.abc.net.au/science/k2/moments/gmis9906.htm

I remember we had this discussion in past. During FsPassengers betatesting or DGIV betatesting

Anyway, it could be cool if the astronauts could survive, say 30 secondes at 10G... You'll have to act fast to correct
the situation!!!

Pagir

[Fearless]

CTV BUG

Short description:

Ariane5/CTV uncontrollable spin CTV-LEO4 to ISS Scenario

Severity

serious enough to get dizzy


Complete  description

After the CTV has seperated from the final stage booster, she goes into uncontrollable spin.

Reproduce bug

will retest

Miscallenous

[no matter]

I should check the archive, it has been fixed by Momo but may be there is a wrong file in the archive?

The file CTV-LEO4-ISS.txt (in Config\W-Ariane5) should contain the following txt:

-79=PlaySound(Sound\CTV\Radio2.wav)
-21=PlaySound(Sound\CTV\Lancement.wav)
0=engine(0,100,7)
10=roll(3,90,36.5,80,1)
30=pitch(83,30,60)
90=pitch(30,20,30)
120=pitch(20,20,20)
138=PlaySound(Sound\CTV\Sep1.wav)
140=pitch(20,20,20)
160=pitch(20,20,40)
177=fairing()
200=pitch(20,15,30)
230=pitch(15,15,110)
340=pitch(15,25,5)
345=pitch(25,25,130)
475=pitch(25,0,15)
490=pitch(0,0,40)
530=pitch(0,-5,10)
540=pitch(-5,-5,5)
545=pitch(-5,0,30)
556=PlaySound(Sound\CTV\Orbite1.wav)
565=pitch(0,0,10)
565=engine(0,0,5)
570=engine(0,0,15)
580=jettison()

I am going to try the launch.



Message modifié ( 21-09-2007 02:04 )

[no matter]

[EDIT]: sorry, the solution was not good



Message modifié ( 21-09-2007 02:32 )

[no matter]

I have checked the archive, the file is the right one.
I can't reproduce too.

[EDIT]:
I don't know what can cause that spin, the guidance is off after main stage jettison, so it can't cause a spin after the separation of the last stage and the CTV.

Can you give me the FPS you get when the separation occurs ("F" key). Low FPS can cause this. Internal or external view?



Message modifié ( 21-09-2007 02:38 )

[Fearless]

no matter wrote:
I have checked the archive, the file is the right one.
I can't reproduce too.

[EDIT]:
I don't know what can cause that spin, the guidance is off after main stage jettison, so it can't cause a spin after the
separation of the last stage and the CTV.

Can you give me the FPS you get when the separation occurs ("F" key). Low FPS can cause this. Internal
or external view?

FPS was 56 and I was in cockpit view.  I will retest though when I get home from work.



Post Edited ( 09-21-07 10:41 )

[siriusfett]

Suggestion Scn Launch Ariane5-ES-ATV2 to the moon:

For good an alignment with the moon:
Date MJD 54721.6141

Modification targets on MFD MAP:

BEGIN_MFD Right
  Map TYPE
  Ref. Earth
  BTARGET Kourou_csg
  OTARGET MOON
  ZOOM
  TRACK ONE
END_MFD

modification GUIDANCE_FILE:

10=roll(3,90,119,80,1)

I obtained a rinc of 0.65, somebody can it make a test with these values, for confirmed?



Message modifié ( 21-09-2007 11:12 )

[Fearless]

Fearless wrote:

no matter wrote:
I have checked the archive, the file is the right one.
I can't reproduce too.

[EDIT]:
I don't know what can cause that spin, the guidance is off after main stage jettison, so it can't cause a spin after the
separation of the last stage and the CTV.

Can you give me the FPS you get when the separation occurs ("F" key). Low FPS can cause this.
Internal
or external view?

FPS was 56 and I was in cockpit view.  I will re-test though when I get home from work.

UPDATE:

1.  Having had a look more closely at it, The spin commences just before LEO4 seperates from the main booster.  It
happens both in cockpit view and in external view.

2. At T+584.7 the levelling off drops from 0.00 to between -35.64 and -39.74 and commences the spin just before the
seperation.

3. The CTV-LEO4-ISS.txt file contains the correct data as shown in your post.



Post Edited ( 09-21-07 10:52 )