[CLOSED] [BETA8] of DeltaGliderIV

[n122vu]

Bug Report - Scenario Configuration

In the Mission Scenario "The Art of EVA" - when you EVA the crew of the crippled ship, their suits have 0% RCS fuel.  
This makes the EVA and rescue next to impossible, as when the crew EVA, they are also rotating out of control along
with the ship.  

Not sure if this was meant to be a "feature"  to make the mission more challenging, or if this is truly an
accidental configuration error.  

Regards,

n122vu

[Felix]

Okay, I see you have a point there. One last suggestion, then I'll shut up and go looking for important stuff again.
If the reason should indeed be Gs, however, might it not be an idea to disable G-checks in safe mode, as it seems that you
have done with temperature checks? After all, I could imagine problems like with the elevator could happen with powerful
motherships, too, though I might be wrong there, and the loss of realism should be really negligible. Stowing crew inside an
Ares-rocket or whatever you attach the DGIV to isnt that realistic either.


Here's the screenshot you wanted:

[n122vu]

Felix wrote:

I have this problem also.

n122vu

[sunshine135]

Mine has those boxes also. I just assume that those are ENTER boxes due to the text editor used for the Mmu.

[DanSteph]

Felix a écrit:
Here's the screenshot you wanted:

"Square in help text line" solved, of course return char at end of line, what is funny is that they
don't appear on my computer !!??

Will see others things after sleep

Dan

[willy88]

Hmm, well, since the UMMU has built in help, why doesn't the DGIV have it as well?

[AndyMan]

It does. Called the checklists.

Dan, I am not on beta team, but the space elevator bug sounds to me alot like what happens when you land gear
up. No other systems besides the ones against the ground. Does the ships status still read as "Landed" while the
elevator holds it?

[DanSteph]

AndyMan a écrit:
Dan, I am not on beta team, but the space elevator bug sounds to me alot like what happens when you land gear
up. No other systems besides the ones against the ground. Does the ships status still read as "Landed"
while the elevator holds it?

Might be the reason, one or more value doesn't read what it should be for sure...

Dan

[DanSteph]

n122vu wrote:
Bug Report - Scenario Configuration
In the Mission Scenario "The Art of EVA" - when you EVA the crew of the crippled ship, their suits have 0%
RCS fuel.  

Very strange, I see no reason for that in this particular mission, I just tried and it work as expected...
Can you reproduce it ?

Dan

[DanSteph]

Felix wrote:
I have a Mission Specialist named John F. Kennedy. The EVA select thingy tells me he's "Miss John F.
Kennedy", which doesn't exactly make me think of "Mission Specialist".

Corrected "Miss" changed for "Spe"  14 scenario edited also.

Thanks

Dan

[Artlav]

DanSteph wrote:
Very strange, I see no reason for that in this particular mission, I just tried and it work as expected...
Can you reproduce it ?
Dan

EVA RCS/control bug:
UMMU RCS fuel are often set to some apparently random value when it egresses.
Futher research shows, that the RCS fuel is set to the amount of fuel in one of the host vessed (DGIV) tanks.

Here is the example scenario with 100% reproducibility on my system:
http://www.rumaxclub.ru/etc/evarbug.txt
EVA the captain - 100% RCS, eva the engineer - 56% rcs.
Change the amount of fuel in the DGIV to 24%,
EVA the captain - 24% RCS, eva the engineer - 100% rcs.

Also, sometimes the MMU is in ROT mode on the ground after egress or TP-landing, making it uncontrollable, as i reported a
few betas earlyer, which seems to be linked to some of the vessels around - switching to lin changes MMU too.

Both facts suggests some sort of runaway pointer or buffer/struct overflow.

Both bugs are a few betas old, but i didn't re/reported them earlyer since there was no clear reproduction scheme.



Post Edited ( 04-21-07 10:59 )

[DanSteph]

Artlav wrote:
Here is the example scenario with 100% reproducibility on my system:
http://www.rumaxclub.ru/etc/evarbug.scn

Oops 404

I'm curious to see the scenario as the RCS tank fill is hard coded and there is absolutely no C++ lines that touch
this value (no buffers at all that can overflow)

ph_rcs  = CreatePropellantResource (MAX_RCS_FUEL);  // RCS tank

Dan



Post Edited ( 04-21-07 11:01 )

[Artlav]

DanSteph wrote:

Oops 404

Dan

Server bug.
http://www.rumaxclub.ru/etc/evarbug.txt , rename to scn.

[DanSteph]

Artlav wrote:
http://www.rumaxclub.ru/etc/evarbug.txt , rename to scn.

Thanks, unable to reproduce bug, RCS set to 100% as expected
Anyone have this bug with this scenario ?

-Also do you have any special settings in orbiter ? (unlimited fuel, other ?)
-Does it reproduce on a fresh install of Orbiter/Beta 8  ?
-Is it Orbiter with patch P1 ? (and beta 8?)

Thanks for help

Dan



Post Edited ( 04-21-07 11:13 )

[DanSteph]

Artlav wrote:
Also, sometimes the MMU is in ROT mode on the ground after egress or TP-landing, making it uncontrollable, as i
reported a few betas earlyer, which seems to be linked to some of the vessels around - switching to lin changes MMU
too.

Never had that one also, there was one scn wrong (save the idiot) where the RCS was not set but it was a scn
problem. A buffer overflow of this sort beetween two modules is almost impossible and even, it would more likely
create CTD or other than just switching the same stuff in both vessel... Also no one reported this until now.

Did you tried this on a fresh Orbiter install with P1/beta 8 ? (thought I don't see any reason for such bug !??)

On witch planet/asteroid was it ? the G matter sometime (at light G I disable automatically the walk routine, you must
use RCS to move)

Dan



Post Edited ( 04-21-07 11:21 )

[DanSteph]

DanSteph wrote:
Thanks, unable to reproduce bug, RCS set to 100% as expected
Anyone have this bug with this scenario ?
Dan

After some tries got it finally, I'm working on this...

Dan

[Artlav]

DanSteph wrote:

Artlav wrote:
http://www.rumaxclub.ru/etc/evarbug.txt , rename to scn.

Thanks, unable to reproduce bug, RCS set to 100% as expected
Anyone have this bug with this scenario ?

-Also do you have any special settings in orbiter ? (unlimited fuel, other ?)
-Does it reproduce on a fresh install of Orbiter/Beta 8  ?
-Is it Orbiter with patch P1 ? (and beta 8?)

Thanks for help

Dan

Confirming, 2006-P1, beta 8, no modules sans orbitersound, extmfd and scneditor, no extraordinary settings (MFD refresh=0.01,
no damage sim, all visuals, lv7 max, others standard).
It's not 100% reproducible on that setup, but every second run have RCS fuel set to the DGIV amount in either the first or
second mmu.

That's what it looks like:
http://www.rumaxclub.ru/etc/dgivrcseva.zip (AVI, DivX5, 697Kb)

Can't reproduce the noncontrollable bug - it happens on the Moon now and then, but very hard to catch.

[DanSteph]

Artlav a écrit:
EVA RCS/control bug:
UMMU RCS fuel are often set to some apparently random value when it egresses.
Futher research shows, that the RCS fuel is set to the amount of fuel in one of the host vessed (DGIV) tanks.
Dan

Solved !!!

No buffer overflow of course but a copy of the "mother" vessel status applied to child.

GetVesselStatus(vs)
vs.Fuel=1.0; <--- forgot this one
Eva (vs)

So the "child" had simply same setting than mother ship. The fact that it didn't happened all time
come from orbiter I think, difference in timing. (when I was debuging step by step for example
I didn't had it)

May thanks for your help and for catching this one.

I "close" your problem, can you please watch about the other problem with "rot" setting "changing"
other vessel around and open another post if you can reproduce it ? (so I can "yellow" it as it's a different
problem than "fuel")

Dan

[JoshB]

DanSteph wrote:
Might help for funny mission I achieved to be in orbit with only one turbopack (required two attempt)

Dan, you're right that only one turbopack is needed -- not sure why I needed two before, probably because I was flying it
really badly at first.  

I was successful in doing a turbopack rendezvous at least three times.  If the DGIV is heading towards brighton beach, then
you should take off with the turbopack when it is about 120km away.  The exact number would depend upon how well you fly the
Mmu.  Cut off the TP engine when your velocity is at or a little above the DGIV's velocity.  (Of course the orbital hud will
make this a bit easier.)

It is eerie during the final part if the timing is right -- the DGIV will zoom in out of nowhere and stop (relatively
speaking) right beside you.  With checking just the initial heading and not worrying about it later, I was able to inject
into an orbit with RInc of 0.60 degrees.

I'm tweaking the starting scenario a little more then I'll send it to Dan and put it online.

[Artlav]

DanSteph wrote:

I "close" your problem, can you please watch about the other problem with "rot" setting "changing"
other vessel around and open another post if you can reproduce it ? (so I can "yellow" it as it's a different
problem than "fuel")

Dan

It seems that the second problem is related with the first - each time the MMU refuses to move it was egressed with non-full
tank, and refilling the tank of the disabled MMU makes it move.

[DanSteph]

Artlav wrote:
It seems that the second problem is related with the first - each time the MMU refuses to move it was egressed with
non-full tank, and refilling the tank of the disabled MMU makes it move.

Can you record this problem and remind to test it in beta 9 ?

Dan

[Artlav]

Update on the weight/control bug:

UMMU weight bug (?):
What about WeightKg parameter of UMMU? I can't see where it is saved in the scenario file.
If you exit the MMU from the vessel, exit the sim, start it again and get into the vessel, the weightKg parameter will be
diffirent.

UMMU ground control loss bug:
If the UMMU RCS fuel amount is less that 67%, then the ground mode controls will not work, and will be set to rot/lin of the
host vessel on egress. This holds true for both egress with little fuel bug and for spending fuel, i.e. in TP flight.
100% reproductible on the Moon.

[DanSteph]

Artlav a écrit:
UMMU ground control loss bug:
If the UMMU RCS fuel amount is less that 67%, then the ground mode controls will not work, and will be set to rot/lin
of the
host vessel on egress. This holds true for both egress with little fuel bug and for spending fuel, i.e. in TP flight.
100% reproductible on the Moon.

Do you have a scenario ? I'm unable to reproduce this. Tried with 50% fuel on moon, hover, landing,
control was working as expected.

Dan

[Murdock]

Hi Dan,
I downloaded DGIV beta 8 and did some more tests with TX winged booster.

First thanks to Killingsnake for the link to Fuel MFD, I downloaded it and it works perfectly.

I tryed to copy the whole DGIV configuration as suggested by Killingsnake instead of just
changing name from DGIII to DGIV in the scenario conguration:
it works exactly the same way so this confirms that DGIV configuration is perfectly spawned dinamically.
I believe I found the cause of the CTD when switching between focus ships:

CTD happen when RCS mode is set to ROTATION on TX and is not on DGIV and I try to switch focus.
The reason why I didn't discover it on first attempt was that DGIV is set by default to LINEAR
and TX mode on the ground is AIRFOIL ONLY then it changes automatically to RCS+AIRFOIL
above 30 km so CTD happened only above that altitude.

Cheers
Virgilio  

[Artlav]

DanSteph wrote:
Do you have a scenario ? I'm unable to reproduce this. Tried with 50% fuel on moon, hover, landing,
control was working as expected.

Dan

Any Moon-landed scenario.
Start The Art of EVA scenario, where you are on the Moon in MMU already, open scenario editor->propellants.
Exact point is 66.3724%
66.3724% - runs around fine, 66.3723% - stands still.