[Closed] [BETA10] of DeltaGliderIV

[Joe_BAR]

DanSteph a écrit:

Joe_BAR a écrit:
Elevon control not reset

When changing control mode "on the fly", Elevon position si not cleared.
For instance :

Tried to solve it with simple way but didn't worked, I have a complicated workaround
that would run each frame during the simulation, as this case is very rare (you may be
the first one to hold stick while changing control mode ) I'll will leave this "bug",
no need to lose proc cycle for something that may occure once every 10 years.

Thanks

Dan

Hi Dan, my two cents...

I had imagined some very easy way but maybe Im out since I did'nt open my C++ for two years

I guess you have some vars to store atmo control status (none pitch only or auto).
So on the "Timestep" part off the program you could have simply insert a check like

if elevon_control_var = false then reset elevon...

But I imagine that may be a little more tricky...

Indeed I think we may live with this horrble bug

[DanSteph]

Pagir a écrit:
Personnaly, I prefer to make my reentry "Viking style" on Mars: Pro104s40 to get a good aerobraking,
then after the heat peak and at low altitude, I keep using Pro104 but firing but I use the hovers: this way, I keep the
ship with a reasonable vertical speed AND I'm losing horizontal speed.

Okay okay... !!!!

Retro, hover and main thrust allowed for 104 and 105.

1-D65 say that one must have retro and hover door *closed* before reentry this forbid retro and hover.
2-if one is enough stupid to open the door and fire retro or hover at the bad time despit
the D65 he might not complaint at Spacetech company (I mean.. err.. his burried body might not complain )

Dan



Message modifié ( 14-05-2007 15:11 )

[DanSteph]

Joe_BAR a écrit:
Hi Dan, my two cents...
I had imagined some very easy way but maybe Im out since I did'nt open my C++ for two years

That's not the problem,

Reseting elevon to zero doesn't work right after you disabled control, you have to reset elevon
the next timestep when control are effectively disabled by the previous timestep.

IE: cou can't do:

{
DisableControl(TRUE);
ResetElevon(TRUE);
}


It doesn't work, Orbiter forbid that.
So it would require:


if(bOrderToResetElevon==TRUE)
{
    ResetElevon(TRUE);
    bOrderToResetElevon=FALSE;
}
{
DisableControl(TRUE)
bOrderToResetElevon=TRUE;
}


See? disable done next frame and one test done every frame (million time after some hour of play)
just to avoid a VERY rare case that may happen on 1/5000 player or never. (as this was never
reported since DGII)

One test take only some proc cycle you may say, the fact that the DGIV still run at 40-80 FPS
on my old computer despit the 37'000 lines of code is due to that: I optimize as much as I can the code.

Dan

[Pagir]

DanSteph a écrit:

Pagir a écrit:
Personnaly, I prefer to make my reentry "Viking style" on Mars: Pro104s40 to get a good
aerobraking,
then after the heat peak and at low altitude, I keep using Pro104 but firing but I use the hovers: this way, I keep the
ship with a reasonable vertical speed AND I'm losing horizontal speed.

Okay okay... !!!!

Retro, hover and main thrust allowed for 104 and 105.

1-D65 say that one must have retro and hover door *closed* before reentry this forbid retro and hover.
2-if one is enough stupid to open the door and fire retro or hover at the bad time despit
the D65 he might not complaint at Spacetech company (I mean.. err.. his burried body might not complain )

Dan

Well... (He's gonna hit me...) hover only, not main trust (because main trust isn't affected by heat). So...
someone could fire the main engines even if the heat shield shows 1400C, and it shouldn't be allowed...

So: main and retro: no
hover: yes...

Pagir

[DanSteph]

Pagir a écrit:
Well... (He's gonna hit me...) hover only, not main trust (because main trust isn't affected by heat). So...
someone could fire the main engines even if the heat shield shows 1400C, and it shouldn't be allowed...

Well, you preffer hover but someone else would come soon with retro or main request because
he want to use it for various reason.

Also it would not be consistant to forbid such a dangerous things as hover and not retro
(wich is as dangerous as hover) and main (wich is way  less dangerous)

Dan

[kipper]

Pagir wrote:
For the skip reentry ("bounce effect" on the atmosphere), it was never used with a manned
ship Pagir

Absolutely incorrect.  Used on both Apollo and for Russian re-entries.

I just want to use the ME and RETRO to add/subtract small amounts of energy for downrange correction *before* EI for a
precision landing with AEROBRAKE predicting my PED.

It's a good method, safe when using AEROBRAKE and with some authenticity.  I don't see why DG4 should arbitrarily remove it as a possibility.



Post Edited ( 05-14-07 17:53 )

[Pagir]

kipper a écrit:

Pagir wrote:
For the skip reentry ("bounce effect" on the atmosphere), it was never used with a manned
ship Pagir

Absolutely incorrect.  Used on both Apollo and for Russian re-entries.

Don't want to start an argument here, but you'll have to convince me...

"A skip re-entry is riskier," Lockheed's Johns concedes. "The Apollo traditionalists worry about it." The
Russians performed a couple of successful skip re-entries with their unmanned Zond moon probes in the late 1960s,
however. And today, Johns says, scientists have a much better understanding of the forces that will be acting on the
spacecraft

http://www.popularmechanics.com/science/air_space/4212906.html?page=3

For the Pro104 or P105, I think P105 should continue to forbid retro, hover and main engine, otherwise it will put the
computer in trouble. Only P104 should allow it (at the risk of the user...)

Pagir

[DanSteph]

kipper wrote:
I just want to use the ME and RETRO to add/subtract small amounts of energy for downrange correction *before* EI
for a precision landing with AEROBRAKE predicting my PED.

Ooof had pain to figure what ME and EI mean, got it: Main engine and Entry interface ?

just one point, if you make those adjustements before entry interface you can
do it without engaging the autopilot as you are not already in atmosphere ?

Anyway you have them back, for 105 and 104.

Dan

[DanSteph]

Pagir wrote:
For the Pro104 or P105, I think P105 should continue to forbid retro, hover and main engine, otherwise it will put the
computer in trouble. Only P104 should allow it (at the risk of the user...)

I hesitated a long time for 105 and changed it almost 5 time to finally keep it open

my point is that:

-most people will not have the bad idea to fire anything during a reentry
autopilot because it's not like that that it work usually. Even if, the doors
are supposed to be closed for safety.

-If the guy burn he will learn hard way that it was a bad idea.

-Still a few peoples might like HE ME or RE ( ) for whatewer and special reason as
 you or kipper.

1-It would be frustrating to protect to much user against themself, we might keep the possibility
that they make some idiot things else there would be less fun.

2-Allowing stuff for people that really want them is better than forbiding them for anyone.

Dan

[Pagir]

Aye Aye sir!

At the end, it's your call and I support your call!

Pagir

[kipper]

Skip was used on Apollo 4 and Zond 6 & 7- I didn't mean that it was done on a manned craft - though both craft were skip-capable.

So why would we have ruled it out - it is authentic!  Don't have to convince anybody!

[DanSteph]

Pierre a écrit:
Bad fuel flow indication when dumping fuel.
Severity
Minor. (DGIV detailed Systems functionality)

Will leave this one , workaround is too complicated, take to much time
and the bug is really a detail.

Twilight a écrit:
Short description:
Another Fuel-Dump related bug.
Severity
minor

Same as above.

Twilight a écrit:
The point is that RCS is full, Main is dumping, and still transfering into a full RCS tank.
Short description:

Fuel Transfer Bug
Severity

Moderate (can be deadly)
Complete  description
If a fuel transfer is done on a ship into a full tank, then the tank that's being filled is used, the other tank goes down
unrealisitically.

This one could be annoying, cleared.

kipper a écrit:
Short Description

Cannot use keyboard keypad while using PRO105SPEC40.  
Severity
Medium

Complete description
Cannot use keyboard keypad while using PRO105SPEC40.  Sometime keyboard keypad is totally locked, sometimes I
can only use bank controls but not pitch.
Reproduce bug
Happens sporadically, best way to reproduce is to engage PRO105SPEC40, turn off and re-enagage.  

Miscellaneous

Any feedback on this one ? was unable to reproduce.


Dan

[DanSteph]

Murdock wrote:
Short description:
Crew's hypoxia while wearing space suits
Severity
moderate
Complete description
In case of cockpit decompression in flight two situations happen:
- in space, (0 atmosphere) suits activation with oxi reserve message and no hypoxia warn;
- in low pressure atmosphere (about 20000m altitude) same suit activation message but with hypoxia warn
  confirmed by life support indications
Virgilio

Solved, solved also another related bug: pressure was in pascal instead of psia in this case.

Dan