ProgressM1 beta testing

[n72.75]

Please can you try a little test?
Open orbiter on any scenario, choose a vessel, open scenario editor and delete that vessel (don't choose progress). Does it crash orbiter?

If it does what does it mean.

 

[no matter]

It means that probably something is keeping an invalid handle to the vessel you are dremoving.

When Land MFD is activated for example, instead of removing the vessel then switching focus to another, orbiter crashes.

 

[SPQR]

For me, the CTD happened when the Progress was a burned hulk. It seems that it happened when it should have been automaticaly erased.

I tested deleting, as you asked, with the scenario of the CTV-LEO4 orbiting alone (no ISS and so on). It caused a clean CTD, bringing me back to the Orbiter launchpad.

The Progress CTD caused a real error message (windows) and the end of Orbiter programm (no return to the launchpad). I had no problem before with the Beta-01.

However, leaving the Progress burning in the atmosphere, while being another place else (inside CTV for instance), provoked no CTD, the deletion was effective (thus without witnesses).


Another point :
While with Beta-01 you were warned whern trying to put inside Progress more than 2 crewmen, Beta-02 didn't react that way.
I manage to put 4 UMMU crewmen, however, they were outside, all 4 named "UMMUProgress", without different name and without model.

They appeared inside the 4 Progress' fuel tanks.

It was impossible to make them come back inside Progress or, for exemple, an opened and empty CTV.

While UMMU, the voice, from E key action, which should have tell me "too far from airlock" was mute.

Initial condition, which maybe had a side effect with the crew transfer : just before, with Fuel management, I unloaded tank 02 into ISS and vent what was left in tank 02 and all inside tank 03 and 04.

---------------- EDIT ------------------

I tried to get a second time the UMMU/crew transfer bug without success. The transfer worked well. 2, no more, before and after venting (maybe starting first by venting is the origin ??).

I had UMMU ISS, ProgressM, PIRS, CVEL Soyuz TMA and CTV-LEO6.

However I didn't had time to test reentry CTD, as I provoked another violent one :
- CTRL-5 (choose target in docking view)
- write "Earth" as target (rather stupid, no ? )

 

[no matter]

The Progress CTD caused a real error message (windows) and the end of Orbiter programm (no return to the launchpad). I had no problem before with the Beta-01.

Ok, I can't reproduce that bug but I will investigate and try on a second computer, still with a clean install.

I manage to put 4 UMMU crewmen

How did you manage to put them?

 

[SPQR]

How did you manage to put them?

Hummmm, Murphy's Law ? :sorry:
Look at my edit above.

For the CTRL-5/Eath CTD, here is the log :


**** Orbiter.log
Build Sep 29 2006 [v.060929]
Found 0 joystick(s)
Module AtlantisConfig.dll [API v.060425]
Module DGConfig.dll [API v.060425]
Module OrbiterSound.dll [API v.060425]
Module OrlanMFD.dll [API v.060425]
Module RendezvousMFD.dll [API v.050206]
Module ScnEditor.dll [API v.060425]
Module RadarMFD.dll [API v.050206]
Module ReleaseMFD-ShiftD.dll [API v.060425]
Module CamShake.dll [API v.050206]
Module Accelerometer.dll [API v.060425]
Module ReleaseMFD-Mouse.dll [API v.060425]
**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Zbuffer: 16 bit
Render device: Fullscreen 1024 x 768
Device has hardware T&L capability
Module Sun.dll [API v.050206]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll [API v.050206]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll [API v.050206]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll [API v.050206]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll [API v.041022]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll [API v.060425]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll [API v.060425]
Module Deimos.dll [API v.060425]
Module Galsat.dll [API v.041022]
Module Jupiter.dll [API v.050206]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll [API v.041022]
Module Europa.dll [API v.041022]
Module Ganymede.dll [API v.041022]
Module Callisto.dll [API v.041022]
Module Satsat.dll [API v.050206]
Module Saturn.dll [API v.060425]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll [API v.050206]
SATSAT Mimas: Terms 113
Module Enceladus.dll [API v.050206]
SATSAT Enceladus: Terms 33
Module Tethys.dll [API v.050206]
SATSAT Tethys: Terms 101
Module Dione.dll [API v.050206]
SATSAT Dione: Terms 59
Module Rhea.dll [API v.050206]
SATSAT Rhea: Terms 68
Module Titan.dll [API v.050206]
SATSAT Titan: Terms 100
Module Hyperion.dll [API v.050206]
SATSAT Hyperion: Terms 595
Module Iapetus.dll [API v.050206]
SATSAT Iapetus: Terms 605
Module Uranus.dll [API v.050206]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll [API v.060425]
Module Ariel.dll [API v.060425]
Module Umbriel.dll [API v.060425]
Module Titania.dll [API v.060425]
Module Oberon.dll [API v.060425]
Module Neptune.dll [API v.050206]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Module Triton.dll [API v.060425]
Finished initialising world
>>> ERROR: Missing texture: TMA-APAS\ballon.dds
>>> [C:\Source\Orbiter\Texture.cpp / 781]
Module ProgressM.dll [API v.060425]
Module SSA-LEO6.dll [API v.060425]
Module pirs_DC_1.dll [API v.060425]
Module SoyuzTMA.dll [API v.060425]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
>>> ERROR: Missing texture: U_mmu.dds
>>> [C:\Source\Orbiter\Texture.cpp / 781]
>>> ERROR: Missing texture: U_mmu2.dds
>>> [C:\Source\Orbiter\Texture.cpp / 781]

 

[no matter]

>>> ERROR: Missing texture: TMA-APASballon.dds

This will be fixed, in fact this texture should have been removed from the mesh but it is still there...

>>> ERROR: Missing texture: U_mmu.dds
>>> [C:SourceOrbiterTexture.cpp / 781]
>>> ERROR: Missing texture: U_mmu2.dds
>>> [C:SourceOrbiterTexture.cpp / 781]

belongs to UMMU.

There is nothing to protect from doing something that you did with CTRL+5
This means that there is still work to do on that feature!!

I am still really annoyed with the ctd while reentry occurs, if I can't reproduce, I can't fix!


-----Posted Added-----


I get a possible problem with ummu iss , I have been able to transfer more than 2 members to progress but the exceeding members are wasted once transferred (they can't appear inside progress which is limited to 2 members).

It is really weird because testing the same thing with another ummu vessel than ISS, works perfectly, "error - docked ship is full" message is displayed and no one can be transferred to progress when 2 member are already on board.

EDIT: OK, UMMU ISS problem fixed, this is what is happening when you are trying to force something to work as not intended ^^

 

[SPQR]

I didn't manage to get the reentry CTD again.

I tried with "Progress docked to ISS" scenario (UMU ISS, CVEL TMA, Pirs, CTV & Progress M) and "Progress orbiting" (ISS, Soyuz, Progress => return to ISS) and this time it worked perfectly in both cases.

Sorry. Why does it always happen when you don't take note of the test initial conditions ? :dry:

------------ EDIT ------------------

As error message, wouldn't

"Engine cover closed !"

be better than

"Engine cover not open !"

 

[no matter]

I didn't manage to get the reentry CTD again.

I tried with "Progress docked to ISS" scenario (UMU ISS, CVEL TMA, Pirs, CTV & Progress M) and "Progress orbiting" (ISS, Soyuz, Progress => return to ISS) and this time it worked perfectly in both cases.

Sorry. Why does it always happen when you don't take note of the test initial conditions ? :dry:

------------ EDIT ------------------

As error message, wouldn't

"Engine cover closed !"

be better than

"Engine cover not open !"

"Engine cover closed" is better. I will change the message, thanks.

The ctd when choosing a planet as target is fixed. Targetting a planet will be forbidden in the next beta.
Thanks for getting that stupid bug that should never have been introduced, I just replaced GetObjectByname by GetVesselByName.

I didn't manage to get the reentry CTD again

Good I was affraid of something bad introduced by RCS exhausts rendering ability to be disabled.

 

[SlyCoopersButt]

CTD Happened to me during entry on first go. I do not believe it has anything to do with your ship or it's coding itself. Orbiter crashing when vessels are automatically deleted is a common issue. It's simply best to refrain from auto deletion and leave that to the end user to decide when he or she wants the vessel totally removed from the simulation. The fact that it looks like charcoal should be a good enough indicator that the ship is quite done for after entry.

 

[Yoda]

Okay, tried scenery again ( Progress docked to ISS) and once again got CTD on exerior view during re-entry.
This is what the Orbiter log had to say;

**** Orbiter.log
Build Sep 29 2006 [v.060929]
Found 1 joystick(s)
Module AtlantisConfig.dll [API v.060425]
Module DGConfig.dll [API v.060425]
Module CamShake.dll [API v.050206]
Module CTVMFD.dll [API v.060425]
Module OrbiterSound.dll [API v.060425]
Module Telescope.dll [API v.060425]
Module transx.dll [API v.060425]
Module ScnEditor.dll [API v.060425]
Module RendezvousMFD.dll [API v.050206]
Module OrlanMFD.dll [API v.060425]
Module GPCMFD.dll [API v.060425]
Module AutoFCS.dll [API v.050206]
Module LolaMFD.dll [API v.050206]
Module ScreenCapture.dll [API v.060425]
Module LaunchCompassMFD.dll [API v.060425]
Module UMMUFA.dll [API v.060425]
**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Zbuffer: 32 bit
Stencil buffer: 8 bit
Render device: Fullscreen 1440 x 900
Device has no hardware T&L capability
Joystick throttle: Z-AXIS
No joystick throttle control detected
ERROR: DInput error DIERR_OBJECTNOTFOUND
[C:\Source\Orbiter\Orbiter.cpp / 1624]
Module Sun.dll [API v.050206]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll [API v.050206]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll [API v.050206]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll [API v.050206]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
*** WARNING: Old-style texture contents file Earth_lmask.bin
Module Moon.dll [API v.041022]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll [API v.060425]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Galsat.dll [API v.041022]
Module Jupiter.dll [API v.050206]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Europa.dll [API v.041022]
Module Satsat.dll [API v.061227]
Module Saturn.dll [API v.060425]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll [API v.050206]
SATSAT Mimas: Terms 113
Module Enceladus.dll [API v.050206]
SATSAT Enceladus: Terms 33
Module Tethys.dll [API v.050206]
SATSAT Tethys: Terms 101
Module Titan.dll [API v.050206]
Module Hyperion.dll [API v.050206]
SATSAT Hyperion: Terms 595
Module Iapetus.dll [API v.050206]
SATSAT Iapetus: Terms 605
Module Uranus.dll [API v.050206]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Neptune.dll [API v.050206]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Finished initialising world
>>> ERROR: Missing texture: TMA-APAS\ballon.dds
>>> [C:\Source\Orbiter\Texture.cpp / 781]
Module ProgressM.dll [API v.060425]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state

 

[Thorton]

Very good addon! Thanks!

I got CTD in external view during re-entry.

Also i've noticed a few mistakes in visual model. See the picture:


Correct solar animation you can see here: http://rapidshare.com/files/137961470/Souyz.avi.html

 

[no matter]

Thorton, thanks for the video link and your remarks on visual model
I can fix the animation easily.

I didn't notice that rcs configuration was not the same as a soyuz!
I will fix that. However, it is a huge modification of the rcs model, it can be hard. May be, I can cheat a bit and modify only particle streams location instead of the whole thruster.

I am not sure to understand how does it pitch now I must have a closer look on this.

----
Ok, I can add the choice of activating or disabling reentry deletion.

Unfortunately the log doesn't help much, the best I can do to fix or at least understand is to test reentry and wait a ctd at home while debugging.

 

[Thorton]

About pitch and yaw:

I didn't notice that rcs configuration was not the same as a soyuz!
I will fix that. However, it is a huge modification of the rcs model, it can be hard. May be, I can cheat a bit and modify only particle streams location instead of the whole thruster.

yes, Progress service module construction is a little bit different than soyuz SM.
Do you have plans to add particles in main engine exhaust?

 

[no matter]

About pitch and yaw:

yes, Progress service module construction is a little bit different than soyuz SM.
Do you have plans to add particles in main engine exhaust?

Alright, I understand

No, I don't plan using particle streams for the main exhaust.
I am desperately in need of seeing the real KTDU exhaust !

 

[Thorton]

No, I don't plan using particle streams for the main exhaust.
I am desperately in need of seeing the real KTDU exhaust !

I suppose if you will use particles for main engine exaust, it looks more real than current exaust texture. Now exhaust looks like ion engine exhaust or something like it.

I have some doubts that you can find photo of real KTDU exhaust in space.

 

[Urwumpe]

I am desperately in need of seeing the real KTDU exhaust !

Uses the same propellants as the DO/DPO (RCS), so no surprises there.

The thrust of the KTDU is 315 kg, that is almost exactly the thrust of the primary RCS thrusters of the Space Shuttle (870 lbf or ~400 kg). The ISP is also almost equal, so there should be only a one difference: The fuel used by the Shuttle is different (MMH instead of UMDH), but the difference in chamber temperature should be minimal.

Chamber pressure is equal in both engines (8.62 bar or 8.8 bar)

So, if you replicate the exhaust of the Space Shuttle primary RCS (for example from the camera shots during ET separation) you should be good.

Realistically, the rocket exhaust in a vacuum would look best if you combine particle and billboard exhaust: A small thin underexpanded reddish jet as billboard, surrounded by a cloud of whitish transparent particles (expanding into roughly a 45° cone)

EDIT: Photos of a progress to fire it's engine should be hard to get. A short firing happens shortly after undocking, but I don't know if anybody made of photo of it.

 

[no matter]

These are good clues on how the exhaust looks like, thanks Urwumpe

Thorton wrote:
I suppose if you will use particles for main engine exaust, it looks more real than current exaust texture. Now exhaust looks like ion engine exhaust or something like it.

Yes I understand, the current one does not satisfy me (the blue tint is not what we need here), but I will give another try with a texture and if still not satisfying then I'll probably use particles stream but I have also to keep in mind that particles are frame eaters. (hopefully, I get a method to disable a stream when time acceleration is above x10).

For now, I have implemented the new rcs model, modified the mesh according to this and modified the panel animation (introducing a little problem with the mesh which was not thinked this way...).
Reentry deletion is optional, it needs a tag in the .scn file to be active.
Some work has been made on the Sun tracking function to digest all the thrusters changes.
Ability to undock while a crew memeber is inside Progress is removed (I hesitated a bit between removing the ability or killing the member...).
A Beta3 is coming.

 

[Urwumpe]

These are good clues on how the exhaust looks like, thanks Urwumpe

If you do your own, don't make the exhaust too opaque. Most photos of the Shuttle exhaust had been done with very light sensible camera settings so you can analyze it as engineer (which makes it possible to see stars in many RCS firing shots) - and this got taken to Orbiter as well.

 

[no matter]

BETA3 Version

beta3 is available, see first post of the thread to download.

List of changes:

- Bug fixed: selecting a planet as docking HUD target is no more possible.
- Missing ballon.dds (by Well) added.
- Ability to undock while somebody is still on board removed.
- Mesh modification (RCS).
- RCS model modified, COG is now progress one as maintaining it inside PAO has no more sense.
- reentry deletion is now optional ("RDEL" tag must be added to the progress definition inside the scn file to activate it)
- Sun tracking adjusted to reflect new RCS model.
- Main exhaust moved to particles streams (stll can be improved, that's a first test)
- Using killrot while hlevel is active will toggle hlevel as firing all yaw and pitch thrusters produce a forward linear momemtum.

This version introduces important modifications (cog/rcs model).

Thanks

 

[SlyCoopersButt]

I've just noticed that if there are any crew inside the Progress when it becomes full of wastes they will be trapped inside it and they'll be doomed to go down with the Progress and it's waste in the earths atmosphere:lol:

Also I really think it should be up to the user to be able to undock with someone inside. It may not be meant for live occupants but it's a nice ferry between ships in emergency or other unusual situations.