[Closed] BETA 6 of DeltaGliderIV

[DanSteph]

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



BETA 6 of DeltaGliderIV

For a list of DGIV new features and improvment see at least 1st beta thread here: (closed thread)
http://orbiter.dansteph.com/forum/index.php?topic=11922.msg183132#msg183132

You may also see what was changed/added since 1st beta while reading 2nd beta thread here: (closed)
http://orbiter.dansteph.com/forum/index.php?topic=11925.msg183236#msg183236 and 3rd beta thread here: (closed)
http://orbiter.dansteph.com/forum/index.php?topic=11929.msg183340#msg183340 and 4rd beta thread here: (closed)
http://orbiter.dansteph.com/forum/index.php?topic=11938.msg183499#msg183499 and 5rd beta thread here: (closed)
http://orbiter.dansteph.com/forum/index.php?topic=11984.msg184212#msg184212



Here's the DGIV BETA 6:

Please notice it come with an installer that don't write anything in the registry, it's a clean
installer that will only decompress the file and check that it's really an Orbiter directory.
It will also set a desktop link to the dg4config program, as nothing is wrote in registry you can
delete or move this link where you want.

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

Warning !
-it is a GOOD idea to install the pack after a fresh reboot of your computer otherwise some files may not be copied
properly due to XP or Orbiter holding them. For beta testing it's important to ensure to not have false bug report.


Run:
Run scenario in "Tutorial learn DGIV - What's cool !" it will teach you DGIV and show you latest features.

Correction:
Scenario that start with "--" are new and text are not corrected yet, if you want to correct the english I would be
gratteful but send me a PM first to avoid useless work and correct directly the scenario, don't send me only the texts.
(I have enough work)


List of correction since BETA 5:


DGIV:

-NEW: Payload and skin editor, see Scenario editor of Orbiter
-NEW: autopilot atmospheric PRO110SPEC0
-Cleared bug: Cargo door failure state was not saved in scenario.
-Now hover door broke if open with high temperature.
-Cleaned all scenarios from old DGIII stuff.
-D64 display added check of life support dock valve.
-Cleared MFD label bug
-Added Payload Center to Scenery editor
-MFD label bug cleared
-Cleared bug turn direction on ground not right for backward speed.
-New sound when take off.
-Added, corrected scenarios
-Cleared a lot of small bug (not listed here)

DG4CONFIG:
-Removed all the skin part wich is now done in Orbiter using scenery editor.



Still On my TODO List:
-News scenario, correction of typo and other things in scenarios.
-documentation (help in english welcome)
-New DGIV download page on this site




Much thanks for testing

[Delta Glider3 lover]

Hey DanSteph, I am part of the beta testing team, and the link you sent me brings me to a 404 page, may I please have a new
link to the DeltaGliderIV beta 6 please?
edit: Never mind, I clicked on the wrong link. It is downloading now.



Post Edited ( 04-04-07 02:14 )

[Quick_Nick]

BTW, link works for me.
It's www.orbiter.dansteph.com/public/DGIVBETA/DGIVBETA6.zip for anyone not on the team.
Lol, just kidding, not real link.



Post Edited ( 04-04-07 02:10 )

[dmc14]

Quick_Nick wrote:

BTW, link works for me.
It's www.orbiter.dansteph.com/public/DGIVBETA/DGIVBETA6.zip for anyone not on the team.
Lol, just kidding, not real link.

HAHA!! I thought u actually posted it for a second, that would have been the BEST April fools joke!
BTW Dan, im having no problems yet. Looks great too.

[Quick_Nick]

Yeah, I mentioned I was kidding because I was expecting a lot of flaming otherwise.

[Quantum Burrito Meal]

It still won't let me jettison cargo if cargo bay doors break off before they're finished opening.

Otherwise it's working great, and I had a thought: couldn'y you steal the 'done' button source code from the original DG? it had one in all its special Scenario Editor windows.

EDIT: The search vecctor step in both the docking and null relative speed autopilots spends a ridiculous amount of time wobbling side to side accross the vector.



Post Edited ( 04-04-07 04:08 )

[DanSteph]

Quantum Burrito Meal a écrit:
It still won't let me jettison cargo if cargo bay doors break off before they're finished opening.

I consider them as "jamed" and they block somewhat the release of cargo, I may change the messagw anyway
from "door closed" to "door jamed"

Quantum Burrito Meal a écrit:
Otherwise it's working great, and I had a thought: couldn'y you steal the 'done' button source code from the original
DG? it had one in all its special Scenario Editor windows.

Since 20 years that I program, I know were to find informations, this was almost the first place I searched, the code is
exactly the same but in my case it don't work. Something is missing for sure but I would have to restart from scratch
all the related code without any garantee (and somes risks that I broke something else, I didn't liked at all the code
that I smelled I should have to include).  It's all a balance about advantage/time spent, time was out for this "minor-
feature-button"... maybe on DGV ?

Quantum Burrito Meal a écrit:
EDIT: The search vecctor step in both the docking and null relative speed autopilots spends a ridiculous amount of
time wobbling side to side accross the vector.

What you mean by ridiculous ? 10 secondes ? 1 minute ? on my computer it take 4-10 secondes but this may depend
of the situation or your FPS.... (I have not less than 90 fps almost all the time)

Wich step exactly, starting situation and time spent on this step ? Someone else experiencing this ?

 Thanks !

Dan



Message modifié ( 04-04-2007 05:03 )

[Quantum Burrito Meal]

My graphics card is temporarily out of cation, and I am using the crappy intel onboard graphics, so maybe it's an FPS issue.

Here's a fairly big bug: numpad [-] can still activate retro rockets when retro doors are closed.

Also, sorry if I offended you by saying to nick the code off the DG, I guess it was a bit patronising.

[DanSteph]

Quantum Burrito Meal a écrit:
Here's a fairly big bug: numpad [-] can still activate retro rockets when retro doors are closed.

I never had this bug also, since time that I run the DGIV this always worked perfectly...
Again can you reproduce this, circumstance etc etc.... also  no one reported this until now !?
Are you sure they are closed and not on automatic ?

Quantum Burrito Meal a écrit:
Also, sorry if I offended you by saying to nick the code off the DG, I guess it was a bit patronising.

Uh sorry ? wich code ?

Dan

[Quantum Burrito Meal]

Yeah, I was on mars, I drag the slider, it cautions me, it press numpad [-] and it fires retro rockets. I'll look into that.

And i was talking about the 'done button' code. Sorry again.

[picto]

Y'a pas à dire !
C'est sacrément économique en gazoline ton système !
" Mr Sulu, Prêt pour la téléportation ? "  

On va t'en construire des stations spatiales avec ça, j'te raconte pas !
Mais en fait avec ton système de payload utilisable, serait il possible d'utiliser le DGex
Arm de Papy ? L'est trop grand sans doute ? En lui faisant un DGIV payload config ?





Message modifié ( 04-04-2007 07:58 )

[Hubleman]

Thanks, Dan, I gave it a test it went great,  no bugs found yet but I will report it if I found one.

By the way Picto, I dont understand what you said in that post, because I dont know french but the pic is halarious.

[dudrea]

Bonjour,

Il y a divergence (pas énorme mais sensible) entre les distances affichées entre les affichages "Nav Hud" et "Attachment Hud"
 qui apparait lorsque l'on tente de saisir un objet (commande G)  en EVA

Les vues relatives à cette anomalie proviennent de l'ancienne version, mais j'ai vérifié qu'elle existe également avec la
nouvelle :
Je l'ai constaté en mettant en orbite geosynchrone la charge utile MTKS SAT, mais on peut le reproduire ad libitum à partir
du scénario Payload MTKS-SAT POWER UP.

Nav Hud distance 4,12 mètres



Attachment Hud (image prise juste après) 2,46 mètres




et pour confirmer ce que j'avais déjà signalé sur la possibilité de se mettre la charge utile en "sac à dos" :

[n122vu]

Hubleman wrote:

By the way Picto, I dont understand what you said in that post, because I dont know french but the pic is halarious.

You can translate the text here if you like  
http://babel.altavista.com/

(Sorry for going off-topic)

[picto]

I dont know french

I'm trying to translate it but my english is so poor that I don't know if you'll be able to read it.

I was saying to Dan that his transport system is really a few fuel consumption system.
Then, a little joke about  Star Trek
" Mr Sulu ready for teleportation ! "
I don't know if teleportation is the real name in English.
In my idea that mean : To take an object somewhere and to put it on another place without any delay.
And at least, it will be really easy to build great space stations with this new system
May be it is possible to add DGex Arm by Papyref as a DGIV Payload

n122vu same time !



Message modifié ( 04-04-2007 13:00 )

[streb2001]

Excellent stuff.

Would it be possible to start the Remote Thrust without needing a countdown set? It would be nice to initiate a timed burn
immediately by pressing Start/stop manually. (Even better would also be an option to enter a delta v as an alternative to
burn time!)

'Gear up' and 'Gear down' annunciators still using old voice.

Some typos found so far:

Autoburn messages: '...secondes' should be 'seconds'
PRO105 message: '...CONDITION BEFORE RENTRY' should be '... REENTRY' (or better 'ENTRY INTERFACE'?)
PRO300 message: 'Docking successfull' should be 'Docking successful'
Display menu item 9: 'Antenna/data transfert' should be 'Antenna/data transfer'


Trivial details!
Display 3: 'range' should be 'Range'
Bottom panel: 'Thrusters door' should be 'Thruster doors'
Top panel: I still think 'APU UNIT' should read 'APU' !!

I will keep searching for typos.

Steve

[DanSteph]

dudrea a écrit:
Nav Hud distance 4,12 mètres

*about distance reading not the same in ATTACH HUD and NAV HUD*
This is because one distance is taken from center (NAV) and the other from the attachment
point wich is not in the center.

dudrea a écrit:
et pour confirmer ce que j'avais déjà signalé sur la possibilité de se mettre la charge utile en "sac à dos" :

*About abilitie to grapple anything on the back*
That's a draw back of "universalities" of attachement, you can attach everything. I could limit with some attachment
ID but in this case Ummu would not be able to grapple other addon's object.

Thanks for testing !

Dan

PS: je t'y cause english c'est pour éviter que les gens soumettent les meme trucs.

[DanSteph]

Quantum Burrito Meal a écrit:
Yeah, I was on mars, I drag the slider, it cautions me, it press numpad [-] and it fires retro rockets. I'll look into that.

Tried moving slider, then "-" then slider again then "-" shaked this as much
as I could, no luck,no bug, let me know when you'll be able to reproduce 100% time.

Anyone that have this bug also ?
(retro firing with door closed)

Dan



Message modifié ( 04-04-2007 12:54 )

[dudrea]

Bonjour,

Scenario The Art of EVA

- Rendez vous orbital avec le GL02 en détresse pas de problème particulier...
- EVa puis récupération successive des deux premiers membre de l'équipage (un par un) : rien à signaler
- Pour le troisième (le capitaine) je n'ai pas utilisé l'EVA mais l'Eject, et dans le viseur du capitaine je lis (j'ai du mal
à maîtriser mon hébergeur d'image, donc je ne sais si c'est lisible ici) :

RCS Fuel 98% (c'est normal, je viens juste de stabiliser sa rotation)
O2 Level 995 % !!!!
O2 Time remaining 17:16:51
Je n'avais pas ces valeurs anormales d'O2 pour les autres membres.

[DanSteph]

streb2001 a écrit:
Excellent stuff.
Would it be possible to start the Remote Thrust without needing a countdown set? It would be nice to initiate a timed
burn immediately by pressing Start/stop manually. (Even better would also be an option to enter a delta v as an
alternative to burn time!)

First thanks for excellent testing and report.

Abour remote thrust you mean by default 10 seconds so one can press immediattely ?
I thins case I think a burn should not be done in hurry. Aboud DV this would require panel
change, not time for that near final.

streb2001 a écrit:
'Gear up' and 'Gear down' annunciators still using old voice.

Done

streb2001 a écrit:
I will keep searching for typos.

Corrected all submited, "transfert" was found 15 times in code, corrected them all.

Keep testing

Dan

[DanSteph]

dudrea a écrit:
Je n'avais pas ces valeurs anormales d'O2 pour les autres membres.

Juste une question Tu a de la peine avec l'anglais ? si oui continue en francais sinon l'anglais
serait mieux. Merci.

Ca va etre dans la FAQ ca, en cas d'éjection reservoir spécial a longue durée...
en 1h personne aurais le temps de te secourir.

Dan

[picto]

 I tried to reproduce the bug on mars scenario with retro firing.
No problem here.

[Quick_Nick]

If you're correcting typos, there are a good bit of some of even the same in scenarios.
Also, I've noticed what I think dudrea was talking about, though I don't speak French. I think he may have been
mentioning the ~20hr. 1000% oxygen. I've seen it at least when moving to space in a mmu, but not sure about
EVAing into space.

[picto]

Not a bug, but funny!
If you load a payload ... release it ...
and quite quickly load another one and release it quickly too, you get this ... each time
A good way to increase the max weight of luggage you can take with you in space

[Quick_Nick]

I think they docked...
Pretty funny!