[closed] beta2 of CTV-ATV

[no matter]

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

Beta 2 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
- .bat files moved from the orbiter's root folder to the modules folder.
- habtour bug fixed (but the mesh seems to need some modification, access ramp height is wrong)
- escape tower jettison speed reduced.
- eva door animation speed divided by 2
- separation between capsule and SSA service module can't occurs when docked
[EDIT due to the lack of memory in my head] -no more gap between CTV and Viking modules.

Happy testing!



Message modifié ( 18-09-2007 19:43 )

[no matter]

Reported from the last beta thread
Bug submitted by Fearless:
CTD on CTV-LEO4 docked with ISS scenario.

[EDIT]This one is now solved

Bug submitted by Pagir:
CTD when changing focus between CTV and Viking-lab on CTV-LEO carrying Viking-lab

To check with the new beta, I can't reproduce.
[EDIT]Apparently solved or related to pagir's installation



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

[Pagir]

Maybe you should remove the "DGIV docked to Irridium" Scenario (from the Mission CTV-VIking folder) from the
distribution

Pagir

[picto]

I was searching for it !!!
Sorry NoMatter ... I think I was very tired last night.



Message modifié ( 18-09-2007 19:31 )

[Pagir]

no matter a écrit:

Bug submitted by Pagir:
CTD when changing focus between CTV and Viking-lab on CTV-LEO carrying Viking-lab

To check with the new beta, I can't reproduce.

Still CTD... here's the last line of the orbiter log file:

Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
**** WARNING: Mesh not found: .\Meshes\.msh

Which mesh?

What did I install recently???

Pagir

[no matter]

Maybe you should remove the "DGIV docked to Irridium" Scenario (from the Mission CTV-VIking folder) from the
distribution

yup, fixed!

**** WARNING: Mesh not found: .\Meshes\.msh

This line can be "normal", it is related to spacecraft3 when a vessel doen't have a mesh assigned to the VC. Since
vikings are sp3 without VC...
But I really don't know why the scenario gives ctd in your install.

THIS IS WEIRD.



Message modifié ( 18-09-2007 19:40 )

[woo482]

Hello I Have only tested For 5 mins And I cant find Aney bugs

[picto]

CTV BUG

Short description:

Capsule disappears.


Severity

serious but not so hard to solve I think


Complete  description

The CTRL J bug when docked changed to this ...
The capsule simply disappears.






Reproduce bug

I can do it with every docked situation.
For example when Docked to ISS



Message modifié ( 18-09-2007 19:49 )

[no matter]

Pagir, use this one as Viking-lab.ini, and look at the log to see if the warning (.msh) happens. shouldn't fix the CTD
but...

Code: [Select]

[CONFIG]
MESHNAME=ARD-CTV\Viking-lab
SIZE=6
CAMERA=(0,0,0)
VISIBLE=0
EMPTY_MASS=3000
FUEL_MASS=0
CW_Z_POS=3          
CW_Z_NEG=1
CW_X=1
CW_Y=1      
COG=1.2
CROSS_SECTION=(9.16,9.08,5.54)    
PMI=(1.64,1.62,0.86)  

[CHILD_ATTACH_0]
name=Grap
POS=(0,1.15,1.8)
DIR=(0,1,0)
ROT=(0,0,1)
LOOSE=0
ID=Grap
RANGE=0.5  

; == Docking ports ==
[DOCK_0]
POS=(0.01,0.01,2.48)
DIR=(0,0,1)
ROT=(0,1,0)

; == VC ==
[VC]
MESHNAME=ARD-CTV\Viking-lab

; == sons ambience ==
[SOUND]
AIR_CONDITIONING=Sound\CTV-1\CTV-1aircond.wav
COCKPIT_AMBIENCE_1=Sound\CTV-1\CTV-1amb0.wav
COCKPIT_AMBIENCE_2=Sound\CTV-1\CTV-1amb1.wav
COCKPIT_AMBIENCE_3=Sound\CTV-1\CTV-1amb3.wav
COCKPIT_AMBIENCE_4=Sound\CTV-1\CTV-1amb4.wav
COCKPIT_AMBIENCE_5=Sound\CTV-1\CTV-1amb5.wav
COCKPIT_AMBIENCE_6=Sound\CTV-1\CTV-1amb6.wav
COCKPIT_AMBIENCE_7=Sound\CTV-1\CTV-1amb7.wav
COCKPIT_AMBIENCE_8=Sound\CTV-1\CTV-1amb8.wav
HOVER_THRUST=nosound
MAIN_THRUST=nosound
RCS_THRUST_ATTACK=nosound
RCS_THRUST_SUSTAIN=nosound

; == animations ==
[ANIM_SEQ_0]  ;panels&radiator
Key=K
DURATION=15
REPEAT=0

[ANIM_SEQ_1]  ;panels 45°
Key=G
DURATION=8
REPEAT=0

[ANIM_COMP_0]
SEQ=0
GROUPS=65
RANGE=(0,1)
TYPE=ROTATE
ROT_PNT=(-1.334,0.008,-0.096)
ROT_AXIS=(0,1,0)
Angle=80

[ANIM_COMP_1]
SEQ=0
GROUPS=66
RANGE=(0,1)
TYPE=ROTATE
ROT_PNT=(-1.409,0.008,-0.514)
ROT_AXIS=(0,1,0)
Angle=-170
PARENT=0

[ANIM_COMP_2]
SEQ=0
GROUPS=67
RANGE=(0,1)
TYPE=ROTATE
ROT_PNT=(-1.413,0.008,0.823)
ROT_AXIS=(0,1,0)
Angle=180
PARENT=1

[ANIM_COMP_3]
SEQ=0
GROUPS=88
RANGE=(0,1)
TYPE=ROTATE
ROT_PNT=(1.334,0.008,-0.096)
ROT_AXIS=(0,1,0)
Angle=-80

[ANIM_COMP_4]
SEQ=0
GROUPS=87
RANGE=(0,1)
TYPE=ROTATE
ROT_PNT=(1.409,0.008,-0.514)
ROT_AXIS=(0,1,0)
Angle=170
PARENT=3

[ANIM_COMP_5]
SEQ=0
GROUPS=86
RANGE=(0,1)
TYPE=ROTATE
ROT_PNT=(1.413,0.008,0.823)
ROT_AXIS=(0,1,0)
Angle=-180
PARENT=4

[ANIM_COMP_6]
SEQ=0
GROUPS=62
RANGE=(0.0,0.5)
TYPE=SCALE
SCALE0=(1,1,1)
SCALE=(15,1,1)
REF=(-0.308,0.025,-1.481)

[ANIM_COMP_7]
SEQ=1
GROUPS=65,66,67,86,87,88
RANGE=(0,1)
TYPE=ROTATE
ROT_PNT=(0,0.008,-0.096)
ROT_AXIS=(1,0,0)
Angle=-45

ahhhh, sorry for the 8)



Message modifié ( 18-09-2007 19:50 )

[no matter]

Short description:
Capsule disappears.

Ok,  think I have found the reason, sorry for the annoyance. It will be fixed in the next!

It is good to forbid the separation but don't forget to not delete the mesh

[Pagir]

Ok, the CTD is still there, but the warning is gone from the log...

I'll investigate which modifications I recently did to my orbiter folder...

Pagir

[no matter]

Then I will make the modif on all sp3 ini's as it is better to clear that warning.

[picto]

I can't reproduce Pagir's bug ...
But, I think it is a strange idea to test an addon on a fully installed Orbiter.
Because you will never find two strictly identical Orbiter installs  on two different computers.

BTW ...

Little Zbuffer bugs on habtour.
Just turn around and you'll see them . ( une petite dizaine d'endroits concernés)
Polygones are blinking when two of them are on the same space plane.
Nothing important but ... we are paid to look, so we look ...

[no matter]

Yes, I have seen that. I don't really know how to fix the blink effect.
Habtour needs some work, even the ramp access is wrong.
I am affraid to have included a wrong version of the file.
I must see that with Well.

[picto]

You just need to move a little the vertices of the poly superposed to the other one.

[no matter]

Ah, yes, they are on the same plan... the one over the other. Ok, I can fix that.

I will re-adjust the height of the access to the rocket too. I still need to contact Well, I am not sure to not have
overwritten the good file version with an old version.

[Momo]

bon, je post en Français...

tu ma collé un flag résolu sur la beta1 quand je dis: rotation incontrôlable lors de la séparation du ES de A5... prb sur
le file guidance!

sa continue toujours!!!! là je suis pas d'accord, je le dis et je te corrige:

avant correction:

545=pitch(-10,0,8 )
553=pitch(0,0,20)
556=PlaySound(Sound\CTV\Orbite1.wav)
574=engine(100,0,2)
576=engine(0,0,5)
577=PlaySound(Sound\CTV\Orbite2.wav)
577=engine(0,0,1)
579=engine(0,0,1)
582=engine(0,0,1)

= rotation et donc prb sur une remonté jugé ok par toi!


545=pitch(-10,0,8 )
553=pitch(0,0,30)
556=PlaySound(Sound\CTV\Orbite1.wav)
574=engine(100,0,2)
576=engine(0,0,5)
577=PlaySound(Sound\CTV\Orbite2.wav)
577=engine(0,0,1)
579=engine(0,0,1)
582=engine(0,0,1)

et la plus de prb par hasard!!!

moi je comprend pas... c'est un point facile a règle, mais pas corrigé...
ta beta2 ne serre a rien si tu corrige pas sa rapidement, car pour moi, une bonne mise en orbite sans prb et sans bug
ben sa vaut même pas une beta...

je suis désolé No-Matter, je suis juste apeurer que tu laisse passé sa, car ton taf mérite mieux qu'un bug facilement
rectifiable, et sa je le pense vraiment!
corrige stp... je t'en supplie même

[DanSteph]

Personne n'est infaillible, un problème marqué solved peut etre toujours la.
Les testeurs sont justement la pour informer l'auteur de ce genre de problèmes
pas besoins d'être "apeuré" Momo, c'est le taff  

Quand à la "simplicité d'un probleme" oublie pas que no matter en à 20 à la
douzaines en même temps, pas si évident quand on est dedans.

Sorry for french, Momo just recall a bug from beta1 that is still not solved.

Dan



Message modifié ( 18-09-2007 21:17 )

[Momo]

DanSteph a écrit:
Personne n'est infaillible, un problème marqué solved peut etre toujours la.
La beta c'est justement pour informer l'auteur de ce genre de problèmes pas
besoins d'être "apeuré" Momo, c'est le taff  
Dan

vi, ta raison Dan, mais je voulais marquer par se post pour qu'il ne tombe pas dans l'oublie...
c'est le taff du beta testeur non???
pour moi c'est une chose simple a corrigé, mais faut que tous le monde le sache

voila, j'aime le CTV, donc je corrige le prb dans la mesure du possible...
j'en ferais de même pour le fuel en postant le code ici si le grand chef ne souhaite pas resoudre le prb...

un addon de cette classe doit etre parfait, car il est parfait, et sa c'est le top! car le CTV/ATV et la meilleure réalisation
de c'est 50 derniere année pour Orbiter!

[no matter]

I did the launches (I mean ATV then ATV2, then CTV-lunar (x2) then LEO4 then LEO6, so far it cost 2h to watch that) at home, after having modified some lines (removed all state under 5s). All of them gives a stable orbit at home, if they don't fail on my computer, how can I know there is still some problem on the text, by guessing??

Be sure I hate multistage guidance, be sure to see it fixed if not removed for the next beta.
it is not enough reliable for me. There is alway a computer where it fails. I am fed up with that!

545=pitch(-10,0,8 )
553=pitch(0,0,20)
556=PlaySound(Sound\CTV\Orbite1.wav)
574=engine(100,0,2)
576=engine(0,0,5)
577=PlaySound(Sound\CTV\Orbite2.wav)
577=engine(0,0,1)
579=engine(0,0,1)
582=engine(0,0,1)

= rotation et donc prb sur une remonté jugé ok par toi!


545=pitch(-10,0,8 )
553=pitch(0,0,30)
556=PlaySound(Sound\CTV\Orbite1.wav)
574=engine(100,0,2)
576=engine(0,0,5)
577=PlaySound(Sound\CTV\Orbite2.wav)
577=engine(0,0,1)
579=engine(0,0,1)
582=engine(0,0,1)

You know, 5 s on the bold lines are working at home but fails on many computers, 10 is not enough for certain so i
put 20, and now it needs 30, I think it is not reliable at all. How can I guess that?

There is no other pitch command after this one and it should be stable since it is a (0,0,xxx)
This is unpredictable. I am really fed up by multistage guidance.
May be on manual will it become error free!



Message modifié ( 18-09-2007 21:34 )

[DanSteph]

Momo a écrit:
vi, ta raison Dan, mais je voulais marquer par se post pour qu'il ne tombe pas dans l'oublie...
c'est le taff du beta testeur non???

Vi mais il vaut mieux y aller avec des pincette et diplomatie, de l'autre coté t'a un gars
chargé à bloc de boulot et sur les nerfs. C'est la beta quoi... rush hours, les grand magasins
pendant les soldes...

Sorry again for french, still about not solved bug...

Dan



Message modifié ( 18-09-2007 21:30 )

[Momo]

DanSteph a écrit:

Momo a écrit:
vi, ta raison Dan, mais je voulais marquer par se post pour qu'il ne tombe pas dans l'oublie...
c'est le taff du beta testeur non???

Vi mais il vaut mieux y aller avec des pincette et diplomatie, de l'autre coté t'a un gars
chargé à bloc de boulot et sur les nerfs. C'est la beta quoi... rush hours, les grand magasins
pendant les soldes...

Sorry again for french, still about not solved bug...

Dan

milles excuse No-Matter, dsl...
sinon j'ai rien pigé a ta reponse... mon english a foutu le camps...

[DanSteph]

no matter a écrit:
You know, 5 s on the bold lines are working at home but fails on many computers, 10 is not enough for certain so i
put 20, and now it need 30, I think it is not reliable at all. How can I guess that, How????

maybe multistage guidance is FSP sensitive, mean less precise or prone to error
with low or different FsP ?

Dan

[no matter]

I have made a thousand change on that autopilots since the first version, only by guessing the fix as there is no spin happening at home.

I think it is FPS dependant, I can't see no other reason and it is really annoying as it means that everytime you have
to check there is no hole even if the last command is a stable command and should leave the rcs off after its execution
(I mean a stable pitch like (20,20,15) 20° to 20° in 15s) It needs a line saying to the rocket to not move, create a kind
of killrot.
Very annoying is the fact that I don't need that on my pc.

No problem Momo, it is the guidance that makes me mad, not you! (ce n'est pas toi mais l'autopilote multistage qui me
rend fou!)



Message modifié ( 18-09-2007 21:44 )

[Momo]

no matter a écrit:
 (ce n'est pas toi mais l'autopilote multistage qui me rend fou!)

un prb? des ennuies? Momo est là

si tu veux je les corrige tous pour toi! je le ferais avec plaisir!
comme sa ta le temps pour les autre corrections

mais c'est toi le boss, et tu l'es plus que bien



Message modifié ( 19-09-2007 14:17 )